6 Jul
2007
6 Jul
'07
8:20 a.m.
Hi
I have problems (again) with cdrecord. This time the problem is that
burning exits with this error:
Quickly guessing the name of a drive capable to write CD-R, please wait...
Found /dev/cdrw, assuming dev=/dev/cdrw
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'RW/DVD GCC-4242N'
Revision : '0201'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
DCOP Cleaning up dead connections.
Speed set to 4234 KB/s
Starting to write CD/DVD at speed 24.0 in real SAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
ICE default IO error handler doing an exit(), pid = 9654, errno = 0
Errno: 0 (Success), send opc scsi sendcmd: no error
CDB: 54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 12.195s timeout 200s
wodim: OPC failed.
Could it be that my burner has died? Or are all my cds crap (hardly...)?
This post motivated me to try out cdrdao:
http://www.spankbot.net/cgi-bin/nph-bear/000000A/http/groups.google.com/gro…
But how do I burn a directory of .wav to cd? Seems I need a cue-file,
how do I generate that?
--
peace, love & harmony
Atte
http://atte.dk | http://myspace.com/attejensen
http://anagrammer.dk | http://atte.dk/compositions
6 Jul
6 Jul
8:39 a.m.
On Jul 6, 2007 at 12:20pm, Atte André Jensen wrote:
--
Garry Quested
School of Computing
University of Leeds
Leeds
LS2 9JT
Hi
...
But how do I burn a directory of .wav to cd? Seems I need a cue-file, how do
I generate that?
There's a quick script on this page that i have used in the past:
http://gentoo-wiki.com/HOWTO_Create_an_Audio_CD#DAO_Mode_with_cdrdao
It also mentions a program called tocgen that can do it for you
HTH
Garry.
10:14 a.m.
G Quested wrote:
There's a quick script on this page that i have
used in the past:
http://gentoo-wiki.com/HOWTO_Create_an_Audio_CD#DAO_Mode_with_cdrdao
Thanks. I found "gnome cd master" which seems to be a graphical frontend
to cdrdao. This also fails :-(
How do I know if I have a defect burner, and could something be done to
save it (can it be that something needs cleaning, and is that something
one can do oneself?)?
--
peace, love & harmony
Atte
http://atte.dk | http://myspace.com/attejensen
http://anagrammer.dk | http://atte.dk/compositions
10:46 a.m.
On Fri, 06 Jul 2007 14:14:05 +0200
Atte André Jensen <atte.jensen(a)gmail.com> wrote:
G Quested wrote:
Have you tried running any of these programs as root? I find on my FC5
system I get cryptic errors unless I do.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
There's a quick script on this page that i
have used in the past:
http://gentoo-wiki.com/HOWTO_Create_an_Audio_CD#DAO_Mode_with_cdrdao
Thanks. I found "gnome cd master" which seems to be a graphical frontend
to cdrdao. This also fails :-(
2:37 p.m.
Joe Hartley wrote:
Have you tried running any of these programs as root?
I find on my FC5
system I get cryptic errors unless I do.
sure:
ajstrup://home/atte/music/seq/lovsang/mixes# cdrecord -eject -dao -pad *.wav
Quickly guessing the name of a drive capable to write CD-R, please wait...
Found /dev/cdrw, assuming dev=/dev/cdrw
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'RW/DVD GCC-4242N'
Revision : '0201'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Speed set to 4234 KB/s
Starting to write CD/DVD at speed 24.0 in real SAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Errno: 0 (Success), send opc scsi sendcmd: no error
CDB: 54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 12.673s timeout 200s
wodim: OPC failed.
--
peace, love & harmony
Atte
http://atte.dk | http://myspace.com/attejensen
http://anagrammer.dk | http://atte.dk/compositions
11:12 p.m.
On Fri, Jul 06, 2007 at 06:37:32PM +0200, Atte Andr? Jensen wrote:
status: 0x2 (CHECK CONDITION)
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 12.673s timeout 200s
wodim: OPC failed.
During power calibration phase, the drive found that the medium was not
suitable. It claims a problem with the medium, not the drive. It
claims to be within the area of the medium used for power calibration.
This may be caused by any of the following:
1. recent medium (platter) used on a drive that does not support the
medium, (e.g. due to drive being too old, or lacking firmware support,
or you purchased medium from shop that is incompatible by design),
2. optical obstruction (dirt) on the medium in that area, try another
one, ... something like this has happened to me with fibre or fluff
caught in the hub,
3. laser has deteriorated beyond the point that will write with that
type of medium, try another type of medium.
--
James Cameron mailto:quozl@us.netrek.org http://quozl.netrek.org/
7 Jul
7 Jul
2:17 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Jul 07, 2007 at 11:13:35AM +1000, James Cameron wrote:
On Fri, Jul 06, 2007 at 06:37:32PM +0200, Atte Andr?
Jensen wrote:
It's very likely #1. I had the exact same problem. Those goddamned new
"52X!!" media are useless on my old drive. I can't find
"older/slower" media for sale anymore either.
Planned obsolescence, probably. Evil.
- -ken
status: 0x2 (CHECK CONDITION)
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 12.673s timeout 200s
wodim: OPC failed.
During power calibration phase, the drive found that the medium was not
suitable. It claims a problem with the medium, not the drive. It
claims to be within the area of the medium used for power calibration.
This may be caused by any of the following:
1. recent medium (platter) used on a drive that does not support the
medium, (e.g. due to drive being too old, or lacking firmware support,
or you purchased medium from shop that is incompatible by design),
2. optical obstruction (dirt) on the medium in that area, try another
one, ... something like this has happened to me with fibre or fluff
caught in the hub,
3. laser has deteriorated beyond the point that will write with that
type of medium, try another type of medium.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGjxOWe8HF+6xeOIcRAnVbAJ9cdeDdwl6lr6F53Z/pA1GGJXV3BwCgyt/K
KYzDLFxi+6kOjoRPLoAKhOE=
=4xiz
-----END PGP SIGNATURE-----
7:32 a.m.
James Cameron wrote:
During power calibration phase, the drive found that
the medium was not
suitable. It claims a problem with the medium, not the drive.
A gentle blow on the lens made the problem go away (I've burned three
cds since). I'll stop by a cd shop to pick up a cleaning kit.
Thanks for the replies anyways :-)
--
peace, love & harmony
Atte
http://atte.dk | http://myspace.com/attejensen
http://anagrammer.dk | http://atte.dk/compositions
8:20 a.m.
New subject: Distorded Jamin?
Hi,
I've just seen something strange, Jamin seems to generate some
distorsion even with eq, limiter and compressors bypassed. This
distortion disappear when Jamin is completly bypassed.
Here is a JAAA screenshot showing the distorsion:
http://perso.orange.fr/jsilvestre/jamin.png
With Qloud :
http://perso.orange.fr/jsilvestre/jamin-qloud.png
And Jamin completly bypassed:
http://perso.orange.fr/jsilvestre/jamin_bypass.png
Do I miss something? Is it "normal"?
joel
10 Jul
10 Jul
4:51 a.m.
New subject: Distorded Jamin?
On Sat, 2007-07-07 at 12:20 +0200, joel silvestre wrote:
Hi,
I've just seen something strange, Jamin seems to generate some
distorsion even with eq, limiter and compressors bypassed. This
distortion disappear when Jamin is completly bypassed.
That's a very good question. Could that be crossover distortion? Jamin
divides the signal into three bands which it compresses individually and
then combines them back together.
(btw. I CC'd this to the jamin mailing list)
Here is a JAAA screenshot showing the distorsion:
http://perso.orange.fr/jsilvestre/jamin.png
With Qloud :
http://perso.orange.fr/jsilvestre/jamin-qloud.png
And Jamin completly bypassed:
http://perso.orange.fr/jsilvestre/jamin_bypass.png
Do I miss something? Is it "normal"?
joel
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
5:58 a.m.
New subject: Distorded Jamin?
On Tue, Jul 10, 2007 at 09:51:34AM +0300, Sampo Savolainen wrote:
That's a very good question. Could that be
crossover distortion? Jamin
divides the signal into three bands which it compresses individually and
then combines them back together.
'Crossover distortion' normally means something entirely different,
but I'm pretty sure it is related to the way Jamin does its splitting
into frequency bands, IIRC by FFT. Or else Jamin is doing something
odd to each 128th sample.
Note 44100 / 128 = 344.5 = spacing between lines.
E.g. 1000 - 344.5 = 655.5, one of the two markers.
--
FA
Follie! Follie! Delirio vano è questo !
9:19 a.m.
New subject: Distorded Jamin?
On Tue, Jul 10, 2007 at 09:51:34AM +0300, Sampo Savolainen wrote:
On Sat, 2007-07-07 at 12:20 +0200, joel silvestre
wrote:
It's related to 'latency', process.c, line 386.
The distortion goes away if you set this to zero.
--
FA
Follie! Follie! Delirio vano è questo !
Hi,
I've just seen something strange, Jamin seems to generate some
distorsion even with eq, limiter and compressors bypassed. This
distortion disappear when Jamin is completly bypassed.
That's a very good question. Could that be crossover distortion? Jamin
divides the signal into three bands which it compresses individually and
then combines them back together.
10:30 a.m.
New subject: Distorded Jamin?
On Tue, Jul 10, 2007 at 09:51:34AM +0300, Sampo Savolainen wrote:
On Sat, 2007-07-07 at 12:20 +0200, joel silvestre
wrote:
> Hi,
>
> I've just seen something strange, Jamin seems to generate some
> distorsion even with eq, limiter and compressors bypassed. This
> distortion disappear when Jamin is completly bypassed.
There could be something wrong with the way 'op' is used in
process_signal().
Suppose that run_eq() or run_eq_iir() is called with in_ptr == 0.
That means that the window is applied without any offset w.r.t.
the signal buffer. After the FFT, samples 0..127 in mid_buf have
their final value, accumulated over 16 windows, and are ready for
further processing. They are read via the index 'op' which
therefore should be equal to in_ptr, and not have the 'latency'
offset applied.
--
FA
Follie! Follie! Delirio vano è questo !
6438
days inactive
6442
days old
linux-audio-user@lists.linuxaudio.org
12 comments
8 participants
participants (8)
-
Atte André Jensen -
Fons Adriaensen -
G Quested -
James Cameron -
Joe Hartley -
joel silvestre -
Ken Restivo -
Sampo Savolainen