Still developing this?

[TPS]

@cocoon I haven't seen any development in this project in a long time. JxL has come a very long way since the last commit here, & this fulfills a huge need in its acceptance. Will you be continuing?

[cocoon]

Hi thanks for your question.

I had done some work to adjust the changed arguments and some more fixes and because of your question I updated some components today.

So it should now work with 0.8 if you extract the files from this archive (or use own ones) to the program folder:
https://github.com/libjxl/libjxl/releases/download/v0.8.0/jxl-x64-windows-static.zip

When compiling make sure that the file "Magick.Native-Q16-HDRI-OpenMP-x64.dll" ends up in the program folder.
For some reason it didn't get copied everytime for me and then you can't see any image in the window.

I did not plan to really work more on it, it was more an proof of concept.
In private I created a program that sends (multiple) jobs to an agent to process multiple files / directories based on this.

I wanted to have it ready when JPEG-XL is widely available and integrated into OS ... but that took longer than I expected and still is not there (Windows/Andorid) and got removed from browsers.

[TPS]

JxL's still the best I've found for my uses (general-purpose pic archiving), but the command-line is often too much.

Thanks for updating! 🙇🏾‍♂️

[TPS]

Would you mind releasing a binary? I'm no developer, & it's pretty daunting to try.

[cocoon]

So after long time, I at least added a GitHub action to let it compile and upload artifacts.

You can even fork it yourself and just trigger it.

Currently binaries are here:
https://github.com/cocoon/jxl.Net/actions/runs/11015926800#artifacts

I have not changed anything or looked if there are new changes regarding jpeg-xl parameters.

Back when I started all this I was thinking, if I should even upload this POC, as I was expecting that in some days or weeks a fully managed implementation would arrive.

Google now wants to use "Jpegli".