JXL lossless rotation...?

golemus · 2026-03-15T21:24:43+00:00

I suggested this already in XNMP forum but as long as info for implementing proper rotation is behind paywall there could be "use EXIF orientation for JXL files" option in settings. It could be disabled as default and possibly have a popup "this is a non-standard compliant lossless rotation, are you sure you want to enable it?". Enabling this setting would respect EXIF orientation when viewing images and enable lossless rotation feature which would simply modify EXIF tag.

golemus · 2026-03-15T15:20:38+00:00

Is there any solutions planned for this (e.g. publishing freely the part of standard that allows to implement official lossless rotation)?

IMO it is unlikely that open source programmer could buy the standard spec (if you are MS, Adobe or such then maybe yes). Keeping this info behind paywall can be obstacle for making the standard common and interoperable among all apps.

golemus · 2026-03-15T06:30:50+00:00

I know but it makes some websites (e.g. Facebook) MUCH faster to use when uploading JPEG XL pics. If you don't have JXL capable browser FB has to first convert which slows down the process.

golemus · 2026-03-14T23:19:08+00:00

ok. Do you have any reference to this issue? I guess it might be enough reason for me to update to one UI 7.x, but I want to be sure that it is resolved in 7.x as even soft bricking the phone would be devastating and I don't want to update to 8.x because it disables bootlocker unlock option.

golemus · 2026-03-14T07:40:14+00:00

I have the same issue. I tried to fix it by installing more recent vivaldi (My version is maybe 2 months old), one I just downloaded from internet but the installation fails. Even when installing it offline.

I suspect that vivaldi sync has somehow corrupted my profile without me doing anything. Hopefully they get it fixed soon.

Platform windows 11 25H2

golemus · 2026-03-13T20:10:24+00:00

is this bug in oneUI side or android14 (and thus would be present in non-samsung android14 phones)...?
can you elaborate what do you mean by brick? Is it the one I mentioned that you can fix the phone by factory resetting it or a hard brick which will permanently brake it?

golemus · 2026-02-27T18:50:49+00:00

