.
Jeffrey’s “Data Explorer” Lightroom Plugin

One example of the plugin's 131 ways to group your images
Quick Links
· Latest Download:
     data-explorer-20130501.20.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 for Adobe Lightroom allows you group photos and videos in your Lightroom catalog by more than 100 data criteria. For example, grouping a large folder tree by “Crop Amount” might result in the screenshot seen above.

By clicking “isolate” on each row, the relevant images are shown. The plugin also creates a row-specific collection, such as:

Data Explorer > Crop Amount > Slight Crop

and populates it with the pertinent photos so that you can refer to them later.

The basic purpose is essentially the same as Lightroom's own Library Grid Filter, but Adobe's built-in functionality, though fast, has extremely limited scope. If it were able to handle more than the scant few fields it currently supports, there would be no need for this plugin, but it doesn't, so here we are.

As it is, this plugin lets you inspect and group photos via a bewildering number of criteria, from the mundane (“group by copyright name”) to the esoteric (“group by geoencoded hemispheres”) to the particular (“group by amount of Clarity applied in Develop”) to the advanced (“group by camera-calibration profile”). The entire list of 131 criteria are listed below.

Table of Contents

  1. Download
  2. Search. Filter. Group. Explore.
  3. Related Plugins.
  4. Invocation.
  5. Criteria List
  6. Results Dialog
  7. Availability

Download

This plugin works in Lightroom 5 and Lightroom 4.

Lightroom 4.1 or later is required.

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.

Search. Filter. Group. Explore.

This plugin can be used to search or to browse. A search helps you locate photos that match specific criteria, such as “Where are my panoramas with a really wide aspect ratio?”, while browsing lets you see the range of values represented by some particular criteria in your library, answering questions like “What range of aspect ratios do I have in my library?” (The answer for my catalog at the moment: as tall as 1 : 2.58151 and as wide as 6.4 : 1”).

Browsing can be both fun and useful, especially for catalog cleanup, such as after grouping by “Copyright”, you may see various versions of the same person's name that you'd want to make identical.

Sometimes the results are surprising. While making the screenshot shown at the top of this page, the first thing I noticed was that four photos had an essentially-100% crop! I wondered what they were, and found the answer with one click of the “isolate” button: the four photos were presented and I recognized them as the extrema crops that appeared on this blog post 18 months ago, and an extreme crop of the first photo on this post that I used to use as my online avatar.

Anyway, I started writing this plugin the first time I tried to use the results of an X-Rite ColorChecker Passport in Lightroom, which allows you to make situation-specific camera-calibration profiles for Lightroom's render engine. After trying it with some photos in my library, I quickly lost track of which photos got which profile; it was very frustrating because the only way to know was to inspect each photo's develop settings, one by tedious one, and manually keep a running tally.

Now, I can invoke this plugin on a folder and quickly see:

It didn't take long to solve my immediate need (a crude plugin that merely listed the camera-calibration profiles and their photos), but it's taken three weeks of never-ending “just one more enhancement...” development to whip it into good enough shape to put my name on and release.

Even while writing up this web page after I thought the plugin was ready to release, I realized that Lightroom does not normally subject images hidden within collapsed stacks to catalog operations (such as the grouping operation done by this plugin), so writing this page got put on hold while I addressed that issue in the plugin:

It wasn't straightforward at all, especially to handle it as efficiently as possible, so I burned the better part of a day on just that. Such is the nature of Lightroom plugin development driven by a passion to make things useful.

While talking about searching and browsing, for times when you want only to search, this Data-Explorer plugin may well fill your needs, but you may also want to keep the following plugins in mind as well:

I've not used John's plugin, but it looks to be quite impressive.

Invocation

The plugin is invoked via “File > Plugin Extras > Explore...”, but it's much faster and convenient to invoke via a Lightroom keyboard shortcut.

On Windows, the keyboard shortcut is “ALT-F S E”.

On a Mac, you can set the shortcut as you like. For my own workflow, I've chosen Option Shift Command F”.

