[MEncoder-users] x264 [warning]: non-strictly-monotonic PTS

[Wes Morgan]

On Tue, 6 Apr 2010, Grozdan wrote:

> On Tue, Apr 6, 2010 at 7:01 PM, Andrew Berg <bahamutzero8825 at gmail.com> wrote:
> > With the latest build of x264, I keep getting this. From what I've read,
> > videos with a constant frame rate should not be able to cause this
> > error, which is odd since I don't have any VFR videos and in this
> > particular instance, I even specify the frame rate. Is there any way to
> > either suppress this message so it doesn't flood the terminal (-msglevel
> > all=0 doesn't work, AFAIK only 2>/dev/null does) or prevent x264 from
> > having a problem in the first place? I've seen suggestions to pass
> > --force-cfr to x264, but AFAIK, it's impossible to pass arbitrary
> > options to libx264 from MEncoder.
>
> What? force_cfr in mencoder works just fine here. Mencoder just parses
> available options from libx264 so all that are exposed in this lib
> (and force_cfr surely is) can be taken by mencoder as well.

The odd thing is that ffmpeg wasn't affected by the blu-ray related VFR
patches to x264. I originally thought it had something to do with ffmpeg
setting the timebase, but it isn't. Rather, it appears to be related to
PTS. Setting force_cfr works, so it's not something to waste a lot of time
tracking down. However it seems to me that it really is a bug somewhere,
either in x264 or mencoder.