VCDEasy and BIN/CUE files instead of CDRDAO.

[Draven]

I've just got me a new cdrw writer LiteOn 52246S.And it doesn't seem to support burning with the CDRDAO option in VCDEasy.I think vcdeasy is working very well when it comes to overburning sync issues etc... So i don't want to change software.I have read through the forum and it seems you could make a BIN/CUE file of your mpeg2 and then burn it in VCDEasy...?Here comes my question...Is there any reason why i should not do my SVCD this way ?????

[hashslingingslasher]

No don't worry mine came out fine. If you need to know how to do this BIN/CUE process, i'll tell you.

[vitualis]

I've just got me a new cdrw writer LiteOn 52246S.And it doesn't seem to support burning with the CDRDAO option in VCDEasy.I think vcdeasy is working very well when it comes to overburning sync issues etc... So i don't want to change software.I have read through the forum and it seems you could make a BIN/CUE file of your mpeg2 and then burn it in VCDEasy...?Here comes my question...Is there any reason why i should not do my SVCD this way ?????

Um, that's what VCDEasy does. It first makes a CUE/BIN image with VCDImager and then burns the image using CDRDAO. It doesn't really make a difference whether you set VCDEasy to automatically do the burning step or for it to just create the CUE/BIN image so you can burn it at a later stage.

My LiteOn burner (not the same model) works brilliantly with CDRDAO. Indeed, CDRDAO should work with essentially all modern IDE burners... Have you installed a working ASPI layer on your PC? If not, then give ForceASPI a try (remember, to install it and then REBOOT immediately).

Regards.

[Bondiablo]

If CDRDAO doesn't work for you just let VCDEasy create the Bin Cue files then load them in another program to burn. I used GoldenHawk CDRWin for a while when I was having trouble with one of the earlier versions of VCDEasy.

[Draven]

vitualis wrote:

My LiteOn burner (not the same model) works brilliantly with CDRDAO. Indeed, CDRDAO should work with essentially all modern IDE burners... Have you installed a working ASPI layer on your PC? If not, then give ForceASPI a try (remember, to install it and then REBOOT immediately).

Today i also tried another burner Lite-On LTR482465 it also didn't work.
My problem begun after i had a Artec burner that crashed besauce it didn't work with 90min cdr's(that burner worked fine until that happend). After that i have tried the two Lite-On burners(none of them is on the CDRDAO compability list), but i have used the same ForceASPI as i have with the Artec burner.Should i use another one?? .It says "ASPI seems ok".

Anyway here's my logfile....
[CDRDAO Write]
WARNING: During writing you should avoid to open the Windows Explorer and similar tools
WARNING: CDRDAO does not lock the recording device so that all access action from the Explorer will lead to a failure of the recording process.
Cdrdao version 1.1.7
1,1,0: LITE-ON LTR-52246S Rev: 6S07
Using driver: Generic SCSI-3/MMC (raw writing) - Version 2.0 (options 0x0000)
ERROR: Try again first, then
WARNING: Length of toc (83:08:21, 374121 blocks) exceeds capacity of CD-R (79:57:74, 359849 blocks).
WARNING: Ignored because of option '--overburn'.
WARNING: Some drives may fail to record this toc.
Starting write simulation at speed 2...
Turning BURN-Proof on
Using 16 byte P-Q sub-channel data mode.
Writing lead-in and gap...
Writing track 01 (mode MODE2_RAW/AUDIO )...
Writing track 02 (mode MODE2_RAW/AUDIO )...
cmd finished after 3.410s timeout 20s
ERROR: Write data failed.
ERROR: Writing failed - buffer under run?
ERROR: Simulation failed.

Thanks for trying to help. And bytheway i talked with LiteOn and they says "use Nero".But is there a nero version that is really compatible with SVCD's and supports overburning??

[Draven]

No don't worry mine came out fine. If you need to know how to do this BIN/CUE process, i'll tell you.

Yes! Thank you very much ,and if you have a burning software that supports overburning.

[vitualis]

[CDRDAO Write]
WARNING: During writing you should avoid to open the Windows Explorer and similar tools
WARNING: CDRDAO does not lock the recording device so that all access action from the Explorer will lead to a failure of the recording process.
Cdrdao version 1.1.7
1,1,0: LITE-ON LTR-52246S Rev: 6S07
Using driver: Generic SCSI-3/MMC (raw writing) - Version 2.0 (options 0x0000)
ERROR: Try again first, then
WARNING: Length of toc (83:08:21, 374121 blocks) exceeds capacity of CD-R (79:57:74, 359849 blocks).
WARNING: Ignored because of option '--overburn'.
WARNING: Some drives may fail to record this toc.
Starting write simulation at speed 2...
Turning BURN-Proof on
Using 16 byte P-Q sub-channel data mode.
Writing lead-in and gap...
Writing track 01 (mode MODE2_RAW/AUDIO )...
Writing track 02 (mode MODE2_RAW/AUDIO )...
cmd finished after 3.410s timeout 20s
ERROR: Write data failed.
ERROR: Writing failed - buffer under run?
ERROR: Simulation failed.

Okay. CDRDAO is talking properly to your drive as it appears that you've burnt something (before the process derailed). CDRDAO supports all generic MMC3 drives so even if your model drive isn't explicitly stated, it should still work.

As to your problem, how long does the above burn before you get that error?

I hope you are using 90min media as your image is over 83 min long and it won't fit on most 80min media.

Also, have you tried to actually burn the disc rather than keep it on simulation? The simulation option doesn't work all that well.

Best of luck.

Regards.

[Draven]

vitualis wrote:

