From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/2] FFmpeg Source plugin experiment
Date: Wed, 7 May 2025 15:39:00 +0200
Message-ID: <20250507133900.GL29660@pb2> (raw)
In-Reply-To: <20250505232710.3840135-1-michael@niedermayer.cc>
[-- Attachment #1.1: Type: text/plain, Size: 1836 bytes --]
On Tue, May 06, 2025 at 01:06:40AM +0200, Michael Niedermayer wrote:
> This patch set will remove libpostproc from FFmpeg
> resulting in a master branch like:
> https://github.com/michaelni/FFmpeg/tree/experiment-sourceplugin-master
>
> matching this, libpostproc can trivially become a source plugin like here:
> https://github.com/michaelni/FFmpeg/tree/experiment-sourceplugin-libpostproc
>
> git merge between the 2 will simply put libpostproc back. Both sides
> can evolve and merge will still work fine. Conflicts would only be
> expected if changes cross each other.
>
> This is in fact so simple its almost hard to believe
>
> Also, I have split out libpostproc in a more conventional style
> here: https://github.com/michaelni/libpostproc
> This also has been updated already once to include changes from
> 5months of changes to the build system, libavutil and fate.
>
> Both aprouches can be compared but so far the source plugin style
> is less work and i expect it to continue to be easier.
>
> The idea of course here is to expand this to filters and other
> things. Which again is trivial, nothing really is needed except
> people simply following this style of a source plugin
>
> What will make source plugins even easier is if the files
> that they touch, like allfilters/allcodecs/Makefile/... would be split
> so conflicts change from rare to impossible.
>
> Note, in case this is applied before 8.0, I do intend to include
> the libpostproc source plugin in the 8.0 release, so as not to
> cause more delays or inconveniences
patchset applied
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Does the universe only have a finite lifespan? No, its going to go on
forever, its just that you wont like living in it. -- Hiranya Peiri
[-- 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".
prev parent reply other threads:[~2025-05-07 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 23:06 Michael Niedermayer
2025-05-05 23:06 ` [FFmpeg-devel] [PATCH 1/2] Remove libpostproc Michael Niedermayer
2025-05-14 0:55 ` Andrew Randrianasulu
2025-05-14 2:54 ` Andrew Randrianasulu
2025-05-14 10:21 ` Michael Niedermayer
2025-05-14 10:41 ` Kieran Kunhya via ffmpeg-devel
2025-05-14 12:26 ` Michael Niedermayer
2025-05-14 13:43 ` Kieran Kunhya via ffmpeg-devel
2025-05-05 23:06 ` [FFmpeg-devel] [PATCH 2/2] tests/fate/filter-video: Fix dependancy for codecview Michael Niedermayer
2025-05-07 13:39 ` Michael Niedermayer [this message]
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=20250507133900.GL29660@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