Skip navigation

Hi, when you export versions to other libraries in Aperture, can you not edit them back to their original state?

374 Views 8 Replies Latest reply: Apr 19, 2013 9:53 AM by phosgraphis RSS
1Becky1 Calculating status...
Currently Being Moderated
Apr 18, 2013 12:59 PM

Hi, when you export versions to other libraries in Aperture, can you not edit them back to their original state?

 

I have 3 libraries - one of them has my orignals, then I have an edit library and then a completed one. After I finish editing my photos, I import them into my completed library, but now I can't get them back to thier orignal state or change the editing I have already done in the completed library? It has imported the edited photos as if they are now in their orignal state. There is still a bit of touching up I would like to do when I relook at them but I will have to go back to the original photo in a different library to do this now unless someone can help me do it in the completed library?

 

Thanks.

MacBook Pro (13-inch, Mid 2012), OS X Mountain Lion (10.8.3)
  • léonie Level 8 Level 8 (46,355 points)

    How did you "export versions to other libraries in Aperture"?

     

    If you export your edited images as new Aperture library, you shouls always be able to create a new version from the original image file.

     

    But if you exported your edited versions as plain image fiels, not as a part of an Aperture library, there will be no hope to undo the edits. The editing has been buned in on export.

     

    Regards

    Léonie

  • Frank Caggiano Level 7 Level 7 (22,755 points)

    Hi, when you export versions to other libraries in Aperture, can you not edit them back to their original state?

    No once an image is exported it looses all connection to Aperture. It becomes just one more file on your HD.

     

    Your workflow sounds odd to say the least. Why do you think you need three Aperture libraries, originals, edit and completed?

  • phosgraphis Level 2 Level 2 (285 points)

    Based on your description, what you are doing sounds pretty complicated, and maybe even unnecessary. Perhaps some explanation of why you are using three different libraries would help.

     

    Again, based on your description, it seems like you could be doing everything you describe in a single libary without all the exporting and importing, which inevitably will lead to problems.

     

    Please help us out with a little more information, and your level of expertise with Aperture.

  • phosgraphis Level 2 Level 2 (285 points)

    OK, lots going on here.

     

    re: The "expert" suggestion to have multiple libraries...

    If Aperture is "running slow" that will usually be caused by underpowered hardware, not the size of the library. Regardless, having multiple libraries may make sense if you have totally different genres of photography, e.g., wedding and sports, and want to keep them separate. But using separate libraries for organizing the state of processing your photos is certainly not recommended. As you have discovered, this can lead to problems.

     

    Use one library for all your images, and keep track of the various states of processing the images using Apertures many useful methods...labels, albums, keywords, etc.

     

    re: "I have a lot of photos!":

    How many is "lots"? Are they RAW, JPEG, or both? You need to read up on "managed" versus "referenced" libraries. If you have many thousands of RAW+JPEG photos and are using a managed library then, yes, your library can become pretty large and unwieldy, especially when it comes to backups.

     

    re: "traveling a lot"

    Do you use a separate laptop for traveling? And keep your master library on a desktop? If so, then you need to become familiar with "Export ... as new library" and "Import Library". These tools provide an excellent way to maintain a master library on your desktop, travel with a subset of that library on your laptop, and merge the library used during travels with your main library upon return.

     

    If you don't have separate computers, then I'm not sure where traveling enters into the picture. If you are actually having performance issues, then that needs to be addressed separately. But keeping your photo library organized the way you are currently doing it won't solve anything in the long run.

     

    The Aperture user manual is a good place to get started with these concepts if you already haven't referenced it. And a couple of discussions here on the forum that also might be of help:

    https://discussions.apple.com/message/16003277#16003277

    https://discussions.apple.com/message/11259701#11259701

  • Frank Caggiano Level 7 Level 7 (22,755 points)

    If you really want to do something like this you will need to export the images as a new library and then import that library into whichever library you want the images in.

     

    (Assume o1 is the original library, e1 is the edit library and f1 is the final library)

     

    So for example if you import into  o1 you would then select the images you want to edit export those as a new library and then import that new library into e1. Once you were done editing you would again select the images export them as a new library and import that library into f1.

     

    But this workflow is overly complicated, and dangerous to your images and makes it impossible to keep track of anything.

     

    It would be best if you were to explain your situation, include your hardware setup (system and any external disks) and what your requirements are.

     

    I'm sure a cleaner more robust workflow can be suggested.

     

    regards

  • phosgraphis Level 2 Level 2 (285 points)

    I think I will go back to the one library that you have all suggested and make the most of the folders and albums that aperture offers - this way I can keep better track of all my photos and will be able to conitinue to edit them if I need too. (It was an apple genius in the apple store that suggesed mulitple libraries to me.)

    That would certainly seem the way to go for your situation. 20000 photos isn't a lot, relatively speaking. If you are using fairly recent hardware you shouldn't expect any performance issues because of the number of photos (there may be other reasons for performance issues, though). There are some advantages to using a referenced library, so it would be worth the time to understand the differences.

     

    Glad to help.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.