TMPGEnc SVCD multiplex: does this happen to you?

[homerpez]

I tried to multiplex an MPEG-2 video stream with a separate audio stream, and I was able to do one sucessfully. But, I had to dump out of the program to stop the process!

I then looked at what it was doing to my poor windows swap files... it made them surge upward, taking about 700MB of VRAM to just multiplex the movie! Plus, it takes well over 10 minutes to complete (vs. maybe 2 minutes with bbMPEG)

Sad part is, in order to get my proper timescale before i run it through TSCV, I have to use TMPGEnc to multiplex, then VCDImager can update SVCD scan offsets. bbMPEG produces a timescale half of the real one, so I can't use it!

Is ths normal? How do I fix this?... anything else I can use to multiplex?

<font size=-1>[ This Message was edited by: homerpez on 2001-09-05 18:38:15 ]</font>

[wildcatfan]

Tmpgenc uses alot of virtual memory when it multiplexes....also it uses so much cpu time it will appear to be locked up when it isn't. This is all normal. And yes it IS slower than bbmpeg....

Michael

[daveross]

"Tmpgenc uses alot of virtual memory when it multiplexes....also it uses so much cpu time it will appear to be locked up when it isn't. This is all normal. And yes it IS slower than bbmpeg....

Michael"

What about when I try to cut an SVCD in half? It seems to lock up...I get no response whatsoever, the window just turns white, I have to end up CTRL ALT DEL and shutting it down. This happens most of the time, not always though. Sometimes it just starts working. For VCD's, never have this problem. I encode all standard rates, and use Tmpgenc on VCD and SVCD, btw. Also, what's with the "memory read errors" when doing VCDSVCD cuts in Tmpgenc...seems the encodings still come out ok, so I don't worry to much, but still like to know...

Thanks

[homerpez]

I don't think I agree that it's "looking like it's locked up when it isn't". I know how TMPGEnc behaives normally, with an hourglass sitting there, and you just have to wait until it disappears...

This will continue chugging endlessly, if I wanted to let it. I determined it was over when I kept refreshing explorer and checking the .mpg's filesize. When it got to a certain point, it was as big as it was going to get, yet the program keeps going and going...

After I dump out of TMPGEnc, my RAM/VRAM goes back to norm, and I am able to play the final .mpg, which is complete and works fine.

It just seems like a MAJOR bug that they should have fixed a long time ago (every TMPGEnc version I have still does this). Every SVCD multiplex locks up everything, VCD muxes work fine and complete without hitch...

I guess it's doing what it's supposed to do, even if it's peculiar, odd and plain wrong!

So far it is the only way I can find to provide TSCV/VCDImager with correct timescale information with which I can do GOTO search and exact chapters... just was hoping for a solution that was less buggy!