mh_tnm's profile

48 Messages

 • 

746 Points

Fri, Jan 22, 2021 6:06 PM

Curves (and other adjustment layers) handle lag since v21.0.3 - with video capture

I'm not sure what happened after version 21.0.3 but ever since that version you get epic lag on larger, more heavily layered documents, when using adjustment layers - particularly Curves. Working in 16-bit doesn't help matters (but isn't the primary factor).

To describe the behaviour: you used to be able to click on a handle, drag it smoothly, and then the canvas would update a moment later. Now you attempt the same and the handle doesn't move - or takes an age to, and then jumps - as though massively lagged. So actually doing precise adjustments is impossible.

I don't think my system's under specified - and after all the behaviour's not there's with v21.0.3, but in case it's relevant:

  • Windows 10 64-bit
  • i9-9900K
  • 64GB DDR4
  • Samsung 970 Pro NVME application drive
  • Samsung 970 EVO Plus NVME scratch disk
  • NVidia Quadro RTX 4000 8GB
  • Wacom Intuos Pro PTH-851 (although you get the same behaviour with the mouse)

I've also tested it on a similar but slightly older spec - it's not specific to this machine.

I've video captured the behaviour to try to show the comparison... With the latest version, I'm trying to do the same manoeuvre but the the cursor get's stuck and won't drag, then suddenly does and then lags again. The actual curves interface doesn't update smoothly - almost like it's waiting for the (understandably) slower canvas update before moving. But obviously that makes it unusable.

https://www.dropbox.com/s/sgf0uu43zfkt88f/Job_0342-psb%20Curves%207%2C%20Layer%20Mask_16.mp4?dl=0

Is there any chance we could go back to the old behaviour/performance - I'm worried that this old version that's usable is going to get depreciated and then I'll stuck! 

Responses

48 Messages

 • 

746 Points

5 m ago

I can confirm that this is still the case with the new version (v22.2).

(edited)

48 Messages

 • 

746 Points

5 m ago

I've tested v21.2.5 - it's fractionally more responsive than v22.2 but still far worse than v21.0.3.

48 Messages

 • 

746 Points

Tested v22.3 - still bad.

48 Messages

 • 

746 Points

2 m ago

New version v22.3.1 still markedly slower than v21.0.3.

Of note, even the drawing of the histogram behind the curves handles takes longer.

48 Messages

 • 

746 Points

1 m ago

Tested v22.4 and v22.4.1, both still demonstrate the handle lag when redrawing the canvas.

48 Messages

 • 

746 Points

16 d ago

New version, v22.4.2, exhibits the same behaviour.

Champion

 • 

1.7K Messages

 • 

29.6K Points

@mh_tnm v22.4.2 has fixes for this issue and adjustment layers are now buttery smooth for me. So you're working in 16bit, but what dimensions are your images? How large are the saves? 

48 Messages

 • 

746 Points

16-bit or 8-bit doesn't actually seem to affect things hugely. It's whatever underlying change happened after v21.0.3.

They are big images - at least 4000x6000 pixels (I work on retouching professional magazine photographer's shots, so that's a sort of minimum these days). And usually quite a stack of both normal and adjustment layers - at least 5 and up to about 30. And filesize can range between a few hundreds of MB to a couple of GBs. Which I understand is a heavy load. But it's actually usable on exactly the same images on the old version and hasn't been with later updates, both for the new version 22 and smaller updates to 21.

It's exactly as though they changed it from having the handle follow your pointer regardless of the canvas status, to waiting for the canvas to update - which obviously with this sort of load behaves like unworkable lag.

Champion

 • 

1.7K Messages

 • 

29.6K Points

Yes, i've experienced the same, but it's finally been fixed in 22.4.2. I just tested with a 16b image that has similar specs to yours, with SOs and 20 adjustment layers. Slider response is real-time and very smooth. 
I wonder if it has something to do with the Quadro? Also in Prefs/Tech Prev, is Native Canvas on or off? How about your Performance Prefs?
You might need to nuke your Prefs and start over, sadly.

48 Messages

 • 

746 Points

I will double check on my other machine as that’s got a GeForce card instead. Are you on an AMD card? Have intermittently been nuking preferences to check but must admit I haven’t done with this one yet (the laboriousness of doing so for several versions across three machines is… a bit much).

48 Messages

 • 

746 Points

What perf settings do you run / do you use native canvas?

48 Messages

 • 

746 Points

Mine:

Let PS use - 36448GB

History - 70

Cache levels - 6

Cache title size - 1024k

Use GPU / Advanced (though Basic and Normal are indistinguishable) / Use OpenCL / Anti-alias guides / 30-bit display (as I have one and intermittently need it for calibrated work)

Haven't fiddled with them extensively with the current version but have done so previously to no avail.


Deactive native canvas option - not enabled. 

Champion

 • 

1.7K Messages

 • 

29.6K Points

looks like it's all set up correctly, so it's either the quadro that isn't taking advantage of the fix in the update or yeah, nuke time =(

48 Messages

 • 

746 Points

Just gave it a whirl on the 1080 GTX based machine and it's the same. So it could feasibly be the NVIDIA drivers writ-large that cause the issue I guess but not specifically the Quardo hardware.

You didn't say what your set up is? Would be good to cross-reference to see if there's something different that's meaning you've got a speed boost.