As to your problem, how long does the above burn before you get that error?

I hope you are using 90min media as your image is over 83 min long and it won't fit on most 80min media.

Also, have you tried to actually burn the disc rather than keep it on simulation? The simulation option doesn't work all that well.

I got the error a couple of minutes after it has started to burn in "realburn" mode.But with the latest lite-on burner i tried today, the simulation was almost finished when the error came.No i use 80min cdrw but 83-84min wasn't any problem with my artec burner if i used overburning?? If you are right how much do you suggest i could get on a 80min and 90min ?? I have StarWars in three parts 840MB each, they should fit in a 90min cdr at least ??

[vitualis]

That's probably it.

CDRDAO states that the image is 83:08:21 large (minutesecondsectors) large. You are really pushing it if you use 80min media.

Generally, I will not overburn by over 1 minute and this is a farely safe number (almost all burners and discs will be able to handle it).

For an image 83min large, unless you KNOW that your media can overburn to that degree (not many can), I strongly suggest that you use 90min media.

Best of luck.

Regards.

[Draven]

vitualis
Thanks man for your advise .Yesteraday i tried to burn 81min on a 80min cdrw and it went ok.Strange though that i could burn up to 84min with another burner but with the same media....

[Anonymoususer]

I was having problems with VCDEasy because of the ASPI Drivers but that is now fixed but now the problem is that the Burn Option is not highlighted..it says that it cannot be enabled because of XML output or something...? anyone know how to unlock the burning option...? Nothing in the CDRAO option is highlighted..

[Anonymoususer]

ok scratch that last post...I had to give it a reboot..now Im having a problem burning the Mpeg 2. Ive messed up like 4 CD's trying to burn this shit. I installed the ASPI Drivers, it works perfect until the writing track part where this is what it says :-


[CDRDAO Write]
Cdrdao version 1.1.5
0,0,0: YAMAHA CRW8824E Rev: 1.00
Using driver: Generic SCSI-3/MMC - Version 1.2 (options 0x0000)
ERROR: Try again first, then
WARNING: Length of toc (81:11:46, 365371 blocks) exceeds capacity of CD-R (79:57:74, 359849 blocks).
WARNING: Ignored because of option '--overburn'.
WARNING: Some drives may fail to record this toc.
Starting write at speed 8...
Executing power calibration...
Power calibration successful.
Writing track 01 (mode MODE2_RAW/MODE2_RAW)...
cmd finished after 21.200s timeout 180s
ERROR: Write data failed.
ERROR: Writing failed - buffer under run?
ERROR: Writing failed.


Im getting really pissed off...someone got a solution..?

[Betamax]

If your CDwriter is atached to IDE (see manual), then it is ATAPI, in which case you always can use the default settings for the driver :

--driver generic-mmc

Most problems are because one uses the maximum speed, but that is not always recommended. Eg, I've got an AMD1.2Ghz and a CDwriter that 'should' be able to write at 16x Speed, though I manage to write multi-track cd's (= S/VCD) only at 8x Speed.
You should try to burn at lower speed, for this use option :

--speed x

where 'x' is a numeric figure (like, 1,2,4,8,12,16,...)

You must be sure your writer can overburn its maximum capacity.
Mine for instance, a HP-9700i tells CDRDAO it can do overburn and cdrdao thinks that everything I write beyond the 80min barier is okay, but in fact it isn't. Yours just fails, mine doesn't but we'll endup with the same result..
Just be sure you don't do overburn, unless you're certain that your burner will accept it.

[Anonymoususer]

Yes...mine can overburn..infacte I once overburned up till 82:10 and the CD worked fine..Also I changed the driver settings for Default...I will try your method for the lowering speed...thanks for the info..

[Anonymoususer]

Well after busting my ass I finally got it to successfuly burn...I changed the driver settings to default and lowered the speed to 4X just to be safe..thanks for the help...

[Anonymoususer]

First CD did burn BUT I selected SVCD as the Type and it made it into a VCD1.1..? and it came out all jerky..obviously..tried to reburn it again got the same DAMN error...Data Write Fail..? is their something wrong with my burner..?Im confused...

[Anonymoususer]

Ok...still having weird problems burning here is the summary of events and problems I've had soo far...

I had been using Nero 5.5+ for a while now to burn my SVCD's..worked fine until last week when I burned an SVCD and came out all jerky even though their is NOTHING wrong with the Mpeg..Ive made sure..burned the SVCD on a CD-RW using Nero and surprisingly It worked PERFECT !. Tried lowering the speed and burning the SVCD on a regular Media using Nero..still same Jerky problem...Decided to switch to VCDEasy because of the compliments I've heard about it soo far..burned the First CD Perfect..really liked it until now...It scans the Mpeg, makes a CD Image file...but when it is about to Write the DATA it fails..Buffer Under Run ?...took BetaMax's advice and lowered the Writing speed changed the Drivers to Default from Generic-mmc..the CD burned good but the problem was that it made it into a a VCD1.1 even though I selected SVCD..?..Unistalled VCDEasy just to see if Nero would work..last hope..still same jerky problem...Burned the movie on a CD-RW worked perfect...burned it on the Regular media at 4X...no change..jerkiness.and Yes the media is fine and my DVD Player has been playing the same media on the previous movies fine...so..Im really stuck right now because I have no Idea what to do cuz Im confused and irritated..

So someone if you have another program for me to try of some help to solving this problem..please do so because it will be very much appreciated..

[Anonymoususer]

Day has passed...still no help...

[Anonymoususer]

Ok how would I burn an Image of the Mpeg2...and how does it work..any link or guide..?