-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: support JPEG decoding #4
Comments
Any idea, how much extra code would it take to actually implement this (how much / which parts of code can be reused)? |
The only thing I know is what Jon Sneyers said. "I want to point out that potentially a JPEG XL decoder could also be used as a JPEG decoder (libjxl currently doesn't do that yet, but it does contain all the code needed to do that), which means the dependency that browsers have on libjpeg-turbo could potentially be dropped." |
Also, if you compare flowchats in slide 20 and 21 it kinda tells you which parts of the code can be reused. |
JPEG provides subset of JPEG XL features (basically it's VarDCT image with only DCT8 varblocks and without fancy image features), so if jxl-oxide could read JPEG bitstream it would be able to reuse most of the rendering code. I'm going to focus on properly implementing JPEG XL features, so rendering JPEG images is in somewhat low priority. It would be very nice to support JPEG decoding though! |
Support JPEG decoding to easily replace libjpeg-turbo and MozJPEG on browsers.
The text was updated successfully, but these errors were encountered: