|San Francisco, California|
Misc Lightroom Plugins
(some very useful plugins, that didn't seem to warrant a whole page for each)
Unlike my other plugins, the plugins on this page are offered with few instructions, or other supporting documentation. However, I will try to answer any questions you may have, and help you with any problems you may have, as long as you're nice to me ;-}
Unless otherwise specified, these plugins are cross-platform (Windows + Mac), Lightroom 3 or better.
To install: unzip to anywhere you like *EXCEPT* system or program directories (e.g. do *NOT* put in C:\Program Files...), then click the 'Add' button in Lightroom's Plugin Manager and select the .lrplugin or .lrdevplugin folder. Do not move or delete the folder after adding - it's used in place.
Some plugins have a RC_CommonModules folder, which just needs to be present as sibling folder to the lrplugin or lrdevplugin folder - just how it is when the download is unzipped - The RC_CommonModules folder is not "added" and must not be moved in relation to the lrplugin or lrdevplugin folder it came with. Installing by way of copying to Lightroom's "Modules" folder, and then restarting Lightroom - is not recommended (because it would require merging of (rc) common modules, and there may be some version incompatibilities).
###1 Mac users: Some plugins use osascript (Mac OS AppleScript interpreter) to help do their deeds. In order for this to work, you must have "access for assistive devices" enabled, e.g.
And due to a bug in Mac OS, you may even have to disable it, then re-enable it.
Toubleshooting and Problem Reporting:
- First step is always to make sure you are running the latest version of the plugin (and preferrably the latest version of Lightroom).
- If plugin won't install and run (i.e. no "green light" in left hand pane of plugin manager), please visit plugin manager / plugin author section, and with offending plugin selected, click 'Save Diagnostic Log To File'. Include the contents of the saved diagnostic file in the body of the problem report. -thank you.
- If plugin installs and runs, but has operational problem, then please send plugin log file (if problem is recreatable, then please enable verbose logging in plugin manager before doing the things that have the problems) to me along with your problem report. How to do this depends on whether its an older "legacy plugin" (based on RC_CommonModules), or a newer plugin based on the elare framework. In either case, you can find the log file in your documents folder and include contents in body of problem report. In the latter case, click the 'Report Problem' button in the top section of plugin manager (make sure the offending plugin is selected in the left-hand pane), and follow instructions... - thanks.
- If you use non-ascii characters in filenames/paths and you are having problems, then please download and run this test plugin and report results to me - thanks.
*** More of my plugins are available here.
acceptance of Download Terms & Conditions will be required
Provides keyword report:
Report is output to the clipboard, so can be pasted in text editor or whatever for printing...
Accessed via Lr's File Menu (Plugin Extras)
v1.0 released 2013-03-06
v1.1 released 2013-03-06 - more info, improved format...
v1.2 released 2013-03-07 - added ability to include keywords which had no associated photos.
v1.3 released 2013-08-12 - added ability to define custom sort order (in advanced settings) and defined a couple of new presets which take advantage of different sort orders.
*** Deprecated in favor of Exportant.
Export Filter (i.e. Post Process Action) to modify export parameters dynamically based on exif.
@now: Hardcoded to set export 'Resolution' to that found in exif.
Edit In Lightroom (moved)
Pretends to be other plugins so you can do things to them that they might not be able to do to themselves, like:
* Clear their metadata.
* Clear their preferences.
The main purpose of this plugin, so far, is to scrub plugin data remnants from catalog, for plugins you no longer intend to use. Said data will not affect performance, but it may affect catalog size.
Future features may include:
* Transfer metadata from other sources to their custom metadata.
*** Be careful not to scrub data for plugins that you *are* using, or will use again...
*** Backup your catalog first, before using...
Note: this plugin will not remove table column definitions created in the catalog database to support plugins, only the data these tables contain (that's as much as Lightroom allows plugins to do). If you want to delete those too, you'll need to use SQL - but doing so has no practical value, and I don't recommend it.
Disclaimer: Clearing metadata will work for most, but not all plugins (it will work for those whose metadata definitions do not depend on pre-executing their init module).
Mac users: you may need to rename "subject" plugin folders (meaning not the 'Pretend' plugin) from .lrplugin to something else, try .lrdevplugin.
Also, if plugin gets hosed whilst pretending to be another plugin, you may need to restore it from downloaded zip, then reload (if Mac maybe restart Lightroom too).
v1.3 (2012-10-02) Certified for Lr5.
v1.2.1 (2013-03-31) fixed bug resulting in <eof> in Info.lua upon reload.
v1.2 (2012-12-18) Added direct input for toolkit id, in case you no longer have foreign plugin to pretend to be.
v1.1.1 (2012-09-17) Was only working if metadata module defined. Now works when no metadata module defined.
v1.1 (2012-06-17) Checks first if plugin has metadata to clear before-hand, so its faster if none.
v1.0 (2012-06-16) Initial release.
Undoes effects of AutoSync, after exiting Lightroom, i.e. after regular undo is no longer viable.
Despite the name, it can be just as useful for "undo"-ing a manual sync snafu.
Rolls back develop edit history by specified number of steps, for all images in 'ScrewAutoSync' collection.
Useful for when you had a bunch of photos selected, with AutoSync inadvertently enabled, changed a setting or 3, then exited Lightroom without realizing it.
Hint: Click 'Help' in plugin manager after 'Add'-ing plugin.
Written for Mac+Windows, but only tested on Windows so far - please let me know if you try on Mac before I get to it.
Requisite SQL script provided by Dorin Nicolaescu-Musteață - we thank you.
v1.1.1 (2012-07-12) Fixed typos in UI text.
v1.1 (2012-06-15) Supports multiple adjustment steps.
v1.0 (2012-06-14) Initial release: only supported a single adjustment step.
*** deprecated: replaced by Exportant.
Post-Process Action (aka Export Filter) supports resizing of exported photos by percent.
To use, after installation, click 'Insert' button in Post-Process Actions section of export dialog box. - enter 'Resize by' percent...
Supports Width & Height, Dimensions, Megapixels. Will not support 'Long Edge' nor 'Short Edge' unless you ask for it.
v1.1 (2012-06-05) "Bullet-proofed" it, and added support for megapixels.
v1.0 (2012-06-04) Initial release.
(despite the misnomer) Helps migrate Lr4 catalog to Lr5b
*** Note: In the verbiage which follows, you can replace Lr3 with Lr4 (or present catalog, whichever version), and replace Lr4b with Lr5b (or target catalog being created, whichever version).
Although the original intention of this plugin was, in conjunction with some other plugins, to be able to create an almost complete Lr4b version of an Lr3 catalog, it can still be used to rebuild a clean Lr4.X catalog from an Lr3 or potentially problematic Lr4.X catalog.
Note2: This is not a "hack" - i.e. it only uses Adobe-endorsed methods - there is nothing it does that you couldn't do yourself, manually. Put another way, all it does is add photos to the catalog (in proper stack position) and create collections, the rest is done via the other plugins - using only Adobe-supported plugin functions...
- allows you to import photos from Lr3 catalog, and maintain stack positions.
- imports all regular collections, and publish collections from Lr3 catalog.
- LrFourB needs your photos to be in the same location when reading (importing) Lr3 stuff as they were when saving (exporting) Lr3 stuff. It adds photos to your catalog, in place, based on path. So, make whatever backup copies you want to have before doing the migration.
- If you will be using Lr3 on the same photo copies as Lr4b, it is safer to not save xmp in Lr4b. If you forget, then remedy by re-saving xmp for those photos in Lr3, or just don't read Lr4b-saved metadata (xmp) in Lr3. Put another way, it may be best to let Lr3 be the xmp master, and confine Lr4b edits to your catalog until final release. It shouldn't be that big of a deal if you goof up, because Lr3 should just ignore xmp things from Lr4b that it doesn't understand. But Adobe recommends not relying on this while Lr4 is still in beta, and that's probably good advice.
To sync Lr3 smart collections with Lr4 catalog you will need:
To import virtual copies:
- xEmP (to export/import virtual copy definitions)
- Does not transfer edit history.
- Although it does save Lr3 preferences in an easily digestible form, on a per plugin basis, its up to the individual plugins what to do with those saved preferences - LrFourB does nothing with them.
- You need to set up all of your publish services - this plugin will then create the publish collections.
*** Note: This plugin is not very polished, but it should work well enough if you follow the instructions - please let me know if problems.
Step 0: use xEmP and SQLiteroom in Lr3 to save all virtual copies and smart collections, respectively.
@v0.2.1 (2013-05-03) Eliminated creation of extraneous (properties) file in catalog directory.
@v0.2 (2013-04-15) Enhanced for Lr5b.
@v0.1 (2012-04-30) Certified for Lr4.
@v0.0 (2012-01-15) Initial release.
*** UNLESS YOU NEED PARENT FOLDER NAME, GRAND-PARENT FOLDER NAME, OR GREAT GRANDPARENT FOLDER NAME, THIS PLUGIN IS DEPRECATED IN FAVOR OF
Provides Title, (mini) Caption, (mini) Headline, Folder Name(s), Filename and (virtual) Copy Name, as Metadata for Library Filters
*** And: Folder Path, which may be more useful for smart collections than lib filtering.
This is a very simple metadata plugin so you can view all photo titles in metadata column of library filter bar. I tossed in a (one-line condensed) caption, headline, filename and copy-name while I was at it (and folder path).
Note: You can opt to replace spaces with something else (e.g. '_') to make it easier to find metadata containing spaces (using native Lightroom lib filter / smart collections).
*** Note: Manually updating metadata is optional, but it is recommended to do whole catalog once after initial installation. After that the metadata will be updated automatically according to the settings in plugin manager - metadata is updated in a leisurely fashion in the background, but it will give priority to selected photos, so select photos for it to update if you don't want to wait... )
Visit plugin manager if you're the curious type or it's not working like you expect.
@v1.6 (2013-12-13) Added 'Base of Filename' and 'Filename Extension'.
@v1.5 (2013-04-25) Added custom replacements (e.g. replace space with '_').
@v1.4 (2012-11-20) Fixed bug in preset manager: '>', '<', '>|', '<|' buttons were broken. Also, added option for different log file location.
@v1.3.1 (2012-10-24) Background updates were not happening properly. Also fixed a potential error that some users were having - possibly induced by changes made in 1.3.
@v1.3 (2012-10-23) More options in pre-op prompt, for cases when none or only one image is selected.
@v1.2.1 (2012-10-22) Changes to Elare Plugin Framework only: new preset manager, and most importantly - fixes an updating error experienced by Lr3 users.
@v1.2 (2012-06-10) Added folder-path, and folder name(s).
@v1.1 (2012-06-10) Added mini-headline (same as original headline, except possibly scrunched).
@v1.0.1 (2012-01-23) Bug fix: caption formatting was different in manual update vs. auto-update, resulting in auto-updating all photos even after a manual update.
@v1.0 (2012-01-22) Initial release
*** deprecated in favor of Exportant.
Allows exported files to be named any way you want.
- ExportNamer will allow you to export photos with filenames that include pixel-count, aspect-ratio, or any other metadata available to ExportNamer, which includes metadata in any other plugin, like DevMeta, ExifMeta, or CustomMetadata. Its a post-process action, so it can (theoretically) be used with any export or publish service.
- Its an export filter whose method is somewhat of a kluge.
- It can't be used with publish services that require the filename as originally expected (e.g. for subsequent uploading).
- Nor can it be used with other "normal" export filters in the chain (since it "breaks" the chain of expectations by altering the filename).
- It requires some rudimentary editing of a lua text configuration file for customization - instructions and examples are included, but still...
- You have to dismiss a dialog box after every round of exports (explanation upon request).
more good news:
- Example presets are included to generate names that include pixel-count, cropped-dimensions (with no spaces), and aspect-ratio, as well as special handling for virtual copy naming...
- It works well with hard-disk export service, or the export service it is packaged with.
This plugin works by creating two files initially - one with a name you don't want (which satisfies the export service), another with the name you do want (which satisfies you). After you dismiss the dialog box upon export completion, the ones with the names you don't want are deleted. Details for why it works this way are available upon request.
@v1.0 (2012-01-06) Initial release.
@v1.1 (2012-09-01) Added (plugin-manager) presets, and robustened checking for dependent settings, to maximize the odds that it works first try - no errors... :-)
@v1.2 (2012-11-17) Added export presets, and another plugin manager preset which will prepend catalog name as export subfolder. *must* be used in conjunction with a filenaming preset having '_ExportNamer_' custom text as prefix, like the one that comes with it: 'Export Namer - Custom Prefix'. @v1.2 - Export Namer is Lr4 compatible (previous versions were Lr3 only).
Assures keywords assigned to exported photos are exactly the same as the photos being exported. If you noticed how Lightroom no longer exports hierarchical keywords "correctly" (like it used to) @Lr3.5, this is the plugin that corrects the problem.
Note: You must have:
- 'Minimize Embedded Metadata' unchecked,
- 'Write Keywords as Lightroom Hierarchy' checked,
- and 'Add to This Catalog' checked, for the export to work.
Also, if you get a metadata flag, synchronize to the south (downward), not to the north (upward). In other words, write metadata from catalog to disk (e.g. click 'Overwrite Settings'), not the other way around.
You can also visit plugin manager and check the "automatically save metadata" box to avoid metadata conflicts - it uses keystroke emission to do the job, and so is not perfect, but if you are willing to be concious of its caveats, it works... Note, the 'Don't Ask' checkbox in the save-metadata dialog box only works if the export is by way of a plugin, e.g. not 'Hard Disk'.
Note: Export Master can not cleanup keywords left behind that have zero photos assigned to them, but you can (Metadata Menu -> Purge Unused Keywords).
When Lightroom exports catalog-bound photos through post-process actions, all post-process actions are invoked, then the default keyword handling is applied to the photo file itself, asynchronously, then the photo is added to the catalog, asynchronously, and then metadata is read from the photo to the catalog, asynchronously. ExportMaster tries to wait until Lightroom has done all that before proceeding with keyword correction. Unfortunately, its not easy to tell when all that has completed, so ExportMaster depends on you to confirm before proceeding. That's what the prompt that says "Please wait..., then click..." is all about.
If the photo is in the catalog already, then things are different, however there is still a race condition between Lightroom and ExportMaster post-process action.
To make sure things happen in the right order (thus avoiding metadata conflict issues), there are some delay tuning parameters accessible by clicking 'Edit Advanced Settings' in the plugin manager - do attend to these if you are having problems, or if you want to optimize for your system...
@v1.1.1 (2011-11-15) Minor (mostly aesthetic) changes.
@v1.1 (2011-11-09) Delay tuning enhancements.
@v1.0 (2011-11-08) Initial release.
Collection Agent (moved)
Checks for Hydden problems.
One day, it will check everything there is to check (ha-ha)..., today - it just checks for missing files and missing color labels.
Initial motivation for this plugin was finding out an important photo file was missing. How long had it been missing? - probably a very long time, I'm guessing, anyway: too late now... The other motivation was missing color labels, although truth betold, one can recover those simply by filtering the label string metadata - oh well: now there's two ways...
Notes about color labels:
- due to a bug/omission in Lightroom (SDK), it is not possible to check for missing labels per se, so it checks for "white" instead (which is the "reversion color" when a label is "not found") - works just as well, as long as you aren't using "white" as the label string for some of your legitimate labels, which given what I know now, would not be a good idea anyway.
- Labels are stored as strings, and can be any string. Label sets map the strings to colors, and vice versa. So a label is typically only valid in one set, so the problems arise if you assign or change a label in one set, then change sets, the label goes missing. Theoretically this could be on purpose, but in my experience, its more often an accident, and causes the problem being checked for by Dr Checkyl.
Ideas for future checks:
- Lens Profiles (check if profile enabled, that specified profile exists). - I don't monkey with lens profiles m'self, so this may take a while to get around to.
- Metadata conflicts (will require startup script - may be deferred until Lr4). The way I do things, these usually come up immediately after editing in external app, and so are detected by visual inspection, but not always...
- Missing sidecars (e.g. jpeg & xmp). I don't use jpeg sidecars, and xmp is managed by ChangeManager, so this may never happen.
- Disabled develop settings (for those who generally keep enabled, and who disable just for comparison). I mostly enable immediately after disabling, so this not pressing either.
- Specified Metadata Item Is Empty (for those who like to make sure every photo has a ...) Although that's easy enough to do using a smart collection, looking for items that don't contain a e i o u.
- Corrupt images: I don't really know how to do this, but it should be on the list. Maybe tap into a command-line validator...
PS - I take requests.
Advanced Color Editor can check for missing camera calibration profiles. - this was a biggie.
To use: after installing or updating plugin, select photos to check, or deselect all to check all (sounds backwards, I know), then click the 'Check' button in plugin manager. In addition to or instead of looking in the log file for details, see Dr Checkyl collections in Lightroom.
@v1.0 Initial release.
Publish Service Assistant (previously known as "Unmark for Republish" - moved)
Extract JPEGs From NEFs v1.1.0 (Lr2 too, but Windows Only) *** Almost completely deprecated now...
*** Deprecated in favor of the new and improved NxToo - which works on Mac too. Previewextractor auto-rotates the image itself, and therefore will be displayed in the correct orientation in Windows OS proper, and any other software whether it attends to auto-rotation metadata or not. Whereas NxToo rotates your files if necessary using rotation metadata which is only recognized in 3rd party software like Lightroom and ACDSee...( not sure about Mac ). The biggest issue however in my opinion, is that preview-extractor does not handle metadata and icc-profiles (which means if you shot AdobeRGB in-camera, the preview-extracted jpeg color will be off). NxToo will transfer metadata from the raw to the extracted jpeg, and icc-profile as well, if present, and if not present, will assign a proper icc-profile from its own repertoire. Also, with NxTooey, you can extract just selected photos, instead of always whole folders, and there are other perks...
Nikon raw files have a full-size jpeg "preview" image stored in them - even when shooting RAW-Only. PreviewExtractor.exe can extract them. This plugin is a pretty simple wrapper that just invokes PreviewExtractor.exe on the folder containing selected photos. Note: It does all photos in all folders containing selected photos.
(Hint: Invoke using 'File Menu -> Plug-in Extras')
PS - Requires PreviewExtractor.exe presently available here.
Invert Tone Curve preset (not a plugin)
Makes dark tones light and light tones dark.
Folder Notes v1.0.0
View/Edit photo folder or catalog notes from within Lightroom.
*** Hot tip: Ctrl-J to enter a new-line in Windows. Option-Return on Mac.
(Hint: Invoke using 'File Menu -> Plug-in Extras')
Lightroom Catalog Backup v1.1.1 (Lr2 only)
Simply makes a copy of your catalog file in the same directory with a date suffix appended, and does not require exiting Lightroom. There are more complete and configurable backup solutions findable if you poke around, but if cheap and dirty (er, I meant "quick and easy") is all you need - this one's great.
(Hint: Invoke using 'File Menu -> Plug-in Extras')
Rotate Landscapes On Export v1.0 (Windows + Mac, Lr2 + Lr3)
Rotates all photos with aspect-ratio > 1 by 90 degrees clockwise, using exiftool/orientation metadata. Should work for all viewers that respect this metadata - most do, but Windows does not. Not sure about the iPad - please let me know.
*** Mac users: You must have exiftool pre-installed or it won't work.
*** Windows users: exiftool is included in the lrplugin folder. If you want you can replace it with one of your own choosing.
Acts like an export but simply distributes the contents of a folder (and subfolders-recursively) to another directory with subdirectories all having the same number of files or limited by megabyte count. Useful for constraining for email, CD burning, etc...
@v2.4 Certified for Lr5.
@v2.2 Added button to plugin manager, for updating the plugin, and uninstall.
@v2.1.2 Changes to framework should have minimal impact on this plugin.
@v2.1.1 fixes problems with preset manager.
@v2.1 implements managed export interface for use with Export Manager.
More scripts may be added in the future, but also, you can clone edit and rename...
1. Download and unzip "Miscellaneous Scripts" (link above).
2. Create 'Scripts' folder in Lightroom Presets folder - you can find the correct folder by clicking this button:
(hint: Edit Menu -> Preferences to bring up dialog box) Obviously, if folder already exists, then you don't have to create it.
3. Copy .lua files from downloaded/unzipped script zip to above-mentioned 'Scripts' folder.
4. Restart Lightroom.
Note: after installing according to instructions above, you should have a folder named 'Scripts' inside a folder named 'Lightroom'. In that 'Lightroom' folder should also be folders for your various presets and templates, e.g. 'Develop Presets', 'Export Presets', and 'Filename Templates'. In that 'Scripts' folder is where the lua files in the downloaded zip (once unzipped), should be placed. If done right, then there will be a scripts menu (right-most menu in Lr menu bar) after restarting Lightroom. Once scripts are on the menu, you can edit them and re-invoke them from the menu without restarting Lightroom (they are reloaded afresh upon each invocation). Here's a portion of how it looks on my computer:
and finally (after restarting Lightroom):
2013-05-28 - Initial release.
See README.txt file after downloading for installation and usage instructions.
Note: Most likely issue you'll run into has to do with macro security. I recommend self-signing the macros in your project, and then ascribe trust to them - all other macros to be untrusted. That way, you're not bothered by the security warning prompt every time you open Outlook, but you are still protected against foreign macros. If you already own an appropriate (trusted) certificate, then you should use it instead of creating a self-signed certificate.
- Another option is to enable macros in your project each time you open Outlook, so they'll be ready to use when you are ready to use them.
- Yet another option is to disable macros when opening Outlook, unless you want to use them, in which case you'll have to reopen Outlook...
More info here: http://www.howto-outlook.com/howto/selfcert.htm#signing
2013-10-11 - Initial release.
*** More of my plugins are available here.
Enjoy! - Please let me know what you think if you are so inclined.
|Static content updated 2008-07-20||Copyright 2007 - robcole.com - all rights reserved.||Dynamic content updated 02:14:08 PM|