On Tue, Aug 23, 2016 at 3:09 PM, Carl Eugen Hoyos
wrote:
> Hi!
>
> 2016-08-04 13:50 GMT+02:00 Robert Krüger :
> > the log level of INFO does not seem appropriate for the message
> (h264dec.c,
>
> This should be fixed now: The level is below default now if the buffer
> is increased when decoding t
Hi!
2016-08-04 13:50 GMT+02:00 Robert Krüger :
> the log level of INFO does not seem appropriate for the message (h264dec.c,
This should be fixed now: The level is below default now if the buffer
is increased when decoding the first frame (nothing lost), the level
is warning if the increasing hap
2016-08-04 14:41 GMT+02:00 Robert Krüger :
> On Thu, Aug 4, 2016 at 1:55 PM, Carl Eugen Hoyos wrote:
>
>> 2016-08-04 13:50 GMT+02:00 Robert Krüger :
>> > the log level of INFO does not seem appropriate for the message
>> > (h264dec.c, line 531). If it is a condition that shouldn't really happen,
>
On Thu, Aug 4, 2016 at 1:55 PM, Carl Eugen Hoyos wrote:
> 2016-08-04 13:50 GMT+02:00 Robert Krüger :
> > the log level of INFO does not seem appropriate for the message
> (h264dec.c,
> > line 531). If it is a condition that shouldn't really happen, it should
> be
>
> It does happen, see at least
2016-08-04 13:50 GMT+02:00 Robert Krüger :
> the log level of INFO does not seem appropriate for the message (h264dec.c,
> line 531). If it is a condition that shouldn't really happen, it should be
It does happen, see at least two related tickets iirc.
> a warning, otherwise it should be debug (e
Hi,
the log level of INFO does not seem appropriate for the message (h264dec.c,
line 531). If it is a condition that shouldn't really happen, it should be
a warning, otherwise it should be debug (especially for library users this
floods the logs as this seems to happen for many files.
Would a pat
