From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 7DA784B2B5
	for <ffmpegdev@gitmailbox.com>; Wed,  3 Jul 2024 13:26:08 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C8A2068D972;
	Wed,  3 Jul 2024 16:26:05 +0300 (EEST)
Received: from haasn.dev (haasn.dev [78.46.187.166])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1F06C68D85B
 for <ffmpeg-devel@ffmpeg.org>; Wed,  3 Jul 2024 16:25:59 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=haasn.xyz; s=mail;
 t=1720013158; bh=kmKLwi0Tz+19a4/xLVc18iTQ/43ssJ9gLtdLxVyOcJU=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=R9qMzbgCBvCjuMapniN3MozKy/2NulNCX+ps1lt70oyCc0vHcJvlr4wN23mu2n8vk
 lgfK+l/uNbRbzetzi018Ii3GpkL8rdya8qy+UkLWnfkssW2VNRh333VEr/jAdd2rhw
 3WqA4pPisYnlwDKmcGF7kS1wkQr78LqJGco3a/w0=
Received: from haasn.dev (unknown [10.30.0.2])
 by haasn.dev (Postfix) with ESMTP id C39D141A55
 for <ffmpeg-devel@ffmpeg.org>; Wed,  3 Jul 2024 15:25:58 +0200 (CEST)
Date: Wed, 3 Jul 2024 15:25:58 +0200
Message-ID: <20240703152558.GB29034@haasn.xyz>
From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
In-Reply-To: <20240702152700.GC15496@haasn.xyz>
References: <20240622151334.GD14140@haasn.xyz>
 <20240702152700.GC15496@haasn.xyz>
MIME-Version: 1.0
Content-Disposition: inline
Subject: Re: [FFmpeg-devel] [RFC]] swscale modernization proposal
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/20240703152558.GB29034@haasn.xyz/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On Tue, 02 Jul 2024 15:27:00 +0200 Niklas Haas <ffmpeg@haasn.xyz> wrote:
 
> 1. Is this a good idea, or too confusing / complex to be worth the gain?
>    Specifically, I am worried about confusion arising due to differences
>    in behavior, and implemented options, between all of the above.
> 
>    That said, I think there is a big win to be had from unifying all of
>    the different scaling and/or conversion filters we have in e.g.
>    libavfilter, as well as making it trivial for users of this API to
>    try using e.g. GPU scaling instead of CPU scaling.

After prototyping this approach a bit (using an internal struct
AVScaleBackend), I think I like it. It specifically makes handling
unscaled special converters pretty straightforward, for example - the
"unscaled" backend can be separate from the generic/scaling backend.

We could also trivially plug in something like libyuv, or some other
limited-use-case fast path, without the user really noticing.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".