John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Tue, Oct 22, 2019 7:44 PM

Acknowledged

Lightroom Classic: Preset hover preview incorrect for Incremental Temperature / Tint

[This bug still exists in LR 10.0. See here for sample images to test with:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-preset-hover-preview-incorrect-for-incremental-temperature-tint/5f5f46154b561a3d4272bc43?commentId=5fc3e345ce4ce1357af23986]

The preview of a develop preset when hovering over it in the Presets panel is incorrect when the preset contains IncrementalTemperature and IncrementalTint values and the photo being edited is raw. To reproduce:

1. Open a non-raw in Develop and change Temp and Tint to +20.

2. Save a preset "Temp/Tint" with just White Balance checked.

3. Open a raw in Develop.

4. Hover the mouse over Temp/Tint and observe the change to the photo.

5. Click on Temp/Tint and observe there isn't any additional change to the photo (as expected).

6. Move the mouse pointer over the photo. Observe that the photo colors noticeably change.

7. Repeatedly move the mouse pointer back to over the Temp/Tint preset and then back over the photo and observe the change in colors.

Here's an example:

Original photo:
Image httpsd2r1vs3d9006apcloudfrontnets3_images1811476RackMultipart20191022-50813-e9a6bq-Untitled_inlinepng1571773220

Develop Loupe view with mouse hovering over Temp/Tint preset:

Develop Loupe view after applying Temp/Tint preset with mouse over photo:

Tested on LR 8.4.1 / Mac OS 10.14.6 and Windows 10.

See here for the original report:
https://community.adobe.com/t5/Lightroom-Classic/Issues-with-Preset-loupe-view-in-Lightroom/m-p/10683152#M160260

Here's another preset that exhibits similar symptoms, though it doesn't contain IncrementalTint/Temperature, but apparently only when applied to Canon EOS R raws:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-preset-hover-preview-incorrect-for-...

Responses

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

a year ago

Another person with the same problem: https://community.adobe.com/t5/Lightroom-Classic/Preset-different-look-between-navigator-and-developer/td-p/10608711

syd107

1 Message

•

60 Points

@John_R_Ellis

still having this problem. has there been a fix???

2 days ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

No fix yet. Adobe will update this bug report when there is.

2 days ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

a year ago

And two more people with the problem: https://community.adobe.com/t5/Lightroom-Classic/Issue-with-Temperature-and-Tint-When-Applying-Presets/td-p/10667438

karsten_tufts

2 Messages

•

78 Points

So this is my post.... Everything is the same as the OP stated except all of my files were in the RAW format. Glad the OP brought this to attention over here as it seems like its the better place to get these bugs resolved.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

"all of my files were in the RAW format"

Right, the bug appears to only strike when previewing a preset on raw files. But the preset must be originally made from a non-raw (or manually edited).

a year ago

karsten_tufts

2 Messages

•

78 Points

ahhh got ya. Thanks.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

a year ago

And another: https://community.adobe.com/t5/Lightroom-Classic/Preset-Bug-Lightroom-Creative-preset-problem-preset-glitch/m-p/10687285#M160442

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

a year ago

John, you don't mention this, but it appears this issue is only present on Mac systems. I'm using a Windows 10 version 1902 system and following your seven step procedure I do not see any change in rendering.

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Hmm, I observe the same incorrect behavior in my LR 8.4.1 / Windows 10. Can you post the contents of the preset's .xmp you created?

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

Created using a Canon 5D MKII JPEG file and applied to the same CR2 raw file shot raw+JPEG. Here you go:

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21        ">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">;
<rdf:Description rdf:about=""
    xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/";
   crs:PresetType="Normal"
   crs:Cluster=""
   crs:UUID="F9FD8EF470DFCA48A53C50BC8FC62329"
   crs:SupportsAmount="False"
   crs:SupportsColor="True"
   crs:SupportsMonochrome="True"
   crs:SupportsHighDynamicRange="True"
   crs:SupportsNormalDynamicRange="True"
   crs:SupportsSceneReferred="True"
   crs:SupportsOutputReferred="True"
   crs:CameraModelRestriction=""
   crs:Copyright=""
   crs:ContactInfo=""
   crs:Version="11.4.1"
   crs:WhiteBalance="Custom"
   crs:IncrementalTemperature="+20"
   crs:IncrementalTint="+20"
   crs:HasSettings="True">
   <crs:Name>
    <rdf:Alt>
     <rdf:li xml:lang="x-default">Temp & Tint +20</rdf:li>
    </rdf:Alt>
   </crs:Name>
   <crs:ShortName>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:ShortName>
   <crs:SortName>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:SortName>
   <crs:Group>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:Group>
   <crs:Description>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:Description>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Your preset causes the misbehavior in my LR 8.4.1 on both Windows 10 and Mac OS 10.14.6. So something else must account for the difference.

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

I checked it with CR2 files from Canon camera models 300D, 600D, 6D, and G9 X MKII and they all exhibit the issue! For some reason the Canon 5D MKII CR2 files don't display the issue. You can download 5D MKII CR2 files to test here: https://www.imaging-resource.com/PRODS/E5D2/E5D2THMB.HTM

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

I see the misbehavior with this sample Canon 5D MKII raw:
https://www.imaging-resource.com/PRODS/E5D2/E5D2FARI00050.CR2.HTM

But it's barely noticeable. Here's the Photoshop difference of the hover and non-hover previews:

Image: https://prod-content-care-community-cdn.sprinklr.com/579ad3b6-f7b1-4c16-a256-99ed28ff7b58/RackMultipart20191023681531n1w-236d7eac-7925-41d2-92e9-00c01ebb2e86-996066948.jpg1571870882

Image: https://prod-content-care-community-cdn.sprinklr.com/579ad3b6-f7b1-4c16-a256-99ed28ff7b58/RackMultipart20191023681531n1w-236d7eac-7925-41d2-92e9-00c01ebb2e86-996066948.jpg1571870882

I set the whitepoint in Levels to 10 -- thus, most of the differences in the red channel are 1, 2, or 3 (out of 255).

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

I wonder why the 5D MKII so much less pronounced compared to other camera models?

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

To answer that, I think we'd need to understand how IncrementalTemperature/Tint get applied to raw photos.

a year ago

a2zproductions

15 Messages

•

212 Points

a year ago

I made a video showing where the Bug is.
https://youtu.be/-gOiOzjgr6s

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

I think you're experiencing a different bug, or some variant of the one reported above. For the recipe I provided, in my configurations, changing the Profile from Adobe Color to another profile (e.g. Adobe Monochrome or Adobe Vivid) and then back to Adobe Color restores the appearance to that after applying the preset and moving the mouse off of the preset, not to the hover preview.

Can you please right-click that preset to show it in Finder, then edit the .xmp in TextEdit and copy and paste the contents here? I'd like to see what might account for the difference.

a year ago

a2zproductions

15 Messages

•

212 Points

It is the same behavior as the original post. When you hover over the preset everything looks normal until you select the preset and hover over the photo. The photo turns noticeably more red.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

But I don't observe what you observe with changing the profile from Adobe Color and back. That's why I'm wondering if there might be something different about the preset.

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

John, I can confirm if 'Treatment & Profile' is checked when creating the WB Develop Preset with a JPEG file the rollover issue is no longer present. Also when applying it to a raw file it does NOT change the Treatment or Profile settings. That appears to be the easiest fix for now.

Image: https://prod-content-care-community-cdn.sprinklr.com/579ad3b6-f7b1-4c16-a256-99ed28ff7b58/12383sspd1w_inline-6659fb18-b712-49f0-9de2-ef8d1892294a-950561500.jpg1571871073

Image: https://prod-content-care-community-cdn.sprinklr.com/579ad3b6-f7b1-4c16-a256-99ed28ff7b58/12383sspd1w_inline-6659fb18-b712-49f0-9de2-ef8d1892294a-950561500.jpg1571871073

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Hmm, I still see the misbehavior when Treatment & Profile is selected creating the preset. Here's the preset:

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21        ">
 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">;
  <rdf:Description rdf:about=""
    xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/";
   crs:PresetType="Normal"
   crs:Cluster=""
   crs:UUID="7555FE67FFDA49DB96C9097DFA1B697B"
   crs:SupportsAmount="False"
   crs:SupportsColor="True"
   crs:SupportsMonochrome="True"
   crs:SupportsHighDynamicRange="True"
   crs:SupportsNormalDynamicRange="True"
   crs:SupportsSceneReferred="True"
   crs:SupportsOutputReferred="True"
   crs:CameraModelRestriction=""
   crs:Copyright=""
   crs:ContactInfo=""
   crs:Version="11.4.1"
   crs:WhiteBalance="Custom"
   crs:IncrementalTemperature="+20"
   crs:IncrementalTint="+20"
   crs:ConvertToGrayscale="False"
   crs:CameraProfile="Embedded"
   crs:HasSettings="True">
   <crs:Name>
    <rdf:Alt>
     <rdf:li xml:lang="x-default">Temp/Tint +20, Profile</rdf:li>
    </rdf:Alt>
   </crs:Name>
   <crs:ShortName>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:ShortName>
   <crs:SortName>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:SortName>
   <crs:Group>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:Group>
   <crs:Description>
    <rdf:Alt>
     <rdf:li xml:lang="x-default"/>
    </rdf:Alt>
   </crs:Description>
   <crs:Look
    crs:Name=""/>
  </rdf:Description>
 </rdf:RDF>
</x:xmpmeta>

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

Hmm, I still see the misbehavior when Treatment & Profile is selected creating the preset.

My bad! I created a new JPEG develop preset instead of modifying the existing preset and it does exhibit the rollover shift with 'Treatment & Profile' checked.

a year ago

a2zproductions

15 Messages

•

212 Points

a year ago

It happens to random presets. I have 100s of presets I've created personally, some with Treatment & Profile checked and not checked. The fact is, it's a BUG that needs to be addressed. I've tried posting this elsewhere only to be reprimanded by the forum "Hall Monitors". I make a living using Lightroom and I've paid Creative Cloud monthly for years now. I just want to draw attention to the problem so I can get back to work without this BUG slowing my workflow to a crawl with my daily projects.

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Though there have been numerous reports of this bug on the user-to-user form for a while, unfortunately no one was advised to report it here.

But now that it's here, the more it can be narrowed down, the more likely Adobe will be to fix it sooner. Your video is a good demonstration of the problem. And if you upload the contents of one or two of your presets that exhibit this problem, then it will be more likely that your instance of the problem gets addressed. (I.e. if your problem isn't caused by IncrementalTemperature/Tint, and Adobe doesn't have any way to reproduce your problem, then it won't get fixed.)

a year ago

a2zproductions

15 Messages

•

212 Points

a year ago

As requested, here is the preset used in the Video I posted earlier in this thread that exhibits the color shifting after applying the preset Bug.

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">;
<rdf:Description rdf:about=""
xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/";
crs:PresetType="Normal"
crs:Cluster=""
crs:UUID="41498806AD2E4B4186FAFA3F06ED85AE"
crs:SupportsAmount="False"
crs:SupportsColor="True"
crs:SupportsMonochrome="True"
crs:SupportsHighDynamicRange="True"
crs:SupportsNormalDynamicRange="True"
crs:SupportsSceneReferred="True"
crs:SupportsOutputReferred="True"
crs:CameraModelRestriction=""
crs:Copyright=""
crs:ContactInfo=""
crs:Version="11.4.1"
crs:ProcessVersion="11.0"
crs:WhiteBalance="Custom"
crs:Temperature="5246"
crs:Tint="+3"
crs:Saturation="-8"
crs:Sharpness="52"
crs:LuminanceSmoothing="0"
crs:ColorNoiseReduction="25"
crs:VignetteAmount="0"
crs:ShadowTint="-9"
crs:RedHue="+5"
crs:RedSaturation="-24"
crs:GreenHue="+9"
crs:GreenSaturation="+5"
crs:BlueHue="-18"
crs:BlueSaturation="+45"
crs:Vibrance="+30"
crs:HueAdjustmentRed="+13"
crs:HueAdjustmentOrange="0"
crs:HueAdjustmentYellow="-5"
crs:HueAdjustmentGreen="-19"
crs:HueAdjustmentAqua="0"
crs:HueAdjustmentBlue="0"
crs:HueAdjustmentPurple="0"
crs:HueAdjustmentMagenta="0"
crs:SaturationAdjustmentRed="0"
crs:SaturationAdjustmentOrange="-24"
crs:SaturationAdjustmentYellow="-31"
crs:SaturationAdjustmentGreen="+6"
crs:SaturationAdjustmentAqua="0"
crs:SaturationAdjustmentBlue="+4"
crs:SaturationAdjustmentPurple="-100"
crs:SaturationAdjustmentMagenta="0"
crs:LuminanceAdjustmentRed="-8"
crs:LuminanceAdjustmentOrange="-15"
crs:LuminanceAdjustmentYellow="-1"
crs:LuminanceAdjustmentGreen="0"
crs:LuminanceAdjustmentAqua="0"
crs:LuminanceAdjustmentBlue="0"
crs:LuminanceAdjustmentPurple="0"
crs:LuminanceAdjustmentMagenta="0"
crs:SplitToningShadowHue="0"
crs:SplitToningShadowSaturation="0"
crs:SplitToningHighlightHue="69"
crs:SplitToningHighlightSaturation="12"
crs:SplitToningBalance="0"
crs:ParametricShadows="-18"
crs:ParametricDarks="+24"
crs:ParametricLights="0"
crs:ParametricHighlights="0"
crs:ParametricShadowSplit="25"
crs:ParametricMidtoneSplit="50"
crs:ParametricHighlightSplit="75"
crs:SharpenRadius="+1.0"
crs:SharpenDetail="25"
crs:SharpenEdgeMasking="0"
crs:PostCropVignetteAmount="-16"
crs:PostCropVignetteMidpoint="50"
crs:PostCropVignetteFeather="50"
crs:PostCropVignetteRoundness="0"
crs:PostCropVignetteStyle="1"
crs:PostCropVignetteHighlightContrast="0"
crs:GrainAmount="0"
crs:ColorNoiseReductionDetail="50"
crs:ColorNoiseReductionSmoothness="50"
crs:LensProfileEnable="1"
crs:LensManualDistortionAmount="0"
crs:PerspectiveVertical="0"
crs:PerspectiveHorizontal="0"
crs:PerspectiveRotate="0.0"
crs:PerspectiveScale="100"
crs:PerspectiveAspect="0"
crs:PerspectiveUpright="0"
crs:PerspectiveX="0.00"
crs:PerspectiveY="0.00"
crs:AutoLateralCA="1"
crs:Exposure2012="+0.90"
crs:Contrast2012="+51"
crs:Highlights2012="-100"
crs:Shadows2012="+43"
crs:Whites2012="+21"
crs:Blacks2012="-46"
crs:Clarity2012="+21"
crs:DefringePurpleAmount="0"
crs:DefringePurpleHueLo="30"
crs:DefringePurpleHueHi="70"
crs:DefringeGreenAmount="0"
crs:DefringeGreenHueLo="40"
crs:DefringeGreenHueHi="60"
crs:Dehaze="0"
crs:Texture="-26"
crs:OverrideLookVignette="True"
crs:ToneCurveName="Custom"
crs:ToneCurveName2012="Custom"
crs:LensProfileSetup="Custom"
crs:LensProfileName="Adobe (Sony FE 50mm F1.8)"
crs:LensProfileFilename="SONY (Sony FE 50mm F1.8) - RAW.lcp"
crs:LensProfileDigest="9AE4A323BA9A4C4460CE6BEF81D4F741"
crs:LensProfileDistortionScale="100"
crs:LensProfileChromaticAberrationScale="100"
crs:LensProfileVignettingScale="0"
crs:HasSettings="True"
crs:CropConstrainToWarp="0">
<crs:Name>
<rdf:Alt>
<rdf:li xml:lang="x-default">Gibson Silver</rdf:li>
</rdf:Alt>
</crs:Name>
<crs:ShortName>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:ShortName>
<crs:SortName>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:SortName>
<crs:Group>
<rdf:Alt>
<rdf:li xml:lang="x-default">Gibson Sisters</rdf:li>
</rdf:Alt>
</crs:Group>
<crs:Description>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:Description>
<crs:ToneCurve>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>32, 22</rdf:li>
<rdf:li>64, 56</rdf:li>
<rdf:li>128, 128</rdf:li>
<rdf:li>192, 196</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurve>
<crs:ToneCurvePV2012>
<rdf:Seq>
<rdf:li>0, 13</rdf:li>
<rdf:li>64, 65</rdf:li>
<rdf:li>174, 171</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012>
<crs:ToneCurvePV2012Red>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Red>
<crs:ToneCurvePV2012Green>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Green>
<crs:ToneCurvePV2012Blue>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Blue>
<crs:Look>
<rdf:Description
crs:Name="Adobe Color"
crs:Amount="1.000000"
crs:UUID="B952C231111CD8E0ECCF14B86BAA7077"
crs:SupportsAmount="false"
crs:SupportsMonochrome="false"
crs:SupportsOutputReferred="false"
crs:Stubbed="true">
<crs:Group>
<rdf:Alt>
<rdf:li xml:lang="x-default">Profiles</rdf:li>
</rdf:Alt>
</crs:Group>
</rdf:Description>
</crs:Look>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

As I suspected, this preset doesn't have IncrementalTemperature/Tint settings. I tried it on raws from several different cameras and didn't observe the bug. But I did observe the bug using this sample raw from the same camera you were using, a Canon EOS R. And I also observed that changing the profile from Adobe Color to Adobe Monochrome and back then changed Loupe view to match the hover-preset preview, as you did.

So there's something camera-specific about this preset, unlike the the one in my recipe.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

I updated the original post to include a link here. (Product developers sometimes don't carefully read the entire bug report and miss things.)

a year ago

a2zproductions

15 Messages

•

212 Points

You're Absolutely Right! I just checked the same preset with some files from my Sony A7 III, Canon 5DMK II & Canon 5D MK III. None of those cameras Raw files exhibit this behavior. So it's camera specific to the Canon EOS R.

a year ago

dennis_velai

4 Messages

•

94 Points

a year ago

There seems to be several more than just me that has this problem. Do we know how much of an effort it would take to fix the bug? and when we might expected to be fixed?

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

a year ago

I found at least 5 people reporting similar symptoms on the other forum. But so far, only you and I have clicked Me Too above. The number of Me Too's influences Adobe in prioritizing bugs (it's one of many factors).

Adobe rarely discloses much about bug fixes, unfortunately.

Rikk

Adobe Administrator

•

9.2K Messages

•

128K Points

a year ago

Before filing this bug I need additional information.

Workflow:

Select non-raw file and create preset containing relative WB slider adjustments.
Select raw file and mouse over preset created in step 1 - move over image area.
Apply preset

Result:

#2 & #3 produce visibly different results?
This visual difference extends to export as well?
Of the two, #2 or #3, which is correct or most correct?

Adobe Photography Products

Quality Engineering - Customer Advocacy

a2zproductions

15 Messages

•

212 Points

Rikk,
I just tried what you suggested. Since I shoot both RAW & JPG, I took 2 files from yesterday's shoot and dropped them into Lightroom. The JPG didn't experience the color shift after applying the preset. The RAW file shifted to red/orange as soon as I applied and hovered off of the preset panel. & Yes, the shift extends to export as well.

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

#2 & #3 produce visibly different results? YES

This visual difference extends to export as well? The export file looks like the raw when NOT hovering over the preset as expected.

Of the two, #2 or #3, which is correct or most correct? #3 is correct when not hovering over the preset

LR 8.4.1 on Windows 10 version 1902

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

With the IncrementalTemperature/Tint preset, #3 (Loupe view of the preset applied to a raw image) matches the appearance in LR 6.14 of a preset with the same settings applied to the same raw image.

That indicates that #3 is the long-standing behavior of such presets.

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

I did some more checking and the Temp & Tint preset does not change the raw file WB settings by an incremental amount. The WB settings are in fact set to a specific amount determined by the 0-100 Temp & Tint setting used when creating the JPEG preset. Using Temp and Tint settings of +20 produce fixed Temp 6477 and Tint +27 settings when applied to any raw file regardless of its WB setting. Using Temp & Tint 0 settings when creating the preset produce Temp 5001 and Temp +10 when applied to a raw file.

This is most likely not the user's intent when creating a JPEG preset with Temp & Tint settings so of little use when applied to to a raw file. In fact "relative" preset capability was requested nine years ago at the below post and still has not been implemented.

https://feedback.photoshop.com/photoshop_family/topics/relative_presets_would_save_the_day.

However, you can apply an "incremental" Temp & Tint adjustment in the Develop module to a raw file is by using a local adjustment as outlined at the below link.

https://feedback.photoshop.com/photoshop_family/topics/relative_presets_would_save_the_day?topic-rep...

a year ago

a2zproductions

15 Messages

•

212 Points

