ten10

Okay - one last info to add. Just for a test, i've erased the above activated sRGB IEC61966-2.1 profile out of the profile list and activated the generic sRGB profile "CalibratedDisplayProfile-4.icc" as standard, and deactivated the ticked setting "using own settings ...". Now after doing that, i've started Affinity Photo v1.6 and for some unknown reason, it's still working and doesn't produce any yellow tint on a white document. I've restarted the PC and Windows 10 and it's still working without a problem. So this is a very odd behaviour and can't be really explained, at least noch by me ... .

Pšenda - thx a lot for the hint towards that topic. And reading through it and checking the same color management stuff in my Windows 10, like discussed there, i made the same changes in selecting my own color profile in the given list called " sRGB IEC61966-2. " . After adding it manually and set it to standard profile, i've tested the result with Affinity Photo v1.6 and v1.7beta - and now v1.6 produces no yellow tint on a white blank document anymore, it's white as it should be (and in v1.7 beta it's still white, so in this beta version of Affinity there must be some changes already implemented, which work with other color management profiles, too). If someone else comes across this problem and wants to call up this color management (german "Farbverwaltung") window quickly, they just need to push the button-combination "Windows+R" (or right-click on the Windows Start button and select "Run" in the list or in german "Ausführen") and this Run (Ausführen) window appears, where you can just type in "colorcpl" and the color managment windows will be opened. I've added a snapshot of my color mangament window and the settings now. The second profile in the list called sRGB was set as the main profile before, which obviously made problems with Affinity Photo v1.6 or lower, but not with v1.7 beta.

Thanks for your replies. - S - .... i've tried what you've suggested - but i ran Affinity Photo v1.6.5.135 and Affinity Photo v1.7.0.258(beta) side by side - opened a new blank document with the exact same settings in both versions. And the appearing blank document in Affinity v1.6... has a light yellow tone - but in Affinity v1.7... appears a nice white blank document. So definitely something's going on in ths v1.6.5.135 version i would say ... Since this was the quickest test to do, i'm not sure if it really will make a difference anymore, to go through this aphoto file stuff like emmrecs01 suggests (it has nothing to do with just one particular photo/image, the problem occurs with any image) i edit with this version. Because it seems to be clear now, that there is something odd going on and it looks like it doesn't matter what i will change in other settings, since there is an obvious difference between official and beta version of Affinity Photo. As far as i remember, when i bought Affinity Photo back in 2017 i believe it was v1.5 something, that this problem wasn't there yet. It must have started with higher version v1.6 .

I'm running Affinity Photo with official version 1.6.5.135 ... i've deinstalled or reinstalled it at least 5 times now - no change in behaviour explained below. As long as i work with photos/graphics inside Affinity Photo everything seems fine. But when i save my done images (doesn't matter if tiff, png, jpg ...) the saved image gets saved with a whitebalance shift of about 20% towards cold temp. But when i load this same image back into Affinity Photo v1.6 , the image whitebalance gets set back those 20% in the warm temp direction, so it's looking again, like it's suppose to. If i load those temp-wrong saved images into another graphics software like PaintShop Pro for instance - then there is no temp-shift happening. PaintShop Pro shows the image with that 20% cold temp shift - like any Windows 10 image-viewer, too. What tells me, that there is something wrong in this version, is that i've downloaded the beta version of Affinity Photo - version 1.7.0.258(beta) . And silly as it is, Affinity v1.7 doesn't reproduce this error - it's working fine and flawless and saves and loads the images without any errors or color temp-shifts. So that's why i'm working now only with the beta version v1.7 of Affinity Photo - the v1.6 version is useless now with this error - and like mentioned above - even after de- and re-installation this problem doesn't disappear. Is this a known error the Affinity team is aware of, or does that only occure on my PC and Windows 10 Pro ? But since any other graphics program doesn't do this color-temp shift (Affinity Photo v1.7..., PaintShop Pro, Gimp, Paint.Net, Adobe Photoshop CS2 ....), it has to be mostly software related, then being a problem with my PC or Windows 10 ... Take a look at the images - the grey moon is what you see in Affinity v1.6... and the blue-color moon is what gets saved (and looks exactly that way loading it into Affinity v1.7 or PaintShop. And if you take the blue looking moon and load it back into Affinity v1.6, it's back to normal grey - so i wonder, what happens here, even in a freshly new installed Affinity v1.6 ???