From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] VDD conference invitation - Dublin 22-24 Sept 2023 Date: Fri, 8 Sep 2023 12:19:45 -0300 Message-ID: <933017df-99bb-1f69-11fc-4ba48c463b10@gmail.com> (raw) In-Reply-To: <20230908130949.GW8640@pb2> On 9/8/2023 10:09 AM, Michael Niedermayer wrote: > There has been a marked shift of project goals over the years. While long ago FFmpeg > was "all of multimedia". With time the scope of the project has shrunk. > FFserver was removed not improved, not replaced. > the video encoder core we had, which encoded from mpeg1 to mpeg4, msmpeg*, rv* and others > and at the time was the best encoder available (not anymore now, no) but after mpeg4-asp, > modern video encoders where no longer added to ffmpeg. In one case a advanced encoder for a fringe > format was rejected Which encoder was this? Also, people not submitting encoders is beyond our power and has been the case for more than a decade. All important video codecs past mpeg2 (H.264/5, VP8/9, AV1, etc) have never gotten an encoder in lavc. What i would worry the most about is decoders being written in external libs and glued into lavc. Fortunately VVC is not going that way, but others have and still are. > AI based filters are neglegted at a time everything is shifting > to neural networks and AI. Clientside / "in browser" also has become very important but > is absent from our documentation, our fate tests, and so on If there's something that's 100% corporate interest and not a project from multimedia hobbyists, it's AI. _______________________________________________ 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-08 15:19 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-17 17:42 Jean-Baptiste Kempf 2023-08-20 13:01 ` Tomas Härdin 2023-08-20 15:54 ` Jean-Baptiste Kempf 2023-09-08 13:09 ` Michael Niedermayer 2023-09-08 14:53 ` Derek Buitenhuis 2023-09-09 13:58 ` Michael Niedermayer 2023-09-08 15:19 ` James Almer [this message] 2023-09-08 18:27 ` Michael Niedermayer 2023-09-08 15:21 ` Ronald S. Bultje 2023-09-09 16:24 ` Vittorio Giovara 2023-09-08 15:42 ` Rémi Denis-Courmont 2023-09-09 14:31 ` Michael Niedermayer [not found] ` <22ED92D8-8653-434B-8EAB-ECBA451D8E20@cosmin.at> 2023-09-08 17:39 ` Cosmin Stejerean via ffmpeg-devel 2023-09-08 17:43 ` Kieran Kunhya 2023-09-09 7:04 ` Tomas Härdin 2023-09-09 13:53 ` Michael Niedermayer 2023-09-09 19:23 ` Tomas Härdin 2023-09-14 18:25 ` Michael Niedermayer 2023-09-09 14:49 ` Michael Niedermayer
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=933017df-99bb-1f69-11fc-4ba48c463b10@gmail.com \ --to=jamrial@gmail.com \ --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