On Fri, Sep 22, 2017 at 08:20:24AM +0200, Thomas Hartwig wrote:
> Attached is the clean patchfile. I want to give some small
> background: the problem happens in javacpp. It looks like there is a
> problem handling pixelformats not correct at all when used for pixel
> grabbing. This is why I mentio
Attached is the clean patchfile. I want to give some small background:
the problem happens in javacpp. It looks like there is a problem
handling pixelformats not correct at all when used for pixel grabbing.
This is why I mentioned it in a streaming context.
However this patch is a small workarou
On Thu, 21 Sep 2017 22:55:14 +0200
Thomas Hartwig wrote:
> The problem is this warning is flooding the console with deprecated
> warnings for every decoded frame. However decoding works well. This is
> an issue with an Axis camera H264 stream received via rtsp for instance.
> There are several
2017-09-21 22:55 GMT+02:00 Thomas Hartwig :
> It looks like vendors are not changing their encoding easily. ;-)
The warning is not related to the vendors (or input streams
in general).
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
On Thu, Sep 21, 2017 at 10:55:14PM +0200, Thomas Hartwig wrote:
> The problem is this warning is flooding the console with deprecated
> warnings for every decoded frame. However decoding works well. This
> is an issue with an Axis camera H264 stream received via rtsp for
> instance. There are sever
The problem is this warning is flooding the console with deprecated
warnings for every decoded frame. However decoding works well. This is
an issue with an Axis camera H264 stream received via rtsp for instance.
There are several complaints about it in the WEB for years now and I
could not find
