Converting to VCD header -gt; Oversized .bin only, anything, specific, because, convert

andy

anyone else get the problem that the resulting bin file(created through DVD2SVCD or VCDEasy) is much too big to be burned after converting the header to VCD? (note: this is not specific to this plugin)
for example: I get 825MB, though the actual mpg file is 717MB.
Whereas before converting the header, the bin file is 733MB and the mpg is 723MB
It doesn't have anything to do with cutting, because this movie is only 45 minutes long, so the whole thing is just in this one file.  And when converting it back, i get my 733MB bin file again.  Can anyone explain this phenomenon?

D9: Moved

Problem post, my friend

Originally posted by UltimateDBZ
D9: Moved

Problem post, my friend  

i suppose you're right, i just actually moved it out of the deep sticky for the VCDHeader plugin, which is in the advanced forum, so i figured this was an advanced issue.  Doesn't matter to me, as long as someone can help figure out what's happening here.

i say that if u try to burn the image on 80min cd u will not fail.

i have 74 minute cd's, that's why i chose that filesize, and yes, i tried it, and cdrdao gives me the error that the file is too big to ft.

But if i burn the original image before converting the header, it burns fine.

The reason why these third party plug-ins are in the advanced forum is that they are not really supported by us.  We, including DVD2SVCD, do not know enough about it to really help.
They are mostly supported within the plug-in thread itself.  Sort of like it's own little forum in a forum.

Mark

well, now that this hack is within DVD2SVCD itself, I have to bring this up again.  I just did my first conversion with 1.1.3b3 with bbmpeg set to mux as a MPEG1.  My muxed video file is 726MB, while the .bin file is 835MB.  Doesn't that seem like an aweful lot of padding data?

And if i remux it as a SVCD, the muxed mpg comes out to 724, and the .bin file comes out to 734MB, which is fine.  So the problem seems to be somewhere between the bbmpeg stage and the .bin creation.  As I said above, even if you create the image in VCDEasy, it ends up with over 100MB of who knows what data in the .bin.

So, there either needs to be different bitrate calculations done if you are encoding an SVCD and muxing as a VCD, or maybe someone can figure out where this 100MB is coming from and how to get rid of it.

btw, i'm doing this because my friend has a dvd player that lets him play SVCDs muxed as VCD's, not just to nag

Does the lack of response here mean that nobody's even using the VCD header trick?  Please, if someone is successfully using it, let me know.

I am having the same problem. Hoping to find a solution soon.

RC

hi , i have the same problem.
showthread.php?s=amp;threadid=50603

i have increased the forced mux-rate in bbMPEG , till the underflow-errors were gone. but the bin-file is the same as with underflow-errors :too big for the cd.
i hope there is soon a workaround or a solution for the prob , cause i need the vcd-trick for my dvd-player.

Yeah I tried that too. Same thing. I really need this option also, as my DVD player doesn't support SVCD either.

hi,when you used the vcd-trick in bbMPEG is, besides the big bin-files, the output-movie in sync? i did avi2svcd with the vcd-trick and the movie was total out of sync :each of them video,audio and subs.has anyone of you the same prob? take care.

Oh, I forgot to tell you, in the bbMPEG settings when selecting MPEG1 please double click on the radiobutton, that way you'll get the default values for MPEG1 in bbMPEG. I don't know if that'll help, but it's worth a try.

Originally posted by dvd2svcd
Oh, I forgot to tell you, in the bbMPEG settings when selecting MPEG1 please double click on the radiobutton, that way you'll get the default values for MPEG1 in bbMPEG. I don't know if that'll help, but it's worth a try.

that's what i've been doing

i double-clicked mpeg1 and got the mpeg1-values in bbMPEG. the result was ,as said before,out of sync.

Originally posted by dvd2svcd
Oh, I forgot to tell you, in the bbMPEG settings when selecting MPEG1 please double click on the radiobutton, that way you'll get the default values for MPEG1 in bbMPEG. I don't know if that'll help, but it's worth a try.

I did do that. Did not help.

RC

Hi,
I have the same prob with the audio when using the header trick,I get around the size of the images by changing the cd size to 700 in the bitrate tab,and I thought that may have caused the sync prob,but if others are having the same thing then I guess thats not it.let me know if you get a work around
Thanks

Originally posted by marcor
hi,when you used the vcd-trick in bbMPEG is, besides the big bin-files, the output-movie in sync? i did avi2svcd with the vcd-trick and the movie was total out of sync :each of them video,audio and subs.has anyone of you the same prob? take care.
I finally decided to test my DVD player with a header tricked SVCD, so i changed the filesize to 650MB. Now, on my APEX 5131, the audio is waaaay off, and it skips too.  it seems like the audio is playing too slow, but the tone doesn't sound wrong, so it has to be these skips or silent spots that are quickly adding up, making the audio far behind the video even after a minute or 2.  My buddy's player is supposed to be able to play these, so i'm gonna have him test this disk out when he goes back home in a week....i guess more results will follow.

I am just curious.  You own the 5131, which is an awesome SVCD player.  Are you making this disc for somebody else?  I may have missed that part if you said so.

BTW if you didn't know I did some extensive testing with the 5131 and the following is my results for XSVCD playability.

Max Bitrate 5500, but be safe and set the max to 5000.  Sometimes 5500 would fail.

Plays 99 minute CD's of up to 990MB's of overburned video.
Plays 80 minute CD's of up to 828-830Mb's of overburned video.

Plays raw mpg's with AC3 audio, but will not play a SVCD with AC3 audio so you must burn as data so max on a disc is around 700mb's.

Mark

and reading the forum comments that it plays SVCD's using the header trick.  The thing that is most strange to me is the more than 10% increase in filesize when using this trick.