.
Jeffrey’s “GPS Proximity Search” Lightroom Plugin

This plugin allows you to find geoencoded images in your Lightroom catalog that are within some specified distance from a location you choose.

This plugin works in Lightroom 5 (and older versions as far back as Lightroom 2, 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.

For details, see the Announcement and Instructions, and the version history below.

(This plugin works with images that have already been geoencoded: if you'd like to geoencode images, see my Geoencoding Support plugin.)

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 Lr4 to Lr5, 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 )

20140731.76 Registration fix for Lr5.6
20140729.75 Previous updates broke support on Lightroom 2
20140722.74 Update to recognize "new" Google Maps urls
20140715.73

Fixed an issue with Creative-Cloud revalidation.

20140712.72

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

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

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.69 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.68 Build-system update
20140621.67 Added an "Expunge Plugin Data" section to the plugin manager, to allow plugin data to be cleared from the catalog.
20140422.66

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

20140417.65

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

20131031.64 The new fast proximity search added in 20130929.63 would finish silently (wouldn't report "no images found") if there were none in range, but some were sort of close.
20130929.63

Added a new "File > Plugin Extras" menu item: "Fast Full-Catalog Proximity Search", to isolate all photos in your catalog that are geoencoded within X distance of the current photo.

In Lightroom 5 on OSX it's ridiculously fast (a second or two). On Windows or older versions of Lightroom, it takes longer... two and a half minutes to search 130,000 photos on my circa 2010 laptop.

20130926.62 Oops, fix a bug introduced in the previous update
20130925.61

A fix for the previous update.

20130919.60 Changed all distance calculations from spherical geometry to ellipsoidal geometry, raising the level of accuracy from "way more than good enough" to "ridiculously overprecise". :-)
20130613.59 Better support for plugin revalidation.
20130611.58 Yet another Lr5 update
20130524.57 Apparently, a recent change broke things on Lr2, which some folks apparently still use.
20130501.56 Update for Lr5
20130412.55 Build system update.
20130328.54 Fix for the registration system.
20130209.53 More build-system maintenance
20130206.52 Tweak for my registration system
20120608.50 Fix an "attempt to perform arithmetic on field" error.
20120526.49

Update to handle the Mac App Store version of Lightroom.

Tweak for Lr4.1RC2.

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.48 Update to handle 4.1RC
20120309.47 Had broken registrations in Lr2; Update to the debug logging to better track down timing issues that might arise.
20120304.46

More updates for Lr4.

20120221.45

More updates for Lr4.

20120128.44

Considering the utility of the Map Module in Lr4, I don't intend to really support this plugin for Lr4 and beyond, but in order to at least let it run, I've had to adapt for Lightroom APIs being discontinued in Lr4.

20120114.43 More tweaks for Lr4b
20120112.42

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

20111210.41

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

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.

Had issues with the registration button sometimes not showing.

20110103.40

For Lr3, now offer the option to populate a collection with in-range images, that then can be sorted by distance from the search epicenter.

Replaced the ugly reporting dialog shown after a search with a different ugly reporting dialog.

Now remembers the search epicenter input text from invocation to invocation.

Canceling a search now really cancels everything, rather than merely leaving the results where they were when cancel was hit.

In Lr3.2 or later, returned the most-selected-image thumbnail that went missing in Lr3.0.

20100829.39 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100820.38 Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin, so am pushing out rebuilt versions of all plugins just in case.
20100817.37

Added code to allow plugin revalidation after having been locked due to a bad Lightroom serial number.

20100625.36 Yikes, shaking out some more build issues.
20100624.35 Discovered a nasty build bug; pushing a new version in case it affects this plugin.
20100608.34

This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

20100516.33 Update for the Lr3 beta.
20100317.32 Oops, introduced a bug that caused the plugin to become disabled on Windows if it was enabled when LR started.
20100315.31

Wholesale changes that attempt to honor the user's locale settings for numeric display (e.g. Europeans writing 3,14156 for pi). I've probably missed some spots, so let me know if you find some.

20100225.30

Tidied up the UI a bit.

Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version.

20091205.29 Minor internal debugging tweaks.
20091027.28 Fixed an "EXEC" error introduced into the previous version. Also more LR3b fixes.
20091022.27 Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system.
20090714.26

Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it.

20090604.25 It seems that the thumbnail being used to illustrate the "most-selected" image was, in some cases, taking over the entire screen. I think I've fixed it.
20090525.24 Added an "import location from Google Earth" button, as well as a "Show Crosshair Target in Google Earth" button. The crosshair target is really helpful when pinpointing a spot exactly, and it's much nicer, I think, than others I've seen.
20090521.23

Renamed the plugin label from "GPS Proximity Search" to "Proximity Search", since GPS isn't really a synonym for "geoencoded location".

Fixed a "loadstring" error some users got.

20090510.22 Added a link in the Plugin Manager to the plugin's update-log RSS feed.
20090509.21

Redid the internals so that proximity searches on small groups of images (say, several thousand images or less) are now much, much faster. Added the thumbnail of the most-selected image to the dialog. Removed the plugin expiration, which I should have done before, but apparently forgot.

20090425.20 Tweaked how the plugin tries to update itself during the one-click upgrade process, to hopefully get things working for those few Windows users that have never had it work. Crossing fingers. We'll see.
20090313.19 It seems that PayPal doesn't give everyone a "Unique Transaction ID" in the registration confirmation mail; some people get a "Receipt Number". So, the registration dialog now accepts that as well.
20090228.18 Fixed a bug that caused a plugin crash if my server couldn't be reached during registration.
20090129.17 Small housekeeping update for the new locales supported by Lightroom 2.3.
20090116.16 It turns out that the automatic upgrade stuff doesn't work if the plugin folder has been renamed from its original. That should generally not happen, but it's possible, so the plugin now checks its own location reports the issue to the user if it finds it.
20090115.15 Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people.
20090110.14 Added a checkbox in the Plugin Manager to turn on enhanced debugging (more stuff in the plugin's debugging log), and added a button in the same place that sends your log to me. Particularly for “the upgrade button doesn't work” and “error while uploading” type issues, this should be useful for debugging.
20090107.13 Can now handle Google-map urls that result from an address lookup.
20081211.12 Development seems to have settled down, so pushing back the expiration for several months...
20081126.11 The "within" input box was limited to a maximum value of 100. Hadn't noticed that. Removed the limit.
20081124.10 Perhaps fixed a problem whereby the "Upgrade Now" button didn't work for some Windows users. We'll see whether it works when those users upgrade from this version to whatever version is next.
20081121.9 Fixed attempt to concatenate field 'base' error. Push expiration data back again.
20081117.8 No new functionality in this version, but a huge upheaval in the underlying code to repair an unfortunate design choice I made early on in the development that had limiting consequences I'd not foreseen. There are likely bugs introduced in this version, and as such, it has a short expiration date to encourage updates as those bugs are reported and fixed. If you do run into an error, please send (via email) the log referenced in the upper-right of the Plugin Manager. Thanks.
20081115.7 Push out the expiration until the end of the year....
20081030.6 Oops, yesterday's push broke it when not using my GPS-Support plugin. I think this'll fix it.
20081030.5 Fixed a crash introduced in the previous version. Now handles urls from non-US versions of Yahoo! Maps. Fixed a few bugs in the latitude/longitude parsing code, so that it now actually handles hand-written lat/long pairs the way it was documented to handle them before.
20081030.4 Now properly handles the dialup version of Yahoo! Maps when accepting a url for the search epicenter location.
20081029.3 Now compatible with my GPS-Support plugin. I also removed the "View location in..." plugin-extra items from this plugin, because I moved them to the new one.
20081022.2 Added the "GPS Proximity Results" metadata tagset, so now now the results view is a bit cleaner than using the "All Plug-in Metadata" tagset.
20081017.1 Initial Public Release

Comments so far....

Is there any way to index the GPS data in some way that permits faster searching? ETA for me is 5 minutes to search against 21k images in the catalog.

Not easily… the plugin has to manually check each target image, so the only way to get around things would be for you to select fewer images prior to invoking the search. —Jeffrey

— comment by Andy on October 22nd, 2008 at 12:44pm JST (5 years, 10 months ago) comment permalink

I’ve just found out that Lightroom actually supports plugins now and tried out your GPS search. Very well done, I’ve waited for that feature already… There’s only one problem here: Doing a search on my 3000 photos updates the “within range” field that I can filter on then. Doing another search breaks things when filtering on this: Within range = yes, flagged and unflagged photos, no colour label. The number of results in the metadata columns are inconsistent (usually the number must be the same in every selected row of all columns, but it’s not anymore) and it finds way too few photos. The problem is gone after a Lightroom restart. Lr 2.1 on Windows XP here. Any idea what’s going on there? Screenshot of the invalid programme state upon request via e-mail.

— comment by Yves on October 25th, 2008 at 7:10am JST (5 years, 10 months ago) comment permalink

Lovely idea, especially in this day and age of geotagging – which I whole heartily think is a worthwhile activity for future use.

I was wondering if for a potential geotagging plugin you could pull the same api Picasa does for Google Earth (should you go this route for tagging) and pull the info that way.

I use Picasa w/ lightroom – it’s way way faster as a DAM tool and the google earth integration is awesome (if not a little slow for me); I can’t see me leaving Picasa completely as speed in lightroom is a world apart (instant v seconds or minutes to do things) from it, but the more time spent in one application for metadata-ing the files the better in my opinion.

Thanks for this plugin, and the others, they truly make LR a usable product :)

— comment by Mike Lee on October 28th, 2008 at 7:17pm JST (5 years, 10 months ago) comment permalink

Jeffrey,

Tried to get this to work last night and kept getting a errors:
[....]
At line 9075: Attempt to access property “data” that’s not declared in Info.lua

All my images tried were d300 nefs and are hard coded withthe GPS using Geosetter taking the data from a Phototrackr GPS.

Any ideas ?

Many thanks in advance

Simon

I introduced an error yesterday, sorry. I just pushed .6 that should fix it. —Jeffrey

— comment by simon leppard on October 30th, 2008 at 10:45pm JST (5 years, 10 months ago) comment permalink

Jeffrey

Super thats working now….

Many txs

simon

— comment by simon leppard on October 30th, 2008 at 11:50pm JST (5 years, 10 months ago) comment permalink

Hello Jeffrey,

Thank you for this plugin, it’s great!

The searching functionality works well, and the metadata are displayed correctly.

But I have a small problem with the filter’s functionalities of the library: “Meters Away” and “Direction” don’t work. Only the filter “Within Range” works correctly.

I’m working with Windows XP (French) and Lightroom 2.1.

Yes, unfortunately, this is a bug in Lightroom. I reported it some time ago, so here’s hoping that the next update addresses it… —Jeffrey

— comment by Etienne on October 31st, 2008 at 8:42pm JST (5 years, 10 months ago) comment permalink

Working great now against GPS data in the Nikon NEFs I have. Fantastic plug-in! Thanks.

— comment by Phil Scott on November 1st, 2008 at 5:04am JST (5 years, 10 months ago) comment permalink

Hi Jeffrey
This concerns GPS proximity search 20081030.6
I am working with LR2.1 Win Vista (in French , so my translation of messages is certainly inaccurate.)

First it’s really great to be able to search from gps coordinates INSIDE LR . Congratulations and thank you for this great work

I have a little problem : when I add “within range” in the library filter, it shows correctly the 17 pics within range (the “YES” filter), but does not select the pics out of range : LR says : “no picture corresponds to the filter”, when I select the “NO” filter . While in the filter its sorts them out correctly ( 17 are well classified within “YES” filter, and 16 are well classified out “NO” filter)

— comment by Herve on November 10th, 2008 at 2:23am JST (5 years, 9 months ago) comment permalink

Hi Jeffrey
This concerns GPS proximity search 20081030.6
I am working with LR2.1 Win Vista (in French , so my translation of messages is certainly inaccurate.)

First it’s really great to be able to search from gps coordinates INSIDE LR . Congratulations and thank you for this great work

I have a little problem : when I add “within range” in the library filter, it shows correctly the 17 pics within range (the “YES” filter), but does not select the pics out of range : LR says : “no picture corresponds to the filter”, when I select the “NO” filter . While in the filter its sorts them out correctly ( 17 are well classified within “YES” filter, and 16 are well classified out “NO” filter)
This happens when I select “ALL” in the contry field filter (33 pics)
BUT not when I select “France” in the country field filter , (33 pics) as all were taken in France . In that case every thing works fine !!

This is, unfortunately, a bug in Lightroom. As far as I know, my plugins are the only ones in the world using this “custom metadata” feature, so it hasn’t gotten much testing yet, so my plugins are doing the testing. )-: —Jeffrey

