John Cupitt
It looks like we must only call `g_mutex_clear()` once, so it should be called from `_finalize()`, not from `_dispose()` :(
Yes, I saw that haha. Safe, but a little ugly.
I've not revised jxlload or added more than four channel support, but let's try to merge, this PR has taken far too long. We can do another round of work...
Phew! Thanks for the review!
Hello @euzada, Did you try the official win binary? It should include `jxlsave`. https://github.com/libvips/build-win64-mxe/releases/tag/v8.15.2 You need 8.15.2 w64 all.
Oh, strange, let me try here.
I tried on a win10 VM and it seems to work: ``` jcupi@DESKTOP-HGI6HBR MINGW64 /f/Pictures $ ../vips-dev-8.15/bin/vips.exe copy DL-742.png x.jxl jcupi@DESKTOP-HGI6HBR MINGW64 /f/Pictures $ ../vips-dev-8.15/bin/vips.exe --version vips-8.15.0 ``` And the...
Could it be running out of memory? Until very recently, libjxl could use HUGE amounts of ram for larger images. vipsdisp 3.0.4 for win is built against a recent libjxl....
I tried making a JXL image with libjxl 0.7: ``` $ /usr/bin/time -f %M:%e vips replicate nina.jpg x.jxl 2 3 10983132:22.56 ``` That's 11gb of memory for a 12k x...
Hello @Rasaa84, You could maybe do: ```python image == 127 ``` Now the image will have 255 in every position which had the value 127 and 0 elsewhere, so you...