This is all getting a bit convoluted. The deal is, and I have confirmed this... Presets work perfectly normal on my Canon 5D MKII, Canon 5D MKIII, Canon 5D MKIV, & Sony A7 III Raw Files. When using the same exact preset on a Canon EOS R RAW file, the preset only looks normal when hovering over the preset in the preset panel then goes orange/red when the preset is applied and the mouse is no longer hovering over the preset panel. As someone who works exclusively in RAW, this Bug with the Canon EOS R Raw files is making my workflow slow to a crawl.

a year ago

a2zproductions

15 Messages

•

212 Points

*UPDATE* I just discovered that the problem seems to be isolated to the Adobe Raw Profiles only. If I use any of the Adobe Raw profile to create my preset the behavior is shift in color orange/red when hovering off the preset panel. If I chose another Profile such as Camera Standard, Legacy Camera Neutral, everything functions properly. Make sense? This just in, I heard from a friend that it is happening on the Nikon D750 as well. hmmmmm.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

a year ago

Rikk,

a2zproductions' preset problems have somewhat different details from the recipe I posted: the problem preset doesn't contain IncrementalTemperature/Tint, it seems to apply only to one camera (Canon EOS R), and it appears limited to just Adobe profiles.

Would you prefer to fork it into a separate topic or leave it here? I updated the original post to include a link to his subthread here, but it might get lost in the noise...

a2zproductions

15 Messages

•

212 Points

It's happening on the Nikon D750 as well.

a year ago

robert_somrak

Champion

•

902 Messages

•

14.8K Points

Unlike a2zproductions the issue happens on my Canon 5dMkII but the effect is very subtle

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Which preset causes the issue on the 5D MKII, the IncrementalTemperature/Tint preset or a2z's preset?

a year ago

robert_somrak

Champion

•

902 Messages

•

14.8K Points

Sorry, its the Incremental Temperature/Tint preset so not the same as a2zs issue

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

I can confirm the rollover color shift after applying a2zproductions preset to a Canon EOS R CR3 file, but not with a Nikon D750 NEF or Canon 5D MKII.

a year ago

Rikk

Adobe Administrator

•

9.2K Messages

•

128K Points

John, If we have two distinct issues here that do not overlap we should probably fork that topic. It will make things more actionable for writing bugs and reporting to the Lightroom Classic team.

Adobe Photography Products

Quality Engineering - Customer Advocacy

a year ago

todd_shaner_6660895

Champion

•

2.3K Messages

•

38K Points

Rikk, the incremental WB Temp & Tint preset issue (i.e. created with JPEG and applied to raw) appears to affect all camera models.
The second example preset https://console.getsatisfaction.com/photoshop_family/conversations/lightroom-preset-hover-preview-in... created with a Sony ARW raw file contains actual (i.e. relative) Temp and Tint values. I only see the rollover issue when it is applied to EOS R CR3 raw files. The only "camera specific" setting in that preset is the Sony lens profile. This should have no affect on color rendering so it appears this issue is unique to the Canon EOS R camera.
The actual root cause may be related, but from my testing the second preset issue using relative WB Temp & Tint settings is clearly Canon EOS R camera specific.

a year ago

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Perhaps its best to keep one topic for now, since the symptoms overlap -- the preset hover preview doesn't match the applied preview -- though some of the details are different.

a year ago

a2zproductions

15 Messages

•

212 Points

a year ago

The issues still happens using a preset containing a Canon Lens Profile applied to an EOS R CR3 Raw file. I am convinced the problem lies in "Adobe Color" in the Profile section as this shift does not happen if another Profile such as "Camera Standard" is chosen and saved into a preset. Below is the preset with the Canon Lens Profile that still exhibits the color shift/hover behavior:

