Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'jpeg xl'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 4 results

  1. It would be great if Serif could add some transparency of the encoders used, versions and the equivalent parameters for the encoder libraries. Give us a scale in the documentation or similar, so we could check with the encoder library to more precisely tune our final output quality. Currently the quality slider exposed in the export interface isn't directly comparable to anything from the encoders used, this makes it difficult to ensure similar quality when exporting across multiple applications. Some background for the request. JPEG XL is supported in Affinity 2, but nowhere is it documented what library, which version, what effort settings or what quality/distance equivalent the quality slider in AFP corresponds to. This information could be hugely useful when more precise control of final output quality is desired, and not only for JPEG XL but all export formats supported. *There's no third-party notice for anything to do with JPEG XL.
  2. Hi everyone and Serif. I have a few questions and wishes, and I believe they’re very relevant now that MacOS will get official JPEG XL support. 1. Is it known how Affinity implements JPEG XL? I believe it would be with libjxl, but I can’t find any references to it in the software. If it is libjxl, I believe from browsing the official JXL Discord, which have official developers and the head developer active, that Affinity might’ve implemented libjxl wrong when it comes to export; reference here. Affinity might use an out-of-date version too, as files can be quite inflated in size versus using the newest release of libjxl. Hopefully it’s a priority to keep the library up to date, as the encoder quickly grows more efficient. 2. Once dependencies are updated and improved, if libjxl is used, could we get more direct options exposed? Currently it’s difficult to know what the slider does, I guess it exposes —quality but a certain answer would be great. WebP has more export options in the dialog so it seems possible. To end, thank you for implementing JPEG XL.
  3. JPEG XL export consistently crashes with transparent background exports in the latest release 2.0.4 and on the beta 2.1.0.1742 on Windows 10.0.19045. Steps to reproduce 1. Create a new document with a transparent background 2. Add a rectangle 3. Go to File > Export ... 4. Use these settings: 5. Using high Quality settings you'll see the export fail or the file crash with the export dialog loading 6. Best quality apparently immediately hard crashes the app as well from the export dialog, since that was the version I last used, I can't show my settings for export.
  4. There's been a few threads on these forums about JXL but no real feedback from Serif on their plans other than an answer that it might happen some day. I really do think Serif should consider JXL seriously and be a first mover in regards to this format. The reasons for supporting JPEG XL is many, a new actually great format for >8bit final export, possibility of lossless quality, transparent conversion to JPEG for compatibility, better compression and more. Some sources: source 1, source 2. The reason I think Serif should be a first mover in regards to this format is that no new format will ever get the chance at dethroning JPEG from it's role if nobody ever implements it in their software. Browsers do support JPEG XL (JXL) but the enablement is hidden behind browser flags currently, partly because nothing else supports JPEG XL at this time.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.