/g/ - Technology

Technology and shit

[X]

Mark sensitive


File: JPEG_XL.png (25.39 KB)
JPEG XL support Anonymous 08/12/21(Thu)03:56:49 No. fg-3T1IXMQU [Report]

Can JPEG XL be enabled now that even current ungoogled-chrome has support for it built-in ( chrome://flags/#enable-jxl)? Supported browsers: https://www.caniuse.com/jpegxl

>>
Anonymous 08/12/21(Thu)18:31:46 No. fg-6M6I8V3O [Report] >>fg-Y9G28HRA

>>fg-3T1IXMQU (OP) Hijacking this thread to mention that posting webp images doesn't work

>>
Anonymous 08/13/21(Fri)03:44:36 No. fg-Y9G28HRA [Report]

>>fg-6M6I8V3O Can also confirm that webp doesn't work either.

>>
File JPEG_XL.png (25.39 KB)
JPEG XL support Anonymous 08/13/21(Fri)03:46:26 No. fmeta-PKFHXX98 [Report] >>fmeta-EZYM1QCK >>fmeta-QGEQOID2 >>fmeta-H2QPKXME >>fmeta-P8NJX1KC

Can JPEG XL be enabled now that even current ungoogled-chrome has support for it built-in ( chrome://flags/#enable-jxl)? Supported browsers: https://www.caniuse.com/jpegxl Also requested was webp, posted this on /g/ before I saw meta >>fg-3T1IXMQU (OP)

>>
Anonymous 08/17/21(Tue)21:24:27 No. fg-RT5KQNKG [Report] >>fg-F4X08QL1

>>fg-3T1IXMQU (OP) What is this "JPEG Xl"?

>>
Anonymous 08/17/21(Tue)22:35:06 No. fg-F4X08QL1 [Report] >>fg-HUQ35XWJ

>>fg-RT5KQNKG The most efficient image format that is practical to use. This was ~2MB as PNG, now it's ~1MB as JXL. Lossless: https://files.shittyurl.org/z4izory7.jxl If you haven't JXL support enabled in your browser yet, download and feed it into https://squoosh.app/ instead. But if fchan allowed the format, we could directly shitpost with jxl.

>>
File download.jxl (0.04 KB)
Anonymous #Usagi 09/21/21(Tue)11:20:17 No. fg-JHM2HAKU [Report]

>>fg-3T1IXMQU (OP) JPEG-XL

>>
File Screenshot_20210923_032355.png (23.44 KB)
Anonymous 09/23/21(Thu)10:26:33 No. fg-HUQ35XWJ [Report]

>>fg-F4X08QL1 avif in real world usage offers better compression ratios compared to jxl, even if the avif encoder is slow as balls. in overall usage (as well as niche professional use cases) id still give jxl the win considering that the encoder is much faster. but for the benefit it offers to people who need to encode, jxl is unduly cuntish to passive consumers who must decode images. i have a massive booru collection ive encoded to both avif and jxl formats, but decoding jxl is more taxing than avif to the extent that dolphin (which i assume is doing something stupid like regenerating thumbnails) spikes the cpu usage to 100 each time the jxl folder is opened, but not on the avif folder. i havent rigorously tested or compared the time it takes to open images in gwenview (its usually negligible for both avif and jxl) but on the really high resolution images it sadly takes many seconds to decode the image (both on avif and jxl) when png or jpg is almost instantaneous. ymmv, im on a core2duo so something made in the last decade may have better results


[Post a Reply] 7 / 3

[Home] [Rules] [FAQ]

All trademarks and copyrights on this page are owned by their respective parties.

Theme: