On Sun, 7 May 2017 12:01:11 -0700
Aaron Levinson wrote:
> Are you also planning to change ffmpeg_videotoolbox.c? See below for
> more comments.
>
> Aaron Levinson
>
Pushed. Changed what I felt like I could change. Thanks for the review.
___
ffmpeg-
Are you also planning to change ffmpeg_videotoolbox.c? See below for
more comments.
Aaron Levinson
On 5/2/2017 8:26 PM, wm4 wrote:
This adds tons of code for no other benefit than making VideoToolbox
support conform with the new hwaccel API (using hw_device_ctx and
hw_frames_ctx).
Since Vide
On Wed, 3 May 2017 05:26:04 +0200
wm4 wrote:
> This adds tons of code for no other benefit than making VideoToolbox
> support conform with the new hwaccel API (using hw_device_ctx and
> hw_frames_ctx).
>
> Since VideoToolbox decoding does not actually require the user to
> allocate frames, the
This adds tons of code for no other benefit than making VideoToolbox
support conform with the new hwaccel API (using hw_device_ctx and
hw_frames_ctx).
Since VideoToolbox decoding does not actually require the user to
allocate frames, the new code does mostly nothing.
One benefit is that ffmpeg_vi