[Photo] Rendering Glitch

[SamMN]

Loaded a photo on Photo (attached), and in the 'work area' there's a white/grey filter applied to the whole area, that appears and disappears. Not been able to screenshot it, or screen record it, because it doesn't seems to stop whenever it's being focused on by something else. Had to use my phone to try and capture it. Tried closing Photo and re-opening the photo afresh, same issue.

First time I've ever encountered this. From what I can tell, it's caused by the ICC profile (I changed it to sRGB, the issue immediately stops). The photo was exported from the (Apple) Photos app on macOS. Looks like it defaults to Apple Wide Color Sharing Profile (or at least it did for this, first time I've used the app), which it would seem Affinity doesn't like?

Running on a Mac Mini, M2 Pro. Monitor is a 31.5" UltraFine™ UHD 4K Ergo IPS Monitor with USB Type-C™

[Dan C]

Hi @SamMN,

Thanks for your report!

I can confirm that this is a known issue which is logged with our development team - as you've found this affects M2 devices only when using the 'Apple Wide Colour Gamut' profile.

There are 2 options to workaround this issue whilst our devs work to resolve this, either you can use a different colour profile, or you can disable Metal rendering under Affinity Photo 2> Settings > Performance and this flashing workspace issue should stop.

In the meantime I'll be sure to 'bump' this issue with our dev team to bring it to their attention once again. I hope this helps

[raily74]

I'm glad I found this post so I don't have to write a new bug report. I have the same problem on a Mac Studio M2 Max with Studio Display. For the moment I have disabled metal rendering as a workaround and am hoping for an update that will fix this problem. Thank you!

As a small addition: When you cut out the image and print it, it comes out of the printer much too light. So it's not just a problem with the view.

[Affinity Info Bot]

The issue "M2 Mac flashing workspace - when using Apple Wide Colour Gamut" (REF: AF-473) has been fixed by the developers in internal build "2.3.0.2150".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.