Replies: 1 comment 1 reply
-
The encoder of jxl is not that fast so you probably will need to wait a bit longer. And on the @ImageMagick side we had to disable code optimizations due to an issue with VisualStudi deadlocking when building the current code. That is probably causing this slowdown. When the next version of libjxl is released we can check if we can enable the compiler optimizations again. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Magick.NET version
Current
Environment (Operating system, version and so on)
Win10, VS2022, Magick.NET-Q8-AnyCPU
Description
Hi there,
are there any known issuses regarding JXL? Im trying to load a JXL image with the latest version and it takes about 6s to load these image using the constructor.
I figured out that if i downgrade Magick.NET-Q8-AnyCPU and Magick.NET.Core to v9.1.2, the same image takes about 200ms to load.
Also i'm not able to load a jpg and write it back to disk as jxl. The write function just freezes and don't came back.
Thanks for your help.
Steps to Reproduce
var i = new MagickImage(pathToJXLFile); -> took 6s
var j = new MagickImage(pathToJPG);
j.Write("C:\Temp\image1.jxl",MagickFormat.Jxl); -> freezes without exception
Beta Was this translation helpful? Give feedback.
All reactions