Matt H

Gotcha, thank you! I guess I had missed the earlier discussions.

Normally I use the Extreme level of the denoise filters to add a certain subtle effect to some of my photos. Anyway, it will be missed...

Ah, this is on a v1.6 afphoto file, indeed. However, I also do see the massive screen glitch for a brief moment before the crash. (I left Metal compute enabled.) Also, can you say what happened to the Extreme denoise sliders? They seem to max out at 100% now in 1.7.

First question: What happened to the "extreme" denoise sliders? Second question: I am able to cause Affinity Photo to crash repeatedly by loading a file, selecting a nested (?) layer, then Filters -> Noise -> Denoise..., then selecting the parent layer. AP immediately crashes. *boom* I've attached a macOS diagnostic from one of the crashes. bug_report.txt

I'm also experiencing slowdowns when using inpainting and selection refinement. Isn't Metal supposed to be faster? Why does turning it off improve performance?

I'd like to +1 this suggestion. Not every tool is always useful (even inpainting or clone) -- I think seam carving can be useful sometimes. In fact, I have quite a few photos that would benefit from it. Here's a new implementation of it in Go: https://github.com/esimov/caire -- and goes to show that there is still demand for and interest in this algorithm. And remember that this isn't just for cropping: it's also for expanding, which is the part I would find exceptionally useful. Little anomalies could be fixed up with clone or inpainting tools and similar. I do hope you'll consider adding this Affinity Photo. It would make it a highly competitive feature.