• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

P: Issues when applying presets with custom curves 13.3

Explorer ,
May 22, 2024 May 22, 2024

Copy link to clipboard

Copied

I've posted this as a comment in another bug, but thought it would be best, to open a seperate issue.

My Problem is the Following:

Since the Update to 13.3, applying presets to an unedited picture in the develop tab randomly does not affect the custom curve saved within that preset. Also the preset is not shown as applied, so I can't change the intensity of the preset. When I change to another picture and then back to the one I applied the preset to, the correct curve is shown, but has no effect on the image. I need to manually change the curve a little bit, and wooosh it's applied. Another option is to apply a different preset and then switch back to the one, I wanted to apply in the first place. I have had performance issues (RAM leaking, slow downs etc) for years and it's annoying, but at least I can get rid of those by restarting every 30 or so minutes. But this just slows me down so much it's painfull.

For reference, I've attached 2 Screenshots. This right here is how the picture and the UI looks after applying a preset:

Lightroom Bug1.PNG

As you can see, color changes ETC are applied, but the Curves are not affected and the "Amoiunt" Slider is grayed out, even thou the preset was applied.

Next I applied another preset and then this preset again. This is how it looks:

Lightroom Bug2.PNG

As you can see, now the Curves where applied correctly and the amount slider is back. This is how it always was and how it's supposed to be. It doesn't always happen, but it does happen in like 70-80% of cases right now, so not something I can just ignore. Not sure if this is something, that other people are experiencing, but I hope, somebody has an idea how to fix it. Until then, I'll roll back to 13.2 .

 

What I've tried so far and did not work:

  • Reinstall
  • Optimize cataloge
  • Export Presets, delete them in lightroom and re-import them
  • Create a new cataloge
  • Cleanse the Cache

 

 

Here are my System Infos (Minus Personal Info):

 

Lightroom Classic version: 13.3 [ 202405092057-40441e28 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19045
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3,6GHz
SqLite Version: 3.36.0
CPU Utilisation: 1,0%
Power Source: Plugged In, 255%
Built-in memory: 32692,9 MB
Dedicated GPU memory used by Lightroom: 5815,3MB / 12011,0MB (48%)
Real memory available to Lightroom: 32692,9 MB
Real memory used by Lightroom: 6854,8 MB (20,9%)
Virtual memory used by Lightroom: 14316,0 MB
GDI objects count: 1181
USER objects count: 4091
Process handles count: 3036
Memory cache size: 3255,4MB
Internal Camera Raw version: 16.3 [ 1863 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1759MB / 16346MB (10%)
Camera Raw real memory: 2030MB / 32692MB (6%)

<deleted>

Bug Fixed
TOPICS
Windows

Views

2.3K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 26, 2024 Jun 26, 2024

Hi @felixb62617238 ,

We have attempted a fix for this issue in the latest 13.4 release. Can you please try the same and let us know?

Thanks,

Arjun

Votes

Translate

Translate

correct answers 1 Pinned Reply

Adobe Employee , Jun 27, 2024 Jun 27, 2024

Fixed in 13.4

Status Fixed

Votes

Translate

Translate
27 Comments
Adobe Employee ,
Jun 26, 2024 Jun 26, 2024

Copy link to clipboard

Copied

@felixb62617238 ,

Glad to hear that the issue is fixed. Thanks for confirming!

 

Thanks,

Arjun

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 27, 2024 Jun 27, 2024

Copy link to clipboard

Copied

LATEST

Fixed in 13.4

Status Fixed

Votes

Translate

Translate

Report

Report