Maximum i-frame interval does nothing in second pass

[Katie Boundary]

When doing a two-pass XviD encode, if you change the maximum i-frame interval between the two passes, the second pass will ignore the new setting and use the same i-frame interval that was used during the first pass.

Is this intended behavior or a bug?

[Cary Knoop]

First of all, why use XviD, it's an old and inefficient CODEC.
Second, why change essential parameter values? Two-pass is only useful to optimize the encoding for a given fixed size.

[Sharc]

As far as I know it is by design. The position of I, P and B frames are determined in the first pass of a 2-pass encode. The second pass does not (must not) change it. Changing it would undermine the purpose of a 2-pass encode.

[Katie Boundary]

First of all, why use XviD

Because everything that's "better" is too much of a pain in the ass to install and/or use. Or just poorly documented.

[Cary Knoop]

Because everything that's "better" is too much of a pain in the ass to install and/or use. Or just poorly documented.
Using H.264 or H.265 is not any harder than using XviD.

What it takes is the willpower to adapt to newer technology instead of maintaining 'rusty' views thereof! :)

[StainlessS]

Yip, x264 is way way better than XVID, however, I aint too keen on adopting x265 as yet.
[probably because my go-to player in android (MX Player) cant seem to seek in x265 stream, back to beginning or keep going only, was also maybe 10 bit where problem, not sure].