View Full Version : Version Set
kevreid
March 26th, 2005, 08:14 PM
I've complained about this to Adobe and read posts here that people have had the same problem. Just checking to see if anyone has come up with a solution.
When editing using "standard edit", the image is often not recognized as part of the version set when saved. Instead one has to make a stack with the original and the edited version.........what a pain. This happens about 1/3 of the time. Why would this function work sometimes and other times not?
Thanks for an update.
brian
April 12th, 2005, 12:03 AM
I see you didn't get a reply. I am having the same problem as are others, but I have heard nothing from Adobe. Do you know if you had the problem before upgrading to 3.0.1? I am wondering if that is the problem. I tried just a few times, but couldn't reproduce the problem with 3.0.
Patricia Heere
April 12th, 2005, 12:41 AM
A version set must have the exact same name for each version. If you duplicate the original and have a "copy", it won't be recognized as a part of the original version. Version sets are different versions of an exact photo and file name. I have had that problem too and found out that it was because I did something "different" than saving as an exact copy of the file.
Pat
brian
April 12th, 2005, 11:40 AM
That is not the problem that I am having. I let PSE automatically name the file, and add its "edited-n" extension to the name. Sometimes it ends up in the version set and sometimes it doesn't all using the same procedure. When it is not in the version set the organizer doesn't recognize it at all. In order to see it I have to make Organizer search the directory. It then adds it as an additional file, not part of the version set. This makes things difficult because now that it is out of the version set I can't manually add it back in. Ends up making version sets useless.
I still am wondering if this problem came with 3.0.1.
Patricia Heere
April 12th, 2005, 01:50 PM
I was working yesterday with collaging some old photos and a couple of times I inadvertently hit the X at the top of the photo rather than going through file, save as. In those instances the photo did not go into a version set but was "thrown" into the organizer and I had to search it out. I don't think it is a bug with the program because when I carefully make sure that I am saving the original file (not a copy I might also have open on the screen at the same time) and use file, save as, I always get the command to add to a version set. If, for whatever reason, I don't get that option, I go back over the steps I have taken and can usually find where the file is different in some way and not a "version" of the actual original photo.
Pat
brian
April 12th, 2005, 03:26 PM
Pat - It seems that you are not having the version set problems that myself and others are having. Are you using 3.0 or have you installed 3.0.1?
Patricia Heere
April 12th, 2005, 05:27 PM
I'm pretty sure I am using 3. Nothing was in the addendum that I needed or wanted. Guess I'm lucky I thought that way. I still notice though that I have to be very careful that I am making a "version" of the original document. Sometimes I have copies open on the desktop for comparison but if you don't do that then maybe that add on did something to the program. I know that whenever windows updates my computer things go bonky all over the place. Maybe that happened with the update to PSE?? Matt K said the other day that he wasn't having a problem either. I wonder if he is using 3.1.
Pat
kevreid
April 12th, 2005, 06:43 PM
I did not do the upgrade to 3.1 so the problem exists in 3.0 as well.
All four means to save an image from the editor (close the window, save on tool bar, save from file drop down, save as from file drop down) all bring up the same menu. In that menu are the save options. One of those options is to save in the version set. It should not matter what the file name is, if the save to version set box is checked, it should save to the version set, right?
In my case, I don't change the file name anyway, I use the prompted version, _edited1 etc. I have gone back to see if any of the images that didn't save to version set had something strange in the file name.....nothing. They are consistent. It is an intermittent problem and I wish Adobe would get it together on this "bug".
Patricia Heere
April 12th, 2005, 08:34 PM
OK. I just tried to do what your last post said. Not sure I completely understood you but when I opened a file in the editor and made a couple of changes to it then tried to close it using the arrow or save as, I did not get the save in version set prompt. That is because at that point there was no version set. It does NOT work the same as it does in quick fix mode in the organizer. The editor does it differently. When I bring the file back in and make FURTHER changes to it, I get the version set prompt. If the version set prompt is greyed out, it means you are still saving the first version of the edit - thus no prompt to save in a set. If you make a duplicate of your original in the editor and work on that duplicate then save it in save as you will not get the prompt. If you then close your original you again will not get the prompt. The editor views these as two separate documents. If you bring a photo into the editor, duplicate it, close the original and work on the duplicate then save the duplicate, you will not get the version set prompt. Again, this is a separate document. This puts two photos into the organizer, one of which will be a version set provided you have made more than one edit to it. If you want, you can stack the original and the version set and when you unstack them you can further unstack the version set. This allows you to have different versions of a working file so you can go back and change things without having to redo the whole mess. I'm not sure I am explaining this well and understandably but the quick fix function in the organizer and the editor work differently in this instance. In quick fix you make a few quick adjustments to the "after" picture and if you are happy with those you click on close and get the prompt for a version set. When you are working in the standard edit mode there if often more than one edit (i.e. lots of layers) and those working with files like that would be using the save as command and getting the version set prompt for ongoing edits to the same photo.
I think the real problem with all of this is that there is no real documentation with PSE3. The integration of the Photoshop Album into the Photoshop editing package should have been more thoroughly explained. I don't think the version set problem in the editor is a bug, it is just hard to understand when it works differently in the organizer section.
Pat
Patricia Heere
April 12th, 2005, 09:51 PM
I just re-read you post again and need to clarify a point. Are you saying that when in the editor and you close a file you always get the version set prompt - no matter what? That is unusual. I only get the version set prompt when I am working in the editor if I use file - save as and then only when I am working in a second or third "version". Any other time it is greyed out and I can't check the box. Are you saying that you always get the prompt and then check the box (and see the checkmark) and your picture just goes somewhere? If the version set prompt is working you should be able to make a checkmark in the box and then you will get a message that if you save in a version set, etc etc to which you have to reply ok. Are you saying that you can do all these steps and it still won't save to the set? If so then we are talking about something different for sure.
Pat
kevreid
April 16th, 2005, 09:56 PM
Thanks for attempting to help with this issue Pat. I do wonder if we are talking about the same thing. When I say the version set prompt, it’s just part of the whole save box. It’s one option of several. Do you get a separate box just for saving the version set? If so, I’ve never seen that.
I generally only use the standard edit feature so let’s focus on that. In the editor, I do get the prompt regardless of how I ask it to save. I have never seen the option for version set grayed out. I always have it checked. I’m not making a duplicate or a copy when brought into the editor. That’s the huge advantage to PE3 and the organizer to me, the original image is never changed, it is always saved as a separate image. About 70% of the time, it’s saved as a version set, which means 30% of the time it’s not doing what it’s supposed to.
I’ve had it happen when saving as a jpeg as well as a PSD. It’s happened with the PSD layers left in tact and with the layers flattened. The only consistent thing I can pinpoint is when I have given the final click from the save prompt (which contains the version set check box), if it saves the file quickly, I know it will make a version set. If I get the hour glass for several seconds, it’s not going to.
Patricia Heere
April 17th, 2005, 12:00 AM
OK. I just tried what you said and didn't make a copy but used the original. I did both a save and save as and got the prompt to save as a version set. I have never encountered the problem you have wherein the program does not save as a version set when I have asked it to so maybe there is something in your particular software that is wrong. I wonder if it might be a memory thing? The biggest files I have are about 50mb and they take awhile but they do go into a version set. I did notice today that when I saved a psd as a jpeg for printing purposes that it would not give me a version set prompt because I had changed the extension but that is the only time I have not been able to save in a set. I don't know what, if anything we are doing differently.
Pat
kevreid
April 17th, 2005, 09:57 AM
Changing the extension should not prohibit you from saving to the version set.........that's kind of the point, it is still a version. As I said, I can't make the version set prompt gray out under any circumstance. It just sometimes doesn't do as told.........save as part of the version set even though the box is checked.
Patricia Heere
April 17th, 2005, 01:41 PM
I'm not sure what I am doing differently from you. I do sometimes get a greyed out checkbox. Today I am going to do a collage on a couple of old photos and I will see if I get either a greyed out box or save to a version set that saves another way. So far I haven't noticed that I had a problem. I think that the JPEG thing was a name change but not sure. Admittedly I'm not super proficient at all of this so maybe I just haven't gotten into something that won't save like it should. I'll let you know if I have any problems when I try to do this project today as I rather suspect it will involve quite a few layers and I like to try and save every 4 or 5 steps so I can re-create if I need to.
Pat
Patricia Heere
April 18th, 2005, 01:56 AM
I spent the whole day on a project and found out my computer works version sets in the following way.
If I make an edit and save as I get the version set command, check it and the computer saves the work but does not close the photo.
If I make an edit and save, I get the version set command, check it and the computer saves the work and closes the photo.
If I make a duplicate of my work so I can flatten it and print a trial copy, then try to save the duplicate I do not get the save as version set option - it is greyed out.
I must have saved dozens of times using all three methods and the computer was consistent in how it handled the commands. If I saved as a version it went to a version. If I did not get the option then it was because there was something different about the file (in this case the word copy).
I did notice that as my file got huge and I wanted to save as a version set , the computer processed very slowly and a couple of times I thought it had not taken the command and I gave it the command again which locked the computer up for awhile. I just installed 1G of RAM and it does help with moving things along but my processor is 3.2ghz and can only process large files just so fast.
The only thing I can think of that might be causing a sporadic problem is if the computer is having processing trouble.
I don't think it is an Adobe bug because I think my program is working the way it is supposed to unless there is something else I don't understand.
Pat
vBulletin® v3.7.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.