I understand that XnView, and lots of other image viewers does not support more than 8 bits per layer, which is OK, since more does not make sense anyway in the presentation on a monitor.

However, my issues is merely that the image does convert correctly when the pixel components are more than 8 bits. I would expect that an image only using 0 and maxval would look the same, but that is not the case.

I have attached a number of PAM examples, going from 1 bit (maxval = 1) to 16 bit (maxval = 65535), and this shows that XnView does not handled 2 byte component values correctly, since the view changes when going from 8 bit (maxval = 255) to 9 bit (maxval = 511), where 2 bytes are required.

Can I do anything to help fixing this, since I would very much like PAM with 2 byte components to show correctly in XnView ?

MortenZdk wrote:However, my issues is merely that the image does convert correctly when the pixel components are more than 8 bits. I would expect that an image only using 0 and maxval would look the same, but that is not the case.

OK, I see.

MortenZdk wrote:Can I do anything to help fixing this, since I would very much like PAM with 2 byte components to show correctly in XnView ?

Providing samples – which you've already done – is the best way to help the developer of XnView (Pierre).
I believe he's very busy right now getting the beta of MP v0.85 out, but hopefully he'll find the time to look into this.