Very high CPU usage with Procedural Texture and Mesh Warp

[M1000]

This is the CPU usage while only moving the cursor over the testfile I added.

HighCPU.afphoto

[NotMyFault]

This is probably by design and no bug. A get high CPU utilisation on Mac mini (up to about 50%), too whenever the PT filter is active, and a bit lower (30%) when inactive.

As long as Photo renders the file correctly and with good refresh rate and reacts snappy to any user input there is no reason to assume any bug, as the sw works as designed.

[M1000]

On 1/13/2024 at 5:26 PM, NotMyFault said:

with good refresh rate and reacts snappy to any user input

And there's the problem. When I add a pixel layer and try too draw, it gets very choppy. And it also depends on the zoom level from usable at a low zoom level (7,5 %) too unusable at a high zoom level (100%). Added a video to demonstrate this.

[NotMyFault]

That is correct, but probably unavoidable. I complained about the same issue long time ago.

 

The Live mesh war and perspective filter have a computational complexity where every pixel depends on all other pixels in the document (not only visible, but out oof canvas areas, too). I don't think there will be any cure.

 

Workaround:

• temporarily add rasterised copies of for PT filters, and deactivate PT. If you modify anything below, delete the temp layers and make a fresh copy.

 

 

 

[M1000]

Although I replaced my graphics card since my last post (1050 Ti to RTX 3060) I think there has been some optimization done, since this is the CPU usage while only moving the cursor over the testfile now:

Drawing on a new pixel layer is now much smoother too, whilst still being zoom-dependent.