My experience matches that of the OP. When creating a new version and changing the name to one that already exists, NX offers no option to overwrite. Instead it pops up a message saying that name already exists, dismissing the message simply returns me to New Version dialog where presumably it wants a new name entered.
While we're on the topic of extra steps, I'd still find it aggravating to type in the name of a version I just opened or created. A new dropdown menu option for Update_Existing_Version would be nice, especially if it expands to reveal a list of your named versions. Icing on the cake would be if NX remembered the most recently opened version (in the current NX session) and pre-selected that name in the list.
I guess you have never used software that has version control built in. What Nikon is doing here is common in that world and is considered a best practice. They are protecting the versions inside the NEF file. You can do what you want to the NEF file. The intent is not to make it fool-proof or difficult.
Is it killing you guys to leave the intermediate versions in there?
But, if you makes you feel better to complain.....
Yes I have used software with versioning capabilities, adn not all of tehm prevent uou from "updateing" a version or force you to create a new one just to update an existing one.
Cluttering up a file with unneeded versions is a waste, confusing, and potentially can cause other errors. I name my versions with something meaningful, so when I want to cahnge one, I don't necessarily want to rename it.
When determines what is a "best practice"? Seems to me the customers should.
As for your last comment, I would only say I think it is uncalled for.
I started this thread to ask how to do something and express my opinion about what might work better. Others have thought it worthwhile to comment as well. Whether Nik or Nikon want to do anything about that is up to them.
If the best practice police want to target me, be my guest. But it was also perhaps a best practice of Nikonians not to have a separate forum for Capture NX and Nikon software, yet that seems to have worked out OK once the customer's wishes were heard.
A little touchy today, aren't we? Many version control software packages don't let you delete or directly change intermediate versions. At least not unless you are the person running the server that has the master program running on it. Even then it is an exception process.
This is quite normal in both document creation/editing and software development environments.
I guess I just don't see the big deal. I've been using Capture NX2 for a few weeks now and I didn't think twice about this particular behavior. Maybe I am just used to concept and appreciate the intent. There are plenty of things I don't like about how Capture NX2 does things, but I am learning more about how it works and don't find it to be a large enough bother to get excited about it. Pretty soon those things I don't like will be second nature and won't be an issue at all.
I've tried to explain why the software works the way it does and how it is a tried and true concept. I think it is a good idea and you hate it. It looks like our votes cancel each other out. Maybe you can figure out a way for it work for you too.
After you're used Capture NX for a few years, like I have, maybe you will appreciate the limitations and frustrations of dealing with it. Conventional ways of doing things don't mean anything, other than limiting thinking of the best way to do something.
As for "touchy", I think that is an entirely inappropriate comment.
Get a thicker skin. You are way too sensitive for the Internet.
So far I have read about the Capture NX 2 version control features in three respected books (I purchased all three) about the software. The three books speak highly of the feature and do not suggest there are any negatives to it. Yes, these are books about the software so I expect them to not be negative. But not every feature is praised either. The positives mentioned actually make sense.
I've seen a lot of complaints about various aspects of Capture NX 2 all over the Internet. It's astounding how many complaints there are! But this is the first time I have seen the version control feature dispraised like this.
"Best practices" don't get to be "best practices" because they don't work or are stupid. I understand you don't like the feature. "Best" here is relative. As I pointed out earlier, I think the feature is a positive and so do a lot of other people along with Nikon and probably Nik software. With a good naming convention I am sure you can work around this "feature".
Wed 10-Feb-10 03:07 AM | edited Wed 10-Feb-10 03:14 AM by James23p
Well I use NX2 all the time but to be honest I have never used the version function and if I had I did by accident!
But lets stay on target here we all have functions we like and dislike. I love NX2 and it is my main RAW editor thus my embarresment for not knowing the version function. But we need to not make this personal. Personal attacks are against the ToU.
Now if someone can in a nutshell explain the version function and what it is used for. I just upload my images to ViewNX, open them in NX2 and edit them and convert to JPEG if needed and print or send to the photofinishers.
PS Is the version function the drop down menu that I use to revert to the original NEF and the various versions I saved or were working on?
Wed 10-Feb-10 05:13 AM | edited Wed 10-Feb-10 05:14 AM by James23p
Ah so I was using it! I guess for me an overwrite function is not a must since it seems to work for me even if unknowingly! I do shoot RAW so I do tend to work several versions for different purposes ie BW, Sepia etc.
With versioning, you can make a series of edits to the image, save it as a version in the file, and then make additional or completely different edits, and save them in the same file. You can then easily switch between versions without having to redo your work. You could, for instance, have and color and a B&W version of the same image, all saved in the same NEF file. I don't know what the limit is on the number of versions, but probably more that I'll ever use.
And yes, the version menu is at the top of the edit list.