From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] VDD conference invitation - Dublin 22-24 Sept 2023
Date: Fri, 8 Sep 2023 15:09:49 +0200
Message-ID: <20230908130949.GW8640@pb2> (raw)
In-Reply-To: <05e2d1c7-956b-4ce5-a1a2-69e83ae484ab@betaapp.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1560 bytes --]
On Thu, Aug 17, 2023 at 07:42:17PM +0200, Jean-Baptiste Kempf wrote:
[...]
> Propose a talk, from 5min to 30min.
As i will not be at the conference, here are some quick words
In the past, most developers in FFmpeg where primarly FFmpeg developers. But as FFmpeg is
used by almost everyone now, that has changed and many developers in FFmpeg today are
primarly developer of 3rd party projects using FFmpeg.
Should decissions in FFmpeg be made to maximize benefit / be optimal for FFmpeg ?
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. 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
Whats the scope of FFmpeg ?
And is this direction that is taken optimal for FFmpeg, and what people want ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Elect your leaders based on what they did after the last election, not
based on what they say before an election.
[-- 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-08 13:10 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 [this message]
2023-09-08 14:53 ` Derek Buitenhuis
2023-09-09 13:58 ` Michael Niedermayer
2023-09-08 15:19 ` James Almer
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=20230908130949.GW8640@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