This pops up a dialog that allows you to select the criterion to explore by:

You can pick something from the dropdown box (currently showing “Aspect Ratio...” in the screenshot above), or just start typing search terms, and the dialog immediately transforms into an effective way to find the item you want among the 131 criteria the plugin supports:

Clicking on any criterion returns you to the initial dialog with that item selected, but if the search results in just one criterion, you can press ENTER to immediately launch Data Explorer with that criterion as the basis for grouping.

The “Include items hidden within collapsed stacks?” option is off by default because with large sets of photos it can cause quite a delay because when enabled, the plugin must fetch stack-related data from the catalog, then walk the list inspecting each stack for new photos not already included.

This doesn't take long for small sets of photos... on my laptop it takes about a second to do 1,000 photos, but even this is highly dependent on what else Lightroom is doing in the background. (When I select “All Photographs”, Lightroom turns my CPU into a space heater as it renders thumbnails in the background.)

But that time adds up, and it's a one-minute delay for 60,000 photos. Because the process must finish before the grouping process can be launched, I made the entire option default to unselected.

By the way, here's an interesting general little Lightroom workflow tidbit: Lightroom ignores stacks if you select both Folders and Collections, bringing anything that had been hidden within collapsed stacks into the target set. So, if you select “All Photographs” in the upper left of Library and see X of Y photos” in the filmstrip instead of just Y photos”, and if this can't be explained by you Library Filter, you have photos hidden within collapsed stacks.

If you then option-click (ALT-click) on any folder, you're not really adding anything new to the target set because any folder's photos are already included with “All Photographs”, but because you've now got a collection and a folder selected, Lightroom ignores stacking and voilà, you're at a straight-up Y photos” that really is everything in your catalog.

You can apply the same idea while viewing a specific folder if you create an empty collection (perhaps named “Empty”) that you can add to the selection.

Criteria List

The following table lists the criteria currently available.

