Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] ipfsgateway: Remove default gateway
Date: Thu, 25 Aug 2022 15:57:28 +0200
Message-ID: <20220825135728.GV2088045@pb2> (raw)
In-Reply-To: <CAK+ULv6rkqUAeZGe044JBA=wCxN9YiCrhzp_RUWPPUWw_saHVA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3504 bytes --]

On Wed, Aug 24, 2022 at 10:18:04PM +0100, Kieran Kunhya wrote:
> >
> > for libxml2 these problems are less likely to hit us as we likely never
> > need a
> > "new xml feature" but for a (de)muxer we quite likely will need the
> > latests version on every platform.
> > Also we have regression tests, external libs make that impossible
> > as the version of external libs can change the behavior. Again this
> > is a issue for mxf maybe less so libxml. You can also see that we have no
> > tests involving  any of the external encoder libs, for that very reason.
> > With each external lib that is needed for core features this would
> > become a quickly growing problem
> >
> >
> 
> Going back to technical arguments instead of utopian pipedreams (replacing
> YouTube and Tiktok lol). 

Well, who would have dreamt that humans will be able to fly ?
Maybe if the worlds best engineers and scientists and alot of capital was used
That where the Wright brothers, no actually it was not. The smartest people
with most degrees and alot of governemnt funding was a competing team that
i dont even remember the name of. The Wright Brothers had no degrees and
funded their stuff from the revenue of their bicycle shop

Or maybe create a free OS. That linux pipedream
Or maybe reverse engeneering all codecs and writing free implementations?
You know many of the people who did that yourself. Another pipedream

Or editing the human genome maybe, you know when you start with a single
celled embryo you can, wait no. There actually are a few people who had
the majority of their liver cells gen-edited in vivo as adults long after
their birth, to treat a rare desease called ATTR amyloidosis

...

Now maybe it will always stay a pipedream that all the evil sozial media
and communication platforms get replaced by privacy preserving, free speech
respecting, non adverziser controlled things. Quite possible, even quite likely
Then again maybe someone, maybe Elon Musk with twitter will take a bite
out of these giants. I have no clue.
My point was just that this sort of stuff would fit into FFmpegs mission
if somone wanted to do it. Its something id be happy to support.


> You will never fit all the features of complex
> containers like MXF, MP4, TS (and for argument's sake XML) inside a
> generalised framework like FFmpeg.

Maybe true but the reason is not that it cant be dont just that there are
features noone uses and noone needs.
I do know some video codec specs and there are bizare things in them that
arent worth the paper they are written on.
The features that are used or that people need, we must support IMO.


> 
> Likewise with dav1d, we have seen that an external lib has allowed them to
> introduced new paradigms such as mixed frame and sliced threads without
> having to redo the whole framework of dozens of codecs. There is value to
> this. There are also a lot of modern codec features which aren't easily
> fittable into FFmpeg such as dependent substreams.

The framework has, will and must evolve. Theres alot thats different between
FFmpeg 10 years ago and today.
External libs wont fix that btw. If the framework doesnt handle feature X
then it also doesnt with an external lib. User apps using the framework have
the problem both ways.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are best at talking, realize last or never when they are wrong.

[-- 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".

  reply	other threads:[~2022-08-25 13:57 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 22:27 Derek Buitenhuis
2022-08-11 12:08 ` Timo Rothenpieler
2022-08-11 16:26   ` Mark Gaiser
2022-08-11 16:49     ` Timo Rothenpieler
2022-08-11 17:21       ` Mark Gaiser
2022-08-11 17:35         ` Timo Rothenpieler
2022-08-11 17:56           ` Mark Gaiser
2022-08-11 19:18             ` Derek Buitenhuis
2022-08-11 20:18             ` Michael Niedermayer
2022-08-11 22:03               ` Timo Rothenpieler
2022-08-11 22:51                 ` Derek Buitenhuis
2022-08-12 13:43                   ` Mark Gaiser
2022-08-12 14:22                   ` Vittorio Giovara
2022-08-12 14:30                     ` Kieran Kunhya
2022-08-12 14:34                       ` Mark Gaiser
2022-08-12 14:45                         ` Kieran Kunhya
2022-08-12 14:48                         ` Derek Buitenhuis
2022-08-12 14:50                           ` Kieran Kunhya
2022-08-12 14:55                   ` Nicolas George
2022-08-12 15:05                 ` Michael Niedermayer
2022-08-12 17:01                   ` Nicolas George
2022-08-12 17:18                     ` Michael Niedermayer
2022-08-12 17:21                       ` Timo Rothenpieler
2022-08-13 16:29                         ` Michael Niedermayer
2022-08-13 19:06                           ` Timo Rothenpieler
2022-08-14 18:00                             ` Michael Niedermayer
2022-08-15 14:09                           ` Nicolas George
2022-08-15 14:27                             ` Jean-Baptiste Kempf
2022-08-17 15:03           ` Tomas Härdin
2022-08-18 14:31             ` Michael Niedermayer
2022-08-19  9:15               ` Tomas Härdin
2022-08-19 12:52                 ` Mark Gaiser
2022-08-22  9:12                   ` Tomas Härdin
2022-08-22 12:52                     ` Nicolas George
2022-08-23 12:53                       ` Ronald S. Bultje
2022-08-23 12:55                         ` Nicolas George
2022-08-24 16:35                       ` Tomas Härdin
2022-08-24 20:54                         ` Michael Niedermayer
2022-08-27  7:05                           ` Tomas Härdin
2022-08-28 14:14                             ` Michael Niedermayer
2022-08-24 21:03                         ` Michael Niedermayer
2022-08-24 21:18                           ` Kieran Kunhya
2022-08-25 13:57                             ` Michael Niedermayer [this message]
2022-08-25 14:41                               ` Kieran Kunhya
2022-08-27  7:29                           ` Tomas Härdin
2022-08-27  7:53                             ` Paul B Mahol
2022-08-27 11:30                               ` Tomas Härdin
2022-08-27 17:34                                 ` Baptiste Coudurier
2022-08-28 11:49                                   ` Tomas Härdin
2022-08-15 17:53 ` Michael Niedermayer
2022-08-15 19:35 ` Derek Buitenhuis
2022-08-15 19:37   ` James Almer
2022-08-15 21:47   ` Michael Niedermayer
2022-08-15 21:57     ` Nicolas George
2022-08-15 23:53       ` Mark Gaiser
2022-08-16 14:46     ` Michael Niedermayer
2022-08-14 13:24 thelostone123

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=20220825135728.GV2088045@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