[Libav-user] [FFmpeg-user] "Competitors" or do we want to stay alive?

Gonzalo Garramuño ggarra13 at gmail.com
Thu Jun 19 17:37:49 EEST 2025


Your title for the message is kind of scary but...

El 4/4/25 a las 09:58, Paul B Mahol escribió:
>
>
> On Fri, Apr 4, 2025 at 10:06 AM Andrew Randrianasulu 
> <randrianasulu at gmail.com> wrote:
>
>     Sorry for being frustrated lately.
>
>     Realities of all this "modern development" vs me tend to be not in
>     favor of
>     our project.
>
>     I looked up two "other" projects in video editing.
>
>     MLT is well-known and going on for nearly two decades.
>
>     In this year release notes we see:
>
>     https://github.com/mltframework/mlt/releases
>
>
>     =====
>
>     https://github.com/mltframework/mlt/releases/tag/v7.30.0
>
>
>     Added support for mlt_image_yuv420p10, mlt_image_yuv444p10, and
>     mlt_image_yuv422p16 in avfilter, swscale, and rescale filters.
>     This facilitates using these pixel formats end-to-end when using only
>     FFmpeg producers, certain avfilters, and avformat consumer. This
>     means it
>     is possible to do 10-bit end-to-end on the CPU when being careful
>     to select
>     compatible components and options to avoid conversions. One can
>     pass-through HDR; however, you must set the color_trc and pix_fmt
>     properties on the avformat consumer (see ffmpeg -h full for these
>     values).
>     The avformat consumer automatically converts MLT colorspace
>     (integer value)
>     to FFmpeg's colorspace and color_primaries (unless explicit) options.
>
>     ====
>
>     I take this as "floating point pipeline still not here".
>
>     Olive branch is even more depressing:
>
>     https://github.com/olive-editor/olive/issues
>
>     Last non-CI commit was in ... september 2023?
>
>     May be developing moved somewhere, but this mean all exiting new
>     bugs and
>     state of being incomplete for  few more years, given that even
>     with most of
>     hard work done by OpenGL, OCIO, ffmpeg etc remaining NLE core is
>     not that
>     simple, as it turned out to be.
>
>     Natron does not do audio, as far as I know, and also hanging on a
>     thread
>     (single developer).
>
>     Blender is a Big Shot now, with predictably big requirements both in
>     software (try to build it on Slackware) and in hardware. Driven by
>     higher
>     end!
>
>     And whole "Oh lol X is deprecated, everyone rewrite themselves to
>     Wayland"
>     push. I bet there might be way to resistance say Intel's or Nvidia
>     "HDR on
>     X" proposals in Xwayland but who will do all this work for single
>     application? 
>
I did and so did Blender.  Both probably with the help of AI in less 
than 3 months.

>     It took Valve's money effectively to get anything at all done
>     in this area.
>
>     https://www.phoronix.com/news/X11-DeepColor-Visual-RFC
>
>     from 2017 ....
>
>     https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.html
>
>     It took whole 8 years to get into "usable in mpv" state, and producing
>     video usually have higher demands than playing back.
>
>     I am fairly sure someone will write something in Rust (so it will
>     break in
>     6 months time because Rust is for Big D Developers who have no
>     problems
>     with such churn) or c++ 25 because c+11 is too archaic and all new
>     courses
>     are about $latest (double meaning of $ here).
>
>     Again, I do not think this is only individual developers fault,
>     just more
>     complex issue with constant stream of *new*  hardware we supposed
>     to fix in
>     field by writing software, somehow (HDR displays are all or
>     nothing, so
>     HD(R), SD and GUI all must be mixed on host side). And general
>     "culture" of
>     individualism (because Silicon Valley, bebe!)  and effectively social
>     darwinism (where are XDTV and libquicktime? killed by constant API
>     churn
>     ....).
>
>     I see no escape from this, at larger scale. And this makes me even
>     more
>     frustrated.
>
>     cc ffmpeg-user/libav user because otherwise no one from "outside"
>     will ever
>     read this.
>
>
> I think you should use this: https://github.com/richardpl/lavfi-preview
>
> It is fast and small, and make work done. No monthly subscriptions, no 
> trials, no usb dongle needed.

Thanks Paul.  It  is nice to see you share your immense knowledge for a 
change.  Read the book "Pay it forward" (don't watch its movie 
adaptation which is horrible).  It is so far the best idea I've heard 
about how to make the world a better place.

P.S.
I assume Google did their first wrong move with me: all my emails from 
libavuser got removed.  If it was not Google and I got (deservedly) 
banned from ffmpeg or libavuser, please let me know.  Funny enough I 
*did* get this (last?) email.

-- 

Gonzalo Garramuño
ggarra13 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ffmpeg.org/pipermail/libav-user/attachments/20250619/2c7cf699/attachment.htm>


More information about the Libav-user mailing list