On Mon, 25 Sep 2017 16:14:08 -0700
Aman Gupta wrote:
> On Wed, May 24, 2017 at 6:47 AM, wm4 wrote:
>
> > With the new decode API, you can't handle errors directly in the API
> > user - you only know that the hwaccel did not initialize at all.
> >
> > Add some approximate logging.
> > ---
> > l
On Wed, May 24, 2017 at 6:47 AM, wm4 wrote:
> With the new decode API, you can't handle errors directly in the API
> user - you only know that the hwaccel did not initialize at all.
>
> Add some approximate logging.
> ---
> libavcodec/videotoolbox.c | 6 ++
> 1 file changed, 6 insertions(+)
On Wed, 24 May 2017 15:47:36 +0200
wm4 wrote:
> With the new decode API, you can't handle errors directly in the API
> user - you only know that the hwaccel did not initialize at all.
>
> Add some approximate logging.
> ---
> libavcodec/videotoolbox.c | 6 ++
> 1 file changed, 6 insertions(
With the new decode API, you can't handle errors directly in the API
user - you only know that the hwaccel did not initialize at all.
Add some approximate logging.
---
libavcodec/videotoolbox.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavcodec/videotoolbox.c b/libavcodec/videot
