Quoting Soft Works (2022-02-09 07:19:23)
>
> Sure. Don't understand my reply as an objection I don't even know what
> xvmc is (or was). I rather see the burden and effort that it takes
> to retain all those compatibility paths and at the same time how it
> is blocking innovation and progress.
>
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Anton Khirnov
> Sent: Wednesday, February 9, 2022 6:49 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/mpeg*: drop the XvMC
> hwacce
Quoting Soft Works (2022-02-08 22:34:42)
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Anton Khirnov
> > Sent: Tuesday, February 8, 2022 10:37 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> &
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Anton Khirnov
> Sent: Tuesday, February 8, 2022 10:37 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/mpeg*: drop the XvMC
> hwacce
Quoting Andreas Rheinhardt (2022-02-07 02:46:08)
> I thought that removing components is only possible at a major version
> bump. Am I wrong?
AFAIK we provide no API guarantees for specific components being
available.
--
Anton Khirnov
___
ffmpeg-devel
Quoting Soft Works (2022-02-07 03:18:54)
> I sometimes wonder whether there exists a single API user who
> really understands this (very special) kind of logic and
> would make decisions based on that understanding.
>
> When it's not even fully understood internally, how should it
> be understood
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Monday, February 7, 2022 2:53 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/mpeg*: drop the XvMC
> hwaccel code
>
> On 2/6/2022 10:46 PM, Andreas
On 2/6/2022 10:46 PM, Andreas Rheinhardt wrote:
Anton Khirnov:
XvMC was last relevant over 10 years ago, if ever. There is no reason to
use it today.
---
MAINTAINERS| 1 -
configure | 9 -
libavcodec/Makefile| 2 -
Anton Khirnov:
> XvMC was last relevant over 10 years ago, if ever. There is no reason to
> use it today.
> ---
> MAINTAINERS| 1 -
> configure | 9 -
> libavcodec/Makefile| 2 -
> libavcodec/avcodec.h | 12 --
>
XvMC was last relevant over 10 years ago, if ever. There is no reason to
use it today.
---
MAINTAINERS| 1 -
configure | 9 -
libavcodec/Makefile| 2 -
libavcodec/avcodec.h | 12 --
libavcodec/error_resilience.c | 9 -
10 matches
Mail list logo
