Koepi - 15022003-1 Bug

[PowerMacG4]

Encoder: Koepi's XviD-15022003-1 release

Problem:
WAY too many I-Frames in a row.

Things I think may have caused the problem:
-Min-I frame was set to 1
-Alt-Curve was set to 100/200 instead of default

Other settings other than default
-VHQ lvl 1
-Luma Mask
-Chroma ME

[Tester]

That's a known bug that also relates to previous builds

search the forum

[Teegedeck]

Originally posted by PowerMacG4
Encoder: Koepi's XviD-15022003-1 release

Problem:
WAY too many I-Frames in a row.
...
Things I think may have caused the problem:
-Min-I frame was set to 1

This isn't a problem, it's the way it's supposed to be! :angry: Please read some documentation before posting.

[PowerMacG4]

I did read the documentation, and I read these forums all the time. The xvid.org development forums are full of people posting that 'it doesnt work', so I come here. Anyway, I fixed my problem by loading defaults (again), and setting min I-frame interval to 6 (as suggested for earlier builds, I thought the 'bug' was 'fixed' and could be safely set to 1).

Calm down.

[Teegedeck]

Originally posted by PowerMacG4
I did read the documentation, and I read these forums all the time. The xvid.org development forums are full of people posting that 'it doesnt work', so I come here. Anyway, I fixed my problem by loading defaults (again), and setting min I-frame interval to 6 (as suggested for earlier builds, I thought the 'bug' was 'fixed' and could be safely set to 1).

Calm down.
Don't worry, I'm not really angry. ;) It's not like you did anything insulting. But you just missed something in the docs, anyway, my friend:

IF you set min I-frame interval to '1', THEN it means there is NO minimum interval at all!

The codec then is free to set an I-frame whenever it wants to. BUT this quite the right way to do it, because XviD only uses I-frames when they consume less data (=are smaller) than P-frames would be. In 2-pass this can get a bit screwed up because you usually set an I-frame boost and thus let I-frames always be larger than P-frames. But this can be overcome easily by using an 'I-frame bitrate reduction' that, well, deducts the same amount of bits from an I-frame if it comes too shortly after a preceding I-frame ('below I-frame distance'). It is advisable in this case, though, not to restrict I-frame quantizers to '2'.

The thing that triggered my reaction, was that we've become a bit touchy with people calling everthing a bug without giving their own doing a second thought. In your case, there was nothing wrong with XviD. It just did what you told it to do.