follow x264's default keyint-min behavior
Issue #24
resolved
x265 currently sets keyint-min to be equal to keyint-max if it is not assigned. I'm pretty sure x264 does something different. We should follow their approach
Comments (3)
-
Account Deleted -
reporter nice, thanks. I've applied this
-
reporter - changed status to resolved
follow x264's keyframe-min logic [CHANGES OUTPUTS] (closes
#24)If no --keyint-min is specified, default to max/10, and clamp the value to between [1, max / 2 + 1]. This allows x265 to insert I frames when scene cuts are detected between keyframe-min and keyframe-max
→ <<cset 898ccce491e9>>
- Log in to comment
Well, if keymin isn't manually set, x264 would choose min(fps, keymax/10). Excessive values are also clipped to [1, keymax/2 + 1].