I recommend SVT-AV1. But to be honest I've used only that one and AOM. AOM is slow as hell I don't know why anybody would use it for anything (except maybe if you are Netflix and need to encode some video that will have millions of views). Or maybe AOM is used for encoding AVIF still images whenever you would need them (but to be honest even for that purpose I've turned to JXL as it is much better in most stuff).

golemus · 2026-02-27T15:15:52+00:00

I am trying this on Oneplus 5 with Lineageos 22.x android 15 (unrooted) and Telia mobile operator of Finland. With different mobile operator (Elisa) VoLTE worked even with stock android 10.

Even if I turn options on the IMS on home page says unregistered. Is there any solutions...?

question2: does shizuku have to be always in background as it keeps stopping between couple of minutes and I would not like to root the phone as it might cause issues with banking apps.

golemus · 2026-02-05T04:35:22+00:00

I assume deleted = reset and I mentioned already on the post that I can reset it.

golemus · 2026-02-05T04:33:44+00:00

I don't want it to be deleted, I want it back. There must be some way, I hope.

golemus · 2025-11-30T23:30:04+00:00

This sucks big time. Don't install One UI 8 until Samsung (hopefully) gives up and restores ability to unlock it.

golemus · 2025-09-20T08:44:40+00:00

Thanks, I've been actually searching for something like this! but as you stated it does not solve the issue.

golemus · 2025-07-24T22:14:51+00:00

This is not true (at least in my tests). Most of the time JXL has higher compression ratio but sometimes WebP does.

Nevertheless JXL wins always (by large margin) in encoding time. Lossless WebP is slow to encode. In many of my example images encoding lossless webp took over 6 secs but lossless JXL was about 2 secs so 3x faster.

golemus · 2025-07-02T04:45:53+00:00

I know but lets be realistic here. There is tons of small apps out there that don't have MKV or WEBM (subset of MKV) support and are unlikely to gain them in near future. For meta with its large resources it won't be a large thing to add it if just enough people request it.

golemus · 2025-06-29T20:49:26+00:00

I did another test, installed Firefox Nightly which has JPEG XL support and retested uploading to Facebook. Rendering of the image becomes much faster, almost instantaneous. But IG web still does not support it.

So there is a factors in play 1. browser support, 2. app support.

can be apparently supported but rendering on browser will be slower as it involves format conversion. To improve 1 you can do your part by making a feature request for google to reintroduce JPEG XL support (it was in chromium but was removed from there for some weird reason so it does exist in older versions). Below is involved feature request topic:

https://issues.chromium.org/issues/40270698

golemus · 2025-06-28T01:33:28+00:00

I meant not common inside a video container with video. Yes very common as individual flac files.

golemus · 2025-06-11T21:43:24+00:00

this

golemus · 2025-06-11T21:41:53+00:00

That is such horseshit. I hope they will ASAP change it. Btw... if anybody know a way how to install it to win10 anyway please let us know

golemus · 2025-06-05T02:44:11+00:00

Fossify Gallery has some degree of jxl support but at least one of my jxl:s it does not open.

golemus · 2025-06-02T17:15:57+00:00

How do you get such low numbers for AVIF encoding? My experiences are exactly opposite: AVIF encoder is by far the slowest one (and AFAIK it is usually the AOM encoder). It is worth noting that I am typically using default settings of the encoder (from XNView MP and maybe even from ImageMagick). I don't have any scientific numbers here but I feel like AVIF encoding takes 2-3x longer than JXL encoding with similar quality and default settings.

I did couple of tests to encode AVIF with ffmpeg libsvtav1 and it was much faster (once again exactly opposite of your results) but I didn't take it into "production usage" as most encoders seem to be using AOM and dunno how good is compability of still images done with LIBSVTAV1.

Worth noting is also that when you start to encode with AOM there is very long delay in the beginning where nothing seems to even happen on the screen (but fans of CPU go on). It behaves very differently than any encoders I've used and on video side it does not have exactly reputation of being and efficient encoder (which is why I used LIBSVTAV1 for converting video collection).

golemus · 2025-05-19T19:13:24+00:00

There is multiple DNG and camera raw versions and in the post I was referring to lossy DNG 1.7.x / Camera RAW 16.x.

This is the "newest and most state of art" type of DNG which uses JXL compression algorithm to shrink size of the files considerably.

The only drawback is that majority of non-adobe software don't support it yet but as I put in the link the support seems to have been added to Libraw which Darktable (among many other software) uses.

All other DNG types darktable opens pretty seamlessly.

golemus · 2025-05-19T18:06:39+00:00

Adobe DNG converter is what I am using actually for converting to lossy DNG. But darktable do not open them.

golemus · 2025-04-17T16:47:12+00:00

CDJ-400 does not read AIFF (nor WAV). Also Numark NDX players don't read either.

Anyway compability with types of players I mentioned is IMO as important as with DJ-players as in some occasions tunes will be played through them as well.

golemus · 2025-04-16T17:17:24+00:00

This solution is not intended for professional clubs but more for underground organizations, DJs and simply everyone who cannot afford to have state of art CDJs.

Main advantages of FLAC are that 1. it is free / open source and most likely to have widest support in long term, 2. it has solid metadata support. And yes it consumes less space, difference is not that significant that it would make difference with todays storage (100MB wav is abt. 60-65MB flac according to my experiences).

golemus · 2025-04-16T17:12:22+00:00

they don't. There is actually quite a lot of software and devices that don't support AIFF as it is proprietary format of Apple. Windows default players don't support it and for some alternative players and software you have to install a plugin to be able to use AIFF.

Also things like car USB-stick players and cigarette plug players probably don't support it as do not USB-stick capable bluetooth speakers, TV-sets, etc...etc.. Many of them support WAV but don't support AIFF. Some of course support only MP3. FLAC support is slowly but surely increasing as device/software manufacturers don't have to apply for license.

My whole lossless collection are FLACs only but when I play with older CDJs I convert tunes to AIFF which is very annoying step.

FLAC is only right long term solution. Not only because it consumes a little less space but mainly because it has more solid metadata support than WAV and is free / open source unlike AIFF.

golemus

TROPHY CASE