cdrdao - gaps between tracks problem
in [Slackware]
|
Prev: who said slackware not support old versions?
Next: sadc system activity collector missing from slackware 13
From: Mike Jones on 23 May 2010 16:57 Responding to Joerg Schilling: > In article <pan.2010.05.21.21.57.22(a)dasteem.invalid>, Mike Jones > <luck(a)dasteem.invalid> wrote: >>Responding to jr4412: >> >>>> I've tried everything suggested so far, and got the same problem each >>>> time, except for the suggestions that plain bombed out as they >>>> weren't complete commands, which I asked about, and got no response >>>> to. >>> >>> cdrecord/cdda2wav didn't work for you?? >>> >>> what is your *exact* h/ware & s/ware setup? >> >> >>Slackware 12.2, mplayer, audacious, xine, cdrecord, cdrdao, cdda2wav > > cdrecord exists since 14 years, cdda2wav exists since 17 yeras now. > Which version did you use? > > call cdrecord -version and cdda2wav -version Cdrecord-ProDVD-ProBD-Clone 2.01.01a53 (i686-pc-linux-gnu) cdda2wav 2.01.01a53 (i686-pc-linux-gnu) FWIW: I'm seriously thinking I have a hardware (or possibly a config) glitch, based on seeing other's success with exactly the same commands and resources I'm getting failures with. This would explain why I'm not seeing the end results the man pages say will happen. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 23 May 2010 16:59 Responding to Joerg Schilling: > In article > <665b31c9-2b89-45e1-a1af-cf84aa9837d2(a)a16g2000vbr.googlegroups.com>, > jr4412 <jr4412(a)googlemail.com> wrote: >>> Also since Schilling forgot to put the "device=" option into his >>> commands, he got errors. >> >>not in the man page (slackware 12.0 or 13.0). > > The recent man pages are here: > > http://cdrecord.berlios.de/private/man/cdrecord/index.html > > NAME > > cdrecord - record audio or data Compact Disks or Digital > Versatile Disks from a master > > SYNOPSIS > > cdrecord [ general options ][ dev=device ][ track options ] > track1...trackn > > > DESCRIPTION > > Cdrecord is used to record data or audio Compact Discs on an Orange > Book CD-Recorder, to write DVD media on a DVD- Recorder or > to write BluRay media on a BluRay-Recorder. > > Device naming > Most users do not need to care about device naming at all. If no > dev= option was specified, cdrecord implements auto target > support and automagically finds the drive in case that exactly > one CD-ROM type drive is available in the sys- tem. In case that > more than one CD-ROM type drive exists on the system, a list of > possible device name parameters may be retrieved with cdrecord > -scanbus or from the target example from the output of cdrecord > dev=help, then the dev= parame- ter may be set based on the device > listing. > > The device parameter to the dev= option explained below refers > to scsibus/target/lun of the CD/DVD/BluRay-Recorder. If a file > /etc/default/cdrecord exists, the parameter to the dev= option may > also be a drive name label in said file (see FILES section). I got a fail as it looked for sg0, and my stuff is sr0 + hdc Adding device direction as per man page fixed this, but then I got hangs. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 23 May 2010 17:00 Responding to Joerg Schilling: > In article <slrnhvg3mc.vja.unruh(a)wormhole.physics.ubc.ca>, unruh > <unruh(a)wormhole.physics.ubc.ca> wrote: >>On 2010-05-22, jr4412 <jr4412(a)googlemail.com> wrote: >>>> What he means by functioning is duplicates that do not have the 2 >>>> second gap between tracks if the original does not. >>> >>> yes, and if the OP follows the instructions in the cdrecord man page, >>> then there's no gap. >> >>He seems strangely resistant to doing so. When Schilling suggested it, >>he tried running the two lines of command together into one. Also since >>Schilling forgot to put the "device=" option into his commands, he got >>errors. When I told the OP how to put in the device command he objected >>that I was giving him orders without explanation. This is starting to >>look a lot like a troll, rather than someone who genuinely has a problem >>he wants a solution to. > > I did not forget something as most users have a single drive and this is > autodetected by cdrtools since August 2006. As mentioned, adding a device indicator did the trick, but then... -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 23 May 2010 17:01 Responding to Joerg Schilling: > In article <slrnhvg3mc.vja.unruh(a)wormhole.physics.ubc.ca>, unruh > <unruh(a)wormhole.physics.ubc.ca> wrote: >>On 2010-05-22, jr4412 <jr4412(a)googlemail.com> wrote: >>>> What he means by functioning is duplicates that do not have the 2 >>>> second gap between tracks if the original does not. >>> >>> yes, and if the OP follows the instructions in the cdrecord man page, >>> then there's no gap. >> >>He seems strangely resistant to doing so. When Schilling suggested it, >>he tried running the two lines of command together into one. Also since >>Schilling forgot to put the "device=" option into his commands, he got >>errors. When I told the OP how to put in the device command he objected >>that I was giving him orders without explanation. This is starting to >>look a lot like a troll, rather than someone who genuinely has a problem >>he wants a solution to. > > I did not forget something as most users have a single drive and this is > autodetected by cdrtools since August 2006. As mentioned, adding a device indicator did the trick, but then... -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Bud on 23 May 2010 17:05
On 2010-05-23, Mike Jones wrote: > > I got a fail as it looked for sg0, and my stuff is sr0 + hdc > > Adding device direction as per man page fixed this, but then I > got hangs. Ever look at your fstab in /etc ? -- Bud |