Avisynth: Strange Size Prediction Behavior

[rendalunit]

When encoding a divx3 to kvcdx3 with file prediction method, I see that tmpg sees the sample as having the total frames of the movie. It encodes the 100 second sample and then enocdes a black screen for the rest of the frames I tried manually entering the values in SelectRangeEvery to bypass Framecount but it didn't work. Maybe SelectRangeEvery() doesn't work with DivX I'm using Avisynth 2.06

[black prince]

Hi rendalunit,

rendalunit wrote:

Quote:

When encoding a divx3 to kvcdx3 with file prediction method, I see that tmpg sees the sample as having the total frames of the movie. It encodes the 100 second sample and then enocdes a black screen for the rest of the frames I tried manually entering the values in SelectRangeEvery to bypass Framecount but it didn't work. Maybe SelectRangeEvery() doesn't work with DivX I'm using Avisynth 2.06

I've converted many Divx 5.0.2 (avi) videos using file size predictor
via avs script and Tmpgenc shows the correct numbers of frames,
usually 2424 as the range. The file size estimates have been very
close with file size predictor. It could be the codec is conflicting with
others (i.e. divx 4.0, 5.0.2, etc.). Could you have by accident un-
commented a Trim command. Check the video stream using VirtualDub
--> File Information --> Video Stream and look for frame count,
frames per second, etc. While your there take a look at the Audio
Stream and see if it's mp3 or *Unknown.

-black prince

[SansGrip]

Quote:

Originally Posted by rendalunit

It encodes the 100 second sample and then enocdes a black screen for the rest of the frames

It does this for me, too. I solved it by going into Source Range, hitting "Default", then "Move to end frame", then "Set end frame".

For some reason the Source Range dialog sees the correct length, so by doing this you force the encoder to stick within that range.

The bug is either in TMPGEnc or SelectRangeEvery, because I get strange results from WMP too.

Edit: By which I mean, the bug must be in SelectRangeEvery, because I get strange results from WMP too.

[rendalunit]

@SansGrip,

Selecting source range in TMPGEnc solved the problem for me- Thanks!

-ren

[black prince]

Hi SansGrip,

SansGrip wrote:

Quote:

The bug is either in TMPGEnc or SelectRangeEvery, because I get strange results from WMP too.

Never had to set default in Tmpgenc's source range to get correct
frames. Oh well, it's strange.

-black prince

[GFR]

I've had this problem too.

You can solve it in TMPGEnc (with the Source Range tab) or you can add an extra line at the end of the prediction script with a Trim to the desired Framecount.