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

[John R Ellis]

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:

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

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}, 

[Rikk Flohr: Photography]

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

[Rikk Flohr: Photography]

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.

[John R Ellis]

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

[John R Ellis]

Somewhere between 13.1 and 13.4 this actually got fixed.