From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] SDR lib comments
Date: Fri, 29 Sep 2023 11:43:36 +0200
Message-ID: <169598061616.6638.4682492428133822842@lain.khirnov.net> (raw)
In-Reply-To: <20230928192835.GZ3543730@pb2>
Quoting Michael Niedermayer (2023-09-28 21:28:35)
> On Thu, Sep 28, 2023 at 12:28:22PM +0200, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2023-09-23 18:43:44)
> > > Is a seperate library really the right choice for SDR in FFmpeg at this stage ?
> > >
> > > Also code can always be moved into an seperate library
> >
> > we've had postproc in the tree for ages, nobody maintains it or
> > cares about it, yet it seems impossible to get rid of it.
>
> what maintaince does it need ?
> i mean i know the code is ugly but what _needs_ to be changed?
>
> libpostproc implements part of ISO/IEC 14496-2
> (that is the spec for an MPEG-4 ASP decoder)
>
> its content could be moved in libavfilter and or the mpeg4 decoder
> (there are arguments to be made for either)
> but it doesnt belong in a lib external to FFmpeg.
> (and in the process some bits probably can be droped as they
> no longer serve a purpose compared to other filters)
>
> I have too many other things to work on to do a big refactoring of it
> but if there are small bugs in it or questions about it i can look into them
The main problem I see with it is that it is a world unto itself. It
barely interacts with the rest of the project, its APIs use a different
style from everything else, etc.
What does anybody gain from it being in our source tree, as opposed to a
separate library?
--
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-09-29 9:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:43 Michael Niedermayer
2023-09-28 10:28 ` Anton Khirnov
2023-09-28 19:28 ` Michael Niedermayer
2023-09-28 21:05 ` Rémi Denis-Courmont
2023-09-28 22:18 ` Michael Niedermayer
2023-09-29 7:03 ` Nicolas George
2023-09-29 8:23 ` Rémi Denis-Courmont
2023-10-02 10:08 ` Nicolas George
2023-09-29 8:34 ` Rémi Denis-Courmont
2023-10-02 10:06 ` Nicolas George
2023-09-29 12:59 ` Vittorio Giovara
2023-10-02 10:05 ` Nicolas George
2023-09-28 21:07 ` Vittorio Giovara
2023-09-28 22:58 ` Michael Niedermayer
2023-09-29 9:43 ` Anton Khirnov [this message]
2023-09-29 11:43 ` Nicolas George
2023-09-29 13:29 ` Rémi Denis-Courmont
2023-09-29 13:53 ` Nicolas George
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=169598061616.6638.4682492428133822842@lain.khirnov.net \
--to=anton@khirnov.net \
--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