Please elaborate on "this picture will be converted to rgb ..."

[gfnov]

I just installed XnView and when scrolling through RAW files, I keep getting the "this picture will be converted to rgb with 8 bits per component" message. The message includes a checkbox saying "Remember my answer . . .", but then doesn't provide me with a choice. I searched these forums for an explanation of why I keep repeatedly seeing this message. The only explanation I found was this: "If you [sic] image use more than 8 bits per component (48 or 64 bits for example), XnView needs to convert into 8bits/component, the only internal pixel support." This is clearly a warning, but of what? Is XnView actually changing my RAW file and asking my permission to do so? Or is it just doing something internally in the viewer (which seems unlikely, as there would be no reason to tell me about it if that were the case)?

[cday]

When a file is opened in XnView software the bitmap created that is used for any further processing or saving, is 24-bit depth; the original file opened is unaltered, so there is no reason for concern there. You could test using a copy of a higher bit depth file to confirm that.

The warning message you mention can optionally be suppressed if desired when future files with greater than 24-bits per component are opened...

[gfnov]

What is the purpose in warning users of this? Who cares? Users can do nothing with this information, and It is alarming. Consider the time I've wasted (including a bit of yours) because of this message. This occurred within 2 minutes of my first trial run of XnView, and frankly, it has turned me off to testing any further. Who knows what other cryptic messages await.

[cday]

What is the purpose in warning users of this? Who cares? Users can do nothing with this information, and It is alarming. Consider the time I've wasted (including a bit of yours) because of this message. This occurred within 2 minutes of my first trial run of XnView, and frankly, it has turned me off to testing any further. Who knows what other cryptic messages await.

Your original question concerning the meaning of the warning does arise periodically, but surely users do need (or least may wish) to know that any opened image will lose the original bit depth?

And the option to suppress the message on future occasions, which is provided for other similar warnings, is surely useful to streamline processing once that fact is understood?

Edit:

Possibly the wording of the warning message could be enhanced by indicating that the original file will not be altered?

[gfnov]

Hopefully, other users will weigh in, but my opinion remains that users do not need to know this and should never see the message. This is something that should remain under the covers. Probably, if I were editing the photo with XnView, the warning would be important (I use Photoshop Elements to edit). For viewing, no.

[cday]

Hopefully, other users will weigh in, but my opinion remains that users do not need to know this and should never see the message. This is something that should remain under the covers. Probably, if I were editing the photo with XnView, the warning would be important (I use Photoshop Elements to edit). For viewing, no.

XnView MP is a Viewer, Editor and file Browser, so I don't think the warning message can be omitted entirely...

Possibly there could be an option to somehow use XnView only as a Viewer, in which case the message could be suppressed, but that option would in any case probably not be discovered easily.

I'm going to suggest that the wording of the message be modified slightly, to make clear immediately that the file opened will not be changed.

[JimDossan]

Hello!

Just had a similar experience like gfnov, wondering whether something of my images is being altered.

Something like
"This picture has a higher bit depth than 8 bits per component but can only be displayed (and edited) with 8bpc in XnView at the moment. Overwriting or saving a copy will reduce the bit depth of the resulting file to 8bpc permanently."
could be an improvement?


P.S.: I didn't find anything about grave digging in the Rules and Guidelines, should I rather have started a new topic?

[cday]

Just had a similar experience like gfnov, wondering whether something of my images is being altered.

Something like this could be an improvement:

"This picture has a higher bit depth than 8 bits per component but can only be displayed (and edited) with 8bpc in XnView at the moment. Overwriting or saving a copy will reduce the bit depth of the resulting file to 8bpc permanently."

Possibly the wording of the warning message could be enhanced by indicating that the original file will not be altered?

May I suggest something like:

'This picture can only be opened as rgb with 8 bits per component, the original file will only be altered if the image is resaved with the same filename.'

This continuing issue could probably be easily overcome with a little thought!

[JimDossan]

May I suggest something like:

'This picture can only be opened as rgb with 8 bits per component, the original file will only be altered if the image is resaved with the same filename.'

Sounds good to me, it is more concise than my variant!
Had I read that instead I wouldn't have felt the need to dig up some forum posts! :D

[ragazzo]

Possibly the wording of the warning message could be enhanced by indicating that the original file will not be altered?

May I suggest something like:

'This picture can only be opened as rgb with 8 bits per component, the original file will only be altered if the image is resaved with the same filename.'

This continuing issue could probably be easily overcome with a little thought!

Well it hasn't been changed yet and certainly would be an improvement. As a new user, I was also alarmed at the continued use of the original message and came looking for answers. The suggestion shown is much better. It is very difficult to absorb every nuance of a new program with LOTS of options but my original files are considered sacred so it was a little off-putting.

Thank you for reading!

[helmut]

Displaying a warning message when opening an image which only applies when saving/wirting the image really makes no sense.

XnView should remember that the original image has a larger colour range and right before saving the appropriate image a message can be displayed.

[XnTriq]

Related topics:

• 48 bit TIFFs reading/writing → IRIS
• Planetary Data System (PDS) format is hard coded to 8-bit
• Opening 16 bit tiff files
• [Résolu] export PNG 16 bit ?
• loosing ICC profiles
• Is viewing destructive?

External resources:

• Cambridge in Colour: Bit Depth Tutorial
• DIY Photography: 8-bit vs 16-bit – What Color Depth You Should Use And Why It Matters
• Graphics.com: Exploring High Bit Depths in Photoshop
• Photoshop Essentials: The Benefits Of Working With 16-Bit Images In Photoshop
• The Art of Retouching: What is the Difference Between 8-Bit and 16-Bit Color Depth Images?

• Clarification: converted to RGB 8 bits per component
• Warning message "this picture will be converted to rgb with 8 bits per component"
• REQ: Full 16+ bit/channel image support.
• RW2 files

[xnview]

Displaying a warning message when opening an image which only applies when saving/wirting the image really makes no sense.

XnView should remember that the original image has a larger colour range and right before saving the appropriate image a message can be displayed.

yes right, it will be changed

[cday]

Adding a new warning when a file is about to be saved, reminding that the image will be saved at 8-bits per component, is a good idea...

But the existing warning displayed when a file with a greater bit depth is opened also needs to be reworded, as the present wording has frequently resulted in confusion...

The alternative wording suggested above has been supported by interested users, and that wording or something similar seems necessary to provide both an explanation and reassurance when an image is about to be opened that the original file will not be changed.

'This picture can only be opened as rgb with 8 bits per component, the original file will only be altered if the image is resaved with the same filename.'

Maybe that wording could could be briefer, but it was the best text overall that could be found at the time.

Edit:

If it is intended to remove the existing warning before the image is opened, a user could spend significant time editing their image, and then find that their time has been wasted. And since some users could be very unhappy to inadvertently lose their original images, both messages seem desirable.