Jeffrey’s “Bulk Develop Settings” Lightroom Plugin

This plugin for Adobe Lightroom Classic allows you to apply certain noise-related develop settings automatically, in bulk, based upon the camera that created each image, and each image's ISO sensitivity and Lightroom exposure boost.

This plugin works in Lightroom Classic, and older versions as far back as Lightroom 3 (though some features depend on the version of Lightroom).

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

How To Use

Most people will find it most convenient to apply bulk settings immediately after import, and/or after a rough exposure-adjustment pass through just-imported files.

Select the photos you want to bulk adjust, then invoke:

File > Plugin Extras > Apply Bulk Develop Settings

and you'll get a dialog along the lines of:

(screen shot as of plugin version 20150103.48)

That's a really busy, densely-packed dialog (sorry), so let's look at the top a bit closer.

Most of the dialog presents your bulk-develop configuration for a single camera, with tabs along the top letting you choose which camera's config is shown:

Only the configurations for cameras used for photos selected when the dialog is invoked are shown, though the plugin will remember your settings for all configurations over time.

Raw photos (including DNGs) have a separate configuration from JPGs and other non-raw photos. In the example above, two Nikon D4 configuration tabs appear because both raw (NEF) and JPGs from a Nikon D4 were selected.

The entire camera-specific configuration can be enabled or disabled with the checkbox at the top of the configuration.

The configuration itself has five different parts, one for each kind of develop control the plugin can update:

  1. Luminance Noise Reduction
  2. Color Noise Reduction
  3. Sharpening Mask
  4. Contrast
  5. Clarity

Each is configured in the same manner which is why the closeup above only bothers to show the first.

Note: on smaller screens, a less verbose presentation is used for all sections other than the first, to allow everything to fit. The initial screenshot above is an example. Though the presentation is less wordy and descriptive, the meaning of each dialog component remains the same.

In any case, though each control is configured in the same manner, your develop needs and tastes will likely mean that the values you enter differ from control to control.

If you've enabled the only when at its default value option, a control won't be touched by the plugin if it's not at its default value. The intention is to leave prior changes alone.

If a develop control is to be updated, its new value is computed from three things: the ISO speed value used by the camera during capture, and any Exposure and optionally Shadows added in post processing within Lightroom.

For the ISO part...

... you give a pair of ISO values that define an ISO range, and a pair of control values (in the example above, luminance noise reduction values) that define a range to use for the develop setting.

Photos with ISOs less than the lower end of the ISO range don't get any ISO-related develop-control change. Photos with an ISO above the upper end of the range get the maximum of the control-value range. Any ISO value in between gets a control value from the control range.

Then, on top of that, any in-Lightroom exposure compensation or Shadows can add additional control strength.

Setting Recommendations

Configuring the plugin settings for any particular camera involves perhaps more of an artistic sense than a technical one, but I'll offer some general suggestions you might use as a starting point, for when you haven't yet built up a sense of what you want for any specific camera.

To be clear, be sure to understand that my suggestions are certainly based on my own personal artistic sense, and that these suggestions are being made by someone who is an expert in Lightroom plugin design, and not by someone who is an expert in photography or photo development. 😉

Because the plugin bases its calculations on the ISO value for each image, the settings must be configured with an understanding of the ISO range of the sensor. As an example camera, I'll use the Nikanon-Sontax Turbo-Encabulator 7sX, which has a nominal ISO range of 100〜6400, but with boost can go to 25600, but practically speaking, noise starts to show up noticeably in normal lighting at about 3200:

sample settings

With the top section, I've configured it to put at least a little luminance noise reduction (5) for all images, topping out at 50 for ISO 4000 and above. The "4000" here is very dependent on the sensor and how noisy it is at high ISO, so for your own settings at least look at the stated nominal range of your camera's sensor. If you don't yet have a sense of how the sensor behaves, a good starting point here might be about ⅔ of the nominal top ISO.

Color noise reduction gets a much less heavy hand, as Lightroom's default seems to be pretty good to me, and in cases it's not, I feel it's something that needs to be tweaked carefully by hand.

