At the end credits? Yes. Did it happen anywhere on the movie? If it didn't, then it's the MIN bit rate at the point where it switches to end credits, and during end credits. There's just too much black there. You might just want to fix your MIN bit rate to 450Kbps. That should keep a steady low bit rate stream that is high enough to kill that effect.

I'm still tweaking prediction. I'm now at 512:6. Running two sample encodes on two machines.

-kwag

It's even more useful than you first thought, isn't it? :)

In fact it doesn't really add sharpening so much as retain existing sharpness. The other resizers (except for "precise bicubic") soften the image. Lanczos is about the most "accurate" resizer there is, but it's bad for us because we want that extra compressibility that softness brings :).

No worries. Glad you got FitCD figured out :).

Yes -- about the last two or three minutes of the movie. It started with a single audio glitch (one of those real loud ones) and progressively got worse as time passed.

I'm still tweaking prediction. I'm now at 512:6. Running two sample encodes on two machines.

I'm testing too, but in the other direction -- 25:96 right now ;).

128:24 seems to be hitting the target very accurately.

When this thing finally stabilizes, we're going to have to write a "Readme.txt" or something, because I think everyone reading this thread must be either asking for some hard liquor or going bananas changing prediction parameters :mrgreen:

-kwag

Sounds logical, too... :)

:lol:

Yes, I hope no-one is trying to track this in real-time :D. Actually I intend to write up a howto while I'm away for Christmas (24th, 25th, 26th). Thank goodness for the laptop... :)

I smell something is burning. 8O Oh, look out, it must be SansGrip's mind running a prediction test loop :mrgreen:

-kwag

Hey! Of course we are tracking it!
Well, at least we are trying... :wink:
Just hope that you guys don't get lost in the middle of all this variation of granularity and window/sample length. :D

Who said that?? 8O :twisted:

What's my name :?: , where am I :?: :roll:

:mrgreen:
-kwag

Come on guys, give us something...
I have a movie here that is willing to be predicted! :D
What should I use?
I made some samples with these strange settings (512:6, 128:24, 25:96) and all came out with very different prediction. 8O

We're minutes away from having a formula that should work for tonight :mrgreen:.

Drums rolling /\/\/\/\/\/\/\/\/\/\ ........

Ok, after hours of testing and (in my case at least) ingesting caffeine, here is the latest file prediction formula...

Count all the chairs in the movie EXCEPT those with arms, then find the square root. Multiply by your favourite cousin's birthday and add 6. Calculate that value to the power of how many eggs you've eaten in the last two years, then divide by 12 and subtract quite a bit. Swap all digits, convert to hex, and simmer for 45 minutes while stirring constantly.

Then throw that value away, because what you really do is...

Let's say your movie is 96 minutes long, and we're using the new GOP structure with a maximum length of 24. This is the line you'd insert into your Avisynth script to get the sample strip:

Sampler(96, 24)

Pretty simple, eh? If your movie is 115 minutes long, it'd be:

Sampler(115, 24)

This will then give you a nice sample strip. You then do the formula as usual, with an error margin of 2% (in KVCDP) or 0.98 if you do it manually.

If I left anything out, kwag'll fix it :mrgreen:.

Have fun and test lots and let us know...

And here's the old ( hard core ) way :lol:
This is what you add to the end of your .avs script:

Or automatic:

And then use the new formula:
Note: For PAL users, use 25 instead of 24 for the value of SL and change the 24 to 25 in the formula. If any NTSC user has to encode at 29.97, then use a value of 30.

And if I screwed up, SansGrip will fix it :mrgreen:

-kwag

By the way, before you ask: yes, it really did take us that long to come up with something that simple ;). However we're now hopefully on surer ground wrt the formula and I'm fairly confident that the error margin is now set correctly.

Of course, kwag suggested all this days ago. We just had to run everything from Sampler(20, 200) to Sampler(1200, 2) in order to discover that he was, as usual, right all along :mrgreen:.

Thank you and goodnight ;).

Thanks for all your time and suggestions SansGrip :D
This was like a roller coaster. Encode, change, encode, reformulate, encode.... :lol:
Now after seeing all the tests you did, I am also very confident that the file prediction is far better than what we had before.

BIG THANK YOU :wink:

Now, I'm going to bed 8O
Good night all.

-kwag

sansgrip wrote:

"In fact it doesn't really add sharpening so much as retain existing sharpness. The other resizers (except for "precise bicubic") soften the image. Lanczos is about the most "accurate" resizer there is, but it's bad for us because we want that extra compressibility that softness brings . "

yes,i'm with you.
in my tests i really see the difference.
i "mix" with Blockbuster.....cool. :wink:

Since this thread is kinda all about everything, and nobody pays attention to any other one at the moment :D maybe someone can help me with this one...

with the new GOP I encoded frequency again, at 704x576 PAL, and result was really watchable... Usually I only encode in MPEG2 and mux with BBMPEG. I did the same thing with this movie, after encoding the audio with Headache. I muxed it as VCD VBR, forced mux rate 0, write program endcode checked.
The video and audio are fine in sync on my PC, but viewed on my standalone (which plays all KVCDs fine, when i muxed them together with BBMPEG) the audio is slightly too early from the beginning... that never happened before...

any suggestions?

Wow, that's weird... Total frames/MovieTimeInMinutes? Can you explain it a little bit?

It's ok... I got it. :D
It would be easier to understand if it was:
Or even easier (just for my understanding):
Anyway, I just needed to understand it to not get crazy... the formula is as good as always!
Nice work!