TMPGEnc keeps encoding after movie has finished????

[zygot]

yep that's right, using ver 12h the proggie keeps encoding
after it has finished encoding. I have to ctrl alt del to exit tmpgenc. The mpeg is fine but sometimes after encoding I exit the program (but tmpgenc thinks it's still encoding) I lose the hole mpeg which I encode SVCD most of the time. As you can appreciate after a period of time this tends to p%$# one off. I have better things to do than encode a 2 or 3 hour movie (SVCD) then let it encode to the end, normally about 4-5hrs then chew up my mpeg so I have to start again. mmmm....my system is definetely not under powered it is a
AMD 1333
512 meg ram
60 gig h/d (40 gig free)
abit kt7a RAID MB
and other good stuff that's not applicable to encoding.
any suggestions would be great
ps mb and CPU temps are fine, have decent fans, during encoding CPU max temp is 42 (well within limits)

[fugoff]

LMAO! I know the feeling man Since I reverted back to tmpeg12B I have had no problems like this.

[hitechjunkie]

what do you mean by "TMPGEnc thinks its still encoding"? you should be able to exit TMPGEnc cleanly after an encode by clicking on File->Exit.

although TMPGEnc may be done encoding that last frame, it probably hasn't finished writing out all of the encoded frames from temp/buffer area to the final mpeg.

one sure way to determine whether it is completely finished is to use batch encoding and watching the little window. when it is finally done, you'll see all of the final stats of the encode.

[Bucky Wheat]

I have the same, or at least a similar problem. A couple of my films just mess up TMPG.
I can usually see it before I start, because TMPG displays way too many frames, like 470.000 for a movie that has 167.000 in VDub. And the funny part is, after the actual existing frames (ie the movie) is done, it just keeps going encoding black frames.
If I quit then, the movie will most probably play without sound, though the down right corner in Media Player shows, that it has sound.
I also tried it in version 11.20.97 and 11.20.98, always the same.

Any solution?

Bucky

[koinhelgo]

I often get this problem as well when encoding films to mpeg
this isn't usually a problem cos it does eventually finish if you leave it- usually between about 10 and 20 minutes extra (film time) when it does it - I usually encode to mpeg overnight whilst I sleep. This means that when I split it into 2 parts to burn to two vcds I get two hour and a bit mpegs.
It just means you have an hour of a film on one disc and the last half hour or so on the second. My standalone doesn't play the extra black encoded frames though it just stops.
Strangely Media Player shows the longer file, but if you try to drag it to the extra bit it just stops and goes back to start but it will play the main bit OK.
I use version 12 i.
It doesn't always do it so it may depend on some things like film length and whether encoding to a defragged drive or not.
Anyone any ideas?

[Greg12]

i have this. it takes about 2 minutes to unlock.

i can tell when it's done because the vidoe and audio sources will be white n u can change them.

when it working, the area is greyed out

[zygot]

ok I will try some of these ideas and see what happens..
now to answer hitechjunkie's question, can I exit the proggie in the usual way, as I stated the answer is no, also on my system writing out the temp buffers etc takes as long as a sparrow fart. One other point is if the program is behaving correctly why does the elapsed time continue to count even though the mpeg is completed. When it does work correctly the elapsed time stops when encoding finishes, then buffers are flushed etc...but I will also try the batch encode...see if that makes a diff

[hitechjunkie]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>One other point is if the program is behaving correctly why does the elapsed time continue to count even though the mpeg is completed. </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

i usually see this happen when i begin bringing up other apps on my PC while the encoding is taking place. some of the more memory intensive applications (games, video editing of large avi's/mpegs, ripping (dma)), will then place heavy demands on memory, causing portions of the encoding to be moved in/out memory to/from the systems pagefile. this is when it takes a bit longer for TMPGEnc to finalize the mpeg when it's done with that last frame. probably not the fault of the encoder though, but more the memory management subsystem of WinDoze.

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>I have the same, or at least a similar problem. A couple of my films just mess up TMPG.
I can usually see it before I start, because TMPG displays way too many frames, like 470.000 for a movie that has 167.000 in VDub. </BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

yes, this has happened to me as well. and, like you said, if you are watching the total frames in TMPGEnc, it will be some really big number. i'm not sure why this happens, though. i did abort an encode once that had this condition. i managed to abort it as it was halfway thru the 100,000 or so extra frames it was encoding. my mpeg was still good and re-multiplexing the audio/video streams seemed to strip away the added frames.