Personally, I'm a fan of the sharpening mask, which disables sharpening in low-detail areas where noise shows up more readily, such as clear sky, so the sample configuration above reflects that with a fairly aggressive value (50) even at a low ISO of 1000.

I don't personally use the Contrast or Clarity sections.

I said before, the settings are highly dependent on the camera and your personal taste, so if you use these settings as a starting point, be sure to play around and experiment.


A discussion of (a prior version of) this plugin in a pro-photographer workflow is seen at sidecar: post in “Parameter Based Noise Reduction – Part 1”.


This plugin is distributed as “donationware”. I have chosen to make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks.

Registration is done via PayPal, and if you choose to register, it costs the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's sliding fees as a gift to me is completely optional, and completely appreciated.

Note: a Lightroom major upgrade, such as from Lr10 to Lr11 de-registers the plugin in the upgraded version, so if you want to maintain registration, a new ($0.01 if you like) registration code is needed in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.

For details on plugin registration and on how I came into this hobby of Lightroom plugin development, see my Plugin Registration page.

Version History
( Update Log via RSS )

20231015.80 Updates to support the new Process Version 6.

More short-dialog work.


Reformulated the dialog to be even shorter in short-dialog mode.


Clean up unneeded working files that might have been left by the plugin having been run with extra debug logging.


Whack-a-mole with PayPal's random changes.


Warn when PayPal seems to have given a bogus code in the web-confirmation page.

working around 'constant table overflow' error


Updates for Lr10.


Added some extra debug logging.


Work around a bug in Lr9.3 that wipes out local adjustments.

Work around a Windows bug related to canceling out of the registration dialog.


Fixed a "comparison with nil value" bug.


Added "Texture" for Lr8.3 and above.

Try to squeze the dialog down to fit on smaller screens.

Added some extra debug logging to note whether the plugin is enabled.


Updates for Lr9 (Lightroom Classic CC Version 9).


Updates for Lr8 (Lightroom Classic CC Version 8).


Added some extra debug logging.


Build optimization.


Clicking on the version number in the Plugin Manager now copies version info to the clipboard


Added a bunch of debug logging.


Oops, more Lr7 stuff.


Updates for Lightroom 7


Added some debug logging.

Update registration support to handle a stupid bug at PayPal that PayPal refuses to fix )-:


Minor build update.


Add some extra debug logging.


