Minimum keyframe interval broken

[gldblade]

Minimum keyframe interval is broken in the latest build. I'm currently using Nic's and I'll try out Koepi's, but I think this is a CVS thing.

[Koepi]

You're right, I tried set it to 1 and got 5 consecutive IFrames, not right what I expected (no big thing for me though since the core does decide on a very good basis).

Regards,
koepi

[-h]

Setting min interval to 1 "disables" the spacing system, so you'll get consecutive I-frames. Perhaps it should be labeled "I-frames can only occur every x frames", though that's a bit long. I'll just stick it in the tooltip.

Or is it still broken when spacing = 2?

-h

[gldblade]

I use a minimum spacing of 10 and it still gives consecutive frames.

[gldblade]

It's still broken in the latest build. Is it ever going to be fixed? I once saw about 15 I-frames clumped together. Not good...

[-h]

It's still broken in the latest build. Is it ever going to be fixed? I once saw about 15 I-frames clumped together. Not good...

What mode was this in? Minimum I-frame interval *only* affects 2-pass 1st pass mode (and implicitly the 2nd pass modes via the stats file).

It shouldn't even affect the 2-pass mode in a perfect world, because if the codec uses consecutive I-frames, it's because that's as small as the frame can be with XviD's current motion estimation - by forcing them to P-frames, they actually get *bigger*. Thus there is no gain from using a minimum spacing interval in the 1-pass modes, and it's only in 2-pass because consecutive I-frames harm the overflow calculations.

Heh or is it broken in 2-pass 1st pass? :)

-h

[gldblade]

>Minimum I-frame interval *only* affects 2-pass 1st pass mode

Hmm... Maybe this is the problem. I'm redoing the 1st pass stats to see if I did something wrong.