— comment by Herve on November 10th, 2008 at 2:34am JST (5 years, 9 months ago) comment permalink

Hi,

I updated the Ver.13 and there seems to be the same problem as I had last version. Here is the log file

Execution/debug log for Jeffrey’s gps plugin for Lightroom, version 20081111.13
Log started November 11, 2008 12:09PM local
November 12, 2008 03:09AM JST
Plugin folder: /Library/Application Support/Adobe/Lightroom/Plug-ins/gps-jfriedl.lrplugin
Lightroom version 2.1.0 build 512205 for Macintosh (Locale: en).
———————————————————————————————-

At line 13192: ?:13280: attempt to index a nil value

+6.2: At line 13192: ?:13280: attempt to index a nil value

Thanks. Lucas

— comment by Lucas Liu on November 12th, 2008 at 3:12am JST (5 years, 9 months ago) comment permalink

Version 20081030.6

I just installed this for the first time, and receive a bold red mesage “WARNING: this plugin version expires in 4 hours. Please update to a new version soon.”

Is this normal?

btw, great work so far; Lightroom would be a lot less useful without you!

Sorry about that. I guess that plugin has settled down a bit, so hasn’t been updated lately. I’ve pushed a new version. —Jeffrey

— comment by Shaun on November 14th, 2008 at 7:46pm JST (5 years, 9 months ago) comment permalink

