Skip to main content
Participating Frequently
June 17, 2019
Open for Voting

Lightroom Classic: Add to API: LrDevelopController.quickDevelopAdjustImage smallDecrease and largeDecrease

  • June 17, 2019
  • 5 replies
  • 437 views
The new quickDevelopAdjustImage can use the parameters 'small' and 'large' which are aligned with some of the Quick Develop buttons. However, those are only for INCREASING the values. There are no parameters for the Quick Develop buttons that DECREASE the values. This severely limits usefulness of quickDevelopAdjustImage.

Request: Add parameters that are aligned with the Quick Develop DECREASE buttons.

5 replies

Community Manager
December 2, 2019
Im praying for you to resolve this matter. I have been waiting to use the complete Quick Develop module with my midi controller for a long time!! haha

Thanks for all
johnrellis
Brainiac
November 7, 2019
Some reverse engineering reveals how to use the photo:quickDevelop* methods to behave like the <<, <, >, and >> buttons in the Quick Develop panel.

photo:quickDevelopAdjustWhiteBalance ("Temperature", n)
photo:quickDevelopAdjustWhiteBalance ("Tint", n)

With n = -5 or 5, these settings increase or decrease the same amount as using the < and > buttons. With n = -20 and 20, they change the same amount as using the << and >> buttons.

photo:quickDevelopAdjustImage ("Exposure", n)

With n = -16.5 or 16.5, Exposure increases or decreases the same amount as using the < and > buttons. With n = -50 or 50, Exposure changes the same amount as using the << and >> buttons.

photo:quickDevelopAdjustImage (setting, n)

For "setting" equal to one of "Contrast", "Highlights", "Shadows", "Whites", "Blacks", "Clarity", and "Vibrance": With n = -5 or 5, the settings increase or decrease the same amount as using the < and > buttons. With n = -20 or 20, they change the same amount as using the << and >> buttons.

* * * 

With all of these, when the settings reach their minimum or maximum value, further attempts to decrease or increase them leave them at the minimum/maximum, just like the <<, <, >, and >> buttons.

And of course, this should all be documented.  


Participating Frequently
October 26, 2019
Adobe development should stop 'consider' fixing basic programming errors and go actually work for the money your professional customers are paying you. There is nothing to consider.

Customer: This new car only steers to the right, can you fix it?
Adobe: well we consider it, but you can always drive in circels....
Participating Frequently
June 25, 2019
Right, but in the Library module, you can't check ranges for an adjustment, and different file types have different ranges, so using a number is problematic. Also, not having small/large for decreases misses the benefit of small/large for increases, as a person adjusting a photo would want the ability to overshoot an adjustment and move it back down by the same increment.
bhargaveede
Adobe Employee
Adobe Employee
June 21, 2019
Hi Rory,

Thanks for sharing the feedback.
We'll consider it.
However, Once can use LrDevelopController.quickDevelopAdjustImage (settingName, size) with a negative number for size to decrease the values.

Thanks,
Bhargav