 |
San Francisco, California | |||
| USA | ||||
|
|
San Francisco, California | |||
| USA | ||||
NX Tooey Lightroom Plugin
*** *** NxTooey has been deprecated in favor of NxToo - same goal but totally different design ;-)
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:
Note: missing is
When a raw file is being edited in NX2, NxTooey is waiting for it to be saved in NX2, so the jpeg can be extracted for Lightroom:
Once the raw file has been saved in NX2, the progress indicator changes to indicate that the jpeg preview has been updated in Lightroom.
When a cooked file is being edited in NX2, NxTooey is waiting for it to be saved in NX2, so the cooked nef and or tif/jpg copies can be updated in Lightroom:
After a tif has been saved in NX2, the progress indicator changes, indicating that the tif or jpg has been saved, but the cooked nef should also be considered (since it is needed to store the NX2 edit settings):
Once the cooked nef has also been saved, the progress indicator changes again, to indicate that all cooked copies associated with the file being edited have been saved:
As soon as an edited raw file is saved in NX2, this dialog box appears in Lightroom. This dialog box can be used to confirm version name, take a raw snapshot, and/or add a brief edit description to the 'NX2 Edit History' metadata.
Raw-Jpeg metadata in Library panel after the save:
(Base copy name is reserved for cooked metadata)
Raw base photo metadata after the save:
(NX2 Raw Version only applies to raw-jpeg)
After the first cooked nef, tif, or jpg is saved, this dialog box pops up. After all cooked files have been saved, this dialog box can be used for taking a snapshot or adding notes for the 'NX2 Edit History' metadata.
Cooked metadata in library panel after the save:
Plugin Manager Configuration
(since one size does NOT fit all...)
I have settled upon a Lightroom-centric workflow, because Lightroom is the best (for me), in general, in most cases. Still, there are some exceptions and/or differences, which keep me coming back to NX2:
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 so no reason for NX2 for raw there. Lightoom 3's raw conversion and noise reduction are now better than NX2 (IMO). So, 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, generally resort to local correction if its too late to switch to a linear profile. 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 "NEF(Raw) -> Tiff(16) Color Space", 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 you save metadata, but that's not important for the purpose of this document). 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.
*** Purists will claim Photoshop can open the same raw files as Lightroom and so you can see the Lightroom changes in Photoshop, 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...), the point is somewhat moot. - completely moot for the purpose this document serves.
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 + adjustements. You will lose quality however if you subsequently 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. That will change if I finish my most desired feature for this plugin, but I'm jumping ahead... - please bare with me. So, we have the following scenarios:
There are two ways to work on an image in Lightroom that was started in NX2: (1) save a tif or jpeg from NX2 and import that in Lightroom, OR (2) extract the jpeg preview from the raw NEF and import that in Lightroom. Note: Unlike the original jpeg preview in the original raw NEF (which is basic quality), the jpeg preview in the edited raw NEF is top quality, 1st generation, and re-created everytime the raw NEF file is re-saved by applying NX2 editing instructions to the original raw data. Note: versions of NxTooey prior to 3.4 did not always assign the correct ICC profile to the extracted jpeg, nor do programs like previewextractor or dcraw or exiftool. NxTooey 3.4+ does assign a proper icc profile along with as much metadata as it can (configurable).
The only way to work on an image in NX2 that was started in Lightroom is to export a tif or jpeg and load that into NX2. After editing in NX2, the only way to see those changes in Lightroom is to save a tif or jpeg from NX2 and import that into Lightroom. However, the only way to work on it again in NX2 (saving adjustments), is to also save it as a cooked nef. Note, for future reference, in so doing, the original Lightroom edits are forever locked into the base image of the cooked nef. Subsequent edits of the cooked nef in NX2 will never be seen in Lightroom, except by re-saving the tif or jpeg.
Refresher: If one starts an image in NX2, then one can simultaneously work on the same image in Lightroom and NX2, since one can edit the raw NEF in NX2 and use the jpeg preview as the base image in Lightroom to work on. Reminder: the reason for this is that NX2 is capable of updating the base image to which Lightroom edits are applied (the extracted jpeg preview or a saved-as tif/jpeg).
Unfortunately, the converse is not true - there is no way for Lightroom to update the base image to which NX2 edits are applied. The solution (short of Nikon and Adobe collaborating for our sakes), is to be able to merge an exported Lightroom image into a cooked nef, thereby updating the base image to which NX2 edits are applied. If I ever figure out how to do this, I will.
I was thinking of doing this by re-writing the cooked nef from a plugin. But that's a lot of work, since there is no native lua tif support that I know of, and it takes more know-how than I presently have to write that code. A more likely solution is to write/modify or use an already existing tool to do it. Note: nefs are very much like ordinary tif files with some Nikon proprietary data embedded. So if you ever have any ideas about pre-exiting tools that could do it, or source code that is already close. please let me know!
To reiterate: what needs to be done is to re-write a cooked nef (which is nearly the same as an ordinary tif), preserving all the cooked nef metadata (which is in standard tif format), but simply replacing the main image with that from a tif or jpeg file exported from Lightroom. If you have any ideas how this might be done, or where to start... - please, please, please - let me know!!!
| raw | 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. |
| raw-jpg | The jpeg extracted from the raw. Represents, in Lightroom, the original raw or raw edited in Nx2. It can be enhanced non-destructively in Lightroom after the raw is edited in Nx2. Note: unlike the sidecar jpeg that your camera creates, an extracted jpeg by default will include no metadata nor a proper ICC profile (meaning the colors will only be right if the image was shot in-camera as sRGB, and has not been assigned or converted to a different profile in NX2). So, unless an extraction software advertises proper handling of icc-profile & metadata (which requires considerable extra programming effort) you can assume extracted jpegs are sRGB & stripped. NxTooey 3.4+ handles icc-profile correctly and metadata. |
| cooked | In general, means an RGB image after raw conversion, but for the purpose of NxTooey, it means one of three files: cooked-nef, cooked-tif, or cooked-jpg. |
| cooked-nef | 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 | The very first one of these is exported by Lightroom for Nx2, with Lightroom edit adjustments applied, for Nx2's sake. After that it is 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 | 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 when using single-ver mode of "edit edit in nx2". |
| NX2 Version | The equivalent of Lightroom virtual copies in NX2. See the drop-down at the top of the NX2 edit-list. |
| NX2 Application | Absolute path to NX2 in Windows, or app-name in Mac. |
| Saved-RGB Sub-Extension | For Single-Ver mode of 'Edit Raw in NX2'. If you shoot raw-only, you may find life simpler by leaving this blank. Likewise, if you don't mind overwriting in-camera jpeg with NX2 jpeg, blank is best. However, if you want to distinguish NX2 saved jpegs from in-camera jpegs (or any other jpegs), then this sub-extension will do the trick. Example filename: ND300_12345.nx.jpg ('nx' is the sub-ext). |
| Raw-JPG Sub-Extension | raw-jpg files will be named {base}.{sub-ext}.jpg, for example: |
| Cooked Sub-Extension | Cooked files will be named {base}.{sub-ext}.{ext}, for example: ND300_12345.nxc.nef or ND300_12345.nxc.tif |
| Jpeg Color Space | Used for conversion from Tif to Jpg when optimizing cooked edits. Generally its 'AdobeRGB' or 'sRGB' (without the apostrophes) - case sensitive. |
First, configure nx-tooey in the plugin manager (see above).
Second, it is recommended to check 'Treat JPEG files next to raw files as separate photos' in Lightroom preferences ('General' tab). This may be required for cooked edits or single-ver edits if tif and jpg will both be saved (otherwise they look like a raw/jpg-sidecar pair).
(for when you want just one NX2 version, and are willing to save a tif and/or jpg in NX2 for use in Lightroom)
Note: In this scenario, Nx2 does the raw file conversion, so you can take advantage of active d-lighting, Nikon lens corrections, ... Lightrooms roll is more that of an external pixel editor - you can apply Lightroom changes to the tif or jpeg, but you will not be able to take advantage of Lightroom camera profiles, raw white balancing, raw lens corrections, ...
Note: In this scenario, Nx2 does the raw file conversion, so you can take advantage of active d-lighting, Nikon lens corrections, ... Lightrooms roll is more that of an external pixel editor - you can apply Lightroom changes to the jpeg, but you will not be able to take advantage of Lightroom camera profiles, raw white balancing, raw lens corrections, ...
Note: In this scenario, the Lightroom edits to the original raw are only done once. If it is desirable to redo the original raw edits in Lightroom, the whole scenario needs to start over, since it is presently not possible to update the base image in the cooked nef (this is the missing piece I hope to fill some day). Thus, all Nx2 edits will have to be redone from scratch. Note however, that the subsequent edits in Lightroom to the tif, are still valid, and may not have to be redone.
Note: If a jpg is saved and the tif is a fresh export that has not been added to the catalog, the tif will be automatically deleted.
Note: if you save the cooked nef but not a tif or jpg you will be prompted, since Lightroom can't see NX2 edits in a nef file. Likewise, if you save a tif or jpg but not a nef, you will be prompted, since without the cooked nef, you will not have the benefit of non-destructive editing in NX2. Unlike the former prompt, the latter prompt can be turned off.
Note: I recommend if you choose 'ProPhotoRGB' for "NEF(Raw) -> Tiff(16) Color Space", 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.
This is for error recovery only. The purpose is to bind one or more cooked, raw-jpg, or saved-rgb photos to an original raw. This is not necessary unless something goes wrong, like an error occurs in NxTooey or Lightroom crashes. The original raw must be the most selected photo, and the others will be associated with it so they can be edited in NxTooey again. If you select a photo that should be editable in a certain way, but you get an error like: "selected photo is not associated with any raw file...", try 'Link to Base Photo'.
The purpose is to delete big tifs and/or cooked nefs in favor of keeping fewer and smaller files, like maybe just a jpeg. I found quite often I'd keep a cooked tif and nef around for a while until I realized I'd likely not edit again, then convert the tif to jpg and delete tif and cooked nef, so I rolled this into a menu action. Note: no files will be deleted by NxTooey. What will happen, is the tif will be converted to jpeg and then the tif and nef will remain selected, so you can delete them both or just one type, as you see fit. - Try it after a cooked edit! - you can always delete the jpeg that's created if youe're not ready for it yet.
Note: In this scenario, Lightroom would be used to process the original raw, but finishing touches could also be done in Lightroom to the tif with impunity. Nx2 edits would always be done to the cooked nef.
Examples:
Scenario #1:
ND300_12345.NEF - original (or edited in NX2) raw.
ND300_12345.raw.jpg - jpeg extracted from raw file, a.k.a. raw-jpg.
ND300_12345.raw-2.jpg - jpeg extracted from same raw file, but different NX2 version.
Scenario #2 (first creation)
ND300_12345.cooked.nef - cooked nef.
ND300_12345.cooked.tif - tif for Lightroom.
Scenario #2 (second creation)
ND300_12345.cooked-2.nef
ND300_12345.cooked-2.tif
Scenario #2 (third creation)
ND300_12345.cooked-3.nef
ND300_12345.cooked-3.jpg - jpg saved instead of tif - tif intermediate was automatically deleted.
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 NxTooey?
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: Whats the slowest way to invoke the functions of NxTooey?
Answer: Lightroom's File Menu -> Plugin Extras -> RC NX Tooey ...
Question: Whats the quickest way to invoke the functions of NxTooey?
Answer: On Windows:
On Mac, use the OS/Automater to configure keystrokes, or something like QuickKeys.
Question: How can NxTooey Help?
Answer: By allowing you to open raw or cooked nefs in Nx2 from Lightroom, 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).
A better answer to this question is found in the workflow-howto's above.
Question: What Color Space & Bit Depth are used for the initial TIF in cooked edit scenario, and which one should I choose?
Answer: Your choice, generally ProPhotoRGB/16 or AdobeRGB/16. I usually don't edit cooked in NX2 until color and tone are in the ball-park via Lr, in which case I choose AdobeRGB, so the final colorspace is what I want in Lightroom. ProPhotoRGB may be better suited if color/tone have not been adjusted near enough in Lightroom first, in which case a fuller range of values may help preserve color options in NX2. Truth is I can' tell the difference with my eyes so its all sort of academic to me, but maybe its not to you... Just remember if you choose ProPhotoRGB, and if you're gonna save a jpeg in NX2 for Lightroom, that you convert colorspace to AdobeRGB as final step in NX2, so you don't end up with a ProPhotoRGB/8 jpeg in Lightroom, which is not optimal. Another option would be to save (in NX2) a TIF/16-ProPhoto for Lightroom, then do the jpg conversion to final colorspace in Lightroom.
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 version 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: What is the best colorspace to use for editing cooked tifs.
Answer: Theoretically ProPhotoRGB, but then you'd better remember to do a conversion to AdobeRGB or sRGB as the last "edit" step in NX2 before saving a jpeg for Lightroom, or you'll be worse off than if you'd started with AdobeRGB. Practically, if the tone and colors have already been adjusted in the ball park in Lightroom, then there will probably never be any perceivable difference when using AdobeRGB instead of ProPhotoRGB, and you won't have to remember to convert the colorspace in NX2 before saving a jpeg.
Question: What is the best colorspace to use for optimizing cooked tifs to jpeg.
Answer: AdobeRGB may be the best for you, since it usually looks the most like the other editings in Lightroom and NX2 (e.g. raws & 16-bitters). However, if you always export jpegs as sRGB, I could argue for optimizing to sRGB instead, so that what you see in Lightroom, is what you'll see after exporting. Personally, I export (almost) all jpegs as AdobeRGB since all my export presentation software/firmware supports it. I reserve sRGB exports for the rare occasion when I export for email or other times when the export presentation software is unknown, since the most common way for a crappy app to screw up jpeg display is by assuming its sRGB, and many legacy apps (e.g. internet browsers) only do sRGB.
Question: Whats all this about NX2 Versions...?
Answer: If you don't use NX2 versioning (see definition in section above), just leave this field blank when editing raw in NX2. If you do create named versions in NX2, and you want a separate raw-jpg for each in Lightroom, then be sure to associate the NX2 version name with the raw-jpg in Lightroom, via the save raw-jpg dialog box, or after the fact by editing nx2-version metadata in the library panel.
Question: Whats the difference between Extract Jpeg Sidecars and Extract Raw-Jpgs?
Answer:
Extract Jpeg Sidecars:
Uses same base name as raw and overwrites previous file of same name if it exists. Jpeg will represent nx2-version as set in Nx2. No strings attached - you will not be able to edit the associated raw ala NxTooey. You can always use 'Open in Nx2' to edit the raw.
The latter will prompt for a freshening or new file to be created and is associated with a specified Nx2 version. Strings are attached that allow editing the associated raw in NxTooey.
Question: Whats the difference between Edit in NX2 (Single-Ver) and (Multi-Ver)
Answer: Starting in v3.7 'Edit in NX2' has been divided thusly:
Multi-Ver is the original: User saves original raw NEF after editing each version, and NxTooey extracts jpegs named {base}.raw.jpg, {base}.raw-2.jpg ... - one for each NX2 version.
Single-Ver was added to support saving a single tif and/or jpg in NX2. RGB image name is fixed and must be {raw-base}.tif or {raw-base}.jpg (lower-case extension, no "sub-extension"). Only supports one version this way.
Question: What are the limitations of NxTooey and what are your plans for the future?
Answer: Without question, the biggest limitation is not being able to update the base image in a cooked nef. Also:
(reverse chronological order)
- Minor aesthetic changes only - keyboard shortcut for optimize menu function, wording of dialog boxes...
- Fixed 'Link to Base Photo' function for single-ver tif/jpg photos with sub-extension.
- Fixed Bug (introduced in v3.7.0): 'Edit Raw in NX2 (Multi-Ver) was not transferring Lightroom metadata (only NEF/exif metadata) to the saved RGB file(s).
- Enhanced 'Edit Raw in NX2 (Single-Ver) to support a sub-extension (to avoid overwriting jpeg sidecar for those Raw+Jpeg shooters who want to keep their in-camera jpeg sidecar virginal).
- Enhanced 'Edit Raw in NX2 (Single-Ver) to allow selection of rgb target (tif or jpg) for editing (like multi-ver has always been), instead of just the raw file.
- Aesthetic change only: Moved the "Done" checkbox in the Single-Ver (save-in-catalog) dialog box.
- Divided 'Edit Raw in NX2' function into 'Single-Ver' and 'Multi-Ver' modes.
Note: Multi-Ver is the original: User saves NEF, and NxTooey extracts jpegs named raw.jpg, raw-2.jpg ... - one for each NX2 version.
Single-Ver was added to support saving a single tif and/or jpg in NX2. RGB image name is fixed and must be {raw-base}.tif or {raw-base}.jpg (no "sub-extension", lower case final extension). Only supports one version this way.
- Fixed bug affecting 'Extract Jpeg Sidecar' when edit-notes were being applied.
- Minor bug fix affecting log file content.
- Added menu function to extract jpeg from raw file as a sidecar (no strings attached - same base name as raw).
- Fixed bug: raw-jpg extraction was failing in presence of camera jpeg sidecar.
- Supports cooked editing of non-Nikon files. As examples, you can now edit cooked Canon CR2 files (auto-converted to tif) in Nx2, or jpeg masters...
- Stack position was broken in 'Extract Jpegs' function.
- Minor aesthetic primping.
- exiftool.exe
updated to latest.
- mac users: consider updating exiftool yourself...
- Fixed bugs having to do with NRW support. Tested using P7000 NRWs.
- Extracted JPEGs always have a proper ICC Profile assigned.
- Added the ability to configure which metadata items you want to be transferred from the raw to the raw-jpg extraction. Much of which won't be viewable without the newest not yet released version of ExifMeta.
- Extracted jpeg oriented correctly, in Lightroom, ACDSee... - image viewers that respect the orientation tag in EXIF metadata, which Windows 7 does not.
- Added option for edit history when using extract-and-import-jpeg, since I sometimes use it instead of doing things the "right" way (Edit Raw in NX2). Snapshot option didn't happen there - oh well.
- Made some enhancements that improve the odds it works with NRW - but haven't tried NRW yet. Send me an NRW file and I'll test & report.
- Prompts for colorspace to be used when exporting cooked tif to edit (prior to this version, ProPhotoRGB was hardcoded)- its also a plugin preference and you can avoid the prompt if its bugging you...
- Fixed the new icc-handling jpeg extractions to work for all cases - previously it was failing when extracting jpegs from raws that had not yet been edited in NX2 (in which case there is not yet an available icc-profile - since they're added by NX2, not the camera).
Please let me know if you have any ideas how to improve it if/when you try it - thanks.
- Changed to use exiftool instead of dcraw for jpeg extraction and subsequent icc-profile handling.
- Handles icc-profile correctly when extracting raw-jpg.
- On Windows: Exiftool is included-with/embedded-in plugin.
- On Mac: Phil Harvey's Exiftool
must be pre-installed by user before running NxTooey.
- Updated with Mac support - includes dcrawx86.
- Fixed an 'Open in Nx2' bug.
- Massaged some misleading text info in the 'Quick Tips'
- Added 'Optimize Cooked Storage' function that converts tifs to jpg and selects all corresponding tif & nef files so they can be deleted by the user.
ALPHA PREVIEW status will be dropped when Mac functionality is tested and debugged. Windows users should be OK.
- Added support for NX2 raw edit versions, cooked editing of virtual copies, plus metadata and snapshotting...
- Moved configuration from lua file to preferences (unfortunately, I did not think to transfer your existing config settings, so you'll have to re-enter them in the plugin manager).
- Coded it to support NEF & NRW simultaneously, although not yet tested for NRW (only NEF).
- Changed stack handling:
Please let me know how it works or doesn't if/when you try it - thanks.
- Fixed bug whereby raw was not opening in nx2 if raw-jpg was selected instead of raw file itself, and raw-sub-ext was set to 'raw' instead of 'NEF' (as example), in the config file.
- Big changes, including additional features to edit raw or edit cooked, with derivative file handling / updating in Lightroom.
- Note: 2.1.0 will be along shortly to add preferences to the plugin manager so you don't have to edit the lua config file. Until then - let me know if you need help or have problems...
- Sorry for the lua config instead of plugin manager.
- Sorry for not trying Lr2 before releasing.
- Sorry for not testing the Mac version before releasing.
- Sorry for not figuring out how to support NRW and NEF simultaneously yet.
- Added a button to the plugin manager to reset all warning dialogs for NxTooey.
Initial release.
*** DEPRECATED - Use NxToo instead... - its better :-)
acceptance of Download Terms & Conditions will be required
NxTooey 3.8.2 - last version ever - no longer supported.
| Static content updated 2010-09-16 | Copyright 2007 - robcole.com - all rights reserved. | Dynamic content updated 07:25:58 PM |