On a more general note Jeffrey, why do your plug-ins have an expiry date and do they in reality really expire i.e. stop functioning. If any particular plug-in appears to be working (I use both the GPS Proximity and Flickr plug-ins) is there then any real need to upgrate? Thanks.

I’ve gone over this all before. Yes, they really stop working, and so yes, there is a real need to upgrade. Getting people to upgrade from old versions is the very reason to have it. —Jeffrey

— comment by ElliR on November 22nd, 2008 at 9:40pm JST (5 years, 9 months ago) comment permalink

hello… your new registration sucks.

i don´t have paypal and im not going to get an account for a one cent transaction.

PAYPAL SUCKS!!!!

— comment by Peter on October 28th, 2009 at 4:45am JST (4 years, 10 months ago) comment permalink

Hi Jeffrey! How about incorporating presets in the Proximity plug-in?

— comment by Lars on January 11th, 2010 at 8:45pm JST (4 years, 7 months ago) comment permalink

I some older version I could get the GPS data out of a .gpx file.
I used it a lot because I use a Garmin 60CSx while taking pictures.
But with the new version, is this function gone??? Atleast I can’t see how to ímport’a .gpx file anymore… Can you help me because to me, it was a VERY, VERY usefull function!

I don’t think my proximity-search plugin ever did anything with tracklogs…. perhaps you’re thinking of my geoencoding plugin? —Jeffrey

