XnView Software

xnview wrote: Thu Mar 27, 2025 8:54 am This problem is supposed to be fixed in XnView MP 1.8.7. Please check and confirm the bug fix here.

I am not using XnView MP. I am using XnConvert and that is where I found and reported the bug.

xnview wrote: Thu Mar 13, 2025 4:06 pm Thanks to your detailed description I can reproduce the problem.

I notice in the bug report it's been "fixed' in XnView 1.8.7, but when will that be fixed/updated in XnConvert, where I reported the bug in the first place?

Thanks.

Thanks. I notice in the bug report it's been "fixed' in XnView 1.8.7, but when will that be fixed/updated in XnConvert?

Here you go. But it's not just these particular jp2 files, it's any jp2 file I try.

Also, I went back to 1.102 and they work just fine.

https://www.transfernow.net/dl/20250312eyveJDdh (Link good until March 19th)

I'm seeing a HUGE bug in the macOS version of 1.104. I'm running macOS Ventura 13.7.4 on an Intel MacBook Pro.

See the .jp2 I'm loading vs. how it appears in XnConvert 1.104.

https://i.postimg.cc/J0H08mfF/cd-somethin-else-cannonball-adderley-2-0000.jpg

https://i.postimg.cc/RZB7gbfm/Screenshot ...

That's the solution? To avoid the Mac App Store version?

Hello,

I was using XnConvert 1.83 since last year, and just updated to 1.90.1 today via the Mac App Store.

Previously I was able to Output to the same folder the input files reside in. Now, I have to choose the folder I want to Output to, and it stays set to that folder until I direct it elsewhere ...