BIN/CUE image to big...but isn't

[dobber2000]

When I create the bin\cue image using vcd easy or tscv the resulting image is too big (the original mpeg is only 789mb).. so i know it should burn onto a 700mb disc using overburn and using fireburner.
The file build shows the track to be 89mins and not 79 mins..how is this possible if the file is only 789mb in the first place.
I have successsfully burned other files even as high as 800mb mpegs...this only happens occasionally.

The file im trying to do is a 2 disc copy of the man who wasnt there..
which i created using tmpgenc (mpeg2 svcd)..original file size was 1.56gb...which i then split again using tmpgenc..then added chapters for both discs...and then created the build..and then the problem.

Any ideas.

[djidjo]

You'd better use CDRDAO in VCDEasy to burn your BIN/CUE. Using overburn, it may work. Otherwise, I don't see any solution...

Djidjo

[dobber2000]

Thanks
I already tried that..but it does the same as Fireburner in that the image is to big ie 89mins....but the mpeg is only 789mb.

[avih]

it seems as if your burning app tries to burn the file as mode 1 or mode2 form 1 (both have error correction codes, about 13% of the actual file size). but vcd/svcd should be burned in mode 2 form 2, which utilizes a larger part of the cd for file storage, without the error correction data.

you can give nero a try with svcd template, just for comparision.

cheers
avi

[dobber2000]

It didnt appear to br the burning app that was causing the problem because even before i attempted to burn it it was telling me it was 89 mins long...so i never burned it...unless i,m using tscv wrongly...which i doubt because i have done at least 50 rips using it.

What i did do tho was multiplex the audio\video file using bbmpeg instead of tmpgenc....and guess what when creating the bin\cue file with tscv it reports the correct length ie 79 mins and not 89 mins.

Must be something im doing wrong when multiplexing with tmpg.