(only) *.RW2-files aren't displayed with correct resolution

*** Please report new bugs here! ***

Moderators: helmut, XnTriq, xnview, Dreamer

Post Reply
SebSebsensen
Posts: 4
Joined: Tue May 27, 2025 4:54 pm

(only) *.RW2-files aren't displayed with correct resolution

Post by SebSebsensen »

I am not sure if this is what the similar current topic is about, if it is a duplicate please merge (not a native speaker, sorry).

I have only noticed this with *.rw2 files after currently getting a Panasonic Lumix to play with.

In the file/folder browser XnView correctly identifies the actual resulution.

when I open the file preview XnView claims that the resolution is a much lower 1920x1440 ONLY when it is an *.RW2 file (or at least as the only one of the RAW files I work with).

The resize function in that view will also treat it as 1920x1440 while right click -> properties gives the correct resolution in the XnView property window.

The setting for Camera Raw are set to original size (default as it comes with a fresh install, and it always works with e.g. *.NEF or *.NRW)

See attached screenshots (again 7z with webp2 as the board software won't take them and it would be too large otherwise), thanks.
Attachments
Screens.7z
(786.22 KiB) Downloaded 2 times
User avatar
user0
XnThusiast
Posts: 2409
Joined: Sat May 09, 2015 9:37 am

Re: (only) *.RW2-files aren't displayed with correct resolution

Post by user0 »

change View combobox from Embedded preview to Full or Half size
in Settings > Read > Camera RAW
SebSebsensen
Posts: 4
Joined: Tue May 27, 2025 4:54 pm

Re: (only) *.RW2-files aren't displayed with correct resolution

Post by SebSebsensen »

user0 wrote: Wed May 28, 2025 1:49 pm
user0 wrote: Wed May 28, 2025 4:58 am change View combobox from Embedded preview to Full or Half size
in Settings > Read > Camera RAW
Ok, toggling the first dropdown seems to change it for this file format, do you have any idea why e.g. *.NEF is not affected by this setting at all?

It should also have no effect on the resize function, or I am wrong?

In any case there must be some bug when the options have different results for different file formats, I think. At least in our own software (nothing with images, though) I would still classify it as a bug - if this is correct it behaves wrong with e.g. Nikon files.

In any case, thanks - I can deal with this for the moment :-)
Post Reply