Two vital (quick) questions about VCDIMAGER...

[homerpez]

First question: What is the maximum filesize (as in total BYTES, not megs) that an 80 minute CD can hold?

Theoretically, it's 800MB. But, windows reports one size, VCDImager or NERO reports another... So what size (total bytes now) should I aim for if I want a .bin image, or NERO-generated VCD or SVCD to fit a CD? Remember... TOTAL BYTES, NOT MEGS. That's BYTES. This is the only standard the same on all OS's, programs, wheras "Megs" is different for some reason... I've had 798 Meg files that won't burn on an 80-min CD in NERO...


Second Question: If I am making an image with VCDImager for an SVCD, and it isn't really "standard" (It happens to have 480x480 resolution, a lower-sized bitrate, and 128k audio).. do I just make a "Standard" image, or do I check "Broken SVCD mode"...


OK I lied...

Third Question: If I'm multiplexing with bbMPEG, and adding the correct offsets to the video stream (SVCD), does having VCDImager do it again hurt anything?... or HELP?...

<font size=-1>[ This Message was edited by: homerpez on 2001-08-26 19:38:10 ]</font>

[Dhruv]

Ok.
You just contridicted yourself. You said you couldn't fit a 798Mb file on a 80 min CD. A 80 min CD can only hold 700Mb!!

The SVCD that isn't standard is a XSVCD, if you're planing to watch it on your standalone DVD player make sure thats XSVCD compatible (click DVD players on the left). No you shouldn't check broken SVCD.

And no, VCD Imager won't hurt anything.,
Dhruv

[homerpez]

Thank God I answered my own question... since you were wrong about something. An 80-min CD DOES in fact hold 800MB, when it's burned in MODE-2 form-2 (only VCD/SVCD/AUDIO can be burned in this format, since it scraps error byte correction)...

But my question was actually what size in BYTES to look for to know if my file was too big. Because, if you're not aware (I wasn't for a while), not only does Windows display ist own "MEGS" figure which may or may not correspond correctly to actual bytes, but when you convert to VCD image it balloons some more...

To answer my own question: Once you remultiplex, and THEN make a .bin image with VCDImager, it makes a file not more than 1MB off what it will be burned to the CD as... so a .bin image of 798MB is 799MB when displayed in NERO.

Thanks...

Anyone else having problems using NERO to burn .bin's?

I tried using the .cue file, but it didn't work... I had to open the actual ".bin" this time, and manually select "MODE-2". Is this a problem?

I burn all my .bin's with Nero and never burn the cue. Use the cue with Fireburner. My bins come up 801 megs in nero and burn like love on a 700 cdr Can't tell ya bytes, though. Hope it helps.

[vitualis]

homerpez,

You can burn about 800 MB onto a 700MB/80min CD. Windows actually does use the correct "megabyte" (i.e., 2^20 bytes). Now, remember that you need to add a few things apart from the the video track (i.e., first logical track is at a minimum 6 seconds long and more if you have menus). Generally, if you keep you mpeg 790MB or below, you should have plenty of room.

When you build an image with VCDImager, it will tell you at the bottom of the build log the size of the image (e.g., [79:40:15] ). This stands for 79min 40sec and 15 blocks. Anything below 80 minutes should be okay on 80 min media(actually, my burner only does 79:55:00 so you should check the full capacity of your burner).

Regards.

[homerpez]

Looks like it did work here...

Just like I said, if I go and do everything, then run through VCDImager, I get no more than 1MB more overhead than the .bin. So long as my total .bin file is not higher than 798MB, I'm fine.

I just have to remember to take the figure I get on FitCD, and lower the AVG bitrate I use by 8-10k per second (if it comes up 1050, I should use 1042 or 1040 instead). Otherwise, it's slightly too big. Live and learn.

Thans for all the help!