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

P: SDK: photo:applyDevelopSettings() truncates the HDR region of tone curves

LEGEND ,
Oct 20, 2023 Oct 20, 2023

Copy link to clipboard

Copied

The SDK method photo:applyDevelopSettings() truncates the HDR region of tone curves stored in the setting ExtendedToneCurvePV2012. This affects my Copy Settings, Any Crop, and Export LUT plugins, and I'm sure there are many others affected.

 

1. Download this catalog, which includes two test pics:

https://www.dropbox.com/scl/fi/bp4qudliz6x0f2q02boux/extendedtonecurve-bug.2023.10.20.zip?rlkey=7w0y...

 

2. From the catalog folder, install "extendedtonecurve-bug.lua" in the Scripts folder.

 

3. Open the catalog in LR.

 

4. Do Scripts > extendedtonecurve-bug, which uses photo:getDevelopSettings() and :applyDevelopSettings() to copy all settings from 1.CR2 to 2.NEF.

 

5. Observe that the tone curve of 1.CR2 is:

johnrellis_0-1697831158248.png

 

while the tone curve of 2.NEF is truncated in the HDR region:

johnrellis_1-1697831270051.png

 

6. Use the Show Catalog Metadata plugin to see that the ExtendedToneCurvePV2012 setting of 1.CR2 has been truncated in 2.NEF:

 

1.CR2:

 

 

    ExtendedToneCurvePV2012 = {--table: 2
        [1] = 0, 
        [2] = 0, 
        [3] = 149, 
        [4] = 88, 
        [5] = 255, 
        [6] = 255, 
        [7] = 302, 
        [8] = 344, 
        [9] = 448, 
        [10] = 473}, 

 

 

 

2.NEF:

 

 

    ExtendedToneCurvePV2012 = {--table: 2
        [1] = 0, 
        [2] = 0, 
        [3] = 149, 
        [4] = 88, 
        [5] = 255, 
        [6] = 255}, 

 

 

 

 

Bug Fixed
TOPICS
SDK

Views

758

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 2 Pinned Replies

Adobe Employee , Oct 20, 2023 Oct 20, 2023

I've logged this John. We will see what the team responds.

Status Investigating

Votes

Translate

Translate
Adobe Employee , Dec 13, 2023 Dec 13, 2023

Greetings all,

 

Updates for the Adobe Photography Products have been released.  The December 2023 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

 

Thank you for your patience.

Status Fixed

Votes

Translate

Translate
4 Comments
Adobe Employee ,
Oct 20, 2023 Oct 20, 2023

Copy link to clipboard

Copied

I've logged this John. We will see what the team responds.

Rikk Flohr - Customer Advocacy: Adobe Photography Products
Status Investigating

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 13, 2023 Dec 13, 2023

Copy link to clipboard

Copied

Greetings all,

 

Updates for the Adobe Photography Products have been released.  The December 2023 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

 

Thank you for your patience.

Rikk Flohr - Customer Advocacy: Adobe Photography Products
Status Fixed

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 14, 2023 Dec 14, 2023

Copy link to clipboard

Copied

@Rikk Flohr: Photography, I still see the same incorrect behavior in LR 13.1 with the bug recipe.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 04, 2024 Jul 04, 2024

Copy link to clipboard

Copied

LATEST

Somewhere between 13.1 and 13.4 this actually got fixed.

Votes

Translate

Translate

Report

Report