Oops, previous update about merged DNGs was too aggressive... skip only HDR DNGs (don't skip merged DNGs that are panos).


Try to make the dialog fit more screens... something seems up lately with how Lightroom reports retina screens to the plugin, so this is sort of a blind fix.

Added an option to skip merged DNGs, and turned it on by default.

20161231.56 Added extra screen-size debug logging
20160402.55 Allow larger ISO-sensitivity values.
20160401.54 Shift into short-screen mode a bit more aggressively.

Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.


Added an option for a hard-upper-limit cap to the settings, so that values are never set beyond them.


In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.


There was a bug in the computation related to how increased shadow effected settings.

Allowed the Ev/shadow-related adjustments to be percent based.


Throw everything into a scrollable view on really short screens.


If an image didn't have an ISO speed value, the Ev-related items wouldn't be applied. They are now, independently.

Redesigned the dialog, and gave each of the controls (luminance noise reduction, color noise reduction, and masking) its own ISO range.

Added the ability to update the contols depending on the amount of negative shadow applied.

Added the ability to update Contrast and Clarity as well.

20150107.47 Build update.
20141019.46 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20140902.45 New build system
20140731.44 Registration fix for Lr5.6
20140720.43 More Creative-Cloud support.

Fixed an issue with Creative-Cloud revalidation.


Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.40 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.38 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.37 Build-system update
20140521.36 Added the ability to isolate updated/unmodified images to a collection

Fixed a bug in the "smoother revalidation" stuff recently added.


Make the revalidation process smoother, especially for folks using Lr5.4 and later.

20140216.33 Squelch an error that popped up if you canceled the import-settings dialog.
20131014.32 Found that with certain settings some math errors would pop up.
20130704.31 Added the ability to set/clear keywords based upon bulk-develop processing.
20130613.30 Better support for plugin revalidation.
20130611.29 Yet another Lr5 update
20130610.28 Final update for Lr5
20130501.27 Update for Lr5
20130412.26 Build system update.
20130328.25 Fix for the registration system.
20130316.24 Switched ISO interpolation to logarithmic, which should provide for more-balanced results. Linear interpolation, which the plugin used to do, is still available as an option.
20130209.23 More build-system maintenance
20130206.22 Tweak for my registration system
20130201.20 Update to my plugin build system.

Holy cow, discovered a bug (thanks Cody Sims!) that could cause appropriate bulk settings not to be updated, depending on what order what settings needed to be applied. This was a huge bug with a major impact on some kinds of shots... I can't believe that I never noticed this one myself... I use this plugin myself with every photo I take. Just dumbfounded, but glad it's fixed.


The plugin was leaving cruft in one's "Plugin Develop Presets" folder; now cleans it up.


Update to handle the Mac App Store version of Lightroom.

Tweak for Lr4.1RC2.


In Lr4, images with PV2012 were being processed with the Exposure from the prior process version. Doh!

Added the ability to export and import settings.

Enhanced the send-log dialog to hopefully make reports more meaningful to me, yielding, I hope, the ability to respond more sensibly to more reports.

20120330.15 Update to handle 4.1RC
20120309.14 Update to the debug logging to better track down timing issues that might arise.

More updates for Lr4.


More updates for Lr4.


Add a bit of bullet-proofing against corrupt catalogs.

More on the march toward Lr4, including upheaval in the code to handle Lightroom APIs being discontinued in Lr4.

20120119.10 added some extra debug logging to try to track down a bug.
20120114.9 More tweaks for Lr4b

Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.


Had issues with the registration button sometimes not showing.

20111201.6 Fixed the bug I was trying to track down with the previous version. As best I can tell, a bug in Lightroom caused the plugin to not work for images with a period in the camera-make name, such as those from Olympus (which give the make as “OLYMPUS IMAGING CORP.”)

Added extra debug logging, when “enhanced logging” is selected in the plugin manager, to try to debug an issue.

Added a system-clock check and reports to the user if the system clock is more than a minute out of date. An incorrect system clock can cause problems with various kinds of communication and authentication with some of my plugins, so I've just gone ahead and added this to every plugin.

When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.

20110912.4 Added the ability to update the sharpening mask.
20110401.3 Big update adding support for color noise reduction, and the segregation of non-raw and raw. Best to make a backup of your catalog before trying this update, just in case.
20101104.2 Reissue after a build change.
20101028.1 initial release

The 30 most-recent comments (out of 55; see all), most recent last...

I found that the plugin doesn’t allow me to input ISO bigger than 99999. I tried to input 102400 but it auto change it to 99999.

And since A7S’s response is pretty linear (according to, I should really be entering 409600 and let the plugin extrapolating all the values in between.

Do you mind raising the ISO limit of the plugin? Thanks.

By the way, the website said I can use `a href…` but when I do, like this: <a href="" title="DxOMark" rel="nofollow">, it is the text after the hyperlink got hyperlinked.

Good catch… I’ve pushed the limit up to 10 million. About the comments, the HTML should be standard, but the description made it seem as if it wasn’t, sorry; I’ve removed it. One does need to close their tags, e.g. follow the link text with </a> —Jeffrey

— comment by Kolen on April 2nd, 2016 at 5:31pm JST (8 years, 4 months ago) comment permalink

This plugin is awesome! I use a lot of your plugins but never noticed this one. I decided to search for something to set noise reduction based on iso and this went way beyond what I was expecting to find! Thanks so much, I’m going to donate now.

— comment by Ryan Smith on May 16th, 2016 at 3:56am JST (8 years, 2 months ago) comment permalink

Awesome plugin, thanks!

Would love to see Profile Correction option so can enable it when doing the bulk develop as it would save another step.

That’s something you can use Lightroom’s existing “apply upon import” mechanism for, no? —Jeffrey

— comment by Christopher on June 19th, 2016 at 3:43pm JST (8 years ago) comment permalink

great plugin like said before.
I have a “Problem” with using 10 as the Default Color noise reduction for ISO 100-400.
I made ISO specific Default profiles in lightroom and set the Color noise reduction in the plugin at 400. But the plugin will Change the ISO 100-400 Pictures too, sett them to the 25 Default of Adobe.
Would it possible to leave the values for the Pictures below the plugin start Setting value (<ISO 400)on there already set value?

There’s an option to have the plugin assign a new value only when the current value is at the default of 25. Turning that on should have it leave your settings alone. —Jeffrey

— comment by Markus on September 10th, 2016 at 1:12am JST (7 years, 10 months ago) comment permalink

Hi Jeffrey,

Great plugin – been using it for ages and it’s just what I need. Am just wondering if there is a problem with version 20160402.55 – it seems to be ignoring my ISO Range settings (400-6400) and also applying adjustments to photos in the range 100-400. I’ve never had this issue before – am I missing something obvious or is there a small bug in this version?

Many thanks,


Next time you run into this, please send a log noting how what happened differed from what you expected. Thanks. —Jeffrey

— comment by Dom on September 25th, 2016 at 2:50am JST (7 years, 10 months ago) comment permalink

I just tried this Bulk Develop Settings plug in and am very pleased. I have been wanting to set-up unique default development settings based on camera & ISO – to be applied at import. This tool allowed me to do so. I created a collection of virtual copies of .dng files with one example of every possible ISO step from 50 to 51200, applied the plug in to all of them and then set the default develop settings for each ISO setting. And was able to do this for primary and back-up camera. May even do so for my iPhone.

The tool design is contingent on ISO rating. I would like to offer for consideration introducing an additional variable of long shutter speed. With astrophotography all the rage, it would be great if there were a way to also apply long shutter noise reduction (above 15 seconds?)

— comment by George Nichols on November 14th, 2016 at 5:38am JST (7 years, 8 months ago) comment permalink

Question/Clarification: I set the tool to apply NR values for ISO range of 400 – 51200. However, the tool is still applying NR values on files with ISO values in range of 50 – 360. I thought they would have been excluded. I verified three times… Am I missing something?

Next time you run into this, please send a log noting how what happened differed from what you expected. Thanks. —Jeffrey

— comment by George Nichols on November 14th, 2016 at 6:33am JST (7 years, 8 months ago) comment permalink

Hi Jeffrey,

I’ve problems on my Levono Yoga Pro 2 with a display resolution of 3200×1800 pixel.
The lowest part of the menu of “Bulk Develepment Setting”, which includes the “OK”-button etc.,
is not visible.
When I switch to a resolution of 2048×1152 pixel everthink is visible.

Any idea how to solve the problem?

Thanks in advance,

Lightroom seems to have changed how it handles high-DPI screens. I just pushed a new version of the plugin that might help. —Jeffrey

— comment by KH Schuldt on January 4th, 2017 at 9:44pm JST (7 years, 6 months ago) comment permalink

Thanks Jeffrey,

it works ! Can’t see a difference in Lightroom, but the plugins menu is now completely visible !


I think I should donate some money again, not only because of this really quick update, but also
because of the updates you are providing for the others plugins I’ve registered.
Great Work – Thanks a lot !

— comment by KH Schuldt on January 5th, 2017 at 8:06pm JST (7 years, 6 months ago) comment permalink

Hi Jeffrey,

I think you’re right Lightroom seems to look different on the high-DPI screen now.

Greetings, Karl

— comment by KH Schuldt on January 5th, 2017 at 8:16pm JST (7 years, 6 months ago) comment permalink


I’m trying to setup a keyboard short cut for the bulk develop plug-in on the Mac but having no luck. Other shortcuts for LR menu items do work but when using either ‘Apply Bulk Develop Settings…’ or the same but no ‘…’ as the menu item to apply the short cut to, it just doesn’t work. Is there some special trick to create shortcuts for plug-ins? REF: LR 6.7, OSX 10.11.6, last 2016 version of the plug-in.


The trick is to include three spaces at the beginning of the command: “<space><space><space>Apply Bulk Develop Settings…”. Lightroom adds those spaces to plugin-related extras, to get them indented in the menu. The three trailing dots must be included as well, simply because they are part of the menu item…. I add them to match the OSX convention that the menu item brings up a dialog instead of just doing some action silently.—Jeffrey

— comment by Matt Schlotzhauer on January 5th, 2017 at 9:57pm JST (7 years, 6 months ago) comment permalink

That did it! Thanks Jeffery….

— comment by Matt Schlotzhauer on January 6th, 2017 at 1:21pm JST (7 years, 6 months ago) comment permalink

Is it possible to add the “Dehaze” control to this plugin? Seems like it’s similar to the clarity and contrast ones… I found this plugin while googling for a way to have lightroom “select” based on develop values, and don’t seem to see that as one of the metadata fields in the library filter bar. But a plugin like this would do exactly what I want (set the dehaze to value 4 for all images which haven’t already had the dehaze set away from the default). I’ve really fallen for that new control since it came out for CC and haven’t updated my “default” import profiles yet. Huge fan of your LR export plugin…
Brent in Cary, NC USA

No, sorry, I don’t think dehaze is meant to be used that way, at least not generally. The plugin dialog is already too cramped as it is. Anyway, this plugin would be overkill if you want a set value for all images instead of an ISO-dependent value… the latter is what this plugin is designed for. Updating your import preset is the way to go. Also, FWIW, I’ve added Dehaze to my Data Explorer plugin (see here) so you can find previously-imported photos whose value hasn’t been modified. —Jeffrey

— comment by Brent Harsh on January 23rd, 2017 at 1:08pm JST (7 years, 6 months ago) comment permalink

I am interested in this plugin however in Lightroom I use 2 sliders for Noise Reduction (NR) in the NR box: Luminance and Detail.
I usually put Detail at 0 and increase the Luminance slider until the noise disappear. Then I increase the detail until I achieve the desire effect.

As far as I can see this Bulk Develop plugin only operates on the Luminance slider ?
How does it work with the Luminance Detail slider ?

Thanks !

Luminance Detail isn’t touched nor inspected with this plugin. —Jeffrey

— comment by S. Germain on January 29th, 2017 at 3:47am JST (7 years, 6 months ago) comment permalink

Hi Jeffrey, amazing plugin. It’s wonderful. I was wondering if you’d be adding a function for tone curves in the future? I regularly use tone curves to futher lift the shadows which means the image needs more needs more noise reduction. Thanks!

— comment by Samantha on February 28th, 2017 at 12:43pm JST (7 years, 5 months ago) comment permalink

We love and rely on this plugin! We just upgraded from 5D iii to 5D iv…does anyone have any recommended settings they use?

— comment by Lincoln on April 15th, 2017 at 7:54am JST (7 years, 3 months ago) comment permalink

Hi Jeffrey,

I’m now trying the latest version of this great plugin, but it is very slow with respect to the prior version. The ‘calculating settings’ dialog appears for minutes instead of seconds with the older version (20160402.55)

Am I doing something wrong? (running on Lightroom-version: CC 2015.12 [ 1125239 ])
For the meantime I switch back to the older version.
Thanks in advance!

Nothing has changed in how settings are calculated, so there shouldn’t be any difference. Next time you run into the delay, please send a log and I’ll take a look. —Jeffrey

— comment by Ben on September 30th, 2017 at 2:44am JST (6 years, 10 months ago) comment permalink

I set luminence noise redution to adjust images that are between 2000-13000 ISO, but images well under 2000 ISO also get adjusted. Did I do something wrong, or is this a glitch in the software?

Let’s take a look… please send a log the next time you encounter this, being sure to mention which image turned out wrong. Thanks. —Jeffrey

— comment by Kevin Hawkins on December 17th, 2017 at 1:52am JST (6 years, 7 months ago) comment permalink

Well. The plugin doesn’t seem to be working properly. I have an image from a d750 with iso 500. Default color correction is zero for this camera.
I’ve set a rule of iso 800 to 25600 to apply color reduction from 1 to 35. The plugin is applying 25 when it shouldn’t even touch this setting. Why?

Are you sure the plugin’s applying the value of 25? That’s the default value for raw files on import, so it was likely that before running the plugin. —Jeffrey

— comment by Carlos Viana on March 19th, 2018 at 9:28pm JST (6 years, 4 months ago) comment permalink

Love this plug-in and have been a happy user for a few years.

It seems like the introduction of the new profiles is causing something weird to happen – every time I apply noise reduction settings in bulk my color profile switches from Adobe Color to Adobe Standard. Any idea what is happening there?

Any tips for using the plug-in with cameras with the Aptina dual conversion gain technology? I have a Sony A7riii and it effectively has 2 base ISO points:

The color profile getting switched is a bug in Lightroom that I have reported to Adobe, and I have the impression that it will be fixed quickly. I don’t know about this “Apting” stuff, and I don’t think that Lightroom would expose more than one ISO value to the plugin, so with respect to the plugin it’s probably a moot point. —Jeffrey

— comment by Doug on July 3rd, 2018 at 11:45pm JST (6 years ago) comment permalink

Hi, I’ve updated LR Classic to version 8, updated the plugin (since my current version stoped working with LR 8), tried to enter my code but it said “Registration code already used for a different Lightroom serial number”. Although I’m using the same LR on the same macbook pro, just updated LR. Do I need to purchase plugin again in order to make it work with LR 8?

Please see this FAQ. —Jeffrey

— comment by Sergey on October 21st, 2018 at 11:45pm JST (5 years, 9 months ago) comment permalink

Thank you for the plugin, I love it.

However, I have a minor visual bug in it. Namely, plugin window doesn’t fit into my FullHD screen. The reason is I’m using Lightroom’s built-in “Large Fonts” option.
See it in menu “Edit->Preferences->Interface->Panels->FontSize: Large – 150%”

This way, plugin’s window height is 1266 pixels, which is a bit more than my monitor’s 1200 px in height. Because of that, I never see a lower block next to “export/import settings” buttons, as well as “ok/cancel” buttons.
That visual bug is a minor issue because I’m using only first two blocks of settings (“Update Luminance Noice Reduction” and “Update Color Noice Reduction”). But that’s a bug nevertheless, so I thought I’d report it.

I’m from Kyiv, Ukraine.

Thanks for the report. Dialog sizing and contents is a real pain point for Lightroom plugins… Adobe just doesn’t give much to work with, and there’s no way to reliably prevent what you’re encountering other than to simply not have so much stuff in dialogs. I try my best to make things fit in most situations, but the 150% size font is an edge case that I can’t handle. )-: —Jeffrey

— comment by Dmytro on May 13th, 2019 at 11:45pm JST (5 years, 2 months ago) comment permalink

Hi Jeffrey, is there anyway that White Balance: Temp & Tint can be added to The Bulk Development Settings? I batch process both Canon and Sony raws and in order to get the colors to match at the venue I shoot at, both models are set to Temp 4700, but I need the Canon files tint to be +26 and the Sony files to be +47.


This is sufficiently a one-off need that it’s not something that would get added to the plugin. However, you can make develop presets that do what you want, and apply them in bulk to each camera’s photos after import. That’s not quite as convenient as the plugin, but it’s the best I can suggest. —Jeffrey

— comment by Matt Schlotzhauer on July 23rd, 2019 at 10:43pm JST (5 years ago) comment permalink

I’m sure you have lots of people asking about this. But your plugins don’t seem to work with the latest version of Lightroom. This plugin in particular is very useful I hope you can update it soon, thanks!

Sorry about that… I’ve pushed out a new version that should work. —Jeffrey

— comment by Ryan Smith on November 5th, 2019 at 6:03am JST (4 years, 8 months ago) comment permalink

Thanks for the updates. Regarding texture, I tend to lower the slider value when ISO rises. How can I do that in the plugin ?

Besides, the slider list is now so long that the dialof doesn’t fir my screen anymore, and I cannot see the buttons in the bottom part (I’m running windows on a 4K laptop screen at a 200% scale).

Regarding the screen, can you send a plugin log so I can see what Lightroom is telling the plugin about your screen. As for texture, I’m surprised it took this long to realize that Contrast/Clarity/Texture can go negative, so need special control. I’ll give it some thought…. —Jeffrey

— comment by Tokumeino on December 6th, 2019 at 10:44pm JST (4 years, 7 months ago) comment permalink

Hi, Philippe from France !
I ‘m testing your -Bulk Develop Settings- and I’m exicting about.
I would like translate it to share it with buddies, but I don’t understand the way to do it.
I have look in the TranslatedStrings_** files and I haven’t found à link between the english sentances and the interface.
See the folowing exerpt from the TranslatedStrings_fr.txt file.
“$$$/RegexInfo/ago=il y a ^1”
“$$$/ListSeparator/NonUltimate=, ”
“$$$/ListSeparator/Ultimate=, et ”
“$$$/PairSeparator= et ”
“$$$/TimespanUnitJoiner= ”
“$$$/TimePriorToBirth=^1 avant la naissance”
“$$$/RegexInfo/DecimalYearOld=à l’âge de ^1 an”
“$$$/RegexInfo/DecimalYearsOld=à l’âge de ^1 ans”
“$$$/Age/0Y_0M_0D=jour de sa naissance”
“$$$/Age/0Y_0M_1D=un jour”
“$$$/Age/0Y_0M_4D=^4 jours”
“$$$/Age/0Y_1M_0D=exactement un mois”
“$$$/Age/0Y_1M_1D=un mois et un jour”
“$$$/Age/0Y_1M_4D=un mois et ^4 jours”

Thank you for your help

Sorry, the plugin is not set up for translation, except for what you found (which is for the parts of the plugin that work with my People-Support plugin). —Jeffrey

— comment by Philippe on February 12th, 2020 at 10:52am JST (4 years, 5 months ago) comment permalink

The plugin is deleting all local adjustments in the latest LR release (9.3)

I don’t know if the issue happens with other plugins

Wow, you’re not kidding, thanks for the report. I’ve filed a bug report with Adobe. —Jeffrey

— comment by Carlos André Viana on July 7th, 2020 at 3:26am JST (4 years ago) comment permalink

Hey Jeffrey, I’m not sure if you are aware but it seems that this plugin is deleting all local adjustments when I run it in the latest LR release. I’ve used it for years and love it, so hoping this can be fixed please 🙂

Yeah, it seems to be a new bug in Lightroom. I’ve reported it, and have update the plugin to, I hope, work around the problem. —Jeffrey

— comment by Paul Fox on July 23rd, 2020 at 6:50pm JST (4 years ago) comment permalink

I found what it seems to be a bug. If it is not, it shouldn’t work this way.

The plugin doesn’t change the noise reduction when shadows or exposure are increased in post production, when the image is below the minimum iso range.
eg. If I set the iso range to 800-9600 to a image with a iso of 200, and I add 1EV of exposure, the noise reduction isn’t affected which is wrong, because considerable noise is added when increasing exposure or shadows in post production.

I think the algorithm should consider that the increase of the exposure is equivalent to an increase of the iso. in the example i gave you, adding 1EV to a iso 200 image is equivalent of iso 800

What you describe is how it should be working, so perhaps you’ve found a bug. I’ve added a bit more debug logging to a new version that I just released; could you upgrade to it and send a plugin log with details about how what actually happened differs from what you expected? Thanks. —Jeffrey

— comment by Carlos André Viana on August 28th, 2020 at 3:07am JST (3 years, 11 months ago) comment permalink

Is this folder from this plugin? info.regex.lightroom.bulk-develop

It has a lot of files

Oh, I bet that’s in Lightroom Application-Support folder? If you run the plugin while the “extra debug logging” option is turned on, it leaves the temporary files behind. Generally, leave that option turned off unless you’re actively preparing a log to send to me. Still, they shouldn’t stay around forever, so I’ve just pushed out a new version of the plugin that cleans up all prior temporary files regardless. —Jeffrey

— comment by madeinlisboa on February 13th, 2022 at 10:37am JST (2 years, 5 months ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

IMPORTANT:I'm mostly retired, so I don't check comments often anymore, sorry.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting