From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] SDR lib comments Date: Fri, 29 Sep 2023 00:58:44 +0200 Message-ID: <20230928225844.GB3543730@pb2> (raw) In-Reply-To: <CABLWnS8Qd88UrwU+byAJ4ARgApMZ3KvuEvPSR2QKpNxxJm33nQ@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2471 bytes --] On Thu, Sep 28, 2023 at 05:07:17PM -0400, Vittorio Giovara wrote: > On Thu, Sep 28, 2023 at 3:28 PM Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > 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 ? > > > > making sure that the library builds on all supported system, doesn't have > security holes, etc is it failing to build ? i would expect if it fails to build to be contacted about that. Or well if not that people would not expect it to be fixed by me. are there security holes ? If so i would expect them to be reported to ffmpeg-security or me or something like that. > or for packagers to bundle the library > > > > libpostproc implements part of ISO/IEC 14496-2 > > (that is the spec for an MPEG-4 ASP decoder) > > > > We're going a bit off topic, but you're referring to something preceding > H264 which means is something older than 20 years -- while old formats > surely need to be supported against digital obsolescence, the > code:functionality ratio is certainly not worth it (who uses ASP > nowadays?), There is substantial amounts of existing material in ASP [...] > > > > 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 > > > > I think the main reason libpostproc was mentioned is that we don't want a > repeat of the history for SDR - so far you're only developer expressing SDR currently is completely self contained in a input device/demuxer. Thats the very opposite of libpostproc which is a bit of video filtering a bit of mpeg4 ASP and neither in libavfilter (which did not exist when libpostproc was created) nor libavcodec The main obstacle to cleanup libpostproc is probably the old style interleaved SIMD code. Again this has no parallel to SDR thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-28 22:58 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 [this message] 2023-09-29 9:43 ` Anton Khirnov 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=20230928225844.GB3543730@pb2 \ --to=michael@niedermayer.cc \ --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