> From: Santanu Chatterjee <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [LIH] Re: How to write VCD > Date: 23 Sep 2002 19:11:30 +0530 > > But now, I am facing another problem (rather, I am confused). > vcdimager created two files, viz. "videocd.bin" and "videocd.cue". > The cue file is a simple text file containing the names of the tracks, > while mplayer can directly play the bin file. So I thought I will have > to burn the bin file to the blank CD. > > I cannot say that I was fully successful. When I play from the > CD I wrote, there is only one track containg all the five tracks > present in the original CD. I cannot choose which one I want to play > using 'mplayer vcd://2'. > > So, I would like to know whether I have to burn both the files. > If yes, what should be the procedure: > $ cdwrite -v dev=0,0,0 videocd.bin videocd.cue > OR > $ cdwrite -v dev=0,0,0 videocd.cue videocd.bin > OR > $ mkisofs -r -J -o videocd.iso videocd.cue videocd.bin > $ cdwrite -v dev=0,0,0 videocd.iso > > Regards, > Santanu Chatterjee > [EMAIL PROTECTED]
you can't write vcd-s with cdrecord. you have to use cdrdao for that. the syntax is: $ cdrdao write --device 0,0,0 videocd.cue it may not be 0,0,0 on your system; alter as needed. and yes, the argument to cdrdao is the *toc* file and not the bin file. the above example assumes both the files are in the current folder. and as rajesh said earlier, you need not go through the tedium of first ripping the tracks with vcdrip and then again making a cue/bin image out of the mpeg files. just do it directly with cdrdao like this: $ cdrdao read-cd --read-raw --source-device 0,0,0 data.toc the same caveat for 0,0,0 applies here. this will create the files data.bin and data.toc in the current folder (this bin file, too, is readable by mplayer). then write the vcd as specified in the first example, substituting "videocd.cue" with "data.toc". if you have two cd drives, do it directly with $ cdrdao copy --source-device 0,0,0 --device 0,1,0 this will do the whole ripping and writing for you at one go. if you add "--on-the-fly" to that it may be a little faster, but not as safe. if you add "--save" to the first successful cdrdao command you give, the common options like "--device" and "--source-device" will be saved to ~/.cdrdao, and you won't need to provide them every time. this goes not only for vcd-s, but any kind of cd you may throw at cdrdao, including many disks unreadable by other software. it's really a wonderful piece of code. - t. -- cogito, ergo es. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