<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">;
<rdf:Description rdf:about=""
xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/";
crs:PresetType="Normal"
crs:Cluster=""
crs:UUID="743B22F3B80D458BBA108F2568470BF8"
crs:SupportsAmount="False"
crs:SupportsColor="True"
crs:SupportsMonochrome="True"
crs:SupportsHighDynamicRange="True"
crs:SupportsNormalDynamicRange="True"
crs:SupportsSceneReferred="True"
crs:SupportsOutputReferred="True"
crs:CameraModelRestriction=""
crs:Copyright=""
crs:ContactInfo=""
crs:Version="11.4.1"
crs:ProcessVersion="11.0"
crs:WhiteBalance="Custom"
crs:Temperature="5246"
crs:Tint="+3"
crs:Saturation="-8"
crs:Sharpness="52"
crs:LuminanceSmoothing="0"
crs:ColorNoiseReduction="25"
crs:VignetteAmount="0"
crs:ShadowTint="-9"
crs:RedHue="+5"
crs:RedSaturation="-24"
crs:GreenHue="+9"
crs:GreenSaturation="+5"
crs:BlueHue="-18"
crs:BlueSaturation="+45"
crs:Vibrance="+30"
crs:HueAdjustmentRed="+13"
crs:HueAdjustmentOrange="0"
crs:HueAdjustmentYellow="-5"
crs:HueAdjustmentGreen="-19"
crs:HueAdjustmentAqua="0"
crs:HueAdjustmentBlue="0"
crs:HueAdjustmentPurple="0"
crs:HueAdjustmentMagenta="0"
crs:SaturationAdjustmentRed="0"
crs:SaturationAdjustmentOrange="-24"
crs:SaturationAdjustmentYellow="-31"
crs:SaturationAdjustmentGreen="+6"
crs:SaturationAdjustmentAqua="0"
crs:SaturationAdjustmentBlue="+4"
crs:SaturationAdjustmentPurple="-100"
crs:SaturationAdjustmentMagenta="0"
crs:LuminanceAdjustmentRed="-8"
crs:LuminanceAdjustmentOrange="-15"
crs:LuminanceAdjustmentYellow="-1"
crs:LuminanceAdjustmentGreen="0"
crs:LuminanceAdjustmentAqua="0"
crs:LuminanceAdjustmentBlue="0"
crs:LuminanceAdjustmentPurple="0"
crs:LuminanceAdjustmentMagenta="0"
crs:SplitToningShadowHue="0"
crs:SplitToningShadowSaturation="0"
crs:SplitToningHighlightHue="69"
crs:SplitToningHighlightSaturation="12"
crs:SplitToningBalance="0"
crs:ParametricShadows="-18"
crs:ParametricDarks="+24"
crs:ParametricLights="0"
crs:ParametricHighlights="0"
crs:ParametricShadowSplit="25"
crs:ParametricMidtoneSplit="50"
crs:ParametricHighlightSplit="75"
crs:SharpenRadius="+1.0"
crs:SharpenDetail="25"
crs:SharpenEdgeMasking="0"
crs:PostCropVignetteAmount="-16"
crs:PostCropVignetteMidpoint="50"
crs:PostCropVignetteFeather="50"
crs:PostCropVignetteRoundness="0"
crs:PostCropVignetteStyle="1"
crs:PostCropVignetteHighlightContrast="0"
crs:GrainAmount="0"
crs:ColorNoiseReductionDetail="50"
crs:ColorNoiseReductionSmoothness="50"
crs:LensProfileEnable="1"
crs:LensManualDistortionAmount="0"
crs:PerspectiveVertical="0"
crs:PerspectiveHorizontal="0"
crs:PerspectiveRotate="0.0"
crs:PerspectiveScale="100"
crs:PerspectiveAspect="0"
crs:PerspectiveUpright="0"
crs:PerspectiveX="0.00"
crs:PerspectiveY="0.00"
crs:AutoLateralCA="1"
crs:Exposure2012="+0.90"
crs:Contrast2012="+51"
crs:Highlights2012="-100"
crs:Shadows2012="+43"
crs:Whites2012="+21"
crs:Blacks2012="-46"
crs:Clarity2012="+21"
crs:DefringePurpleAmount="0"
crs:DefringePurpleHueLo="30"
crs:DefringePurpleHueHi="70"
crs:DefringeGreenAmount="0"
crs:DefringeGreenHueLo="40"
crs:DefringeGreenHueHi="60"
crs:Dehaze="0"
crs:Texture="-26"
crs:OverrideLookVignette="True"
crs:ToneCurveName="Custom"
crs:ToneCurveName2012="Custom"
crs:LensProfileSetup="Custom"
crs:LensProfileName="Adobe (Canon EF 24-70mm f/2.8 L USM)"
crs:LensProfileFilename="Canon EOS-1Ds Mark III (Canon EF 24-70mm f2.8 L USM) - RAW.lcp"
crs:LensProfileDigest="E54C41E7B7D49594FF5E60B650754194"
crs:LensProfileDistortionScale="0"
crs:LensProfileChromaticAberrationScale="100"
crs:LensProfileVignettingScale="0"
crs:HasSettings="True"
crs:CropConstrainToWarp="0">
<crs:Name>
<rdf:Alt>
<rdf:li xml:lang="x-default">Gibson Silver Canon Lens Profile</rdf:li>
</rdf:Alt>
</crs:Name>
<crs:ShortName>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:ShortName>
<crs:SortName>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:SortName>
<crs:Group>
<rdf:Alt>
<rdf:li xml:lang="x-default">Gibson Sisters</rdf:li>
</rdf:Alt>
</crs:Group>
<crs:Description>
<rdf:Alt>
<rdf:li xml:lang="x-default"/>
</rdf:Alt>
</crs:Description>
<crs:ToneCurve>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>32, 22</rdf:li>
<rdf:li>64, 56</rdf:li>
<rdf:li>128, 128</rdf:li>
<rdf:li>192, 196</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurve>
<crs:ToneCurvePV2012>
<rdf:Seq>
<rdf:li>0, 13</rdf:li>
<rdf:li>64, 65</rdf:li>
<rdf:li>174, 171</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012>
<crs:ToneCurvePV2012Red>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Red>
<crs:ToneCurvePV2012Green>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Green>
<crs:ToneCurvePV2012Blue>
<rdf:Seq>
<rdf:li>0, 0</rdf:li>
<rdf:li>255, 255</rdf:li>
</rdf:Seq>
</crs:ToneCurvePV2012Blue>
<crs:Look>
<rdf:Description
crs:Name="Adobe Color"
crs:Amount="1.000000"
crs:UUID="B952C231111CD8E0ECCF14B86BAA7077"
crs:SupportsAmount="false"
crs:SupportsMonochrome="false"
crs:SupportsOutputReferred="false"
crs:Stubbed="true">
<crs:Group>
<rdf:Alt>
<rdf:li xml:lang="x-default">Profiles</rdf:li>
</rdf:Alt>
</crs:Group>
</rdf:Description>
</crs:Look>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>

