XnView Software

This is not a bug, it is an unsupported proprietary format. No open-source raw editor can open it.

I can only confirm this, on Windows 10 and 11. Somehow we have lost our dearest histogram.

Using ver. 1.9.3 for a day or so, I didn't notice any such problems, so it looks fixed to me. Thank you!

Ducks can be particularly resistant!

https://filebin.net/92sxqq4fox6jxzf5

With version 1.9.x I am experiencing a similar (same?) issue when using a specific switching mode, but unluckily I am not able to find a way to reproduce it every time. It does happen most of the time, though.

1. Start with a fresh portable Windows version.
2. Settings > Switching modes: select ...

I do "unlock" downloaded archives before extraction to make Windows happier ...

ART
FOSS

Be well!

Since the last changes, you also need the exiftool_files folder, like this:

While the camera does not seem to be supported by LibRaw yet, the main FOSS raw editors - RawTherapee, ART and darktable - can already handle this format. (With no LensFun support for this lens.)

littleBarVersion=2 works fine, thank you all very much!

digiKam has this habit, buttons all over the place, it requires a lot of mouse movements. While improvements are generally a good thing, I find this one unnecessary and troublesome.

And, perhaps, interface changes could be less frequent, even when they do improve the usage, they are disturbing by ...

Settings - General - Save session on program exit

Renaming profile from ...125cdm²... to ...125cdm2... removes the problem.

Enabling the metadata management of archived images looks an overly complicated and mostly unneeded feature to me, more like a caprice.

I can't reproduce the problem, all umlauts are OK here. Perhaps check settings - metadata - encoding:

(The "embedded comment" is, so it looks, in utf-8 in this case, but there are all kinds of them still fooling around.)