cdrdao - gaps between tracks problem
in [Linux Help]
|
Prev: A spanked spammer...
Next: nvidia geforce 9500 dualview
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: Mike Jones on 23 May 2010 17:05 Responding to Joerg Schilling: > In article <pan.2010.05.21.22.13.12(a)dasteem.invalid>, Mike Jones > <luck(a)dasteem.invalid> wrote: > >>> Dude, I just told you wnat to do (maybe you got confused because your >>> mailer chopped up the line) >> >> >>IT DIDN'T WORK. Ok? >> >>cdda2wav -vall cddb=0 -B cdrecord -v -sao -useinfo *.wav >> >>=[FAIL] (errors about device) > > Your fail: you did not give any information Some. If you want a full report, say so. > >>cdda2wav -D /dev/dvd -vall cddb=0 -B cdrecord -v -sao -useinfo *.wav >> >>=[FAIL] (hangs,doing nothing) > > Your fail: you did not give any information Some. If you want a full report, say so. > >>cdda2wav -vall cddb=0 -B cdrecord device=5,0,0 -v -sao -useinfo *.wav >> >>=[FAIL] (errors about device) > > Your fail: you did not give any information Some. If you want a full report, say so. > Are you interested in help? I'm getting a distinct feeling you're pissed of because I'm struggling with something close to your heart here. Be sure, I am indeed struggling with this, and its taken me this long come to the conclusion I have faulty hardware or a screw up somewhere else on my system I'm not looking for conflict here, so if you could take that on board we might do a little better with the communication, ok? So, would you like me to run through everything I've tried, with full reports and outputs? -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 23 May 2010 17:06
Responding to Joerg Schilling: > In article <pan.2010.05.20.23.33.44(a)dasteem.invalid>, Mike Jones > <luck(a)dasteem.invalid> wrote: > >>>> Just follow the EXAMPLES sections in the cdrtools man pages..... >>>> >>>> cdda2wav -vall cddb=0 -B >>>> cdrecord -v -sao -useinfo *.wav >>>> >>>> This is known to work since 12 years now ;-) >> >>I failed the above examples. Where does the -device stuff go? > > If you are talking about the exaples above and fail, you most likely > don't use recent original software. Cdrtools implement auto-target > features since 4 years in case that you only have a single drive. > > In the other cases, it guides you to the right parameters. See my other posts on this one. Ta. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs. |