folder-watch-20100111.10.zip
· 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 attempts to fill deficiencies in Lightroom's built-in Auto-Import facilities, allowing you to auto-import images in place, in a folder or a whole tree of folders. It's likely of most use to those who shoot tethered.
This plugin is currently in beta release, without much documentation. Please see the version history below for information.
Availability
This plugin is distributed as “donationware”. I wrote it and 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 costs the minimum 1-cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is optional and completely up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
Lightroom 3 — Registrations in Lightroom 2.x will not carry over to Lightroom 3 when it is released, so plan that you'll have to re-register if you upgrade to Lightroom 3. (That's for the real Lightroom 3.... registration is not required in the Lightroom 3 Public Beta, but be warned that plugin support is spotty and plugins may not work well there.)
( Update Log via RSS| 20100111.10 | Reimport a scanned file if it has changed (size or create/modification date). Thus, if you move a file out of the scanned tree from within Lightroom and later add another file with the same name, it'll get imported. I also now report only the number of files scanned each time; folders are not included in the scan count. |
| 20091221.9 | Added some heuristics to avoid importing a file that's still being written to disk. Modification times reported to the plugin are a bit imprecise, but if an image file seems to be less than a second old, it is not imported. |
| 20091205.8 | Minor internal debugging tweaks. |
| 20091022.7 | 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.6 | 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. |
| 20090521.5 | Fixed a "loadstring" error some users got. |
| 20090511.4 | Now it quietly ignores images that Lightroom can't process. The failure is noted in the plugin log. (It's on the to-do list to expose an "activity log" where this event might be more readily accessible.) |
| 20090510.3 | Added a link in the Plugin Manager to the plugin's update-log RSS feed. |
| 20090509.2 | Added a "show splash dialog" option to the "upon import of a new image..." configuration, so that you can be informed when the plugin imports a new image in the background for you. You can configure whether the splash is shown, and if so, for how long before it automatically disappears. I've not tested this too much, so I don't know what problems it might cause having a background task (the folder watch plugin) throw up a splash dialog. It seems to work okay, except... .. if a splash dialog pops up while you're painting local corrections, it'll do bad things to the current brush stroke, such that after dismissing the splash dialog, you'll have to undo the brush stroke you were working on and redo it. I also realized one other caution: when the plugin imports a photo for you, that import action is added to the undo stack. This happens whether the import is accompanied by a splash dialog, or if it's totally silent in the background. The worry this creates is that if the import happens just before you do a bunch of undos, you may unwittingly undo back past the import and not even notice. The only option I see around this problem is even worse: having the import pop up a warning dialog that it's about to clear the undo stack, and then actually have it clear the undo stack. So, if this is a practical worry for you, enable the splash screen. I also fixed the home-page url, and the folder-to-watch edit box, which would sometimes show only a partial folder path on a OSX. The report of overall session imports is now red when something's been imported this session. It also turns out that if you reload the plugin, Lightroom doesn't completely do away with the previous instance, so it was possible to have multiple versions of the plugin running and not even know it. It's a big hairy mess, but I think I've worked around it in this version. The plugin also refuses to scan if it's not enabled. I also added an option to restart the watch when Lightroom is started, so that you can have it running all the time. Along with that is an option to throw up a splash screen during Launch if the plugin has been set to scan at launch. You can use this to remind yourself that the thing is running. |
| 20090428.1 | First public version. Pretty rough at this point. Currently, everything is controlled from the Plugin Manager, which is probably not the best UI. Pick your folder to watch, the frequency with which to check, then click the "watch!" checkbox to turn it on. You can then leave the Plugin Manager and, most likely, open the target folder in Grid Mode (perhaps sorting to most-recent first). Some random notes:
|
Fantastic! I’ve wished that there was a way to setup “in place” auto imports ever since I installed Lightroom.
Thanks!
btw, it would be great if there were the option to have Lightroom call up the import dialogue when new images are detected. I’m not sure if that’s possible.
It’s not possible, unfortunately. The Lightroom plugin infrastructure gives exactly one option to the “import new photo” hook, and that’s to stack the new photo with some preexisting photo. I’m sure future versions of Lightroom will expand on this, but now it’s as bare bones as it can be, which limits the practical usefulness of this plugin. —Jeffrey
Jeffrey, when it does an ‘import’, where does it import it to?
I have a file structure, outside of LR…and the catalog inside LR mimics that same structure.
The reason I ask….I have the ‘2009′ tree on the watch list (currently ~7K images…take 0,4 sec to scan). Set up to only import new images. I added an image which created a subfolder. I can’t tell if it imported the image, but the folder was definitely not set up (in the catalog). BTW…I have never set an ‘Auto Import’ settings.
Thanks…John
It imports them in place. If the folder doesn’t currently exist in the tree you point to, it’s added. You should find it in the Folders panel on the left side of the Library module. If it’s on a volume (e.g. drive) not currently represented there, it’s added. To the best of my knowledge, though, this plugin is the first and only plugin to take advantage of the (limited) import support provided by Lightroom’s plugin infrastructure, so there well may be bugs that have not come to light, so if you can’t find it after fishing around, please contact me via email. —Jeffrey
just one question.
As i didn’t find a lot of documentation about this plugin, can you tell me the difference between this plugin and the automatic function in lightroom” auto import”?
sorry for my English…
ciao
+Marko
The built-in Automatic import copies from the import location, while the plugin imports in place. Also, the plugin can handle a whole tree. —Jeffrey
There were a couple “bugs” (caused by what I keep in my file structure). Took me a while to report them, but Jeffrey fixed them overnight…(luckily his day :~)
Folder-Watch is absolutely wonderful. Exactly what Adobe should have built into LR in the first place.
The “tree” I have F-W watching covers the entire 2009 shoots to date. I add things to the tree from multiple sources…from CF/SD card (using Downloader Pro); export from LR; WIP or output from PS, web or email reduced size copies from Qimage Pro. It doesn’t matter where they are from…whenever I add something to the tree F-W will automatically import it…and show it in LR in the subfolder structure that I like and have created outside of LR.
Thanks, Jeffrey….another great plugin.
John
This plugin is great. Just a question: since there is no official API in Lightroom SDK for import, how could you do that?
Cheers
Giuseppe
There is: see LrCatalog:addPhoto —Jeffrey
Plug-in is fast, but I can’t figure out how to have LightRoom automatically display the most recent import using Loupe-view. I thought the point was to be able to review your work while you are shooting, but the current implementation requires me to click on the newly imported image to display it, which is not helpful in a fast paced environment which is the norm for tethered or wireless shooting.
I agree with your assessment of the requirements, but it’s just not possible given the current version of Lightroom. The best I can come up with is to view the target folder in grid view, with large thumbnails, sorted by Added Order or Capture Time, in reverse (click the a/z next to the sort to reverse the order). Then, the most recent picture will always be in the upper-left corner. If Lightroom’s plugin infrastructure would give the plugin a way to make a photo selected, I’d do it, but it doesn’t, so this is the best I can come up with. Sorry. —Jeffrey
Hi,
for my workflow it would be best, when a MasterFile, which was recently changed and saved under the same name, would be imported to the catalogue and the last Version removed from the catalogue, because I do not keep all tiff-versions when I work on an image. At the moment I have to save the recent version under a new name (will be imported by FW) and manually remove the old version from the catalogue.
Thank you very much
Dominik from Germany
I don’t quite understand… if you make a change to a tiff master image, I would think that Lightroom would notice the file change and refresh its view of that image. It certainly does this if you’ve invoked the edit of the master image via “Edit in..”. —Jeffrey
Thanks, I normally invoked PS from LR only the first time after raw conversion in LR, so the further changes were not recognized by LR when I changed a MasterFile in PS later…
No problem to start generally from LR, so this issue is fixed for me, thanks again
Dominik
You are totally right, the changes are noticed even when the editing was not invoked via LR…
Very nice PLugin
Dominik
Thanks for all the high quality stuff you have got out.
I wanted to check if there is any way I could “sync” my smart folders in LR with a Folder Tree on my disk.
This is because I shoot a lot of pics of similar type like Wildlife in Karnataka, India, My Daughters, Photo Shoots for clients etc. I need a mechanism to display this in multiple places like Picassa Web Albums and keep those albums updated new content as I add more pics into LR any suggestions and tools will be welcome.
Thanks a bunch.
A Vari
There’s not an easy way, no, because LR doesn’t give its plugins any access to collections. However, it’s easy enough to create an export preset for one of my export-to plugins with settings to indicate “upload only new or changed”. You then could develop a habit of visiting a collection, selecting all its photos, then invoking the export preset. I sort of described something similar here. —Jeffrey
Thanks Jeff for your comments, very kind of you.
I went through the process and it seems like a good process considering what we have now. However I would like to ask you something more…
Would it be a lot of work to create an option in one of your plugins that could do the following?
Save to disk instead of a web service
Create the folder structure from the source in the exported destination for e.g.
Source -> c:/Photos/Japan/Autumn/*.raw
Destination -> c:/Photos/Japan/Autumn/*.jpg
This option is built in to Lightroom… see the “export location” section of any Export Dialog. A related option is Tim Armes’ LR2/TreeExporter plugin —Jeffrey
to take an e.g. from your photo stream
Add a filter to choose images to export from the source folder e.g. Images with 5 Stars / Color Red, Changed Images etc.
You already have the update option.
This will help a lot as LR is a great tool especially
when shooting in RAW
Can provide a nice workflow for most crucial tasks
And is probably as good as it gets with respect to the technology of Post Processing
However, it is not very good at sharing images. I can understand Adobe wanting to control how we use “our” images, use only my slide show etc.. Many have tried and failed before them.
There will be many requirements to share images into multiple end use scenarios – could be Web Services, DVD Slide Shows, Media Center (Apple TV, Windows Media Center), etc. These we understand now, more will come up.
Right now all this is a pain as there is no simple solution. From what I know, you are the closest to one.
A Vari. Bangalore, India
Jeff,
Thanks for the link. It seems to do some of what I need, but I see that LR/Morgify is also updated, so more experimentation
Thanks Again.
A Vari
Great plugin!
I am shooting a lot of school pictures, and this plugin will save me a lot of time
There is one function I would like to have in this plugin, and that is the ability to autotag the pictures when they are imported.
To keep track of the person in a picture I use barcode scanners and a database. If this plugin can connect to a database, capture a name and tag the imported picture that would be a great feature
- Jan-Tore -
That’s a bit too specific to add to the plugin, but I’ll think whether I can make some kind of generic something that runs after the import that might allow it…. —Jeffrey
For us that converts our .CR2 (raw files) to DNG upon importing photos in lightroom.
This plugin will not work for us? Hence it auto adds raw files without any dialog?
Yes, sorry, the Lightroom plugin infrastructure doesn’t offer much for doing import… I can just point LR at a file on disk, and hope. Maybe it’ll be better in LR3… —Jeffrey