First, I would like to note that this is not the same as RAW and non-RAW specific presets. In this case the preset does work with both RAW and JPG files, just not consistently.
A preset in certain scenarios will work ALL the time with a RAW but only works SOME of the time with a JPG
Create a preset using the following method
Select photo and do a RESET so no settings are applied Create a Preset called ZeroSaturation (I think this can be any slider) Save the preset with ONLY Saturation selected
Select photo Do a RESET Apply a Saturation that is not Zero Apply the ZeroSaturation Preset. (The Preset works with BOTH JPG and RAW) Apply Dehaze Apply Clarity Select Dehaze Apply the ZeroSaturation preset. (The Preset did NOT work the JPG)
History on RAW As you can see the preset works all the time on the RAW. When you execute the preset on the Dehaze step the history is cleared above Dehaze and the preset is executed and registered as a history step RackMultipart20180416440413cd4-5f066d73-1ba6-4b96-bdd4-d47d2bccf843-1796825975.jpg
History on JPG. As you can see the preset works on the JPG when the saturation is not zero but it does not not execute when the saturation is zero. When you select Dehaze and execute the preset the history above Dehaze is Not cleared and the preset is not registered in history. APPARENTLY NOTHING HAPPENS. RackMultipart201804164461eeyka-36ec5049-a1eb-4f05-8c94-c353e60d715d-131261697.jpg
I realize Saturation is already ZERO and the preset is not needed but the the behavior should be the same for both JPG and RAW and the preset should execute and be registered in history when pressed.. The JPG behavior is very disconcerting to the user because NOTHING happens.
Lightroom Classic CC 7.5 was released today and should address this issue. If you don’t see the update in your Creative Cloud App, hit the [Ctrl/Cmd]+ [Alt/Opt]+[R] to force a refresh.
Give the new version a try and let us know if it solves the issue.
Are you using Develop or Quick Develop to (Reset, Apply Preset)?
Quick Develop works - likely because the preset is only applied to one of the 3 images and it picks up the 2 unapplied images and leaves the Active alone.
Develop doesn't but I am betting it is as-designed behavior. You can't apply a preset to Active image twice. So essentially, you are doing nothing here when you apply the preset a second time.
Develop for all of them. I think if the original bug in this post has something to do with this behavior and is why I posted in this thread. I discovered this as I apply a preset in develop and if like the look I then select other photos by shift-click with auto sync on and immediately try to apply that preset. It used to work. Now I have to do a command-z to get rid of the preset in the most selected and then shift-click the others and then it works. Or just select the others. If the effect is subtile I may forget to do this.
Thanks for the clarification. can confirm the difference you explained between library and develop.
I can see what you are saying that this is designed behavior in the Develop module as the preset shouldn't be applied twice in a row but it is a surprising behavior when you first encounter it. With Autosync in Develop if the command isn't executed on the most selected than it won't apply to the other photos. I thought it used to work differently but maybe I am mistaken.
I still hope the original issue in this thread gets resolved. Any word on its resolution?
While working on the recent issue I noticed something in the history panel and command-z's I was doing that may help solve the ORIGINAL problem.
Create a preset called TEST that changes the Exposure
Select a photo
Apply preset. TEST. (Its added to History)
Add Contrast. (Its added to History)
Apply preset TEST (Its not added to History) (It appears to the user it didn't work!)
Add Highlights. (Its added to History)
Do an Undo. (popup says "Undo Highlights")
Do an Undo. (popup says "Undo preset TEST" although this step is not in History)
Do an Undo. (popup says "Undo Contrast)
It appears that the problem is that the second application of TEST is being correctly applied IF CHANGES ARE MADE IN HISTORY after the first application of TEST but the step is not recorded in History. Previous versions of Lightroom before Lr7 would record this in History. Not recording the step in history is what is disconcerting to the user and should be fixed.
I do agree that TEST should not be applied twice in a row but if an edit step is done after the first application of TEST is should apply AND BE RECORDED IN HISTORY a second time. It used to previous to Lr7