— comment by Stefan on February 6th, 2010 at 3:58am JST (4 years, 7 months ago) comment permalink

Since upgrading to Proximity Search 20100315.31 earlier today, whenever I start up LR2.6 I receive the following error message – ‘An error occurred while reading the scheme for the plug-in ‘Proximity Search’. The plug-in will be disabled’. Upon clicking OK Lightroom starts up as normal but of course in the Manager the plug-in is disabled. I am able to click on ‘Enable’ which works but when Lightroom is shut down and then restarted the same error message is repeated. XP3 SP3.

Thank for the report… just pushed .32 that should fix it —Jeffrey

— comment by Alan on March 16th, 2010 at 11:49pm JST (4 years, 5 months ago) comment permalink

Have you had any feedback from adobe regarding fixing the thumbnails working with LR3 in the reverse geotagging function?

You’ve got to realize that it’s not a case of “fixing”… I was going way Way WAY out of the normal path to finagle the thumbnails I was getting… it was imperfect, unreliable, and highly unsupported. I invested a lot of work to get even that much working, and now it’s all for naught, and I don’t blame them one bit because I knew the risks when I went down that path. I know users don’t care about this background…. they just want the feature back, as I do when I use the thing (it’s one of the few plugins that I actually use), but it’s best to consider it fun while it lasted, rather than something now broken. I did ask them about hooks so I could try the same thing again, and for whatever reason those hooks did not appear, but I have one last idea in the back of my mind to explore. I don’t think it’ll be fruitful, but you never know…. —Jeffrey

— comment by Jesse on June 18th, 2010 at 2:10pm JST (4 years, 2 months ago) comment permalink

I tried copying the contents of gps-proximity-20100625.36.zip to my plug-ins directory a McAffee blocked the file GetCurrentGEView.exe because it says it contains the Artemis Trojan. What’s the source of this file and is it safe? I can force it through but would like to understand where the file came from and is it a possible pattern false alarm from my Virus software?

Thanks. Haven’t tried any of your plug-ins yet, waiting for Adobe to fix the LR 3 import problems first before I do any more work with any of my databases!

The plugin is fine… report it to McAffee so that they can update their stuff. The exe hasn’t changed in a year, so it’s frustrating that they still can’t get their act together. —Jeffrey

— comment by Dan on July 13th, 2010 at 10:26am JST (4 years, 1 month ago) comment permalink

