I don't know how XnView handles errors or if this causes any hiccups. Either way, you might want to delete the whole section (which holds the settings for Image » Add Text...). Please remember to quit XnView prior to editing the INI.
Okay, I removed the entire section as you advised.
However, I am still able to corrupt those photos.
I went to the directory with the photos
made a copy of one in XnView's browser
then opened it XnView
set the saturation to 0
double-clicked to return to the browser (which would auto-save)
and voila! Corrupted image again.
No, I think we were onto something with the bits out of whack. That's not something that can be fixed with an ini setting - it's something in the way that XnView writes changes to jpeg files.
However, it seems like an obscure problem, but I think it *is* an issue with photos created by certain cameras, seeing how they can use different standards and seeing how XnView has to deal with the likelyhood of any/all of them simultaneously.
Brother Gabriel-Marie wrote:No, I think we were onto something with the bits out of whack. That's not something that can be fixed with an ini setting […]
What I meant to say: My observation that “XnView has either trouble finding the embedded thumbnail or it can't decide which one (Composite:ThumbnailImage vs. Composite:PreviewImage) to use” won't “help Pierre find out what's going on” because it turned out to be a false lead.
Did Pierre get the samples? (I didn't want to forward them without having asked for your permission to do so.) Can he confirm that any of them are indeed corrupted?
Steps to reproduce:
1. view image in Viewer mode (I only tested for jpeg).
2. save image (ctrl+s, overwite existing)
3. press Enter to switch to Browser mode
4. image did not finish saving and is now corrupted
… but all of these utilities confirmed JPEGsnoop's diagnosis: Everything seems to be in perfect order.
As mentioned earlier, I've been “able to reproduce some of it some of the time”, but I never ended up with a corrupted JPEG, even though I've tried to reproduce the problem on several different computers over & over again, which makes me wonder if this phenomenon only occurs on machines with the horsepower of Br. Gabriel-Marie's PC (“30GB RAM and an Intel Core i7-2600”).
@ Br. Gabriel Marie: If I understood correctly, …
Brother Gabriel-Marie wrote:I went to the directory with the photos
made a copy of one in XnView's browser
then opened it XnView
set the saturation to 0
double-clicked to return to the browser (which would auto-save)
and voila! Corrupted image again.
Well, as I've said, it doesn't happen with every jpeg file. Just certain ones (but consistently for those files).
The only other thing I can think of is that I am running Intel Smart Response Technology (ISRT) and have used an SSD to accelerate my C drive HDD. I've also put my pagefile onto that SSD. Those two things provide my system with 15-20 more responsiveness.
So I applied the settings you indicate and I am still able to corrupt the jpeg.
And I can still corrupt the jpeg even if I move the file to another folder on another partition.
If I try to open the corrupted jpeg, I get a popup from XnView saying, "Error opening the file <myfile.jpg>"
