bulk-develop-20130501.27.zip
· FAQ
· Version History
· Update Log via RSS
· Installation instructions
· “Donationware” Registration Info
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This plugin 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 5, Lightroom 4 and Lightroom 3.
The same download works for both Windows and Mac. See the box to the upper right for the download link 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:
and you'll get a dialog along the lines of:
(screen shot is as of plugin version 20120417.16)
For each camera type used in creating one of the selected photos, you create a profile that describes how to calculate the noise-reduction settings based upon the ISO and any post-processing exposure compensation. For each photo, the plugin calculates a straight-line proportional values between the lower and upper bounds you specify.
You can choose to apply the calculations only when they're not already set, or a blanket application regardless
Availability
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 Lr3 to Lr4, de-registers the plugin in the upgraded version, thus requiring (if you want to maintain registration) a new (1-cent if you like) registration code 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
)
| 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. |
| 20120808.19 |
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. |
| 20120604.18 |
The plugin was leaving cruft in one's "Plugin Develop Presets" folder; now cleans it up. |
| 20120526.17 |
Update to handle the Mac App Store version of Lightroom. Tweak for Lr4.1RC2. |
| 20120417.16 |
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. |
| 20120304.13 |
More updates for Lr4. |
| 20120221.12 |
More updates for Lr4. |
| 20120128.11 |
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 |
| 20120112.8 |
Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta. |
| 20111210.7 |
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.”) |
| 20111201.5 |
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 |
Great idea. I love the idea that Adobe had for setting the defaults based on ISO, but they need an interface to tweak those defaults for the different ISO values. Have you thought about modifying this plugin to set luminance NR for multiple ISO values? Such as…
<=100 ~ 0
<=200 ~ 0
<=400 ~ 10
<=800 ~ 20
<=1600 ~ 30
<=3200 ~ 40
<=6400 ~ 50
etc…
Your plugin can be used multiple times to achieve this, but it would be nice to be able to set ranges once that can be applied to groups of photos with widely different ISO values.
That’s pretty much what mine does… set it to 10 @ ISO=400, 50 @ ISO=6400, and it’ll extrapolate for the ISO values in between. —Jeffrey
Great! Another very helpful tool!
In addition to a DSLR I sometimes use a compact camera that really needs that.
Thank you, Jeffrey!
I am new to LR plug-ins … does this export the images or does this apply settings to the images like they do in the Develop module? do they show up in the image’s develop history?
It merely applies settings, and yes, the changes show up in the develop history for each photo. —Jeffrey
This is a very good idea! But after downloading it and testing it for the first five minutes I found some drawbacks:
1) Aside from Color and Luminance noise, it would be great to have an option to adjust the Masking (under Sharpening). To suppress noise I routinely increase Luminance slider and also Masking a bit – the latter avoids sharpening of noisy pixels, which really helps.
2) The computation based on Exposure adjustment is great! But could be much more easily used if it was translated into ISO, i.e. for every +1 EV take it as the base ISO was twice as high (better: slightly more than twice). Something like calculated_iso = original_iso * (2.1 ^ ev_adjustment).
Then you just perform noise setting according the main settings and you don’t need the last section in options (or just to set the coefficient).
Also, it allow things which are currently not possible. For example, I would like to use noise reduction from ISO 800 and even more so for ISO 800 + 1 EV – this is possible, but it will also affects photos with ISO 100 + 1 EV, which is not necessary. (Though it should apply to photos with ISO 400 + 1 EV)
So these are my opinions
Interesting plugin otherwise!
I just pushed a version that handles point #1; thanks for the idea. Point #2 will have to wait for another day… —Jeffrey
Whoa… just used this plugin. Saved me about 3 hours of work as I didn’t have to tweak each individual image.
Thanks Jeffery for your awesome work!
John V.
Thanks for the great plugin, Jeffrey!
It works fine with all my cameras except for the files from my Olympus E-PL1 (both ORF and JPEG). The plugin configuration window stays grayed-out (including the OK button), even when I click all the checkboxes, which contain minus signs when I open the window.
Paul from Canada
Thanks for the report, Paul… I’ve pushed a new version that fixes the problem. —Jeffrey
I’ve added the bulk developer, but there appears no where to go in the Export dialog that will allow me to use it. I’m using LR4 and I don’t see anything that let’s me insert it into the main dialog as you describe. could you please provide more explicit instructions? Thanks.
Bob
I thought they were pretty clear (and made no mention of the Export dialog, since this has nothing to do with Export), but I’ve gone over them and updated for changes in the plugin since I wrote them, so hopefully it’s clear now. —Jeffrey
Jeffrey,
What precise piece of information is this package using to decide what calculations to make. If I use Photomatix to produce a TIFF file and try and apply it tells me there isn’t enough information to work with.
If I use LR to look at the speed it tells me 100 ISO so perhaps it is is looking elsewhere.
I have used your meta data viewer package to snapshot the exif and the difference between the two EXIF is that the normal image has “ISO Setting” and “ISO2″ as 100 whereas the created TIFF has just “ISO” as 100.
I can fix it by running the exif tool to migrate one of the original images EXIF across but should I really be flagging this as a Photomatix bug.
Regards Mike
The plugin asks Lightroom for the data (“What’s the ISO?”). Lightroom probably has some kind of heuristics that it takes data from the embedded XMP data if it’s there, but from Exif if not, but this is just a guess. If Lightroom shows the ISO in the metadata panel, the plugin should be given the same data, but the plugin also needs other data as well, so maybe it’s not ISO at all. Perhaps send a log after a failure? —Jeffrey
Silly me for not looking at your log.
This gave me the pointer that the Make was missing (presumably because Photomatix decided not to say it’s image was from Nikon Corporation despite preserving the camera ID correctly). I’ll e-mail Photomatix to see if this can be fixed….
In the meantime created a Run any command in an export preset to allow me to fix it….
Happy to report that Make is now correctly transferred to the Photomatix target file in version 4.2.5, released 18th Nov 2012 http://www.hdrsoft.com/download/win.html
As a result the bulk Develop plugin works OK…..