I think incorporation of location presets would much improve the otherwise great proximity plug-in. I am using it to locate images taken nearby know scientific plots or know musk ox carcasses in Northeast Greenland. Having presets would make this so much easier.

— comment by Lars on November 24th, 2010 at 4:42am JST (3 years, 9 months ago) comment permalink

I like this plugin which makes geoencoding useful for search. I would like to be able to sort by distance, unfortunately Lightroom doesn’t provide access to this metadata for sorting. One idea I got : as output to plugin create a collection in which the “user sort” is made according to distance.

I was going to dismiss the idea as impossible with the current limited tools that Lightroom makes available to plugins, but then got the idea that I could use “added order” in combination with a distance sort prior to populating a collection, but it turns out for whatever reason (likely a Lr bug) that when do that, “added order” does not work…. but “user sort” inexplicably does! So from version 20110103.40 it can populate the collection (in Lr3 or later) and when you set the collection to “user sort”, assuming you haven’t rearranged the thumbnails yourself, they’ll be in order by distance. Rename the collection if you want to preserve a specific set of results, because the same name is used for each search. Thanks for the great idea! It’s a really kludgy plugin (my first non-uploading plugin, from long ago), but this update helps, at least in Lr3, make it a bit less kludgy. —Jeffrey

— comment by Alain on December 24th, 2010 at 1:15am JST (3 years, 8 months ago) comment permalink

Jeffrey – great plugin. In common with a few other users, I’d really like to be able to use presets with this plugin. Preferably exactly the same presets that I created with your Geoencoding plugin. Is this something on your future feature list? – thanks, Paul.

— comment by paul on May 3rd, 2011 at 12:45am JST (3 years, 4 months ago) comment permalink

Hi Jeff,

The following is a serious gotcha (at least for me): I have a series of Publish Services setup via “jf SmugMug” such that all of my originals automatically get sent “as-is” to SmugMug for backup/archival purposes. This seems to be working fine.

Yesterday I ran a “jf Proximity” on my whole catalogue, which worked as expected, except that LR now considers that **all** of my images have been altered and wants to refresh the archival copies at SmugMug! (that’s >8000 images and about 30Gb) I presume this has been caused by jf Proximity changing the “within range”, “meters away” and “direction” attributes.

From the start, I had configured these Publish services such that no metadata changes would ever trigger an update, but it looks as this might be broken.

I’m using LR 3.3 and up-to-date (as of yesterday) versions of “jf SmugMug”, “jf Geocoding” and “jf Proximity”.

I’d rather not have to restore my most recent catalog backup, so… how can I convince LR to not want to refresh those images?

I’ll have to look into whether the proximity stuff is causing images to be marked for export (it certainly shouldn’t), but in the mean time, select all the affected images, then visit the SmugMug Extras dialog, and “Re-Mark as Published”. —Jeffrey

— comment by Antonio on May 27th, 2011 at 1:03am JST (3 years, 3 months ago) comment permalink

Fantastic plug-ins, 1000x thanks! it really helps to sort through similar pictures taken at around the same place.

But I’m a bit surprised by the slow speed because while it’s searching I notice almost no hard drive activity and CPU is at 0% (Core i7 at 4.4Ghz, 8Gb ram, SSD drive). Do you have an idea where the search is spending its time? I guess the issue comes from LR rather than your plug-in but being a programmer myself I’m really wondering what cause this lack of performance (which is still OK, less than 1 minutes for 1000 pictures).

The delay is the query the plugin makes under the hood to get the image data from Lightroom. I’m not sure what’s going on because it’s a black box to the plugin, but yeah, it’s frustrating. —Jeffrey

— comment by Emmanuel on July 26th, 2011 at 11:37pm JST (3 years ago) comment permalink

How to uninstall? I mean… How to remove all the data the plugin have added to catalog?
Thank you

In all these years this is the first request for something like this. I guess it really should be there, so I’ve added a “Clear Data” item to the “Etc” tab of the Geoencoding-Support Dialog. —Jeffrey

— comment by Danilo on May 30th, 2014 at 10:09pm JST (2 months, 23 days ago) comment permalink

I can’t find the last version with the uninstall feature, can you help me please? Thank you

There’s no uninstall feature… just delete the plugin if you don’t want to use it anymore. —Jeffrey

— comment by Danilo on June 16th, 2014 at 4:56pm JST (2 months, 7 days ago) comment permalink
Leave a comment...

See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. PLEASE REPORT THE NAME AND FULL VERSION NUMBER OF THE PLUGIN WITH EVERY REPORT. Seriously. I need the full version number or I likely can't do anything but ignore the message.


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