> On Jun 17, 2016, at 10:36 AM, Clément Bœsch wrote:
>
> On Fri, Jun 17, 2016 at 09:43:09AM -0400, Richard Kern wrote:
>> Since ca2f19b9cc (h264: switch to h2645_parse for NAL parsing) the hwaccel
>> wouldn’t init (when the first h.264 frame is decoded). It was the same on OS
>>
On Fri, Jun 17, 2016 at 09:43:09AM -0400, Richard Kern wrote:
> Since ca2f19b9cc (h264: switch to h2645_parse for NAL parsing) the hwaccel
> wouldn’t init (when the first h.264 frame is decoded). It was the same on OS
> X and iOS - creating the decoder would return a “decoder malfunction” error.
> On Jun 17, 2016, at 5:31 AM, Clément Bœsch wrote:
>
> On Fri, Jun 17, 2016 at 03:24:10AM +0200, Rick Kern wrote:
>> ffmpeg | branch: master | Rick Kern | Wed Jun 1 21:40:22
>> 2016 -0400| [8e47a99f576da10b2a36e33b6b9acbf1c2da7485] | committer: Rick Kern
>>
On Fri, Jun 17, 2016 at 03:24:10AM +0200, Rick Kern wrote:
> ffmpeg | branch: master | Rick Kern | Wed Jun 1 21:40:22
> 2016 -0400| [8e47a99f576da10b2a36e33b6b9acbf1c2da7485] | committer: Rick Kern
>
> lavc/videotoolbox: fix H.264 hwaccel init issue
>
> Fixes