Problems Authoring CVD in VCDEasy
 

Problem authoring a CVD - Not KVCD
------------------------------------------------

I'm trying to author a NTSC CVD. It's 352x480, MPEG-2 2680kbs VBR, 48.0 khz audio. I mux using TMPGEnc Plus 2.5.

If I mux as "MPEG-2 Super Video CD (VBR)", I get a message saying something about "packet overflow" and that it may not work. If I mux it as "MPEG-2 Video Stream (VBR)" it seems to mux OK.

I then try to author with VCDEasy 2.0 as "SVCD 1.0", but of course due to how it was muxed, it autopads like crazy taking my 774mb file to 837mb and does not fit on a CD.

I can author it OK as "VCD 2.0", if I mux it as "MPEG-1 Video CD (Non-Standard)". But for some reason my standalone reads it as a VCD 1.1 (that's what the OSD shows when it's loaded). Since it sees a VCD 1.1, I lose my sequencing, thus losing my menu that I created.

Is there anyway that I can get this CVD authored as SVCD 1.0 in VCDEasy, or am I going to be forced to go SVCD compliant so that I can use the menu? If that's the case I guess I'll just author as a CVD (VCD 1.1 or 2.0) with MPEG-1 Sequence Header, because I want to preserve for transfer to DVD±R in the future.

Also, why an I getting the error message in TMPGenc when I try to mux correctly as "MPEG-2 Super Video CD (VBR)"

FWIW, my standalone is a GE 1101PA. This player is flashable with the APEX AP-703 region/macrovision free firmware. Using either firmware reads a VCD 2.0 authored disc as VCD 1.1.

Thanks in advance.

Ely

You must to mux with bbmpeg, selecting SVCD, Be sure that forced mux rate = 0, (no overflow message) I think it is all.
Later VCDEasy, select SVCD. Don't worry about initial resolution msg.
BTW: I think resolution should be 352*480 (not 358*480 as in your post)

Yeah, that was a typo - I'll edit it. It is actually 352x480. Thanks, I'll give bbmpeg a try.

Do you know if this is the exact problem (as far as the TMPGenc error msg is concerned)? Have you seen this before or are you just suspecting that bbmpeg may be the solution?

I saw packet overflow problem many times with tmpgenc. Using bbmpeg and selecting forced mux rate at 0, we are leaving bbmpeg to select mux rate automatically (computed by program), avoiding that problem. TMPGEnc can't do that. I think your problem is this one, but not sure, sorry.

Thanks :lol: I will definitely give it a try. I appreciate your help.