dennis_velai

4 Messages

•

94 Points

a year ago

So, is Adobe going to fix this bug or are they hoping that no one will notice?

John_R_Ellis

Champion

•

5.5K Messages

•

97.5K Points

Based on past experience, it takes at least 1, usually 2, release cycles for an acknowledged bug to get fixed. But many bugs take much longer, and many more never get fixed. (LR releases about once every two months.) Adobe rarely says when bugs will be fixed, so we just have to wait.

a year ago

dennis_velai

4 Messages

•

94 Points

Oh, thats very uninspiring. Any tips to get around the problem? Since right now i can't edit photos since im fully reliant on presets.

Thank you in advance.

a year ago

smit_k

Employee

•

294 Messages

•

7.8K Points

a year ago

We have logged a bug for this.

dennis_velai

4 Messages

•

94 Points

Thank you.

I hope you can solve this quick.

a year ago

a2zproductions

15 Messages

•

212 Points

a year ago

An Update was released today. The BUG is NOT FIXED! It is the same as it ever was. Here goes 6 more months of dealing with this.

John_R_Ellis

Lightroom Classic: Preset hover preview incorrect for Incremental Temperature / Tint

Responses

John_R_Ellis

syd107

John_R_Ellis

John_R_Ellis

karsten_tufts

John_R_Ellis

karsten_tufts

John_R_Ellis

todd_shaner_6660895

John_R_Ellis

todd_shaner_6660895

John_R_Ellis

todd_shaner_6660895

John_R_Ellis

todd_shaner_6660895

John_R_Ellis

a2zproductions

John_R_Ellis

a2zproductions

John_R_Ellis

todd_shaner_6660895

John_R_Ellis

todd_shaner_6660895

a2zproductions

John_R_Ellis

a2zproductions

John_R_Ellis

John_R_Ellis

a2zproductions

dennis_velai

John_R_Ellis

Rikk

a2zproductions

todd_shaner_6660895

John_R_Ellis

todd_shaner_6660895

a2zproductions

a2zproductions

John_R_Ellis

a2zproductions

robert_somrak

John_R_Ellis

robert_somrak

todd_shaner_6660895

Rikk

todd_shaner_6660895

John_R_Ellis

a2zproductions

dennis_velai

John_R_Ellis

dennis_velai

smit_k

dennis_velai

a2zproductions

Helpful Widget

Tags