(Due to limitations in Lightroom's plugin infrastructure, items marked with a “*” take longer to process.)

In Lightroom Library
File Currently Available?*File is available, or offline (e.g. on an external disk not currently connect)?
File TypeFile type (DNG, JPEG, Raw, Video, ...)
Folder NameName of the folder (without path) the file is in. Useful to isolating images in a parent folder when there are also images in a subfolder.
Path NameFull path of the folder the file is in. Useful to isolating images in a parent folder when there are also images in a subfolder.
File ExtensionFilename extension (jpg, NEF, AVI, mts, CR2, ...)
Copy NameVirtual-copy name for the photo/video.
Virtual-Copy CountNumber of virtual copies a master image or video has.
Snapshot Count*The number of snapshots for the related master photo.
Stacking StatusStatus with respect to stacking (within its parent folder).
Stack-Membership SizeNumber of photos/videos in its stack (within its parent folder).
Position in StackPlace in stack (within its parent folder).
RatingStar rating (a number from 1 to 5).
Color LabelColor label name.
KeywordsList of keywords (can be long!).
Keywords (exportable)List of keywords included on export (can be long!).
Equipment
Camera Make and ModelCamera manufacturer and model name.
Camera Make, Model, and Serial NumberCamera name with its serial number.
LensThe lens used to take the photo (e.g. “50 mm f/1.4”).
Focal LengthFocal length of lens as shot (e.g. “85 mm”).
Focal Length 35mm EquivFocal length of the lens as shot, in full-frame 35mm terms (e.g. “135 mm”).
SoftwareSoftware used to process/create the photo prior to import into Lightroom.
Exposure
Exposure*Exposure summary (e.g. “1/60 sec at f/2.8”).
Total Exposure (camera Ev)Total camera exposure (Ev), derived from the shutter speed, aperture, and the ISO speed rating.
Total Effective Exposure (effective camera Ev)*Total effective camera exposure (effective Ev), derived from the shutter speed, aperture, and the ISO speed rating, then adjusted to reflect any Exposure added or removed in Lightroom.
Shutter Speed*Shutter speed used to take the photo (e.g. “1/60 sec”).
Aperture*Aperture used to take the photo (e.g, “f/2.8”).
In-Camera Exposure Bias*In-camera exposure bias/compensation (e.g. “-2/3 EV”).
Lightroom Exposure Adjustment*Amount of overall exposure compensation applied in Develop.
FlashWhether the flash fired (“Did fire” or “Did not fire”).
Exposure ProgramExposure program (“Manual”, “Aperture priority”, “Landscape”, ...).
Metering ModeMetering mode (“Center-weighted average”, “Spot”, ...).
ISOISO Sensor-sensitivity speed rating (e.g. “100”).
Subject DistanceSubject distance (e.g. “1.92 m”); often wildly incorrect.
Size
Cropped?Has a crop been applied in Develop? (“Cropped” or “Not cropped”)
Crop Rotation*Amount of crop rotation applied in Develop, rounded to the nearest degree (e.g. “2° CCW”).
Crop Amount*Relative area of the image cropped away from the original, in percent. Larger numbers indicate images left with increasingly smaller areas compared to their original.
Megapixels (post-crop)Image size, after any Develop crop/rotation adjustments, in megapixels.
Megapixels (original)Original image size, prior to any Develop crop/rotation adjustments, in megapixels.
Width x Height (post-crop)Dimensions, after any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”)
Width x Height (original)Original dimensions, prior to any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Length of Long Edge (post-crop)Length of the long edge of the image, after any Develop crop/rotation adjustments, in pixels.
Length of Long Edge (original)Length of the long edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Length of Short Edge (post-crop)Length of the short edge of the image, after any Develop crop/rotation adjustments, in pixels.
Length of Short Edge (original)Length of the short edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Width (post-crop)Width of the image, after any Develop crop/rotation adjustments, in pixels.
Width (original)Width of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Height (post-crop)Height of the image, after any Develop crop/rotation adjustments, in pixels.
Height (original)Height of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio (short:long, post-crop)Aspect ratio of the image, after any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”)
Aspect Ratio (short:long, original)Aspect ratio of the original image, prior to any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio (width:height, post-crop)Aspect ratio of the image, after any Develop crop/rotation adjustments (e.g. “5 : 4”).
Aspect Ratio (width:height, original)Aspect ratio of the original image, prior to any Develop crop/rotation adjustments (e.g. “5 : 4”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
File size (bytes)File size of the master image or video, in bytes.
Audio sidecar file*The kind, if any, of the audio sidecar file associated with the image
XMP sidecar file*Does the image have an associated XMP sidecar file?
JPEG sidecar file*Does the image have an associated JPEG sidecar file?
Video
Video Trim*Whether the video has had its start and/or end trimmed (“Trimmed at start and end”, “Trimmed at end only”, “Untrimmed”, ...).
Video Length (Trimmed)Length of the video, after any trimming in Lightroom (e.g. “17 min”).
Video Length (original)Length of the original video, without regard to trimming in Lightroom (e.g. “22 min”).
Video Frame RateFrame rate for the video (“15.000 fps”, “29.989 fps”, ...)
Audio Sample Rate (of a video)Sample rate for the audio track of a video (e.g. “48000 Hz”).
Audio Channels (of a video)Number of audio tracks (“Mono”, “Stereo”, “5.1”, ...)
Video Pixel Aspect RatioAspect ratio of pixels encoded in a video (e.g. “1”, “1.3333”, ...)
Develop (except crop)
Develop Sections Disabled*List of disabled Develop-module sections (e.g. “Paint-Based Corrections and Lens Correction”).
Red-eye Corrections*Count of red-eye corrections applied in Develop (e.g. “3 Eyes”).
Spot-Healing Corrections*Count of spot-healing corrections (i.e. dust-spot corrections) applied in Develop (e.g. “27 Spots”).
White Balance*White-balance setting applied in Develop (“Daylight”, “Custom”, ...)
Clarity*Amount of overall “Clarity” applied in Develop, rounded to the nearest +/- 5.
Color Treatment*Color vs. Black & White.
Tone Curve Name*Name of the tone curve applied in Develop (“Linear”, “Custom”, “Strong Contrast”, ...)
Lens Corrections*List of Lens Corrections enabled in Develop (e.g. “Color defringe + Manual”.
Vignette*Amount of post-crop Vignette effect applied in Develop (e.g. “Slight white vignette”, “15 black vignette”, ...)'
Process Version*Name of the Lightroom render engine applied in Develop (e.g. “2012 (standard in Lightroom 4)”).
Has Basic Tone/Presence Edits*Reports whether an images has basic Tone changes (exposure, etc), Presence changes (saturation, etc.), both, or neither.
Camera-Calibration Profile*Name of the camera-calibration profile applied in Develop (e.g. “Adobe Standard”).
Artist / Copyright
Copyright StateCopyright state.
CopyrightCopyright text.
Artist / CreatorArtist's name.
Artist and Copyright Differ?How do the “Artist/Creator” and “Copyright” fields differ? (“Artist contained within Copyright”, “Identical”, ...)
Rights Usage TermsInstructions on how image can legally be used.
Copyright Info UrlCopyright info URL.
ProviderName of person who should be credited when image is published.
SourceOriginal owner of the copyright.
Creator JobJob title of the person that created the image.
Creator AddressAddress for the person that created the image.
Creator CityCity for the person that created the image.
Creator State/ProvinceState or province for the person the created this image.
Creator Postal CodePostal code for the person that created the image.
Creator CountryCountry for the person that created the image.
Creator PhonePhone number for the person that created the image.
Creator EmailEmail address for the person that created the image.
Creator UrlWeb URL for the person that created the image.
Location
CityName of the city where image was taken.
StateName of the state where image was taken.
CountryName of the country where image was taken.
Country Code2 or 3 letter ISO 3166 Country Code of the country.
LocationDetails about a location where image was taken.
Geoencoded HemisphereGeoencoded hemispheres (e.g. “North/East”). This can also be used to answer simple “Geoencoded?” queries, and to find mis-encoded “0°N 0°E” entries.
Geoencoded Location Marked Private*Is the geoencoded location marked a private? (“Private”, “Not Private”, or “Not Geoencoded”)
Geoencoded AltitudeGeoencoded altitude (e.g. “65 m”).
Other Text Fields
Title lengthReports whether “Title” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the legnth.
Title line countReports the number of lines in “Title”.
Headline lengthReports whether “Headline” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the legnth.
Headline line countReports the number of lines in “Headline”.
Caption lengthReports whether “Caption” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the legnth.
Caption line countReports the number of lines in “Caption”.
SceneIPTC Scene.
EventNames or describes the specific event at which the photo was taken.
IPTC Subject CodeIPTC Subject.
IPTC Category (deprecated field)deprecated IPTC Category.
IPTC Other Categories (deprecated field)deprecated IPTC Other Categories.
Description WriterName of the person who wrote the description.
Intellectual GenreIntellectual genre.
Job IdentifierA number or identifier needed for workflow control or tracking.
InstructionsInformation about embargoes, or other restrictions not covered by the Rights Usage field.
Name of Org ShownName of the organization or company featured in this image.
Code of Org ShownCode from a controlled vocabulary for identifying the organization or company featured in this image.
Modeling
Plus VersionThe version number of the PLUS standards in place at the time of the transaction.
Model AgeAge of human model(s) at the time this image was taken in a model released image.
Minor Model AgeAge of the youngest model pictured in the image, at the time that the image was made.
Model Release StatusSummarizes the availability and scope of model releases authorizing usage of the likenesses of persons appearing in the photo.
Model Release IDA PLUS-ID identifying each Model Release.
Additional Model InfoInformation about the ethnicity and other facets of model(s) in a model-released image.
Source TypeThe type of the source of this digital image, selected from a controlled vocabulary.
Property Release StatusInfo on the availability of property releases.
Property Release IDPLUS-ID identifying each Property Release.
Dates
Has a “dateTimeOriginal” fieldA simple yes/no on whether the “dateTimeOriginal” field is present.
Has a “dateTimeDigitized” fieldA simple yes/no on whether the “dateTimeDigitized” field is present.
Has a “dateTime” fieldA simple yes/no on whether the “dateTime” field is present.
Has a “dateCreated” fieldA simple yes/no on whether the “dateDreated” field is present.
Do the various date fields agree?Reports on whether the “dateTimeOriginal”, “dateTimeDigitized”, and “dateTime” fields are the same

Results Dialog

After the plugin does its work, it brings up a dialog to display the results, for example:

I've spent considerable energy on tailoring the presentation and default sort for each of the 131 criteria the plugin supports. In the “Lens” example seen here (which Adobe's Library Grid Filter does support, though not as well), I take care to sort the lenses by focal length, and to pretty up the presentation (e.g. “50 mm” instead of “50.0 mm”).

Some features of the results dialog:

  • Click on an “isolate” button to create a collection named for the criteria and result, populate it with the appropriate photos, and switch to it.

  • Click on the “Isolate All...” button to create all the individual collections and dismiss the dialog.

  • Click on two or more checkboxes to enable an “Isolate Combined Checked Items” button that creates one special collection with all the photos of the checked rows.

  • Click on a column header to toggle the display sort.

  • Click on a photo- or video- count number to display some percentage information. In the example above, clicking on the “8,306” of the “Voigtländer 125mm f/2.5” row reveals that 31.9% of the target photos were taken with that lens (because it's such an oh-so-sweet lens whose results I adore).

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.20 Update for Lr5
20130420.19

Added "Folder Name" and "Path Name" to the list of search items.

20130415.18

Added the “Has Basic Tone/Presence Edits” search item.

Fixed the “dateCreated” search.

20130412.17 Build system update.
20130330.16 Added some Ricoh cameras to the crop-factor database.
20130328.15 Fix for the registration system.
20130311.14

Added "Total Exposure (Ev) and Total Effectiv Exposure (effective Ev).

Filled in some areas where the docs were not yet written.

20130219.13 Added some notes to the aspect-ratio results to denote common aspect ratios (e.g. 16:10 is a widescreen monitor)
20130218.12 Added some extra text fields (title, caption, etc.)
20130214.11

Added the ability to identify images with sidecar files.

In the criteria-selection dialog, warning messages would sometimes get truncated.

20130212.10 Added some date fields
20130209.9 More build-system maintenance
20130206.8 Tweak for my registration system
20130124.6 Added a bunch of Canon cameras to the crop-factor database.
20130119.5

Computation for the megapixel notation for "Width x Height (post-crop)" was wrong.

Many of the pixel-size items crashed when used on videos.

20130111.4

Focal-Length 35mm crashed if a photo didn't have focal-length data.

Added a bit of buffer to the dialog-height calculations to help ensure that the dialog doesn't grow taller than the screen.

20121113.3 Made "Dimensions" available for video.
20121020.2 Added "Lens Corrections"
20121019.1 Initial public release.

Comments so far....

This feature may be useful for something else (ie Catelog Management).

My catelog is 1.2Gb and growing. I am not worried about 1.2 GB disk space, but backup less frequently than I should when exiting Lightroom because of the length it takes.

I have explored my catalog and discovered the following.

Catalog Size 1.2 Gb
Metadata Table 515 mb
History Table 492 mb
Largest 75 images history Approx 253 mb
Largest 200 images meta data Approx 35 mb

It would be extremely useful to find all images which consume individually say more than approx 1mb or 10 mb of catelog space (or some other sensible number / criteria).

This figure could be calculated approximately by querying the Metadata and History on the key of image number (len of string fields within record).

I may have a collection of images which I no longer need or could refine just sitting in my catalog. If this selection was available in this tool, I could isolate these massive metadata hogs (remove, delete, refine, export to an archive catalog,etc) and massively improve the internal storage needs of my catalog.

I welcome any comments.

Unfortunately, Lightroom doesn’t give a plugin insight into much of this. Something running outside of Lightroom could perhaps access the SQL database directly to figure this out, but this seem dicy to do while Lightroom is running. —Jeffrey

— comment by Matt O'Brien on October 23rd, 2012 at 12:35am JST (6 months, 28 days ago) comment permalink

Hello from France,
Great little plug-in – again !
I cannot try it right now, I have only an XP computer available ; I’ll try it tonight on my home computer with LR4.
There is one thing I’d like to have and do not see in your list : would it be possible to find pictures that Lightroom cannot read except for a small preview ? I have sometimes this problem with pictures I get from the internet, always black & white. Lightroom displays a small preview and a warning sign in the top right of the icon of the picture. Here is an example of such a picture (I could only test it was in error on my LR3 on this XP computer, but usually the problem is the same on LR4, I’ll double check tonight) :
http://www.railpictures.net/viewphoto.php?id=411458&nseq=105
I usually get batches of pictures, then have to open all of them to see which one are in error. I then just open these (usually with Irfanview) and save them without doing anything. That solves the problem, but I would like to have just the pictures in error without having to test all of them…
The plug-in is great already, that would just help me to solve one more problem.
Thanks for your great work, I like a lot your plug-ins
Laurent
I don’t know of a way for a plugin to find out that kind of status, but you might consider trying this: select all the newly-imported photos in the library and click on “Auto Tone” in the quick-develop panel, then set the grid sort to “Edit Time”, and ones at the bottom require your Irfanview attention. —Jeffrey

— comment by Laurent on October 23rd, 2012 at 11:18pm JST (6 months, 27 days ago) comment permalink

Hello Jeffrey,
Great idea ! I tried it on LR 3.6 (again, I’ll try on LR 4.2 tonight), and it works… well, not exactly as expected, but it seems the process of auto-toning pictures stops when encountering an image in error. So, once sorted per modification date, the picture at the beginning of the not-modified pictures is one of the pictures in error… At least that helps !
Thx for taking time to find a solution, and continue your great job with your plug-ins !
Laurent

— comment by Laurent on October 24th, 2012 at 4:57pm JST (6 months, 27 days ago) comment permalink

Jeffry,

A VERY useful plugin I have been dreaming about would allow the storage of “smart” filters and collections within actual image folders. One of my major (insert profanity) peeves with LR is that collections are stored way off down at the bottom, where they re really inconvenient to get to and use. IN fact, theyr;e USELESS where they sit, since I have to break my workflow just to use them (insert more cursing). I want these to be accessible from a normal project/image folder. I would pay real money for this kind of functionality.

You would know better than me, but I presume it would be possible to create a (hidden?) metadata file that a plugin reads, and store that metadata file in the actual project folder…yes? What about also storing Develop presets in a separate file, also in the real filesystem project/file folder? That would allow a folder of a job to be mostly portable from one machine to another without the tedious job of exporting/importing a library for one simple folder exchange.

I dislike and cannot use Capture one for a range of reasons, but their Sessions are one good way to do this. I had to make a very difficult choice between LR and Aperture, in which LR won, but I was not happy with the compromise. I very much prefer the Aperture way of allowing the library hierarchy to me stored and accessed with albums, projects, and folders.

Good ideas all, but as you’ve discovered, far from how Lightroom was designed. I don’t seen any easy way (or even hard way) to do these things. )-: —Jeffrey

— comment by Nathan Padilla Bowen on October 27th, 2012 at 2:42am JST (6 months, 24 days ago) comment permalink

Jeffrey,

Just tried it. You are the man! I sometimes have 20 versions of a file, at different sizes and formats from different uses. Now I can see them very quickly in a clean, organized collection.

Next, stack multiple filters from one interface?

Donating now…thanks for the useful plugins.

…San Diego, CA

— comment by Nathan Padilla Bowen on October 27th, 2012 at 2:49am JST (6 months, 24 days ago) comment permalink

Trying your example of copyright info… I ended up with 57 entries! Should be around half that. When using the metadata filters to find erroneous location info, I find I use it like a Smart Collection so that when metadata is “fixed”, it drops out of the filter. Is it possible for this plugin to create Smart Collections vs normal when isolating? I fixed several erroneous groups of copyright names but the collections still contain the now fixed entries under a collection name that doesn’t match the data.

No, that’s the problem… the smart-collection rules are not expressive enough, which is why I made the plugin in the first place. If you could do it all with smart collections or the grid filter, we could dispense with this plugin altogether. As it is, you can quickly reapply the same search on the current photos to re-reflect the new reality. —Jeffrey

— comment by JasonP on November 13th, 2012 at 6:53am JST (6 months, 7 days ago) comment permalink

Hello, another great plugin idea as usual. I’ve come across an issue when trying to examine my photographs by “focal length 35mm equiv”. Shortly after the progress dialog displays “Analyzing…” I get an error message stating “Items:258: bad argument #2 to ‘?’ (number expected, got nil). I’m assuming this is due to me having some bad exif data somewhere in my images (the “focal length” metric works just fine, and properly shows “(unknown)”). Is there anything else I can do to help debug this problem?

- Maryland, USA

Sorry about that… I’ve (finally) pushed a fix that takes care of it. —Jeffrey

— comment by Eric on December 11th, 2012 at 8:21am JST (5 months, 9 days ago) comment permalink

Hi. I love all your lightroom tools, and I’ve just come across this one because I’m trying to filter files based on exifdata that LR doesn’t read (but exiftool does).

The problem is that your tool doesn’t include the specific fields I’m looking for, so… If possible, could you think about adding a custom search to this? Just a key/value search (based on the exif tag name) or a list of all values for a key.

In my specific case, I’m trying to tag different cameras of the same model via the serial (LR reads some serials, but not from this camera). Also trying to add keyword tags for picture effects (e.g. “pop color”) from the camera.

Thanks again!

Sorry, but Lightroom doesn’t make that data available to the plugin. It wouldn’t be impossible if I fire off a separate process to check the photos, but it would be extremely slow, having to read every byte of every photo… potentially hundreds of gigabytes… and could take hours for one search. It just doesn’t seem worth it. )-: —Jeffrey

