Re: [newbie] Command line burning
Barry Michels wrote: I have some ISO files (a downloaded Linux distribution), so I don't need to use mkisofs. However, during burning, I get a coaster, then the following disc is ok. The next one is a coaster, then ok. I ended up with 7 good discs and 4 coasters. There were no changes made to the command line. After getting a coaster, I'd just press the up arrow, replace the disc and hit enter. It's a 800Mhz Celeron running a 16x burner (but I slowed down to 8x after the first coaster, the third CD burned at 16x). Here's the command I used: cdrecord -v speed=4 dev=0,0,0 -pad -data -eject -ignsize filename.iso I pulled that off a message in this thread and changed it for my system. Barry I generally use, cdrecord -v speed=8 dev=0,1,0 -eject /sourcefile.iso -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re[2]: [newbie] Command line burning
Hey, cdrecord: fifo had 11671 puts and 11608 gets. cdrecord: fifo was 0 times empty and 11400 times full, min fill was 85%. Well, as long as the FIFO doesn't go empty I don't think you need to worry about anything. The CD-RW has a buffer of its own, so I assume if FIFO runs out of data there still is at least 2 megs of drive-internal buffer to be written and FIFO can get filled meanwhile. Anyways, you can always increase the FIFO using a switch, don't remember which one, though. (fifo=16 maybe?) This seems to be correct. I never seem to get buffer underuns so obviously cdrecord is being causious in some way, Cdrecord probably doesn't do anything special to prevent buffer underruns. I guess it's just your drive working fine / as expected. Yes my writer, Mitsumi in this case has 2mb of buffer, can anyone tell me the logic of the fact that my older writers which could not exceed 4x write spped all had 4mb of buffer built in to them, yet this 24x write speed Minsumi seems only to need 2Mb of buffer, the logic of the setup escapes me. Obvious it doesn't need it, but why ? The guys at Mitsumi probably assume that you won't use their burner on a 486 with a PIO 3 disk... However I guess you're right, more wouldn't be worse. Apart from that I have 4 megs on my 8x Plextor. -- Greets Roman John Roman Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re[2]: [newbie] Command line burning
Hey, I have some ISO files (a downloaded Linux distribution), so I don't need to use mkisofs. However, during burning, I get a coaster, then the following disc is ok. The next one is a coaster, then ok. I ended up with 7 good discs and 4 coasters. There were no changes made to the command line. After getting a coaster, I'd just press the up arrow, replace the disc and hit enter. It's a 800Mhz Celeron running a 16x burner (but I slowed down to 8x after the first coaster, the third CD burned at 16x). Here's the command I used: cdrecord -v speed=4 dev=0,0,0 -pad -data -eject -ignsize filename.iso I pulled that off a message in this thread and changed it for my system. What does happen? Do you get a buffer underrun? Go to the directory where the iso is placed and try: cdrecord -v -eject -dummy speed=16 dev=0,0,0 ./filename.iso cdrecord -v -eject -dummy speed=8 dev=0,0,0 ./filename.iso cdrecord -v -eject -dummy speed=4 dev=0,0,0 ./filename.iso cdrecord -v -eject -dummy speed=2 dev=0,0,0 ./filename.iso cdrecord -v -eject -dummy speed=1 dev=0,0,0 ./filename.iso and see which one works for you. The -dummy switch makes sure no data is actually burnt to the disc. -- Good luck Roman Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
On Tuesday July 23 2002 06:30 pm, Barry Michels wrote: I have some ISO files (a downloaded Linux distribution), so I don't need to use mkisofs. However, during burning, I get a coaster, then the following disc is ok. The next one is a coaster, then ok. I ended up with 7 good discs and 4 coasters. There were no changes made to the command line. After getting a coaster, I'd just press the up arrow, replace the disc and hit enter. It's a 800Mhz Celeron running a 16x burner (but I slowed down to 8x after the first coaster, the third CD burned at 16x). Here's the command I used: cdrecord -v speed=4 dev=0,0,0 -pad -data -eject -ignsize filename.iso I pulled that off a message in this thread and changed it for my system. Barry Try it with simply cdrecord -v -eject speed=4 dev=0,0,0 filename.iso I got that 'simplified' CL from the cooker page, works every time ;) http://www.mandrakelinux.com/en/cookerdevel.php3 ..even for 699mb iso's ..and who makes the media, not brand name, who really makes 'em? ..and how many mb's are you tryin' to burn to what size disk? A lot of your problem might be less than best quality cd-r's, but also too many extras on the CL, particularly '-data'. I've found I get the best results with a minimum amount of cdrecord options. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re[2]: [newbie] Command line burning
Hi, cdrecord: fifo had 11671 puts and 11608 gets. cdrecord: fifo was 0 times empty and 11400 times full, min fill was 85%. I've stayed out of this 'cause I don't have any 800mb media, never tried/seen any. On another count, I prefer to use mkisofs to make the img, then write to cdr, so I've never encountered your missing '-' situation. I'm curious tho 85% is awful low. I've never experienced less than 95%, usually 98 to 100%. Have you tried burning to that media at 4x? I've also got some generic CMC Magnetics 700mb cdr's, $12 for a 50 spindle. I don't get good results with 'em over 4x tho. yes, I'm burning here ar 8x, not particularly fast but faster than mkisofs can really supply data without the risk of buffer underrun, and so yes I need to reduce the burn rate , else supply a buffer , if such a thing is possible when using a pipe, I don''t know. The lowerst point was 85%, most of the time it's 98-100%, but if it drops any lower than 80% experience tells be to reduce the burn rate or else. However I've just spent the last 2 hours running the avi disc file through and there does not seem to be any problems. Well, as long as the FIFO doesn't go empty I don't think you need to worry about anything. The CD-RW has a buffer of its own, so I assume if FIFO runs out of data there still is at least 2 megs of drive-internal buffer to be written and FIFO can get filled meanwhile. Anyways, you can always increase the FIFO using a switch, don't remember which one, though. (fifo=16 maybe?) Also, did you mean 80 minute cdr's, or 800MB? I've burned over 800 mb's of wav's to a 700mb, 80 minute CD-r. My record is 79m57s ;) As for size, these are indeed 80min discs , but if you turn them over in very good light you can see where the lazer has been and I know that 800mb is total max with my burner. I have to be careful here there is some evidence to suggest not all burners can do it, I'm guessing , but I believe some burners tracking is not quite as good as anothers, or else the software that controls it is not up to the burners mark. whichever. I first learnt of this when my teenage daughters kept giving me 800mb audio discs to copy, and many burner software refused to allow a full copy. But actually most 80min discs , and I've used all sorts of makes and price brackets( price is no indicator of quality) will write up to about 800mb, depending upon whether we are talking about continuous byte streams or whether the job entails endless new files and folders., in other words gaps come into the equation. To clear that up, there are 74 min / 650 MB (~681,000,000 Bytes) and 80 min / 700 MB (~734,000,000 Bytes) disks. You don't fit much more on them than their specified capacity, a few seconds / megs with overburning, however that's not recommended. Tom was talking about 800MBs of WAVs to a 700MB CD. That's because you burnt WAVs as an Audio CD. The Audio CD can store more Audio than Data because with data about one third of all the space is allocated to error correction, which isn't that important with Audio. You still burnt only ~80 mins of Audio, but that doesn't mean you burnt 800 MB. Megabytes refer to data capacity and minutes to Audio capacity so it's not correct to say I burnt 800 MB of Audio. Of course, there are disks which can hold up to 99 minutes of Audio, but they aren't that common. /smartypants (I know, validation error, no opening tag found, insert where appropriate for you ;-) Greets Roman Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
Roman Korcek wrote: Hi, cdrecord: fifo had 11671 puts and 11608 gets. cdrecord: fifo was 0 times empty and 11400 times full, min fill was 85%. I've stayed out of this 'cause I don't have any 800mb media, never tried/seen any. On another count, I prefer to use mkisofs to make the img, then write to cdr, so I've never encountered your missing '-' situation. I'm curious tho 85% is awful low. I've never experienced less than 95%, usually 98 to 100%. Have you tried burning to that media at 4x? I've also got some generic CMC Magnetics 700mb cdr's, $12 for a 50 spindle. I don't get good results with 'em over 4x tho. yes, I'm burning here ar 8x, not particularly fast but faster than mkisofs can really supply data without the risk of buffer underrun, and so yes I need to reduce the burn rate , else supply a buffer , if such a thing is possible when using a pipe, I don''t know. The lowerst point was 85%, most of the time it's 98-100%, but if it drops any lower than 80% experience tells be to reduce the burn rate or else. However I've just spent the last 2 hours running the avi disc file through and there does not seem to be any problems. Well, as long as the FIFO doesn't go empty I don't think you need to worry about anything. The CD-RW has a buffer of its own, so I assume if FIFO runs out of data there still is at least 2 megs of drive-internal buffer to be written and FIFO can get filled meanwhile. Anyways, you can always increase the FIFO using a switch, don't remember which one, though. (fifo=16 maybe?) This seems to be correct. I never seem to get buffer underuns so obviously cdrecord is being causious in some way, Yes my writer, Mitsumi in this case has 2mb of buffer, can anyone tell me the logic of the fact that my older writers which could not exceed 4x write spped all had 4mb of buffer built in to them , yet this 24x write speed Minsumi seems only to need 2Mb of buffer, the logic of the setup escapes me. Obvious it doesn't need it , but why ? I will look into that switch, I didn't know cdrecord had one. John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
Hi, I use 800mb blank discs. I get mencoder to create 780mb film.avi files which I write to disc. b) mkisofs / cdrecord using a pipe === mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize This does the mkisofs to cdrecord on the fly, however it has one major fault, try as a may I cannot get it to work with the larger file size. I have tried -overburn as well as -ignsize . It could well be that mkisofs is the culprit , I don't know, on the otherhand mkisofs has no trouble handling these larger file sizes on it's own. Could it be that cdrecord is just missing the final - on the command line telling it to use stdin? Good luck Roman Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
Roman Korcek wrote: Hi, I use 800mb blank discs. I get mencoder to create 780mb film.avi files which I write to disc. b) mkisofs / cdrecord using a pipe === mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize This does the mkisofs to cdrecord on the fly, however it has one major fault, try as a may I cannot get it to work with the larger file size. I have tried -overburn as well as -ignsize . It could well be that mkisofs is the culprit , I don't know, on the otherhand mkisofs has no trouble handling these larger file sizes on it's own. Could it be that cdrecord is just missing the final - on the command line telling it to use stdin? Good luck Roman so how would this be done then ? John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re[2]: [newbie] Command line burning
Hi, mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize Could it be that cdrecord is just missing the final - on the command line telling it to use stdin? so how would this be done then ? IIRC: mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize - HTH Roman Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
Roman Korcek wrote: Hi, mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize Could it be that cdrecord is just missing the final - on the command line telling it to use stdin? so how would this be done then ? IIRC: mkisofs -r -J -v film.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize - HTH Roman Thanks Roman, It worked :- mkisofs -r -J -v behindenemylines.avi | cdrecord -v speed=8 dev=0,1,0 -data -pad -eject -ignsize - mkisofs 1.15a17 (i686-pc-linux-gnu) Cdrecord 1.11a19 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,1,0' scsibus: 0 target: 1 lun: 0 Linux sg driver version: 3.1.22 Using libscg version 'schily-0.6' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'MITSUMI ' Identifikation : 'CR-48X9TE ' Revision : '1.0C' Device seems to be: Philips CDD-522. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R FIFO size : 4194304 = 4096 KB Track 01: data unknown length padsize: 30 KB Total size: 0 MB (00:00.00) = 0 sectors Lout start: 0 MB (00:02/00) = 0 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type A, high Beta category (A+) (3) ATIP start of lead in: -11634 (97:26/66) ATIP start of lead out: 359849 (79:59/74) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation cdrecord: WARNING: Total disk size unknown. Data may not fit on disk. Starting to write CD/DVD at speed 8 in write mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Performing OPC... Starting new track at sector: 0 Track 01: 6 MB written (fifo 87%) 113.6x. 1.34% done, estimate finish Mon Jul 22 18:26:01 2002 snip Track 01: 689 MB written (fifo 100%) 8.5x. 94.82% done, estimate finish Mon Jul 22 18:19:03 2002 Track 01: 699 MB written (fifo 100%) 8.4x. 96.15% done, estimate finish Mon Jul 22 18:19:04 2002 Track 01: 702 MB written (fifo 100%) 8.1x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 05 7D 89 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.002s timeout 40s write track data: error after 736905216 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 611.697s Fixating... Fixating time: 39.033s cdrecord: fifo had 11671 puts and 11608 gets. cdrecord: fifo was 0 times empty and 11400 times full, min fill was 85%. All written to disc. there are some wornings, minimum fill 85% getting near the limit. what is : Sense Key: 0x5 Illegal Request, Segment 0, anything to worry about ? Anyway , the inclusion of one litle - made all the difference. Thanks, John -- John Richard Smith [EMAIL PROTECTED] Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Command line burning
On Monday July 22 2002 12:54 pm, John Richard Smith wrote: Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 3 Manufacturer: CMC Magnetics Corporation cdrecord: fifo had 11671 puts and 11608 gets. cdrecord: fifo was 0 times empty and 11400 times full, min fill was 85%. All written to disc. there are some wornings, minimum fill 85% getting near the limit. what is : Sense Key: 0x5 Illegal Request, Segment 0, anything to worry about ? I've stayed out of this 'cause I don't have any 800mb media, never tried/seen any. On another count, I prefer to use mkisofs to make the img, then write to cdr, so I've never encountered your missing '-' situation. I'm curious tho 85% is awful low. I've never experienced less than 95%, usually 98 to 100%. Have you tried burning to that media at 4x? I've also got some generic CMC Magnetics 700mb cdr's, $12 for a 50 spindle. I don't get good results with 'em over 4x tho. Also, did you mean 80 minute cdr's, or 800MB? I've burned over 800 mb's of wav's to a 700mb, 80 minute CD-r. My record is 79m57s ;) -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
