On Mon, 24 Oct 2016 12:18:07 -0700
Aman Gupta wrote:
> On Sun, Oct 23, 2016 at 11:20 PM, Aman Gupta wrote:
>
> >
> >
> > On Sunday, October 23, 2016, Richard Kern wrote:
> >
> >>
> >> > On Oct 19, 2016, at 8:45 PM, Aman Gupta wrote:
> >> >
> >> > From: Aman Gupta
> >> >
> >> > ff_videoto
On Sun, Oct 23, 2016 at 11:20 PM, Aman Gupta wrote:
>
>
> On Sunday, October 23, 2016, Richard Kern wrote:
>
>>
>> > On Oct 19, 2016, at 8:45 PM, Aman Gupta wrote:
>> >
>> > From: Aman Gupta
>> >
>> > ff_videotoolbox_avcc_extradata_create() was never being called if
>> > avctx->extradata_size=
On Sunday, October 23, 2016, Richard Kern wrote:
>
> > On Oct 19, 2016, at 8:45 PM, Aman Gupta >
> wrote:
> >
> > From: Aman Gupta >
> >
> > ff_videotoolbox_avcc_extradata_create() was never being called if
> > avctx->extradata_size==0, even though the function does not need or use
> > the avctx-
> On Oct 19, 2016, at 8:45 PM, Aman Gupta wrote:
>
> From: Aman Gupta
>
> ff_videotoolbox_avcc_extradata_create() was never being called if
> avctx->extradata_size==0, even though the function does not need or use
> the avctx->extradata.
Could this be a bug in another part of the code? It see
From: Aman Gupta
ff_videotoolbox_avcc_extradata_create() was never being called if
avctx->extradata_size==0, even though the function does not need or use
the avctx->extradata.
This manifested itself only on h264 streams in specific containers, and
only on iOS. I guess the macOS version of Video