 |
San Francisco, California | |||
| USA | ||||
|
|
San Francisco, California | |||
| USA | ||||
NxToo Lightroom Plugin
A suite of tools to aid in using NX2 in conjunction with Lightroom.
Featuring:
Quick Links (intra-page)
Background Information
See the readme file after downloading for usage and other notes.
There is not a lot to see. Most of the work is done without UI when the following menu items are selected from the
File Menu -> Plugin Extras:
(missing 'Assign Base Photo')
File Watching is auto-enabled whenever a file is opened or edited via NxToo:
User can stop the watcher at any time, for any reason...
File Watching can also be re-enabled at any time, to resume watching for files saved in NX2 that are related to selected photo(s) in Lightroom.
After NIK3_31335_bw.nef has been saved twice.
Plugin Manager Configuration
explained below...
Library Panel Metadata
Shows source of metadata synchronization if enabled.
Can be changed here or via File Menu -> Plugin Extras.
Perhaps it suffices to say that NxTooey had some design flaws that have been remedied in NxToo. NxToo aims at accomplishing the same goals as NxTooey, but in my opinion, better hits the mark. In a nutshell, NxToo's menu functions simply open files in NX2 and start a background task that watches for saved files. Besides assuring the watcher is running, the menu functions only added value over opening files directly in NX2 is they check some stuff, and have smarts to open the file you meant, instead of the one you had most selected (e.g. opens raw file corresponding to jpeg preview, or opens cooked nef corresponding to cooked jpg...). Gone are the single-ver/multi-ver modes of raw editing that were so confusing in NxTooey.
I used to use NX2 instead of Lr2 sometimes for raw conversion to gain lens corrections and better noise reduction. Those days are mostly over. Although Lightroom's lens corrections are (arguably) not quite as good as NX2's lens corrections (for instance, Lightroom does not handle axial/longitudinal CA correction. On the other hand, Adobe supports 3rd party lens correction - which is a real biggie if you use 3rd party lenses, and a don't care if you don't... Also, NX2 does not handle perspective correction, although thats almost not a lens correction, and unlike the other (auto/intelligent/lens-profile-based) lens corrections can be done after the fact (meaning: to cooked files) in Lightroom, or PTLens, or DxO I think), usually Lightroom's are good enough... Lightoom 3's raw conversion and noise reduction have improved to the point that I mostly use NX2 as a cooked editor. I sorely miss the Active D-Lighting that is in NX2 for one-click contrast reduction / shadow-highlight recovery without losing mid-tone clarity, but Lightroom's Fill Light and Clarity serve the same end, and are more flexible, albeit more work required sometimes. I confess I still struggle with the highlight recovery in Lightroom, often resorting to local correction to avoid the flat look that comes from using highlight recovery. Lightroom's highlights tend to be rendered a little timidly by design (presumably), which often I like (lighter tones are less saturated than darker tones), but bringing detail out of the highlights without losing pizazz in the (lights and) mid-tones can be a challenge. An advantage of editing raw in NX2 (over cooked) is you can maintain NX2 edits non-destructively without large intermediate files. Still, nowadays, I mostly use NX2 for cooked editing for the reasons mentioned, then delete the intermediates after a while if it seems I won't be editing any more in NX2. Note: If you're editing cooked, and if you choose 'ProPhotoRGB' for colorspace, then I recommend that you add a color profile conversion to AdobeRGB as the last step before saving a cooked JPEG, otherwise you'll end up with an 8-bit ProPhoto jpeg in Lightroom, which is not optimal.
Lightroom starts with a base image. When edits are made, the settings are stored in the catalog (database). (and in an xmp file when upon 'Save Metadata'). So the only way to see the effects of Lightroom edits outside Lightroom (so far) is to export a tif or jpeg (there are other file formats, but for the purpose of this document these are enough to consider) ***. Exporting a tif or jpeg from Lightroom is the equivalent of doing a 'Save As' to "export" a tif or jpeg from NX2.
*** Photoshop can open the same raw files as Lightroom and interpret develop settings applied in Lightroom, however since the only way you can see subsequent Photoshop changes in Lightroom (unless the only thing you change is camera-raw settings, in which case there is no sense going to Photoshop in the first place) is through a tif (or psd, or jpg...).
NX2 starts with a base image. When edits are first made, they are not stored anywhere (they are just resident in ram). The only way to store the edit settings for later retrieval is by saving in a NEF file. Although the NEF file can have a raw image (original sensor data) or a cooked (RGB) image as the base, there are some important differences between these two scenarios. If the NEF is the original raw file, then the jpeg preview will have all NX2 edits applied - i.e. it is updated every time you save the NEF file after editing - it represents the edited image. If the NEF is cooked, the jpeg preview will never change - it represents the base image not the edited image. Note: you do not lose quality by saving as jpeg, then tif or nef - since what's being saved is always a rendered version of the base image + adjustments. You will lose quality however if you subsequently close and re-open/edit the jpeg instead of a tif or nef...
Lightroom can not read NX2 editing instructions from a Nef file, and NX2 can not read Lightroom editing instructions from the Lightroom catalog (or the xmp file). Presently, the only way to work on a photo in both softwares is to export (or extract) a tif or jpeg from one to be worked on in the other.
| raw | Indicated by upper case 'NEF' or 'NRW' extension. Original camera raw file, which may be edited parametrically in Lightroom (edit adjustments stored in catalog), but may also be edited parametrically in NX2 - edits stored in raw file, along with a top quality jpeg which represents the state after the edits are applied. Nikon raws can be edited as raw or cooked in NX2. Foreign raws must be cooked before editing in NX2. |
| extracted jpeg | preview or sidecar extracted from Nikon raw file. Similar but not identical to in-camera jpeg, except it gets updated whenever you re-save the NX2. Unlike extractions via preview-extractor or dcraw or exiftool, NxToo extracted jpegs have a proper ICC profile assigned, and metadata is transferred from raw file, as well as Lightroom if desired. Extension is always lower case 'jpg'. |
| preview | extracted jpeg that includes a "preview suffix" signature. Unlike sidecars, the preview is updated in Lightroom, whenever the raw is saved in NX2. Extension is always lower case 'jpg'. |
| sidecar | extracted jpeg with same base name as raw. The intention is to use this instead of shooting raw+jpeg. I never use this anymore, but some people may want to extract sidecars after importing raws in order to have a reference in Lightroom of the original in-camera rendering. |
| cooked | For the purposes of NxToo, noun form: an rgb file whose origin is an exported tif with Lightroom changes folded in; verb form: exporting tif with Lightroom changes folded in... |
| cooked-nef | Indicated by lower case 'nef' extension. Base image comes from a tif exported from Lightroom. Its purpose is to store the edit settings for re-editing a cooked file in Nx2. Note: unlike a raw nef, the jpeg preview represents the state before Nx2 edits, not after. Note: this should never be edited in Lightroom proper. I could almost justify not adding it to the catalog at all but then you wouldn't know its there without opening explorer/finder... |
| cooked-tif | Inidcated by lower case 'tif' extension. The very first one of these is exported by Lightroom for Nx2, with Lightroom edit adjustments applied, for Nx2's sake. After that it can be overwritten by Nx2 with Nx2 adjustments applied, for Lightroom's sake. It can be re-edited in Nx2 (either indirectly by way of the associated cooked-nef, or directly if the cooked-nef was not saved). It can also have enhancements applied non-destructively in Lightroom, after being saved in Nx2. |
| cooked-jpg | Must have lower case 'jpg' extension. Like a cooked-tif (after it has been saved already in Nx2). It can be re-edited in Nx2 (either indirectly by way of the associated cooked-nef, or directly if the cooked-nef was not saved). It can also have enhancements applied non-destructively in Lightroom, after being saved in Nx2. |
| saved-rgb | Either tif or jpg saved in NX2. |
| NX2 Version | The equivalent of Lightroom virtual copies in NX2. See the drop-down in NX2 proper (at the top of the NX2 edit-list). |
| Base Photo | Used when 'Transfer Lightroom Metadata' option has been checked. The base photo is the source for the Lightroom metadata being transferred to the target photo. It also determines the stack in which to place newly discovered photos. |
| Save Metadata | The act of saving develop settings and other metadata in the catalog to an xmp sidecar file (in case of raw), or to an xmp block within non-raw (rgb) files. This can be done automatically by Lightroom (not recommeded when using NxToo), manually initiated by user (e.g. Ctrl/Cmd-s), or initiated automatically by NxToo - depending on options set in plugin manager.
|
| Metadata Conflict | Indicated by an exclamation flag in Lightroom, it means file appears to have changed externally and unsaved metadata changes are in the Lightroom catalog. This is a normal occurrence when using NxToo, and conflict flag may be extinguished just by saving metadata in Lightroom - I use the 'Save Metadata' option in NxToo to extinguish these flags, but you can also do it manually (see above). |
| Metadata "down arrow" | Means metadata has changed in Lightroom since last saved on disk (xmp). Correct course of action in the workflow addressed by this document is same as for metadata conflict (see above). |
| Metadata "up arrow" | Means file on disk has changed since metadata was last saved in Lightroom (but there was no unsaved metadata in Lightroom catalog when the file change was detected). For the purposes of this document and NxToo, it's equivalent to a metadata conflict, and the correct course of action is the same (see above). |
| Capture NX2 executable | Absolute path to NX2 in Windows, or app-name in Mac. |
| ExifTool | Path to user-version of exiftool, or leave blank for default. |
| Preview Stack Position | Jpeg preview, when extracted, can be added to catalog, stacked relative to its raw. Note: you also have the option to never extract jpeg previews. This option would be appropriate if you always save a tif or jpg in NX2 for Lightroom's sake, making the preview redundent. Note: this setting only applies when adding preview image to catalog - it does not apply once preview is already in the catalog. |
| Ask each time | This is the inverse of "Don't keep asking". These prompts don't use standard "warning boxes", and so aren't affected by 'Reset Warning Dialogs'. |
| Saved RGB stack position | RGB files, when saved in NX2, will be added to catalog, stacked relative to their associated raw. Note: this setting only applies when adding rgb image to catalog. |
| Cooked tif stack position | Cooked tif files, when doing 'Edit Cooked In NX2', will be added to catalog, stacked relative to their associated base photo, which may be raw, rgb, or virtual copy... |
| Preview filename suffix | Extracted jpeg preview files will be named {base}{preview-suffix}.jpg, for example: |
| Cooked filename suffix | Cooked tifs will be named {base}{cooked-suffix}.tif, for example: |
| Cooked tif color space | Used for conversion of most selected photo to tif for cooked editing. I recommend AdobeRGB if the photo is already in the ball-park, else ProPhotoRGB (in which case, be sure to add a colorspace conversion as last step before saving cooked jpg). Always 16 bits. |
| Transfer Lr Metadata (to preview jpegs) |
Transfers keywords, ratings, title, caption, ... to jpeg preview if so desired. Which things are transferred is configurable via advanced settings. "Initially" means upon first extraction. "Repeatedly" means upon subsequent extractions. |
| Transfer Lr Metadata (to rgb files) |
Transfers keywords, ratings, title, caption, ... to other related rgb files after they get saved in NX2, if so desired. Which things are transferred is configurable via advanced settings. "Initially" means upon first extraction. "Repeatedly" means upon subsequent extractions. |
| Save Metadata | Auto-eliminate metadata conflict flag and metadata change (arrow) flags by saving metadata after file is changed. I keep this checked for convenience, and ignore the subsequent warnings in NX2 when resaving files (file has been changed since opened in NX2). Another option is to leave this unchecked and ignore metadata warnings in Lightroom, and then manually save metadata in Lightroom to clear warnings when you're ready to - its your call...
|
| RGB filename suffix | RGB files will be named {base}{sfx}.jpg, for example: |
| File Watcher | or just "the watcher", This is a nick-name for the background task that is looking for files saved in NX2 related to selected photo(s). You can tell if its active by the progress indicator in upper left corner of Lightroom. You can stop it anytime you want by clicking the 'X', and restart it using File Menu -> Plugin Extras -> NxToo -> Watch for Saved Files. If it doesn't seem to be working, check the status using plugin manager, and consult the log file. |
| Auto-scan control | Leave this enabled, otherwise NxToo won't work. If troubleshooting, this or plugin itself can be disabled. If only this is enabled, then only photos related to most selected photo will be seen by the "watcher". Keep this selected, but the following two de-selected if you want to minimize CPU+DiskAccess and are willing to have all changes ignored except when related to most selected photo. Still requires a little extra CPU+DiskAccess, which is why I kill the NxToo watcher when I'm not actively using it (i.e. when not expecting to save files in NxToo again soon). |
| Auto-scan selected photos | I keep this (and/or the new one just below) enabled too, so files related to any of the selected photos will be seen by the watcher. This is good if you want NX2 to detect changes to any photos selected, but ignore changes to files related to unselected photos. NxToo uses a little more CPU+DiskAccess when selected. |
| Auto-scan all active sources | New @2011-10-08 - Watches for changes to files related to any photos in the filmstrip whether selected or not. Unfortunately, due to a limitation in Lightroom (SDK), NxToo does not know exactly which files are in the filmstrip, but it gets pretty close with the help of the next two items. This is good if you like to select different things in Lightroom while working on other things (in same folders and/or collections) in NX2. NxToo uses a little more CPU+DiskAccess when selected. |
| Include subfolders in folder sources | This should normally be the same as the "Include subfolders" setting in Lightroom (Library Menu -> Show Folders in Subfolders). |
| Include photos even if buried in stack | I keep this enabled, since photos buried in collapsed stacks are essentially "out of commission" for the time being. But you can disable this if you like to collapse stacks but still have NxToo attend to changes related to those underneath. |
| Auto-scan status | Displays real-time health status of background (watcher) task. Note: if watching is not "enabled', the background task isn't doing anything, even if it says "running". |
NxToo supports two metadata items. Together, these define the base photo used as metadata source when 'Transfer Lightroom Metadata' is checked.
Note: You can edit these yourself to change base photo, just be careful - case and punctuation must match base photo as recorded in catalog, exactly. Another way to set it that's less error prone is to use 'Assign Base Photo' (hint: File Menu -> Plugin Extras -> NxToo).
What its for
Editing raw NEF or raw NRW files in NX2.
What you have to do
What NxToo does
What its for
Exporting files edited in Lightroom (i.e. "cooking") for further editing in NX2. Any Lightroom photo, from any vendor, can be edited in this fashion, however it's intention is primarily for use with original camera files after initial Lightroom edits. Can be used to edit virtual copies in NX2 also.
What you have to do
What NxToo does
Notes
I recommend if you choose 'ProPhotoRGB' for "Cooked tif colorspace", that you add a color profile conversion to AdobeRGB as the last step before saving a cooked JPEG, otherwise you'll end up with an 8-bit ProPhoto jpeg in Lightroom, which is not optimal.
What its for
Re-editing already cooked files in NX2.
What you have to do
What NxToo does
What its for
Opening one or more selected photo(s) in NX2, and enabling NxToo to detect saved files.
What you must do
What NxToo does
What its for
Setting or changing the source for metadata synchronization that applies when 'Transfer Lightroom Metadata' is checked.
What you must do
What NxToo does
Notes
This info is used to determine where to get Lightroom metadata when file is updated, if "Transfer Lightroom Metadata" is checked.
Normally you don't need to mess with this, since the base photo is automatically set correctly for previews, cooked derivatives, and virtual copy sources. But its here should you need it...
What its for
Enabling file watching, or re-enabling after previously being stopped.
What you must do
What NxToo does
Notes
What constitutes a related file?
If base of new or changed filename is contained in the target photo, or vice versa, then its related. Base means without the filename extension in this context.
Examples of related filenames:
ND300_31245.NEF & ND300_31245_NV1.TIF
ND300_31245_Coneecheewa.NEF & ND300_31245.TIF
Examples of unrelated filenames:
ND300_1001.NEF & ND300_1002.TIF
ND300_31245_Coneecheewa.NEF & ND300_31245_Sasketchup.TIF
The good news: you can name things however you want and they'll generally be picked up.
The (potentially) bad news: if you have a whole bunch of things selected, and you have "auto-scan selected photos" checked in plugin manager, and you then save a new file in NX2 with some name that could be related to more than one selected photo, you may have to suffer through a prompt whenever the base photo is ambiguous or uncertain.
What its for
Extracting jpeg preview from Nikon raw file for display in Lightroom.
What you have to do
What NxToo does
Notes
This is normally not necessary, since previews are automatically extracted when the raw is saved, if that option is enabled, but if not... Preview jpeg files have a tell-tale suffix appended to the base name to distinguish them from other non-preview jpegs.
What its for
Extracting jpegs from raws with same base name as the raws, so they are seen as sidecars to the raws.
What you have to do
What NxToo does
Notes
This can be used in lieu of shooting raw+jpeg, and makes my other plugin: rc-extract-jpegs-from-nefs based on previewextractor.exe - obsolete. Use it immediately after importing your raws, or whenever.
I'm really not sure all the reasons users may want a jpeg extracted as sidecar instead of preview, but I have a hunch this may be welcome by some. I never use it m'self...
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 NxToo?
Answer: If Lightroom has all the editing power you need, or you can't see any reason to use Nx2 sometimes instead of Photoshop, then this plugin is not for you. If however, you sometimes want to take advantage of the strengths of Nx2 in a Lightroom-centric workflow, with as few headaches as possible, then this plugin will help.
Question: Is NxToo just for Nikon shooters?
Answer: Absolutely not! Even if I shot only Canon raw, or jpeg - I would seriously consider purchasing NX2 for cooked editing - its very powerful and easy to use, and much cheaper than Photoshop. Just having a simple distraction removal brush is a godsend, and the u-points... - don't get me started. And as an external editor to Lightroom via NxToo, it rocks.
Question: Whats the slowest way to invoke the functions of NxToo?
Answer: Lightroom's File Menu -> Plugin Extras -> RC NX Too ...
Question: Whats the quickest way to invoke the functions of NxToo?
Answer: On Windows:
On Mac, use the OS/Automater to configure keystrokes, or something like QuickKeys.
Question: How can NxToo Help?
Answer: By allowing you to open raw or cooked nefs in Nx2 from Lightroom (or rgb files), and by extracting jpeg previews from raw nefs for viewing and/or editing in Lightroom. Note: it makes no sense to extract a jpeg preview from a cooked nef for Lightroom, since its origin is always Lightroom in the first place (given the scenarios addressed in this document), and anyway its appearance in Lightroom will always be the same as the cooked nef itself, since it never changes (at least not yet anyway).
Question: How do I "extinguish" Lightroom's save metadata warning permanently?
Answer: When you have photos selected, and invoke Lightroom's 'Save Metadata' feature, you may get a warning dialog box. Make sure you check the "Do not show again" checkbox before approving metadata to be written from catalog to disk.
Question: I saved a cooked file in NX2, but Lightroom didn't see it.
Answer: You probably saved it to the wrong directory. I've done this a thousand times - NX2 does not default to the directory of the presently open file when saving a different type of the same file - you have to check the directory carefully every time you save a file in NX2. If this was the case, don't forget to go delete the erroneously saved file.
Question: If I save a jpeg, then a nef, will I lose quality?
Answer: No. NX2 "Save As" is more like an export. Although after saving a jpeg, it appears that the file being edited is now a jpeg - its very misleading. NX2 really maintains full quality of whatever you started with plus the edit instructions, and that's what it will use next time you save a file.
Question: How to handle NX2 Versions...?
Answer: You can save different versions with different appendages to the base name, for example, if your raw is: ND300_32456.NEF, you could save a black and white version as: ND300_32456_BW.tif (lower case extension please).
Question: How does NxToo handle metadata transfers?
Answer: There are two sets of metadata that may be transfered:
Question: Cooked nefs don't use the same RGB stack position settings as the others, why not?
Answer: cooked nefs should "never" be edited in Lightroom, but should "always" be edited in NX2 when available. 'Edit Cooked in NX2' contains intelligence for automatically opening cooked nefs when available even if buried in stack. So, it works out nicely to stack them below the others.
Question: What does it mean for the base photo to be "uncertain"?
Answer: Sometimes the base photo is determinisitic (e.g. base photo for preview is always the raw it was extracted from. Likewise, base for cooked photos is always predictable). But, sometimes when RGB files have been saved, the proper base may be ambiguous - e.g. there is more than one file or virtual copy that could be considered a base. In this case the base photo is considered "uncertain", and you will have the opportunity to be prompted in this case, even if not prompted when base photo has been clearly determined.
Question: Is NxToo compatible with Lightroom's "Auto-save xmp" option in catalog settings -> metadata tab?
Answer: It is strongly recommended to turn this option off, and use NxToo's 'Save Metadata' to save metadata for derivatives after transference - this will eliminate the metadata save flags and the metadata conflict flags. This is how I wrote it, this is how I tested it, this is how I use it, and this is the configuration I recommend. On the other hand, I also did brief testing with Lr auto-save xmp option enabled and NxToo's save-metadata option disabled, and had no problems other than metadata conflicts (v4.2.1+) which can be extinquished by pressing Ctrl/Cmd-s.
Question: Why does NX2 complain that an rgb file has been modified since it was opened?
Answer: If metadata is saved in Lightroom, for an rgb file open in NX2, it will appear to have been modified externally to NX2. This warning can be safely ignored, assuming you are just using Lightroom and NX2 and there isn't some other means of altering the file... This is analogous to Lightroom's metadata conflict flag when an rgb file is saved in NX2 that is in the Lightroom catalog.
Question: Can I enter metadata in NX2 and have it saved in Lightroom?
Answer: NxToo makes the assumption that Lightroom is being used for metadata, and NX2 is being used just for editing. Entering metadata in NX2 to be transfered to Lightroom is not supported.
Question: How do you accomplish extracted jpeg image resizing?
Answer: ImageMagick (command-line "swiss-army-knife" image processor) is used.
You must download ImageMagick and browse to mogrify executable. Any executable that will run on your OS will be compatible with NxToo - I'm talking about 32 vs. 64-bit executables for vs. 16-bit images - all will work equally well. The newest version that works is generally the most desirable.
On Mac, I used the command "sudo port install ImageMagick" to install image-magick, which adds the mogrify excutable to /opt/bin/local which is the default path if you do not set one of your own using "advanced settings".
Question: NxToo is acting wonky - is it just me?, or is NxToo funky too...?
Answer: There is always the possibility for bugs, but it is essential to wait for NxToo to complete transfer and save of metadata before changing selected photo(s). You can tell when its complete by looking at the progress indicator in the upper left corner of Lightroom.
Question: Extracted jpeg previews and/or sidecars are sometimes small, dark, and/or dull...?!
Answer: ExifTool has trouble properly extracting the correct jpeg sometimes - dunno why. Solution is to define a named preset (using the preset manager section in the plugin manager), then click 'Edit Advanced Settings'. Set dcraw as your extractor - instructions are inside the advanced settings file itself. Actually, this problem was fixed, so if you are running the most recent version of NxToo, either exif-tool or dcraw should now get the correct jpeg, although dcraw is slightly faster and so is recommended.
Question: How to configure alternative keystroke sequence for 'Save Metadata' feature?
Answer: Click the 'Edit Advanced Settings' button in plugin manager (after entering a preset name).
Question: What are the limitations of NxToo and what are your plans for the future?
Answer:
(reverse chronological order)
- Changed computation of default path for NX2, since new installations go to 64-bit directory now, on Windows.
- Certified for Lr4.
Note: Like all releases, it includes updated framework software, which may induce new bugs, or fix old ones...
- Change made for one specific user only: to add sRGB colorspace option for cooked tiff. I have assumed nobody else would want that option - please correct me if I'm wrong.
- Added some timing tweaks to "advanced settings" to try and help a person having difficulties with preview extraction when saving raw NEF. I don't know if these settings helped, since that person hasn't got back to me since, but I thought I'd share in case anybody else is having problems but has neglected to mention... - I don't have the problem, I just don't know if anybody else is or not...
- Also fixed problem that checking for updates upon startup was being called twice.
- Fixed bug - was adding keywords from base to derivative, but not removing them.
- Improved performance of "all active sources" auto-scan option.
- Added option to the file watcher (in plugin manager) to look for changes to files related to any photos in the active sources (~filmstrip) whether photos are selected or not.
- Added an option to use dcraw instead of exiftool for jpeg extractions, accessible as an advanced setting (do use this option if exiftool extractions are sometimes small, dark, and/or dull - dunno what causes this problem, but here's the solution...).
- Also uses a different storage/retrieval mechanism for recording file change info, so if files pop up that were previously beaten down, that's why - otherwise should work as well as before, maybe even a little better ;-}
- Improved performance of 'Save Metadata' feature.
- Minor enhancement to error message in case NX2 executable is specified incorrectly.
- Also added option to accept NxToo's choice of base photo without
prompting, even when it may be uncertain or ambiguous.
- Changes to allow 'Save Metadata' to work even if jpeg preview is not a member of the collection containing the raw being edited.
- Note: If Ctrl/Cmd-s is not the proper keystroke sequence to save metadata on your keyboard, then you will have to configure the correct keystroke sequence using "advanced settings".
- Corrected very minor bug in logged information.
- Fixed bug cleaning up extracted preview when error occurs before finalizing addition to catalog. Resulted in a later orphaned preview discovery warning.
- Added option to delete orphans when encountered
by watcher (presence of these orphans was generally due to previous errors when running versions of NxToo prior to 4.4.1).
- Removed support for ImageMagick converter packaged with plugin for Windows (it wasn't working on all machines).
- Robustened the error handling around jpeg extraction and resizing (and temp file cleanup in case of error).
- Improved handling of errors that can occur when attempting to resize extracted jpeg.
- Updated for Mac.
- Windows users: added dlls that me be required for the jpeg extraction reduction (ala image-magick) to work.
- Changes to handling of cooked nef - now stacked under cooked tif or jpg if found.
- Changed to store filename instead of path for base photos - that way it still works when photos are moved to a different folder (existing base paths will be auto-migrated).
- Fixed bug in preset manager: switching presets would take 2 tries, after having switched to another plugin and back in plugin manager.
- 1 minor clarification in plugin manager configuration about rgb nef stack position.
- Add extracted jpeg resize option.
- Performance improvements.
- Robustification of save-metadata feature.
- Added base photo extension search path to advanced settings, to provide a more likely base photo option when newly saved photos are discovered that don't fit a recognized filename pattern (previews, sidecars, cooked rgb, ... ).
- Fixed bug: 'Update Plugin' function in plugin manager was broken.
- Fixed bug: Was adding new rgb to catalog
even if 'Cancel' was chosen.
- Plus a few other little improvements and bug fixes...
- Re-worked base photo handling.
Initial release, with latest Windows exiftool v8.63.
(versions 1.0 to 3.X were previously released as NxTooey)
acceptance of Download Terms & Conditions will be required
NxToo 4.6 - newest release: this is the one to download.
NxToo 4.5.4 - for fallback in case newest release has a problem, in which case please let me know.
| Static content updated 2011-09-01 | Copyright 2007 - robcole.com - all rights reserved. | Dynamic content updated 07:25:36 PM |