Apply (copy) layer with LUMA RANGE eats up memory and performs poorly

Hi.

C1 version 13.1.3.13

I noticed that when I copy and apply a layer (with a mask with 30-50% image coverage) with a Luma range defined, C1 ramps up memory usage quite significantly, and shows a very poor performance.

50 images

To be precise, I could not apply this layer to 50 Nikon Z7 images on my Dell XPS-13 7390 2-1 with 16 GB RAM (which is used for both the CPU and integrated GPU). Win10 Home build 19403.

Task manager memory usage ramps up slowly from 6 GB until 15.7 GB, CPU and GPU are both running in the upper third, after several minutes I stopped (because the C1 activities bar almost staled after roughly 1/3 of the images).

20 images

I then tried with 20 images (after a restart) and the ramp started again around 6 GB and ended around 12 GB, but the performance was very very poor though.

Re-generating the preview files for the 20 images, which are having the layer with mask and luma range now, (again, after a restart of C1) was much quicker though, and additional memory increase was reasonable (1.5 - 2 additional GB).

Without the Luma range, apply (only a layer with the mask) is done in about 10 sec..

Conclusion: The apply (copy) of a layer mask WITH Luma Range has a severe memory and performance issue.

Can anyone confirm or falsify this issue?

Thanks and cheers
BeO

ilias Pezouvanis

17. Januar 2023 22:03

I noticed that copy and apply adjustments from one image with layers with mask and luma range to multiple images doesn't work automatically
Every layer is copied with all properties OK opacity and mask from the original image but not the applied luma range only the values that makes unmatched mask when areas of the image are different like clouds in the sky
lets say you have linear gradient mask for the sky and luma range so you mask only the clouds the mask will be in the same position in every image unless you go to each file one by one every layer and open the luma range dialog again it will process again and apply. its a bug that need to be fixed I guess
It will be a powerful tool for time lapses with hundreds of images that need to have flexible masking option

Kommentare