From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Cosmin Stejerean <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] SWS cleanup / SPI Funding Suggestion
Date: Sat, 14 Oct 2023 19:26:37 +0200
Message-ID: <169730439704.32606.15686810952593488392@lain.khirnov.net> (raw)
In-Reply-To: <CAK+ULv6LUUESw6eCygmum8+vHzoejXiogfiMaOH512HScrE6Fg@mail.gmail.com>
Quoting Kieran Kunhya (2023-10-14 16:19:49)
> On Sat, 14 Oct 2023 at 00:17, Cosmin Stejerean via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> >
> >
> > > On Oct 13, 2023, at 4:00 PM, Vittorio Giovara <
> > vittorio.giovara@gmail.com> wrote:
> > >
> > > TBF this is in part why i was suggesting a new library - I feel like sws
> > is
> > > affected by bad brading because of these caching issues and imprecise
> > > conversion, and a new clean api in a new library would make a lot of
> > sense
> > > in my opinion.
> >
> > I think the branding issue would solve itself in short order if the actual
> > implementation of swscale started to be good. My concern with adding a new
> > library is that we'd end up in a situation where we have both swscale and a
> > new library side by side for some extended period of time.
> >
> > By comparison adding cleaner APIs to swscale and then slowly strangling
> > the old APIs (along the lines of Niklas' proposal) would allow for a more
> > gradual transition that has a higher likelihood of success compared to a
> > full rewrite IMO.
> >
>
> The issue is not the API, the issue is that swscale is astonishingly
> complex and difficult to understand internally, there are lots of different
> codepaths and randomly you'll end up with a buggy or slow one and have no
> idea how to fix it.
>
> It's probably easier to start from scratch than to try and understand and
> then fix swscale (years of work).
I've seen more than one attempt to do that over the years, all failed.
While I do agree that sws code is atrociously bad, I think that
* an attempt to reinvent it from scratch is quite likely to fail and
produce nothing of value
* sws can be incrementally improved
--
Anton Khirnov
_______________________________________________
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".
next prev parent reply other threads:[~2023-10-14 17:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 19:19 Michael Niedermayer
2023-10-13 20:30 ` Vittorio Giovara
2023-10-13 21:23 ` Lynne
2023-10-13 22:02 ` Michael Niedermayer
2023-10-13 22:34 ` Niklas Haas
2023-10-13 22:42 ` James Almer
2023-10-13 22:54 ` Niklas Haas
2023-10-13 23:00 ` Vittorio Giovara
[not found] ` <8A960BE2-8364-4AF8-A9B5-E0551C19F9DF@cosmin.at>
2023-10-13 23:16 ` Cosmin Stejerean via ffmpeg-devel
2023-10-14 14:19 ` Kieran Kunhya
2023-10-14 17:00 ` Michael Niedermayer
2023-10-14 17:24 ` Niklas Haas
2023-10-15 14:36 ` Michael Niedermayer
2023-10-14 17:41 ` Kieran Kunhya
2023-10-14 19:38 ` Vittorio Giovara
2023-10-14 17:26 ` Anton Khirnov [this message]
2023-10-14 15:45 ` Michael Niedermayer
2023-10-14 17:53 ` Stefano Sabatini
2023-10-17 14:36 ` Michael Niedermayer
[not found] ` <430D0C5B-53A8-4920-B99A-D8BAD816D715@cosmin.at>
2023-10-17 16:58 ` Cosmin Stejerean via ffmpeg-devel
2023-10-18 21:53 ` Stefano Sabatini
2023-10-17 18:33 ` James Almer
2023-10-17 18:50 ` Rémi Denis-Courmont
2023-10-17 21:57 ` Michael Niedermayer
2023-10-17 22:10 ` Michael Niedermayer
2023-10-18 16:30 ` Rémi Denis-Courmont
2023-10-18 22:12 ` Stefano Sabatini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169730439704.32606.15686810952593488392@lain.khirnov.net \
--to=anton@khirnov.net \
--cc=cosmin@cosmin.at \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git