#5. "RE: Wish list for NX3" In response to Reply # 0
Farmington Hills, US
In addition to new features mentioned above, I like to be able to insert edit steps into an existing list, not just add them at the end of the list. We had insert in Capture NX, but it disappeared with Capture NX2.
Gary in SE Michigan, USA. Co-organizer of the Southern Michigan Chapter Nikonians membership - My most important photographic investment, after the camera. D4, D810, D300, D90, F6, FM3a (black), FM2n (chrome) YashicaMat 124, Graflex Speed Graphic 4x5 My Nikonians Gallery & Our Chapter Gallery
#9. "RE: Wish list for NX3" In response to Reply # 0
1. I want the NX2 'Crop' Edit Steps to indicate what dimensions or proportions they're applying to my image!
And I make heavy use of Versions, so I can think of lots of improvements there: Here's just a few -
2. I want the creation of any new Version, or a change to the text in any existing Version name, to cause the file to be flagged as "changed" (with the asterisk applied etc.), so I can then do a "Save" - guaranteeing that the updated Version info' isn't stupidly, stupidly, time-wastingly and frustratingly LOST when I close the file!
3. I work on many images in a session and I'll typically forget (and forget to note) the highest-version-number reached so far, so I want automatic increments on each new version number; and it should be a simple "2." (for example), instead of always offering us the same clunky "Version 1" to edit or overwrite. (The actual Version numbers are useful as I can then save time by writing "As 3. but less warm" for example.)
4. The "Version name" should be only the name or a short title for the Version, and we should have a separate larger text area so we can add longer notes about the editing we've done in that Version. At present we can write reasonably long notes in the existing 'Version name' box, but there's no line-wrap, so the long "names" soon become hard to read, especially when we choose to "Edit Versions".
NX2 (or 3) would be the idea program, and our NEF files could be the ideal place for us to add general notes about our original image files, where those notes would not be relevant in the final IPTC fields or in our Keywords. But there's nowhere available - unless I add extra text files alongside the photos. This is daft! (IMO).
Where Nikon includes its own "Maker Notes" inside each NEF file, wouldn't it be handy to have an area set aside (in NEFs only) specifically for "photographer's notes"??
NX2 is now my main editing program and I'm looking forward to NX3 (or whatever it'll be called) because in spite of its quirks and its probably wallet-denting upgrade price, I do expect that we'll get some richer features and even better stability.
Sadly (as a part-time computer programmer) I'll predict that the much yearned-for "crop bug fix" will not arrive for a long time ... if ever! It would take a lot of in-memory data storage and much cross-referencing of pixel co-ordinates (meaning even more demand on CPU resources than at present) to keep track of our many Control Points as we adjusted and changed our image proportions. That's quite a tough programming call, I think ... but maybe the (full-time!) Nik programmers will prove me wrong
#10. "RE: Wish list for NX3" In response to Reply # 0 Thu 27-Jan-11 01:19 PM by TiggerGTO
Edited to add my most important request:
Please Nik, give us an indication that something new is being developed and at least a hint of when we might see it and what might be in it.
My list is sort of a cross section of what others have already said:
1) Fix the interactions between control points and adding/deleting crops
2) Allow crop steps to be edited
3) Make NX3 compatible with all the Nik plug-ins (although I guess Viveza would be sort of redundant)
4) Do something/anything to make NX3 fit better into an overall multi-application workflow. If nothing else, work closely with the guys at Camera Bits and make NX3 work nearly seamlessly with Photo Mechanic.
5) Make NX3 a much more stable and robust program
6) Enhance performance and improve the batch workflow
#11. "RE: Wish list for NX3" In response to Reply # 0
New York, US
I'd like everything you guys listed, but I'll settle for any of it and —most important — patch upgrades for upgraded system software to be released the same day (same week, same month) that the system software vendor releases the upgraded system.
Jon Kandel A New York City Nikonian and Team Member Please visit my website and critique the images!
#14. "RE: Wish list for NX3" In response to Reply # 13 Fri 28-Jan-11 02:04 PM by nrothschild
>> The biggest wish is to know if a NX3 is actually happening!
Neil, I will humorously disagree
A CNX3 is as certain as anything short of death and taxes. Nik is software company and software companies using the consumer model can only survive by extracting periodic payments from its customer base in the form of periodic updates. It is only a question of when, not if
The big question is if Nik and Nikon actually listen to their customers. Many of the requests here were widely expressed prior to CNX2, but CNX2 resolved very few of the outstanding major complaints and requests.
I upgraded to CNX2 very begrudgingly and I think only when I was forced to by a camera body upgrade. I think cameras have reached a point in their development where I will not feel compelled to own the latest and greatest. I only hope Nik and Nikon realize that there are many like me and actually respond to our requests.
#15. "RE: Wish list for NX3" In response to Reply # 10
>4) Do something/anything to make NX3 fit better into an >overall multi-application workflow. If nothing else, work >closely with the guys at Camera Bits and make NX3 work nearly >seamlessly with Photo Mechanic.
Hopefully this is not a thread hijacking: what is it about Capture NX2 that would make it work better with Photo Mechanic? I have recently bought PM and really like it and can't see anything, yet, that could be improved in terms of NX2 integration. I do believe there must be stuff; just wondering what it is.
#17. "RE: Wish list for NX3" In response to Reply # 15
At this point, I think it is more a matter that PM works well with CNX2 and the Nikon way of dealing with NEFs.
First, PM fully utilizes the NEF's embedded JPG.
Second, PM has a very sophisticated set of options that allows it to inter-operate with CNX2's color classes, ratings and IPTC tags. And it actually updates the NEF file directly, something that not too many 3rd party apps want to do.
As a result it is possible to configure PM such that either app can change color classes, ratings and IPTC, and the other app will recognize those changes. No minor feat considering the difficulties.
My interpretation of the request you listed above is for CNX2 to support XMP files. Most apps don't want to actually update the NEF file and Nikon won't use XMP files, which is how most other apps share metadata (without updating the NEF).
A good example of this is iMatch. iMatch will post metadata to the NEF, and reads the embedded JPG, but it has a big bold red warning in it's help text that you update the NEF at your own risk . iMatch would be happy to work with an XMP file (and creates them for other apps) if Nikon would.
#18. "RE: Wish list for NX3" In response to Reply # 15
PAStime, Nikon software such as captureNX2 is the ONLY software that can completely read Nikon RAW files (NEF). Other software can open NEF files, but cannot read the complete file (including in-camera settings that you have setup in your D7k).
PM cannot include in-camera settings in an NEF file that it has opened.
The workflow I use is open files (I only shoot RAW(NEF) with captureNX2, then I do most post process editing with cNX2. After that I do most "cataloging" functions with Photo Mechanic.
Hope this helps?
. . .
MY SETUP Nikon D7000 with zoomNIKKOR AF-S DX 10-24mm f3.5, Tamron AF 18-270mm Macro f3.5 Di II VC LD and Tamron AF 180mm f/3.5 Di SP A/M FEC LD (IF) 1:1 Macro Nikon R1 Wireless Close-Up Speedlight System, ZacutoEVF Pro Two SanDisk 32GB EXTREME PRO SDHC-UHS-1 (45MB/S) viewNX2 captureNX2 NIKCompleteCollection Ultimate Photo Mechanic 4.6.6 Annotate Pro Vegas Movio Studio 10 Pinnacle Studio Ultimate 14
#19. "RE: Wish list for NX3" In response to Reply # 18 Sat 29-Jan-11 02:15 AM by nrothschild
>> PM cannot include in-camera settings in an NEF file that it has opened.
Actually, PM does "include in camera settings" to the extent it doesn't open and render the raw data, it just uses the up to date embedded jpg.
I use windows, as does Peter, and I think you do too. What I just said is absolutely true of Windows. Windows PM never renders the raw data.
On a Mac, PM can use Apple's Spotlight to actually render the raw data but CameraBits generally recommends not doing that because Spotlight, like most apps, does not read and apply Capture's edits.
>> Other software can open NEF files, but cannot read the complete file (including in-camera settings that you have setup in your D7k).
Actually, there are exceptions to that. iMatch can be configured to render images from the Raw data. In that case it does apply Nikon's in camera settings. It does that because it can use, among a couple of options, Nikon's software API that more or less correctly reads the in camera settings and Capture edits. I have done that with tens of thousands of D2h files, which need to be re-rendered in order to create iMatch's "offline cache" with a decent size thumbnail.
I believe that Nikon's WIC codec also provides the same rendering function, as well as at least one other 3rd party WIC codec (FastPictureViewer, which I use).
I only mention that because there is actually no fundamental reason why 3rd party apps cannot read Nikon's in camera settings and edits if they use Nikon's API. At least one does, maybe more.
I coached what I said about iMatch for a couple of reasons. First, I can't think of any reason iMatch would render a NEF file after it had been edited in Capture because Capture places an updated full resolution JPG in the NEF. It would only render a NEF if it needs to because the embedded JPG is smaller than the off line cache thumbnail it is configured to create. And secondly, the off line cache images are necessarily very low quality which makes an assessment of "accurate rendering" somewhat problematic and subject to interpretion.
#20. "RE: Wish list for NX3" In response to Reply # 10
Up at 8,000' in the Rockies, US
Over and over again I keep seeing references about CNX2 being built around Viveza as is posted above which I don’t think it is. CNX2 was built around U Point Technology that allows a small amount of what Vivenza does but I find a tremendous difference between CNX2 and the Viveza 2 Filter that I use with CS5. I have often asked reps of Nik Software to have the full version of Vivenza 2 fully integrated as a filter into CNX2 such as Color Efex Pro 3 for CNX2 that I have and use. I would buy a Viveza for CNX2 filter in a heart beat! I really enjoy working with CNX2 and don’t like to have to jump into CS5 to get the benefits of Viveza 2 as I had to do a couple of times today. I can wait for CNX3 but would like to see additional editing filters become available for use with CNX2. It would be a win-win situation for both CNX2 users and Nik Software! Jim
#21. "RE: Wish list for NX3" In response to Reply # 5
>In addition to new features mentioned above, I like to be >able to insert edit steps into an existing list, not just add >them at the end of the list. We had insert in Capture NX, but >it disappeared with Capture NX2.
Thanks Gary, I thought is was just me, I didn't realize we actually lost the feature!
There are certain "Auto" things I would like to save in a settings file (or as a default) so that it runs it afresh on the new image, not running the remembered auto setting, but rather re-running the "auto" setting.
For example: run Auto-distortion control for the image I am on. Or Auto-contrast in the LCH tool, or maybe Black-point/White-point auto-control.
#22. "RE: Wish list for NX3" In response to Reply # 19
San Jose, US
"I only mention that because there is actually no fundamental reason why 3rd party apps cannot read Nikon's in camera settings and edits if they use Nikon's API. At least one does, maybe more."
Despite my discussions with Rick on Adobe Business decisions, when I spoke with Nikon Techs a few months ago they told me that anyone who purchased their API could read the maker data. In some cases like Adobe which needs to work with a very wide selection of cameras and who had over 20 years of established code, doing so might not be in their best interests, but despite what ever flaws there might be in using the API it is available.
#23. "RE: Wish list for NX3" In response to Reply # 21
San Jose, US
While there is not an easy "insert edit steps" command, you can insert edit steps without just adding them to the end if the list. What you have to do is save edit steps below where you want to insert new edit steps. Delete those steps, add new steps and now add back the set you recently saved. Not what we are looking for but doable.
#24. "RE: Wish list for NX3" In response to Reply # 20
San Jose, US
I think I answered this in another thread, but CNX2 was not built around Viveza. first there was CNX based uopn U-Point Technology and it allowed us to add Color control points and vary those points by adjusting atribute handles like hue, saturation, etc. Then NIK/Nikon Produced CNX2 which added Selection points. Next a product called Vivenza was produced for Photoshop which did the things already in CNX and finally a newer version of Viveza was produced that added the functionality of CNX2 selection points that I understand also added 2 new atributes to selection points not in CNX2 (Structure and Shadows). So unless I am very much ill informed (I don't use Vivenza) I do not see how "U Point can do a very small amount of what Vivenza does" as all the U point controls are fully integrated in CNX2 and as such any filters such as color EFEX pRO 3 for CNX2 are also fully integrated and can be used selectively. They are all working in the NEF and do not create TIFFs to do their job.
#25. "RE: Wish list for NX3" In response to Reply # 22
Colorado Springs, US
Guys, we're talking about a "black box" that renders ( a la WIC) or processes the raw image (a la SDK). Again, placing this module in the middle of another application will create a situation where it becomes the limiting factor for performance. Whatever your thoughts are on NX2 (and I think it has many good attributes), it is not a speed demon nor does it excel at batching operations. Whatever program contained this conversion capability would have the same issues. We can pretend it's a viable solution, but it really isn't.
What aren't hidden are some of the settings information related to sharpening, picture controls, etc. You can see them in programs like Photome or EFIX, although Nikon doesn't actually document them anywhere. It's entirely possible that someone could choose to read those parameters and apply their own equivalent processing for them. It wouldn't be the same and quite honestly, there are quite a few people who don't even want it to happen (like me). In addition, doing it for a wide array of cameras and camera bodies would be a mess. I'm personally impressed that Adobe has come up with color profiles similar to the Nikon ones when set at their nominal settings. I don't personally use them, but that shows a fair amount of effort on their part. I can't see it extended further, however.
#26. "RE: Wish list for NX3" In response to Reply # 15
I originally wrote this wishlist item. The guys at CamerBits have put a great deal of effort into making PM work quite well as a browser/launcher front end for Capture NX2. When I added this item, I was not requesting that CNX2 start using or reading XMP files. I do not want sidecar files. Capture NX2 has some bad habits that make it difficult when working with PM. For example, Capture NX2 keeps files locked even if you have closed the editor window for that file. That makes it impossible for PM to update the metadata (including stars and colors). I've gotten into states where I have to close Capture NX2 completely in order to save metadata changes in PM. Also, PM has a nice facility for doing soft crops in the images. It would be great if Capture NX2 could utilize that setting. Perhaps it could see that there is a soft crop and add it as an edit step? At the very least, make sure to write the soft crop back out to the file if you save it in Capture NX2. I've lost lots of PM soft crops by saving changes in NX2. I guess my biggest request is to respect and preserve any additional information that other applications might save in the NEF, like PM's soft crops. It's okay to assume Nikon owns the NEF format, but it needs to play more nicely with others with respect to the metadata in the NEF files.
#27. "RE: Wish list for NX3" In response to Reply # 26 Mon 07-Feb-11 05:50 PM by nrothschild
I have PM configured such that CaptureNX does not lose soft crops. I have not tinkered with my PM settings in quite a while- maybe years - because any change effects how CNX, PM and iMatch more less try to talk to each other. Any time I do try to tinker with it, I have to spend a day or more figuring out the consequences .
I think the solution (and why I preserve soft crops) is that I have PM (and iMatch) set to favor XMP files before the NEF metadata. So CNX2 probably does lose the soft crops written to the NEF but PM doesn't care because it is looking at the XMP file first (assuming it exists and it should if you set PM to write it).
The downside to this is that while CNX2 reads and displays the color labels, ratings and ITPC metadata written by PM, PM can not recognize any changes made in CNX2 because I told PM to favor the XMP sidecar which PM CNX2 does not recognize. It's a one way street
And this is likely one of many reasons why a lot of people (like me) would, at least in principle, like to see CNX work with sidecars. Although in this case there is no guarantee that even if Nikon did update the sidecar that it would not obliterate things like soft crops just as it does in the NEF.
The two apps I have worked with that support side cars next to the NEF (PM and iMatch) both have some quite complex options that need to be set. I could never have figured out how to set up PM and iMatch without the good support that both vendors offer in their support sites (including forum searches of posts generated by prior users). I can't see Nikon offering that level of quality support and for that reason I'm not convinced that sidecars would be viable in the real world to solve the real world problems of those that advocate sidecars.
I don't know the entire history of PM but I suspect that much of what those XMP sidecar preferences are doing was not written day one; it probably evolved. It probably evolved as more users came in to the PM forums with different problems trying to integrate PM with various other apps. Nikon would have to do the same thing, and be reasonably fast providing updates. I've seen CameraBits issue updates only a day or two after a problem was reported (in the form of a beta release, as is their practice- they almost always have one of these beta releases available with their current patches and enhancements). That is a very different style of support than what I would expect from Nikon, and part of the reason I'm not optimistic that Nikon would even attempt it, much less make it work in the real world.
But I could be wrong; I was wrong once in... 1982 I think, about something
Edit: I agree that CNX2's file and folder locking is incredibly annoying . I too am always closing CNX2 so it stays out of the way of my browser work. Does ViewNX have the same problem? I don't use it enough to have tested that or run across it.
#28. "RE: Wish list for NX3" In response to Reply # 27
Neil, Your comparison of CameraBit's support compared to Nikon's software support is the primary reason why I wish Nikon would let Nik control Capture NX2 and beyond. Let the software company control and maintain the software. I can understand Nikon's desire to control the NEF file format and the access to the internal workings of the core that processes and renders them, but please figure out a way to be more nimble with the software and interoperate better with other applications.