View Single Post
Old 21st October 2014, 18:26   #7  |  Link
matt.k
Registered User
 
Join Date: Oct 2014
Posts: 4
So, 2 updates:

The level 4.2 was my fault, not decoder's. I forgot to remove some debug code that has forced the decoder to output 4.2. I've re-uploaded sample without the setting, which has proper level now (3.1).

Max keyframe interval seems to affect the glitch. When set to low number (i.e. 40), the glitch is easy to reproduce. With default value (which seems to be 120) it is much more difficult to reproduce. When set to 0 it doesn't seem to happen at all (but I need to test it some more). 0 is a bit weird, documentation states that keyframes will be output when decoder feels like doing it, but it only seems to output one IDR frame at the beginning and that's it. EDIT: Maybe this also could have something to do with buffering period/picture timing SEI that are output before IDR? EDIT2: Stripping SEI makes no difference.

Last edited by matt.k; 21st October 2014 at 18:54. Reason: added SEI mention
matt.k is offline   Reply With Quote