Strange Sample Prediction... Help!

[muaddib]

I'm having some troubles with sample prediction.
Here is what is happening:

I made an avs script:

LegalClip() 
BilinearResize(480,480)
FluxSmooth()
Blockbuster(method="noise", variance=.5, seed=1)
Sampler(length=24)
LegalClip()

When I load the script in TMPG, I can see with the source range dialog that it has 2064 frames.
But after I encode the sample and load it in TMPG, the source range dialog tells me that the sample has 1230 frames!

This can't be right!
Can someone please test that for me?
Are the number of frames supposed to differ like this?

[SansGrip]

Quote:

Originally Posted by muaddib

When I load the script in TMPG, I can see with the source range dialog that it has 2064 frames.

Load it into VDub and look under File->File Information. I trust it a lot more than TMPGEnc .

[muaddib]

Quote:

Originally Posted by SansGrip

Quote:

Load it into VDub and look under File->File Information. I trust it a lot more than TMPGEnc .

Ok, I did it, and VDub show that the AVS script has the same 2064 frames. That's the right value, because I'm doing an 86:24 sample clip and it’s supposed to be 2064 frames. It is the encode sample that should not be right: 1230 frames with TMPG source range.

Well, as VDub can't read mpeg2 files (that's what I'm encoding), I have to make a D2V+AVS from the M2V to feed VDub that says it has 2061 frames. That is pretty much closer to 2064 than what TMPG says.

So... can I presume that TMPG Source Range it totally wrong when calculating the frames of this mpeg2 sample?

Anyone else noticed that?

[SansGrip]

Quote:

Originally Posted by muaddib

Well, as VDub can't read mpeg2 files (that's what I'm encoding), I have to make a D2V+AVS from the M2V to feed VDub that says it has 2061 frames. That is pretty much closer to 2064 than what TMPG says.

It shouldn't be close. It should be exactly the same .

Quote:

So... can I presume that TMPG Source Range it totally wrong when calculating the frames of this mpeg2 sample?

Did you try hitting "default" in that dialog?

[muaddib]

Quote:

Originally Posted by SansGrip

It shouldn't be close. It should be exactly the same .

That's what I thought

Quote:

Did you try hitting "default" in that dialog?

Yes I did. I hit "default" and then hit "move to end frame".
But now it’s getting worst :

I did another encode of the same script (2064 frames) but with a lower CQ_VBR. The first one was CQ_VBR=11 and the new one is CQ_VBR=9. With this new encoded sample the "source range dialog" says just 914 frames! VDub says 2060.

[SansGrip]

Quote:

Originally Posted by muaddib

I did another encode of the same script (2064 frames) but with a lower CQ_VBR. The first one was CQ_VBR=11 and the new one is CQ_VBR=9. With this new encoded sample the "source range dialog" says just 914 frames! VDub says 2060.

That's very odd -- but why are you loading an MPEG into TMPGEnc anyway?

[muaddib]

Quote:

Originally Posted by SansGrip

That's very odd -- but why are you loading an MPEG into TMPGEnc anyway?

Just to see the number of frames.

[kwag]

Quote:

Originally Posted by muaddib

Quote:

Just to see the number of frames.

Go drink some beers muaddib, you need that

-kwag

[muaddib]

Quote:

Originally Posted by kwag

Go drink some beers muaddib, you need that

I guess you are right.
I'll do that... maybe this way I can forget all this.
or not

[muaddib]

Well, I stopped looking at the frames and decided to encode...
Here are the results:

Predicted file size: 682,61mb
Final file size: 681,97mb
Difference: 0.09%

WOW
That's the closest prediction that I ever had!! This is GREAT!