XnView Software

Just FYI, the 64 bit 'SETUP' download does not match the currently posted hash (403A7D2BE73CFBCDED766013DE394965037161C2E69D42AC6CA66986F5DF8339)

I think the hashes - at least on the Win64.exe version - might need updating as well.
I'm getting a mismatch.

this one 98088D9815F07372091153DD8F0700C286574D9022F71BEE1BCA37294DB07277?



Yes. I get: 2e623c063e661745d1036ccd7e180dd9ddec857fdaa43125042a28b73017ef09

If you are not seeing it ...

I think the hashes - at least on the Win64.exe version - might need updating as well.
I'm getting a mismatch.

Okay. I appreciate your response.
It will be interesting to see if the Microsoft ARM devices succeed in the market, and if they pursue it or revert to Intel.
The application support is fairly thin now.
But obviously support by developers requires some incentive in market share.
So...interesting to ...

Hello,

Is there a Windows ARM64 (AArch64) port planned?

Asking re compatibility with Microsoft's Surface X Pro (Windows 10 ARM based, not x86).
https://www.microsoft.com/en-us/p/surface-pro-x/8vdnrp2m6hhc

Alternatively...has anyone tested, or heard feedback, regarding functionality via the 32 bit ...

I think the SHA256 may need updating for the new 0.93.1 x64 Windows .exe.

I get a mismatch for the current D7493C82CC146803F9FA2315F582547BF312801AC4493BA95CDEA5CF95A72B19

Mark

Not sure this qualifies as a bug, but FYI: the currently listed SHA256 (79F852C616AABE3E4E21AD1F9998A1FE8339AA41C710514D97E21C4AAA67757F) does not match the new (.90) Windows .exe.

I'm guessing it was just not updated.

Same 'bug' here, also on Win7 x64.

When clicking 'OK' on the Capture pop-up box MP will crash.

However, for me, it is an occasional (although frequent) bug, and I have not noticed a pattern to explain the reason it does or does not happen in any instance.

Mark

Ah, good!

I was just not getting the future development aspect.....so thought I was misunderstanding something.

Thank you,

Mark

Thank you.

To clarify....is this behavior different from XnView ('classic')?
The same message appears in both.

In the XnView Classic/MP "What's different..." thread it says:
"Support for full internal bit depth pictures 8/16/32 bits per component"

But I am not clear what is different (if both are ...

Hello,

When opening a "16 bit" .tiff in XnView MP I get the message:

"This picture will be converted to RGB with 8bits per component"

I may be understanding incorrectly but I thought XnView MP was able to open "16 bit per component" (48 bit) files?

Thanks,

Mark