[x264-devel] x264 seems to ignore --min-keyint option

[Paul]

Was trying to match other video streams that I did not want to reencode which already had a constant key frame interval (from a camcorder). When merging these will the new x264 ones it causing the mp4box muxer to start new streams.

Might want to update the documentation to note this. It took me awhile to figure out why the muxing was not working like I thought it would.

Thanks for the info.

Sent from my BlackBerry 10 smartphone.
From: Henrik Gramner
Sent: Sunday, May 17, 2015 10:37 AM
To: Mailing list for x264 developers
Reply To: Mailing list for x264 developers
Subject: Re: [x264-devel] x264 seems to ignore --min-keyint option


On Sun, May 17, 2015 at 6:59 PM, Paul <ranftmaps at hotmail.com> wrote:
> The --min-keyint 30 option appears to be being ignored.
>
> Mediainfo is not reporting a key frames are a constant 30 and is reporting
> that the encoder options were as below.  Please note that in the options
> listed the value of keyint_min=16.

Is there any particular reason why'd you want to enforce a high
keyint_min? x264 is quite good at deciding optimal keyframe placement
by itself.

The technical answer is that keyint_min is actually restricted to the
interval [1, keyint_max/2+1]. Loren made this change back in 2005 (
http://git.videolan.org/?p=x264.git;a=commit;h=648328088b1c4bfb3afcbc92b6711cb7b7b5e068
), but I don't really know the reason behind the restriction and if
that reason is still relevant today. You'd have to ask him.

Henrik
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
https://mailman.videolan.org/listinfo/x264-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20150517/e3136587/attachment.html>