 |
San Francisco, California | |||
| USA | ||||
|
|
San Francisco, California | |||
| USA | ||||
ChangeManager Lightroom Plugin
Lock finished photos to keep inadvertent changes from going undetected.
and/or:
Photo settings comparison (may be used independently of lock functionality): Get detailed list of develop setting and metadata differences between two states of a photo, or two different photos.
Comparison of current settings and metadata (catalog) vs. disk (xmp) - helps resolve metadata conflicts...
Featuring:
System Requirements
Quick Links (intra-page)
Background
See the readme file after downloading for installation and other notes.
File Menu - Plugin Extras
After configuration, the file menu is used to access additional features...
Auto-check Change Prompt
(auto-check was enabled and I reset a photo - this came up immediately)
Library Filter
ScreenShot - Library Panel
(The Smart Collection Drop-down includes the same items).
Batch Check Prompt
(I ran a batch check on 4 photos...)
Interactive Check Prompt
(running an interactive check, a changed photo was encountered...)
Photo Comparison
(this shows two different photos, but would look similar if comparing two different states of the same photo)
Change Manager started with locking. Since plugins can not stop users from changing photos, this inevitably led to exhaustive change detection. Once that was done, the photo comparator was a no-brainer.
| Develop Settings | Adjustments made in develop module of Lightroom (or ACR). |
| Raw Metadata | Metadata available to ChangeManager via SDK - mostly raw (unformatted) versions of same metadata available as 'Formatted Metadata', along with internal stuff that typically does not change or would not constitute a significant change. |
| Formatted Metadata | Metadata like what is seen in right-hand metadata panel in Lightroom. Includes exif/iptc metadata and keywords... |
In a nutshell - after installing ChangeManager (instructions in readme file in downloaded zip), go to the Plugin Manager and configure settings. Then select one or more photos you have finished editing and press Alt-F,S,L (Windows), or File Menu -> Plugin Extras -> Change Manager -> Lock (either platform). If you have auto-check turned on, then edits in develop module (or quick develop in lib module) should be caught immediately. If you prefer to check for changes on demand, then leave auto-check off and use File Menu -> Plugin Extras -> Change Manager -> Check (or keyboard shortcut) to check for changes.
Menu Items
| Lock | Lock selected photo(s). Makes XMP read-only, and records locked state and lock date as custom metadata. Options for snapshotting and marking edit history... If file was in the 'Changed Since Locked' collection, it is removed. |
| Batch Check | Scrutinize all selected photos. Present summary screen with options for each kind of status. |
| Check for Changes | Scrutinize each selected photo, and present details, with options for each photo. |
| Unlock | Makes XMP read-write, and records unlocked state and date. If file was in the 'Changed Since Locked' collection, it is removed. |
| Select To Compare | Part 1 of 2 of photo comparison feature. Establishes the base of comparison. |
| Compare To Selected | Part 2 of 2 of photo comparison feature. Makes the comparison. Note: you must select a different photo or a different edit-history step of the same photo, for the comparison to be sensible. |
| Compare Catalog to Disk | More specifically, compare current develop and metadata settings (which are stored in the catalog) to those on disk, which are stored in xmp block of sidecar or embedded in source photo file. This is the function to use when you have a metadata conflict to resolve... |
| Create Unlocked Virtual Copy | Convenience function to avoid the change prompt that results when using Lightroom proper to create a virtual copy of a locked photo. |
See Elare Plugin Framework page for settings and info common to all elare framework-based plugins
Additional Settings:
| Ignore unidentified changes | Change Manager can detect all develop setting changes, and all Lightroom metadata changes, but it cant identify changes due to custom metadata from another plugin, or photo-publish state... With 'Ignore Unidentified Changes' checked, you wont be bothered by every little unidentified change. But you can also choose to be notified when anything changes, whether its identifiable or not (by unchecking the box). It may be worthwhile to spend a short time with it 'unchecked' just to see what happens, but I'm guessing most people will want to keep it checked before too long. One option that may make sense is to leave it checked when auto-check is enabled, but uncheck it before doing a batch check or interactive check. I leave it checked all the time. |
| Auto-check control | Auto-check is a lightweight ever-present background process, which if enabled will automatically be checking the most-selected photo for changes. I keep this enabled under normal circumstances because I want to know if a locked photo I'm looking at changes, but you may have a preference for doing without the auto-check just to keep from being bothered by each little change, and just go over them once in a while in bulk, e.g. before re-exporting or final delivery... The auto-check only checks most-selected photo anyway, and the biggest risk may be the accidental batch changes (e.g. auto-sync, menus, quick-develop in grid mode, plugins, ...). This is considered a minimum requirement for auto-checking, but let me know if you would like to not check most selected photo, but still check other selected photos and/or whole catalog - it'd be easy to have it that way if anybody wants it... |
| Auto-check selected photos | @v3.1, auto-check options have been extended to include the ability to check all selected photos, in addition to most selected photo. Note: this is done in a leisurely fashion, so if you fire off a set of changes then change the selection, the changes won't be caught, unless you enable auto-check whole catalog. I keep this selected, but you may not want to... |
| Auto-check whole catalog | @v3.1, auto-check options have been extended to include checking the whole catalog for locked photos that have changed since they were locked. Note: this is done in a leisurely fashion, so it could take several hours to check an entire catalog. I keep this selected, but you may not want to... |
| Auto-check status | Status of auto-check process. This should say "running" after initialization, if auto-check control is enabled. If it doesn't, check the log file for clues (you may need to enable verbose logging). If problem not resolved, please report. |
| Wrap Width | Width in real character where to wrap to next line in the edit history. If you're getting the '...' at the end of your lines, then you need to make this number smaller. If you're getting wrappage when there is still room at the end of the line, then make this number bigger. |
| Quick Tips | Some basic info that may be helpful... |
These FAQs come partly from users, and partly from my imagination. Please let me know if there are errors or omissions in this FAQ - thanks.
NOTE: The following Q&A's assume that the plugin is working as I expect... If, after your best effort, still "no go", please let me know.
Question: Why would I ever need or want such a thing as ChangeManager?
Answer: Maybe more than one reason:
Question: I left auto-sync on and accidentally changed some locked photos that shouldn't have been changed, how to amend?
Answers: Thats what ChangeManager is for (among other things)...
Question: Whats all this snap & mark stuff? (it wasn't there before...)
Answer: For V3.0, I integrated snapshot and mark capabilities of the Snap & Mark plugin. Most of my snapshotting happens when locking. Now I mostly use Snap & Mark for making notes in the edit history.
Question: How to revert a virtual copy?
Answer: ChangeManager does not attempt reversion by way of saving independent settings and re-applying them, instead it relies on Lightroom to do that by re-reading xmp. The good news: reversion is "guaranteed" to work properly. The bad news: virtual copies are not supported. You'll have to revert those the old-fashioned way: using the edit-history, undo, or using change manager to compare present settings to locked settings and just manually re-set changed settings.
Question: Why can't I set a range for lock-date setting in smart collections?
Answer: Lightroom does not yet support date types in custom metadata. Unfortunately for the time being, they're being treated as strings - sorry (fingers crossed). For this reason, I tend to use Library Filters more often than Collections for viewing cross sections of photos based on lock-dates.
Question: Lock function (or acceptance), or reversion not working.
Answer: Locking/acceptance and reversion emit keystrokes to get part of their job done, which will be blocked by an open dialog box, or if the cursor is in a text field in Lightroom, or in the case of Windows 7: an item in the task bar needs attention.
Notorious dialog boxes for getting in the way are:
Notorious text fields for getting in the way are:
Notorious items in the task bar that need attention:
Question: Change Manager sometimes takes a moment to figure out what's changed...
Answer: It takes a longer time to determine change details when there are a ton of brush strokes applied. If this becomes a problem for you, you can always exclude brush strokes from the change computation (or anything else for that matter), by editing the "Advanced Settings".
Question: Whats the 'Develop Module' checkbox for?
Answer: Some functions require Lightroom be switched to the library module. The develop module checkbox makes sure develop mode is resumed afterward. The plugin does not know which module its in, but it does know how to switch modules (emits Ctrl/Alt-{module number} or Cmd/Option-{module number} keystrokes, which will work as long as there are no dialog boxes open (or text fields being edited) in Lightroom. Check this box if you want to be in the develop module when its done, or leave unchecked to be in Library module.
Question: What about this 'Collect' function?
Answer: The idea is that the photo remains locked, but it won't illicit a change warning from auto-check. This gets it out of your hair for the moment. Note: if you re-lock, or unlock the photo, it is removed from the change collection. I use the 'Collect' function most when I'm doing multi-photo checks and I really don't know why a bunch of photos are changed. Then I go to the change collection and scrutinize. Upon completion of resolution, they are removed from the change collection, either explicitly or by re-lock/unlock.
Question: Auto-check, auto-check, auto-check...
Answer: Personally, I keep them all checked, since I want to know about any and all significant changes that have occurred post-lock. But, its kindofa bother if you like to experiment a lot or play or tweak. Another option is to allow oneself to do whatever unimpeded, even after lockage, then review the changes manually before exporting or shipping... PS - auto-checking the whole catalog, or all selected photos although done leisurely, will take a bit of CPU (less after first pass is complete), and have the potential to interfere with other manufacturer's plugins ability to access the catalog. If problems, turn off...
Also, you will probably want to turn the auto-checking off if you ventured to consolidate keywords without unlocking first, etc...
Historical anecdote:
-----------------------
Auto-check of all selected photos is a feature that previously existed in more than one plugin, but was "recalled" due to what was deemed to be excessive CPU usage, and other issues. The good news: the new way uses far less CPU, and all previous issues have been resolved. The bad news: it takes a lot longer to get around to checking selected photos and/or whole catalog, and changes to selected photos are more likely to be missed by the auto-check (of selected) feature, if they do not remain selected long enough.
Question: Auto-check does not seem to be working - why not?
Answer: See the log file, and/or turn on verbose logging. - it should provide a clue.
Explanation: Deleting photos while auto-check is on causes hard to handle errors. These are consequently ignored so as not to bother you. Unfortunately, real errors can happen without getting in your face as well. Thats what the log file is for. If verbose logging is enabled, all errors will be in your face promptly.
Question: Why is auto-check of selected photos and whole catalog disabled by default?
Answer: For backward compatibility - so upgrading users don't see a change in behavior without taking explicit action. Otherwise, the default would be 'enabled'.
Question: Beta profile "changes".
Answer: If you were using a Lightroom beta profile when you locked a photo, your photo will appear changed when the final profile is released. In general, it is safe to just accept & re-lock these photos, since the released profile is either the same, or includes some improvement. Still, it may be wise to re-visit and maybe re-export these photos, in case the profiles were improved.
Question: What logger where why?
Answer: Log file is in "Your Documents" folder, filename is: com.robcole.lightroom.ChangeManager.log or something like that. You can view it using the plugin manager.
Question: Should I run a 'batch check', or 'check for changes'?
Answer: I often run a batch check just to get a summary first. Then run the interactive check if something turns up in the batch check that I did not expect.
Question: Whats the difference between 'No changes at all', and 'No significant changes'?
Answer: The former means no changes of any kind whatsoever have occurred (since lockage) - 'nuff said... The latter means something has changed, but nothing significant. Insignificant changes are custom metadata from another plugin, or changes specifically excluded by advanced plugin configuration...
Question: What if I have problems?
Answer: Try turning on log-verbose - not only is more stuff logged but it enables some debug code as well that may help. If you can't figure out what's wrong, then report a problem and send me the verbose log file.
Question: ChangeManager is too cool for words, how can I express my gratitude non-verbally?
Answer: Send Money $$$ - thanks.
Question: ChangeManager is too cool for words, but not cool enough for money - now what?
Answer: Just tell me what you think - thanks.
Question: What are some of ChangeManager's limitations and known problems and what are your plans for the future of ChangeManager?
Answer:
- Photo comparator enhanced to work properly in Lr4b.
Note: I have not yet tried the lock / unlock stuff in Lr4b.
###1 May not work on Lion, yet (or it may...).
- Changed Snapshot & Mark Options UI to use radio buttons instead of checkboxes - saves a click sometimes.
- Fixed bug in photo comparator - was having an error when setting present in one photo was not present in the other.
-
Logs photo comparison and "catalog vs. disk" comparison results.
- Some minor aesthetic enhancements.
- Added 'Compare Catalog To Disk' function which compares current settings in catalog, to those in file containing xmp, on disk.
- Also added support for reversion on Mac.
- Changed formatting of display so all data is included, instead of squeezing each item onto a single line. Helps for comparing keyword and caption differences...
- Added option to omit raw metadata from change considerations (formatted metadata has everything most users care about, so checking the raw form of metadata is generally not necessary). Note: this option is available by clicking 'Edit Advanced Settings' and setting rawMetaExcl to '*'. This makes change manager a little more efficient overall, but will not necessarily be noticeable for a while, since it does a little extra initially to automatically overwrite stored raw settings.
- Fixed a locking/reversion bug induced in v3.5.0.
Version 3.5.1, released 2011-09-08
- Fixed bug in preset manager - it was requiring two tries to switch presets after switching to another plugin and back in plugin manager.
- Change detection date/time handling is now exact. There was previously a fudge factor in there to account for small variations in last-edit-time when changes were made. Not sure if there is any practical implication, but it was bugging me...
- Also, the background process was not pausing like it was supposed to when
doing manually initiated operations, which had the theoretical potential for conflict between background processing and foreground processing, although in practice it rarely if ever manifested.
- Added checkbox to plugin manager, to ignore photos buried in stacks when doing idle-time checks.
- Added button to plugin manager, for updating the plugin, and uninstall.
- Added prompt before switching photos when change detected in non-viewing photo in background.
- Also fixed a bug: detail mark was wrongly indicating changes in point curve when strong or linear selected (it was only correct for medium contrast point curve).
If you try it - please let me know what you think of it.
- Added auto-check options for selected photos, and whole catalog.
- Misc minor enhancements.
- Minor aesthetic changes...
- Added functionality developed for snap & mark plugin, to provide more extensive snapshot & mark options when locking.
- Trimmed out a few excessive dialog boxes.
- Switched to .txt extension
for plugin manager preset backing files.
- Fixed a bug that surfaced when batch reversion attempted for a group of photos that included virtual
copies.
- Added option to create virtual copy when user attempts to changed locked photo (Windows only).
- Added option to file menu to create an unlocked virtual copy
(Windows + Mac).
- I also changed some system code in the elare framework
upon which ChangeManager is built. Mostly effects how errors are propagated. Please let me know if you encounter any anomalous behavior...
-
Fixed a bug in preset manager.
- Also changed some prompts and other minor mostly aesthetic stuff...
- Added configuration option to have 'Lock & Snapshot' be the default "lock" button. Click 'Advanced Settings' in the plugin manager to set this option.
- Made change to keep erroneous 'dateCreated' changes from being detected, which were due to a small change in plugin metadata handling in Lr3.4RC.
- Bug fixed that had the potential to cause an error when doing lock or accept.
- Auto-check now switches to dictated module even if not necessary, so behavior is always same and is predictable.
- Made custom snapshot prefix text persistent.
- Batch Check function: removed custom snapshot text box when no snapshot options are presented.
- Suppressed display of second photo in comparison, when comparing two states of same photo.
- No longer switches modules when menu function canceled.
- Added field for custom snapshot name prefix.
- Added photo comparison to quick-tips (help menu).
- Should be the same as v1.4. I just bumped the version number because I've found the comparison function to be such an incredibly worthwhile new feature.
- Added capability to compare the settings and metadata of two photos or two states of the same photo.
- Changed bookeeping to store "blank" develop settings as 'false' - eliminates erroneous change detection ("blank" -> 'false') for certain settings that start out "blank" when off, but go to 'true' when turned on, then go to 'false' when turned off again.
- Switches to Library module when Develop Module unchecked - used2be sortof indeterminate.
- Was not assuring libary/grid mode when invoking multi-photo reversion from develop module.
- Aesthetic change affecting Mac only: double-ampersands in UI text converted to single ampersand.
- Moved menu items from library menu to file menu (so all functions can be invoked from the develop module), and added keystroke emission to ensure the libary module is selected for operations that need it (e.g. multi-photo locking, and reversion). Also added the develop module checkbox so functions requiring library module invoked from the develop module will return to the develop module upon completion.
- Has been briefly tested on Mac - Status: so-far-so-good - call it a "beta" now - please try on a test catalog and provide feedback.
- Extensive modifications to improve performance and reliability.
- Streamlined lock function and added batch check.
- Cleaned up the UI...
- Note: v1.1.6 was tested on Mac, but 1.2 not yet.
- Various ALPHA releases.
acceptance of Download Terms & Conditions will be required
Change Manager 4.3 - Latest & greatest - this is the one to download.
Change Manager 4.2 - for fallback, in case of problem with latest, in which case please tell me.
| Static content updated 2011-01-14 | Copyright 2007 - robcole.com - all rights reserved. | Dynamic content updated 04:09:02 PM |