[libav-devel] [PATCH] libx264: Don't leave max_b_frames as -1 if the user didn't set it

2012-01-13 Thread Martin Storsjö
max_b_frames is initialized to -1 for libx264, to allow distinguishing between an explicit user set 0 and a default not touched 0 (see bb73cda2). If max_b_frames is left as -1, this affects dts generation (where expressions like max_b_frames != 0 are used), so make sure it is left at the default

Re: [libav-devel] [PATCH] libx264: Don't leave max_b_frames as -1 if the user didn't set it

2012-01-13 Thread Anton Khirnov
On Fri, 13 Jan 2012 23:51:59 +0200, Martin Storsjö mar...@martin.st wrote: max_b_frames is initialized to -1 for libx264, to allow distinguishing between an explicit user set 0 and a default not touched 0 (see bb73cda2). If max_b_frames is left as -1, this affects dts generation (where

Re: [libav-devel] [PATCH] libx264: Don't leave max_b_frames as -1 if the user didn't set it

2012-01-13 Thread Janne Grunau
On 2012-01-13 23:51:59 +0200, Martin Storsjö wrote: max_b_frames is initialized to -1 for libx264, to allow distinguishing between an explicit user set 0 and a default not touched 0 (see bb73cda2). it's generally initialized to -1 If max_b_frames is left as -1, this affects dts generation

Re: [libav-devel] [PATCH] libx264: Don't leave max_b_frames as -1 if the user didn't set it

2012-01-13 Thread Janne Grunau
On 2012-01-14 00:43:45 +0200, Martin Storsjö wrote: On Fri, 13 Jan 2012, Janne Grunau wrote: On 2012-01-13 23:51:59 +0200, Martin Storsjö wrote: max_b_frames is initialized to -1 for libx264, to allow distinguishing between an explicit user set 0 and a default not touched 0 (see bb73cda2).