TMPGEnc: output plays several minutes longer than the source
 

hi all hope you can help me with this...

i am using TMPG to create elementary video but im confused because...

if i convert a 25 fps xvid PAL avi to 25 fps mpeg-2 (without doing a framerate conversion) my mpeg-2 output plays several minutes longer than the source. Surely the playing time should be the same as TMPG should be keeping the same number of frames as the source (it isnt - there are 6000 more frames).

if i convert 23 fps xvid avi to 25 fps mpeg-2 (without doing a framerate conversion) my mpeg-2 output plays several minutes longer than the source. Surely the playing time should be slightly shorter than the source as TMPG should be keeping the same number of frames but playing them faster?

im taking "do not do framerate conversion" to mean that TMPG will not add extra frames to account for frame rate differences but will simply play the existing frames at an adjusted speed.

so basically the question is "where are all these extra frames coming from?"

thank you!

P.S. im new to this so i might have got the wrong end of the stick completely :oops:

ok ive since made some progress (thanx abond) and have now have more information...

this concerns the 25 fps xvid avi im trying to convert to 25fps PAL mpeg-2...

-when i open the avi in virtual dub i have roughly 30000 frames

-when i open tmpg it wants to encode roughly 36000 frames

-if i go to a frame in virtualdub, say frame 18000 and then go to "source range" in tmpg and go to frame 18000 the two frames are different

-in tmpg in the source range popup it displays the correct resolution (544 x 448) but the wrong frame rate (it displays 30 fps)

-the duration of the mpeg-2 is exactly 20% more than that of the avi. this corresponds to 30 fps being exactly 20% more than 25 fps.

so it appears that tmpg is reading the avi wrong but how can i correct or account for this?

thanks!

i dont use tmpg i prefer cce so this will be the only post i make have you tryed what the last few answers in this thread suggest

Stop doing frameserving and open directly your avi in tmpgenc. Your problems will surely end.

And if you need to do filtering, learn about avisynth scripts. You can do whatetever you are doing in vdub with avs filters.

thanx for your help cw and dialhot. however i am aware of the directshow issue and am already opening the avi directly (not frameserving).

i have isolated the source of the problem :D but dont seem alot closer to a solution :( ...

i thought id reinstall tmpg caus sometimes that helps in these sorts of situations. upon reinstall it recognised the correct frame rate of all avis without any problems (i check this by bringing up the source range popup).

however when i moved the directshow file reader up to a higher priority TMPG started thinking every avi was 30 fps

if i move the directshow file reader back down i cant encode xvid avis anymore because it starts bombarding me with error messages

is there any way round this? im surprised more people dont have this problem.

thanks loads

optical

First, uncheck Directshow in tmpgenc. This way you will be sure to not be bothered by it without your knowledge.

Second : what error do you have when doing xivds directly in tmpgenc ?

Third (optional) : what about using a script ?

if i uncheck the directshow file reader then i get the message "write error occured at address 77F83AED of module ntdlll.dll" (see cw's link above)when i press start. this prevents me from transcoding.

i dont really know anything about scripts is that related to frameserving?

thanks

optical

You should reinstall Directx. ntdll.dll is related to it.
And also all your codecs.

Actually avisynth is a frameserver that applies filters to a video according to what you ask to it grant to a script.

thanx dialhot i have installed directx 9.0 b and this has seriously reduced the instances of "ntdll errors." whilst tmpg is still a bit temperamental i am now able to encode divx without the directshow file viewer. if there is an error it always occurs before encoding starts so im able to simply restart tmpg. im truely grateful for your help having been working on this problem for over a week. :D :D :D

thanx loads!

optical