— comment by Mark on January 6th, 2013 at 2:58pm JST (4 months, 14 days ago) comment permalink

Hi Jeffrey

I have a (minor) bug with your Data Explorer: when I am exploring a descriptor with lots of values (Image Width in my case) the “Dismiss” button is shown below the bottom of the screen. The explorer window doesn’t have any resize controls (in fact, the title bar is shown in gray as if it wasn’t the top window), and if you don’t know that the Dismiss button is there, it isn’t clear what to do.

I try to calculate the maximum size of the dialog down to the pixel, but Lightroom doesn’t make it easy, so I’m off somewhere. I’ve just pushed a new version that is less aggressive… if it’s still bad, please email a screenshot and I’ll try to find where my calculations are off. —Jeffrey

— comment by Alan Harper on January 7th, 2013 at 3:34am JST (4 months, 13 days ago) comment permalink

Hallo,

is there a possibility to check also to the points (develop / Basic module) : highlights, shadows, whites and blacks with your plug in data explorer? I am afraid, I could not find it.
If not, will you integrate it in the future?
Thanks & rgds
Pit / Germany

I added the “Has Basic Tone/Presence Edits” search item to a new version I just pushed… does that help? —Jeffrey

— comment by Pit on April 14th, 2013 at 3:20pm JST (1 month, 6 days ago) comment permalink

Hi,

Its possible to build in a search function similar “same develop settings” ?
I work with the function “synchronize develop settings”
I ignore or forgot by mistake some of these images.
Thus, i could filter them later out.
Is this possible?
THANKS!

Best greetings Wolfgang

Wow, that’s a great idea, but I can’t get to it right away… it’s been added to the todo list. —Jeffrey

— comment by Wolfgang on May 19th, 2013 at 9:44pm JST (8 hours 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.

More or less plain text — see below for allowed markup

You can use the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting