Problem creating a CVD/SVCD - Please Help!?!

[e1miran]

Problem authoring a CVD using VCDEasy.
------------------------------------------------

I'm trying to author a NTSC CVD. It's 358x480, 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 it autopads like crazy taking my 774mb file to 837 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, 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 Header, because I want to preserve for transfer to DVD±R in the future.

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

[mats.hogberg]

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.

This is what should work, and how a CVD should be muxed. (But why use such high bit rate at CVD res? It's too high for even SVCD, and might cause your player troubles.)
Try muxing with some other application than TMPGEnc (even if I can't see why TMPGEnc wont work).
Muxing as MPEG 2 Video makes VCDEasy pad the mpg, and it will probably not work at all as CVD (besides getting too big).

/Mats

[e1miran]

Muxing as MPEG 2 Video makes VCDEasy pad the mpg, and it will probably not work at all as CVD (besides getting too big).

/Mats

Thanks for replying.

So even if I was able to mux it as "MPEG-2 Super Video CD" without error message or in another app (like which?), VCDEasy will pad it anyway? I guess that with a full capacity sized file it's not worth it, then.

I should just stick with the VCD 2.0 played as VCD 1.1 in my standalone and lose the menu. The menu works fine in PowerDVD when authored as a VCD in VCDEasy, so it is a problem with my player.

FWIW, my standalone plays the MPEG-2 CVD (with "MPEG-1 Video CD (non-standard) header, authored as a VCD 2.0) at the specified bitrate without a hitch. And, it looks beautiful, especially considering it's a capture from programming that I recorded from my dish to a standalone PVR/DVR.

[mats.hogberg]

So even if I was able to mux it as "MPEG-2 Super Video CD" without error message or in another app (like which?), VCDEasy will pad it anyway? I guess that with a full capacity sized file it's not worth it, then.

No, that was not what I was trying to say. On the contrary - that is what should work. But obviously doesn't, as TMPGEnc complains about packet overflow. (Which could be caused by your high bit rate!) It's muxing as "MPEG-2 Video Stream" that will make VCDEasy (quite rightly) auto-pad the mpeg stream, making it bigger, and probably not working at all.
When muxing as VCD with TMPGEnc, you're doing the "header trick" which mostly is used to fool players that refuse to play SVCD to play them anyway...
My suggestion is that you try something else besides TMPGEnc to mux your audio and video as SVCD.

/Mats

[e1miran]

Thanks, Mats. I'm going to try to mux with bbmeg. I was told on another forum by someone who had the "packet overflow" msg, that muxing in bbmeg solved the problem. I appreciate your help. 8)