Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#76643 - [ffmpeg] jxl screenshot support for mpv

Attached to Project: Arch Linux
Opened by raine (raine) - Tuesday, 22 November 2022, 19:16 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 25 November 2022, 16:59 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No



The recently released mpv 0.35 supports saving screenshots as JXL. On Arch Linux, this is currently not functioning due to ffmpeg being built without libjxl support (despite many other applications support viewing JXL files on Arch Linux).

Flipping on the JXL support in ffmpeg was flat-out rejected by Maxime Gauduin in, in which he promptly closed the issue as Won't Fix, with the justification that "ffmpeg is bloated enough already", and "Even jxl screenshots is a non issue, just save your screenshot as png then convert it to jxl using one of the above." By this logic, ffmpeg should be built with png support only, and all other image formats should be disabled, but it is not the case, and JPEG XL is singled out without a real justification.

After that, another issue appeared which was promptly closed as the duplicated of the previous issue, even though it is closed. It appears all issues are being hammered down aggressively, and this ticket may also meet it's demise similarly. Why?

This push-back against JPEG XL mirrors the recent push-pack from a select group of Chrome developers

JPEG XL is a promising image format with significant benefits and is supported by Qt and GTK (via gdk-pixbuf2) applications in Arch Linux already.
I'm asking other package maintainers to please consider flipping on the JXL support in ffmpeg and mpv.

JPEG XL is already supported in Qt and GTK ecosystems, and other distributions will eventually adopt it for packages that support it, including ffmpeg. This shouldn't be a Won't Fix.

I would be more than happy to submit patches to turn the support on in ffmpeg.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Friday, 25 November 2022, 16:59 GMT
Reason for closing:  Won't implement
Comment by raine (raine) - Tuesday, 22 November 2022, 20:45 GMT
I'd like to add that based on what I'm seeing in the ffmpeg-full on AUR, this is as simple as adding --enable-libjxl in the PKGBUILD, and libjxl to depends.

There is virtually no additional burden on the package maintainer, and having libjxl as a dependency shouldn't be out of question as it is already used by all the major desktop environments.

I found two more issues that got *closed* with the same zeal:

I reiterate that I am more than happy to provide the patch needed to turn on the JXL support in ffmpeg, and also would be happy to step up as a package maintainer as well if Maxime Gauduin thinks it is too much work for him. (Also, his argument with using png for screenshots as a workaround is faulty: writing as PNG is VERY slow for 4K, 6K and 8K videos causing significant stutter, not to mention all the extra disk writes using up the precious write cycles on SSDs to write huge PNG files before converting to JXL with an external tool). Given all the arguments for JPEG XL by Jon Sneyers and the extent of support for JXL that already ships with Arch Linux today, this should not be a "Won't Implement".

(For the package manager, there isn't anything to "implement" anyway. Whether ffmpeg and mpv should support JXL or not was already decided by the upstream, and they already wrote the implementation for this.)
Comment by Toolybird (Toolybird) - Wednesday, 23 November 2022, 07:48 GMT
@Alucryd, this request is likely to keep on popping up. Is reconsideration possible? Fully understand if you're not interested...and if so, please *smash* it closed.

 FS#75830   FS#75982   FS#76106   FS#76277 
Comment by Maxime Gauduin (Alucryd) - Friday, 25 November 2022, 16:59 GMT
I still have no interest in added yet another image format to what is primarily a video and audio tool. ImageMagick and vips exist for a reason. Also I couldn't care less what the chrome developers think, if anything their rejection of the format would instead make me want to adopt it, so please don't draw any misguided conclusion here.

Here are some more reasons for you:
- libjxl is in [community], I'm not bringing and maintaining that package and all its dependencies in [extra]
- depending on libjxl brings 47.6MB of additional dependencies
- there's ffmpeg-full, aka ffmpeg-bloatfest in AUR