Other than the usual bug fixes, the big thing for me is that it now supports Intel Macs... and wow, is it fast!!!! Other changes are resizeable histograms, more keyboard shortcuts and some other user interface changes
The best news is that for exisiting users the update (which should be posted shortly) will be free!
P.S. The press release says the software being shown is beta but the folks from Nik software, who wrote the code, said things are golden master (which means finished!)
Please tell me it remembers your quality settings when making jpegs and please tell me the windows(like browser and base changes and edit steps) stay open if you want. I really get tired of constantly opening the browser and reopening my tweaks. Does anyone in beta have dual monitors because while the interface is great for single setups it really doesn't allow you to use the real estate if you have 2.
In the version I saw, it does remember your quality settings, as well as the last directory you used to save (doesn't always revert back to default directory). Right now, I don't know if any way to keep the browser open with dual monitors, but it is a good suggestion.
Not keeping the browser open was one of the big detractors for me. However, the panes are undockable and moveable over to the 2nd (or first) monitor - which is better than nothing for those of us with 2 monitors.
I was here today, and it looks pretty good. The improvements on the size of the histograms really helps. I did not get a chance to try it out, so I cannot tell if some of my "favorite" bugs have been fixed or not.
Some interesting other pieces of information:
I asked when we could expect NikonView/Nikon View Pro to actually support the edited NEFs by dispalying them properly. The answer was never.
So I then asked was the expectation that NX was supposed to be our browser, and he responded that that was going to be up to the OS developers (IE Apple in this case).
So I then asked if that meant that the SDK would support these edited NEFs, and he replied that it already did.
So I then prodded a little more and got the answer that this version of the SDK which supports the edited NEFs was not yet shipping.
I like Capture NX, but currently I'm still using RawShooter to do my initial sorting of images since Capture offers no way to slideshow the images full-screen and give them ratings.
Likewise I currently have to produce JPEGS of all my finished images, so that I can slideshow them to my wife. Otherwise I would just store the altered NEFs and only convert to JPEG the odd image I wanted to print.
I was viewing this as a stop-gap solution until Nikon View Pro came out. If it's not coming out (and Capture doesn't plan to implement something) then I may think about switching over to Lightroom.
I don't suppose they are making this SDK available to open source developers? (didn't think so)
I gave up waiting for NV Pro, and switched to Photo Mechanic. It's expensive, but it does a lot of things really well. One of those things is that it uses the full-size embedded JPEG from your NEF for previews. The trouble with Nikon View and iPhoto is that they convert the NEF to generate the preview. Thus, the NX "edits" are not displayed. Photo Mechanic can use the Apple converter, but again, it doesn't see the NX changes (only the NX file browser does).
My gut feeling is that the NX file browser was developed to serve as a batch interface and for basic sorting, and was left the way it is as not to conflict with the presumed Nikon View Pro release. If NV Pro is really gone, let's hope that Nikon decides to implement it into NX in some fashion. The NX browser is really not useful for critical evaluation of your files, nor is it intended to be.
> .....One of those things is that it uses the >full-size embedded JPEG from your NEF for previews. > >
I am using Bridge(with arc disabled and the Nikon plugin in its place) which seems to keep up with even the new Nx edits but I find the quality is too low... Bridge is obviously using an embedded jpeg and my question is whether Photo Mechanic uses something better?
It seems to be a real shame that Nikon wants to have a competitive editor and as far as raw goes I really like Nx save for interface nuances, and yet does not have a decent viewing/cataloging software that accurately works with it...from what you have said in terms of a viewer that keeps up with Nx edits we are stuck with the embedded jpg images or the Nx file browser which isn't for viewing or sorting but for batch...not good at all IMHO.
>So I then asked if that meant that the SDK would support >these edited NEFs, and he replied that it already did. > >Doug
Poppycock. The SDK doesn't apply cropping done in NEF's by CNX. A new version of iMatch was just released and it has the latest SDK applied to it. Converting an NEF to a jpg, which Mario swears uses the Nikon SDK tools, does NOT work properly. To my eye the only Capture commands interpreted are those in the Base Adjustments, which is the old Capture 4.4 functionality as I'm told.
I wonder if the forthcoming update to Capture NX also includes support for Windows Vista. According to the Nikon Knowledge Base, they plan on making a Vista-compatible version available for download. Perhaps this is it - although the press release didn't say anything about Vista.
I'm also disappointed that they aren't going to update Nikon View to be able to read the updated NEF's; although, I also noticed in the Nikon Knowledge Base that there are no plans to provide a Vista Compatible version of Nikon View; so, I guess it's a moot point.
I did ask about Nikon view. I did not tag on the "PRO" when I asked. However, since I was pushing him on this, and he said it was going to beup to the OS to handle this, that would imply Nikon View Pro would not display the imges properly? This wouldn't make sense to me as you would think they would use their own SDK.
Hopefully the Nikon Rep at the show was confused about what I was asking and View and View Pro.
However, if they have incorporated it in the SDK, then you have to imagine support in iPhoto and Mac OS X in general would come with an update or new versions as I believe they do use the SDK.
>I did ask about Nikon view. I did not tag on the "PRO" when >I asked. However, since I was pushing him on this, and he >said it was going to beup to the OS to handle this, that >would imply Nikon View Pro would not display the imges >properly? This wouldn't make sense to me as you would think >they would use their own SDK.
You have to wonder if this is coming from Microsoft. They have decided not to update the RAW file viewer for WinXP only saying that you need to buy a copy of Vista to get updated functionality as it was built into the OS.
The RAW viewer for Vista says an upgrade is available, that sends you to a link to Nikon who says it is not available yet. It has been like this for 6 months. Thus NEFs are not viewable in Vista Photoviewer. Ian
>I'm also disappointed that they aren't going to update Nikon >View to be able to read the updated NEF's;
Hello! Am I on the same planet? My copy of NV displays the NEFs edited in NX with the effects of the edits displayed, including those done with color control points. Cropped images are also displayed properly.
Please note: I'm doing the edits in Edit Steps, not Base Settings, so NV's displays aren't because NX is saving the images in an NC 4.4 manner.
Whatever the limitations of NV as an image organizer, inability to display NX edits isn't one of them.
>It depends. If your browser reads the embedded preview JPEG >that NX produces, you see all the edits. If it re-renders >the RAW file, then it won't show what NX did. > >-Jason
I don't think that is right....I tried NV with both re-create thumbnails from actual image data checked and unchecked and in both instances the new edits using steps showed up fine. This helps since my problem with Bridge was the quality of preview. Keep your fingers crossed and maybe ViewPro features will make it into NX.
I think this update will not address the overall way in which batches are performed. Instead, it is intended to be a service release, adding improved performance.
Your suggestions, however, are good ones, and I've already commented on exactly the same idea to the Nik/Nikon team. The code re-write necessary to bring Intel Mac support and Windows Vista support is likely to be where the current efforts have been over the last several months. That being said, the Histogram windows are now enlargeable, as well as the levels/curves windows. This is a vast improvement over the previous version.
There is also more keyboard functionality within things like the LCH editor-- when you place a point on the curve, you can use the arrow keys to move that point up and down or left and right. For me, that's a big deal because accurate adjustment of curves with my mouse is something I could never really do.
Undoubtedly, this release will be a major improvement, but that doesn't mean that more improvements aren't needed (or coming). I think that despite what people say, the Nikon team actually does listen to us photographers. There will always be trade-offs for what new features can be implemented in a reasonable time frame, because that's the nature of the software development business.
As a Mac user, I personally think that the development of UB code was way more important than a better File Browser window. I still want a better File Browser, but I'll let that slide because I'll be getting a HUGE performance improvement with the new code.
>As a Mac user, I personally think that the development of UB >code was way more important than a better File Browser >window. I still want a better File Browser, but I'll let >that slide because I'll be getting a HUGE performance >improvement with the new code.
Will this version be any faster on PPC Macs, or is it just the Intels that get the speed boost?
I think that the Nik guys are always trying to increase the overall speed of the application. The reason that the Intel Macs get such an outstanding speed boost is because they will no longer need to run NX under emulation (Rosetta). The Intel chips are generally faster than their PPC counterparts-- but only when the code is optimized to run natively on them.
Jason P. Odell Colorado Nikonian Author, The Photographer's Guide to Capture NX