On 2/15/16, Hendrik Leppkes wrote:
> On Mon, Feb 15, 2016 at 2:23 PM, Ivan Kalvachev
> wrote:
>> Keep the new XVMC pixfmt at the old position.
>> It was moved away to preserve ABI compatibility with the fork.
>>
>> I'm not really sure this one is better,
>> so I'm ok with dropping it if somebody
On Mon, Feb 15, 2016 at 2:23 PM, Ivan Kalvachev wrote:
> Keep the new XVMC pixfmt at the old position.
> It was moved away to preserve ABI compatibility with the fork.
>
> I'm not really sure this one is better,
> so I'm ok with dropping it if somebody objects.
>
> Have in mind, triggering FF_API_
Keep the new XVMC pixfmt at the old position.
It was moved away to preserve ABI compatibility with the fork.
I'm not really sure this one is better,
so I'm ok with dropping it if somebody objects.
Have in mind, triggering FF_API_XVMC will change a lot of AV_PIX_FMT values,
with or without that pa
