Aperture stacks

Is it possible to create a stack with photos taken at different times? I have photos of the same object taken on different occasions and would like them together for purposes of comparisons, just like is done in stacks. In other words; they are not in sequence.

Suggestion: put them in an Album. It's perfect for this sort of group-making. Flag all the Images you want to group, go to "Flagged", select all, "File➞New➞Album", name your Album, check "Add selected items to new Album", re-select all, un-flag them.
Alternatively, you could use a keyword and a Smart Album. Say, like Cézanne, you regularly go out and make a picture of a local landmark. Since you store your Images in Aperture, you could apply a keyword -- say, "Le Mont St. Victoire" -- to each of them. You create a Smart Album with Smart Settings that automatically filters your Library for all Images with the keyword "Le Mont St. Victoire". Whenever you import a new picture of your landmark you apply the keyword to it. Now every time you select that Smart Album, it automatically shows you all Images in your Library with that keyword.

Similar Messages

MobileMe galleries and Aperture stacks

I'm using MobileMe galleries to share and display some photos. It seems you can't upload images from within Aperture projects when they're stacked, at least only the images on the top of the stacks. I often want to upload a whole project, without unstacking, so I just want to selec-all and create a new album. But all I'm uploading are the top images of each stack. Does anyone know what the solution might be?
Many thanks,
Richard

Richard,
This is expected behavior when using Stacks. The purpose of a stack is to stack groups several images of which you only intend to use one, known as the pick.
One solution to allow you to keep your stacks but use all the images in MobileMe Gallery, is to create a Smart Album within the project and use this Smart Album for your MobileMe Gallery.
Smart Albums you create offer the option Ignore stack groupings by unchecking the "Include stack picks only" from the Smart Album criterion. If this option is deselected (the default for a Smart Album), then all images that meet the criteria for the Smart Album will be available in the Media pane, regardless of stack pick status.
See: Working with Stacks - http://support.apple.com/kb/HT2940
See: "Handling of Stacked Images" in Tips on Sharing with iLife - http://support.apple.com/kb/HT1056
Hope this helps

Aperture plugin copies previews, doesn't import or stack

Has anyone tried the option:
"For images which have been adjusted in Aperture, import full size previews from the Aperture Library (if they are available and up-to-date)."
     …and subsequently selecting…
"For Referenced images left in their original location, place version previews in the same folder as the master image to allow for automatic stacking"
When selecting these option, the plugin copies the master files into a hierarchy in finder, organized by date. Indeed, it does copy JPEG previews, if available.
Perhaps I'm missing something, but it doesn't import these JPEG files into the Lightroom catalog, nor does it automatically stack the preview with the master file.   The Aperture preview files end in _Aperture_preview.jpg. Or in other words, a preview for IMG_2924.CR2 would read IMG_2924_Aperture_preview.jpg

Good question, but difficult to answer. Yes. I completed a 40,000 image import with all options checked.
A couple of things though. The plugin will leave any "referenced" files where they are and copy any "managed" master files in your Aperture library to the location you specify. Previews will be copied to the corresponding old "referenced" master file location, or the new Lightroom location, depending on the source.
Only files with generated previews will be copied to Lightroom. I also saw several errors about previews being "skipped" because they were "not up-to-date". Could be that the preview just does not exist, or that it could not cope with the size of the preview. Just don't know, because Aperture does not make this easy to know what you do and do not have previews for. I strongly suggest you make a conscious decision to delete previews you do not want (makes the result messy), and create appropriate sized previews for what you do want to keep.    So I'd suggest you delete previews, then generate them for all that you need, based on filters. Strongly suggest creating full-resolution previews. You only get one shot, so why not have a full-sized preview.
And it does stack photos with previews. Remember, Lightroom will not stack Aperture stacks. Will only create keywords for them, if the option was chosen, but you can stack them later. Did not have the presence of mind to keyword all my photos that did or did not have previews, so I wasn't able to get a good idea of how accurate the plugin was in stacking previews. Suggest you keyword photos you create previews for so you have some method of validating the conversion afterward, or need to compare output from the error log.
Lightroom DOES NOT allow the use of stacks in the "collections" view. <sigh> So make sure you're using the "catalog" view.

Aperture - multiple versions

Hi all,
As you might know, Aperture easily gives one the possibility to create multiple versions of a photo, e.g. a B&W version, a color cropped version,... In Aperture these photos are grouped in a stack - but can be considered as independent photos.
When switching to the Pages (or Keynote) one has the possibility of easily importing images into a document through the media browser - with some reservations to the resolution though - see my other post:
http://discussions.apple.com/thread.jspa?threadID=936858&tstart=0.
However: the media browser only shows one version of the stack (the one that is the top one in the Aperture stack) - rather inconvenient at times.
Until now I only found 2 solutions that work through the media browser: re-order the photos inside the Aperture stack and quit-restart Pages to refresh the media browser; or unstack the images in Aperture such that the media browser (once refreshed) sees them as independent images.
Another way would be to export the versions one wishes to use as separate images - which at the same time bypasses the resolution issue with the media browser.
But again: this renders the media browser rather useless...
Any hints?
Many thanks in advance,
Christel
15" Powerbook G4 1GHz Mac OS X (10.4.9) ...saving for a 17" MacBook Pro

I am having the same problems, but with only one set of photos (same date only). And, although I love cheerleaders as much as the next guy, I don't need 250 versions!!!
Setup:
1. These photos are in a project containing 3800 photos.
2. The project has .CRW (D60) and .CR2 (1DMkII) files.
3. The problem files are .CR2 files (only for this date).
4. All other files from different dates don't create the same problem (.CRW or .CR2).
5. Aperture Libraray is on internal 300GB SATA drive (not on system drive).
What I tried:
1. I removed 3rd Party Ram (Apple blames all my problems on this, but everytime I remove it the problems persist. Another story).
2. Repaired Permissions.
3. Rebooted.
4. I created a new user. Still have the same problems.
5. Yes, turning off 'Create New Version.....' stops this, but I like having new versions for compare.
Anyone with similar setups and issues?? Any fixes?? Is Apple still working out a way for us 6600 card owners to upgrade??
Narvon
Quad 2.5, 6600, 4GB ram Mac OS X (10.4.5)

Comparing counts after conversion: iPhoto to Aperture

Well, I just finished a major conversion from iPhoto to Aperture. 47,000 photos and videos in a 303 gigabyte iPhoto Library. It was a long and winding road, and I learned a lot about how to compare counts of photos and videos between iPhoto and Aperture. I hope this information helps someone spend a few less hours on the task than I had to.
After an iPhoto-Aperture library conversion, the first check you'll probably want to do, to confirm all went well, is to compare the number of photos and/or videos reported from each application. You'll probably compare the overall total, and/or the total for important subgroups (say, all photos keyworded "family".) Here are some things to be aware of:
- You can run iPhoto and Aperture at the same time, even if Aperture is referencing the photos in their iPhoto library locations. This can make various count comparisons easy. Sometimes though I found the apps suddenly bogged down, and I had to quit one of the two to recover (this was on a 4GB 2.93 GHz iMac).
- Whether your Aperture "stacks" are open or closed affects the photo count reported by Aperture. If you edit an original photo in iPhoto, in the end all you see is edited photo, the original is preserved but tucked away unseen. In terms of a photo count, you still have just one photo. When this photo is imported into Aperture, it comes in as a 2-photo stack (original & edited). If you stacks are closed, your counts should match; if your stacks are open, Aperture will be higher.
- Photos "hidden" in iPhoto come in as "rejects" in Aperture (i.e. a rating of "X" on a scale of X,1,2,3,4 or 5 stars). When the search box in Aperture says "Showing All," you are including the rejects in the count (that is, the count appearing at the bottom of the window in browser mode). If it says "Unrated or better," the rejects are not being counted. Make sure you are consistently including or excluding hidden/rejects when comparing numbers.
- Formats supported by iPhoto but not by Aperture. I have some old (pre-OS X) screenshots in PICT format. Viewable just fine in iPhoto, but they do not get imported into Aperture.
- Some video formats (in my case, MPEG1 Muxed) are imported into Aperture, but are not playable within Aperture, and do not show up if you filter on File Type = Video (that last part seems just plain wrong behavior).
- Every count I saw in Aperture included videos, even when the count was labeled "Photos" (e.g. "23,434 Photos"—you'll see this under Projects, if you group by folder)
- I did have a few items that were *just plain skipped*, with no error dialog, by the import. Scary. But in every case, there was evidence of a problem in iPhoto: I would see a fine thumbnail, but if I tried to open the photo or video, I'd see a gray exclamation point where the photo/video should appear. In every case I successfully found an valid original (in the iPhoto "Originals" folder) and moved it manually into Aperture. Problem is, are you going to try and view every photo you have in iPhoto, checking for exclamation points? I tracked my missing photos/videos down by painstakingly comparing counts in matching slices of time (say, August 2006) in iPhoto and Aperture. When I narrowed a count discrepancy to a set of 100 pics or so, I compared thumbnails between the 2 apps until I found the item missing from Aperture. Not fun.
I hope this helps somebody. Now that I've made the switch, I have a love-hate relationship with Aperture. Mostly love. But that is a separate post. Aperture is also my first Pro app from Apple, and iPhoto and Aperture make a fascinating case study in contrasting user interface design (freedom from choice vs. options galore). Also a topic for another post.
Mike M

Hey, thanks for the comprehensive post. It helped me quite a bit and probably saved me a lot of time; I'm sure it did the same to a lot of people who didn't have an account here as well.

Is it possible to create Panoramic photos in Aperture

I know it is possible to create Panoramic photos in PS, but was wondering if it is also possibel in Aperture.

Imho ( ) it is worth understanding the difference between Aperture and programs like it (LR, etc.), and Photoshop. The difference is compositing. PS and other Graphics programs are built from the ground up as compositors. Aperture and its cousins are Digital Asset Managers and digital photo development tools. You use Aperture to manage your collection of digital photos, and to make any one photo into the best version possible for whatever use you have. Then you export your digital photos from Aperture, and use them in graphics programs to create new graphics.
In general, if you are combining things (text, geometric primitives, multiple graphic elements, etc.), you use a graphics program; if you are optimizing a photo for a particular use, you can do it using Aperture.
For panoramas, I import the photos I'm going to use into Aperture, Stack them and add a color label (so I can see at a glance that these Images are part of that kind of series), check the WB, the export them to a temporary Finder folder. I use Hugin to open all the exported files and stitch them together. Then I import the panorama I created using Hugin and place it as the Stack Pick of the Stack, and make whatever additional adjustments I want for the use I have for the panorama.
Message was edited by: Kirby Krieger

AppleScript Bug: Duplicating stacked images to albums

for anyone else using AppleScript, I encountered this bug a couple of nights ago. I've reported it to Apple.
14-Feb-2009 02:14 AM Gregory Charles Rivers:
Summary:
The Aperture/AppleScript "Duplicate" command when used to add stacked images to albums does not work as expected.
(1) when stacked images are successfully added to the target album, they are added as masters rather than simple album items.
(2) if the source project is not selected in the Inspector, stacked images will not be added to the target album.
(3) "Duplicate" is not a suitable command for adding objects to albums and confuses scriptors. an additional "Add" or "Assign" command should be created expressly for this purpose.
Steps to Reproduce:
* begin of steps to reproduce *
PROBLEM #1
1. [APERTURE] import 3 masters into a new project called "Gregory"
2. [SCRIPT] in a script editor, get the new project's ID:
id of every project whose name is "Gregory"
-> "UkRHKvb/RfmZ8H+Jn/pxRA"
3. [SCRIPT] get a list of the images in the new project:
every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
-> a list of 3 objects
4. [APERTURE] create two albums within the project:
-> "Album 1" and "Album 2"
5. [APERTURE] stack the first two images.
6. [SCRIPT] add only the first image to "Album 1"
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
duplicate theImages's first item to album "Album 1" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
-> the stack that image 1 is a member of, is added to the album, but it's not a normal 'linked' album item.
7. [APERTURE] delete the image from "Album 1" by selecting the image and pressing "Delete" on the keyboard.
-> a warning is sounded but nothing happens. with normal album images, they're simply removed from the album.
-> "Remove from album" is greyed out in the Images menu.
8. [APERTURE] select the first image of the stack within the album and press Command-Delete.
-> a dialog is presented confirming that the images inside the album are masters.
confirm.
-> the image is removed from the album, and from the project!
9. [APERTURE] select the remaining image and press Delete.
-> the image is removed from the album without affecting the master as would normally be expected.
(the work-around for removing 'masters' from the album is to unstack them after which they become 'normal' album items again.)
PROBLEM #2
10. [APERTURE] import the first master again, back into the same "Gregory" project.
-> we now have 3 masters in the project.
11. [APERTURE] stack the first two images.
12. [APERTURE] within project "Gregory", select "Album 2".
13. [SCRIPT] add all 3 images to "Album 1" (while "Album 2" is still selected within Aperture).
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
repeat with i in theImages
duplicate i to album "Album 1" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
end repeat
-> only the unstacked image is added to the album.
14. [APERTURE] select the project "Gregory".
15. [SCRIPT] run the script again.
copy every image version of project id "UkRHKvb/RfmZ8H+Jn/pxRA" to theImages
repeat with i in theImages
duplicate i to album "Album 1" of subfolder "nested" of project id "UkRHKvb/RfmZ8H+Jn/pxRA"
end repeat
-> all of the images are added to the album.
-> the stacked images are still 'masters' rather than simply album items.
PROBLEM #3
the "Duplicate" command should be used for adding images as links to objects such as albums. the use of the "Duplicate" term for this action leads to confusion. an additional "Add" or "Assign" command should be created for this specific purpose.
* end of steps to reproduce *
Expected Results:
whether stacked or not, images added to albums should be simple linked items, not masters, and which when deleted by pressing Delete simply disappear from the album without affecting the true masters.
Actual Results:
(1) stacked images added to albums are added as masters instead of linked items.
(2) stacked images cannot be added to albums if their containing projects are not selected in the Projects inspector.
(3) the use of the term "Duplicate" when applied to adding items to albums is confusing because the images aren't actually duplicated.
Regression:
Unstack all images before running any script that adds stacked images to albums.

I have noticed behavior with drag-and-drop working anomalously different for me than as reported by others. It has not yet been problematic, but definitely anomalous.
It sounds like the Aperture team should forget features improvements for a while and focus on stability.
-Allen

Aperture 2.1 / Photshop bug?

This is a weird one. When I select a RAW image and a version is created, I make my adjustments and send it to be edited in Photoshop (in this case, Elements 4). I do my touch-ups and save the file. The new version appears in the Aperture stack for that photo, but the image is only showing one of the previous layers I created when in Photoshop and not the final flattened version. I flatten the image before I save it, so there is no more selection or any other layer but the background. If I tell Aperture to load the version into Photoshop, it looks fine. But in Aperture's browser and preview windows, it looks like a layer I created from a selection and everything else (that wasn't selected) is black.
Is this a bug or am I doing something wrong?
Matt

Matt-
PS Elements is at version 6 now. First thing is to upgrade. Also, I don't know about PSE but with PSCS3 and OS 10.5.2 Adobe has said that problems exist that would not be resolved until OS 10.5.3 at the earliest. 10.5.3 is out now and at least some issues are fixed.
I recommend that you update to PSE v6 and OS 10.5.3.
Good luck!
-Allen Wicks

IPhoto Pictures Stuck in Aperture

I keep getting a message when trying to delete some photos in iPhoto:
This photo is in an Aperture stack and cannot be put into the iPhoto Trash. Use Aperture to delete this photo.
I have removed all the photos from Aperture, including emptying the Aperture trash. So, not sure why I'm getting this message if there aren't any photos in the Aperture library??? Any ideas would be great, thank you.

1. make a backup of your iPhoto library folder or the 'Originals' folder within.
2. paste this script into Script Editor and save it as an Application.
3. in the Finder, drop the 'Originals' folder from within the iPhoto library onto the new application; what we call a Droplet. the Finder will replace all aliases within the folder and nested folders with their original image files.
the script:
-- begin
to open theFolders
   repeat with i from 1 to theFolders's length
      copy theFolders's item i to theFolder
      if (theFolder as string) ends with ":" then
         replaceWithOriginal(theFolder)
      end if
   end repeat
   return
end open
to replaceWithOriginal(theFolder)
   tell application "Finder"
      set containedItems to every alias file of theFolder
      repeat with i from 1 to containedItems's length
         copy containedItems's item i to theAlias
         try
            copy theAlias's original item to theOriginal
            duplicate theOriginal to theAlias's container with replacing
         on error number -1728 -- orphaned alias
            delete theAlias
         end try
      end repeat
      set containedFolders to every folder of theFolder
      repeat with i from 1 to containedFolders's length
         replaceWithOriginal(containedFolders's item i) of me
      end repeat
   end tell
end replaceWithOriginal
-- end

Auto-Stack stacks erractically

I have problems with auto-stack -- the stacks are more-or-less random. Unrelated photos are grouped, yet ones take only a few seconds apart are not stacked. This seems consistent every time I've tried it. Adjusting the time slider just ends up with a very slow response. The latest project I'm trying it with has 1600 pictures from 3 different cameras, but even continuous sequences from the same one are messed up. I've tried it on reduced selections -- same problems.
I've given up with it and do it all manually now.
Anybody got it working properly?
G5 dual 1.8 GHz Mac OS X (10.4.4) Olympus E-1, E-300 (+ Canon Digital Ixus V2)

I noticed with my Canon XT that there is a bug in Aperture stacking when you first connect the camera up. Perhaps this is causing your problems as well. In my case when the camera is hooked up, and aperture automatically goes to the import mode, all photos on the camera have the same date and time, so the stacking doesn't work properly. What I do to work around it is cancel the import mode, and then turn the import mode on again (click on that arrow in top left corner). This causes all the images to have the correct time in the import window, and stacking works correctly.

Several questions about migrating from iPhoto to Aperture

I'm currently a heavy iPhoto user and am looking into migrating to Aperture. Can anyone give me a sense of what I to expect if/when I make this switch?
Here are several particular things I'm wondering about:
1. iPhoto works great as a computerized photo album for casual browsing. (I can see a page of different events with mouse-over previews, plus I can hide poorer shots so that I can just view the highlights.) Will Aperture be a step back in this department? If so, is it possible to "share" my Aperture photos with iPhoto without keeping two parallel copies of everything?
2. When I import an edited photo from iPhoto to Aperture, will the iPhoto "original" become the Aperture "original" and the iPhoto "modified" become the Aperture "modified? Is the same true if I export an edited photo from Aperture to iPhoto?
3. Does Aperture have an analog for "hidden" photos? I currently mark my best shot from a series by hiding the rest. Will I lose this marking if I migrate to Aperture or is there a way to preserve it?
4. I currently have a number of short video clips (taken with my point-and-shoot's video feature) mixed in with the iPhoto albums. (iPhoto really does let me keep everything organized in one place!) If I understand correctly, Aperture won't let me store these in my Aperture library alongside the still-photos of the same subjects. Is this correct? If so, how have other people handled this?
5. Do EXIF tags get re-read upon import from iPhoto to Aperture? I've got a number of iPhoto files which I've retroactively geotagged with HoudahGeo. Will the tagging be lost (since iPhoto is not currently aware of the geotagging as the EXIF tags have not been re-read)... or will Aperture now recognize this metadata?
6. If worst-comes-to-worst and I give up on Aperture after a few months, how painful will it be to un-migrate back to iPhoto? More importantly, what album metada (e.g. events, albums, ratings, tags, notes, dates, hidden-ness, links between original and modified versions of a photo, iWeb references, etc.) will be lost? In other words, if I were to import everything from iPhoto to Aperture, wipe my iPhoto library clean, and then export everything back from Aperture to iPhoto, what information will have been destroyed?
Thanks in advance for any answers to this long list of questions!

Here are several observations (read: warnings) in case anyone else is considering migrating a significant iPhoto library to Aperture...
A) Pictures marked as "hidden" appear to be silently skipped over (along with video clips, as was expected) when importing an iPhoto library to Aperture. They do not appear in the relevant Aperture project regardless of the filtering options.
B) Both iPhoto originals and modifieds are imported. The former are given the keyword "iPhoto original" and the latter are given the keyword "iPhoto modified." Each pair of photos is put into a single Aperture "stack." Both photos are given the same tags/ratings (so, for example, the un-rotated, uncropped, poorly balanced original will show up alongside the nice clean "modified" if you were to filter for 5-star images), and both files are given identical "version names" (equal to the "name field" in iPhoto). In most cases the original -- not the modified version -- was set as the stack's "pick" and displayed when the stack was collapsed. *Significantly, I could find no way of creating a view in Aperture that showed one copy of each picture, with the "iphoto modified" version displayed for photos that had been modified in iPhoto and the original version displayed for photos that had never been modified in iPhoto!* (This is, of course, the way they are shown in iPhoto.)
C) My understanding of "stacks" is that they are designed to help organize multiple "tries" at the same shot (e.g., I want to make sure that nobody's eyes are closed in the group photo, so I press the shutter six times in quick succession -- I'm going to pick a "best" one will be mostly interested in that shot from then on). This is a fantastic idea! However things get confusing if you are already using stacks to track original and modified versions (as described above)... particularly if your stack should contain six pictures plus original versions of each. Plus, as I mentioned, the "original" version is usually the default "pick" in each stack.
D) After import, "iPhoto original" versions of portrait photos appear un-rotated. Normally, my cameras (including a Nikon D80, an iPhone, and others) mark photos' orientations and they are automatically displayed in the correct orientation. Aperture appears to consider this auto-rotation an iPhoto edit and helpfully displays the "iPhoto original" always in landscape.
E) Aperture may incorrectly import events whose names contain a "/" or a ".", so if your event names contain dates, rewrite them with "-"s before importing to Aperture.
F) Aperture does have a rough mouse-over-the-icon-to-flip-through view, similar to the "events" pane in iPhoto... although you will lose your choice of which photo serves as the default icon for each event when you import your library from iPhoto, and you cannot "hide" photos from appearing in the flip-through as you can with iPhoto.
G) Perhaps it's my inexperience with the program, but I could find no way to sort the project list by date (vs. alphabetically), nor could I find any way to make a correction to a single photo's date/time.
As a bottom line, remember that Aperture is definitely not "iPhoto Plus." It lacks a number of iPhoto's features, but in exchange gives you a number of really slick tools aimed at streamlining a digital photography workflow.
I'd also encourage people to think very carefully before moving a large, well-organized iPhoto library to Aperture. You may lose a fair amount of information, and the result will take a lot of work to "make pretty" again. It does look like a nice program, though. Are you ready to relegate all of your existing pictures to an iPhoto "pre-history" and start over with a blank -- but much fancier -- slate in Aperture?

Moving a method down the call stack

This is partially a blazeds question as well, which I have already inquired about there.
My situation is that I have a consumer.subscribe followed by the rpc, followed by the consumer expected to handle the results of the rpc. What seems to be happening is a race condition between the subscribe and the rpc call - with the results being returned back before some of teh consumers have finished subscribing. This is all being handled in one method. For the most part, it needs to be encapsulated like this because we're using the parsley IoC container. By creating a new context on a button click, it automatically instantiates and initalizes the consumers. A retrievedataevent is then fired straight away.
Is there anyway around this? I noticed that if i create a Timer and set it to 1 millisecond, it somehow fixes itself. Does timer somehow drop the current method down the callstack? Or deprioritize it?
Thanks in advance. I'm banging my head against the wall here

This is the way that Aperture works by design - you just need to get comfortable with album picks, every album can have a different album pick from the same stack, it will be the image that shows up at when the stack is closed.
These may help
[Aperture Organization|http://photo.rwboyer.com/2008/07/apple-aperture-21-organization>
[Aperture Stacks and Albums|http://photo.rwboyer.com/2008/09/aperture-2-organization-tip-more-on-sta cks-and-albums>
[Aperture Album picks and image versions|http://photo.rwboyer.com/2008/12/aperture-2-quick-tip-album-picks-and- image-versions>
Maybe even this that explains how Aperture stacks work vs. Lightroom stacks
[Aperture vs Lightroom stacks|http://photo.rwboyer.com/2008/10/aperture2-vs-lightroom2-stacks>
RB

How can I reorder the stack with the best version on top of the stack?

when i stack the original appears to be on top. i would like the best version to be on top-
say for example the one rated with one star. can i do this?

Yes this is really easy - this is called the stack pick and you can choose it either in the stack menu or using the command-\ short cut. You can also choose a different pick for each and every album the stack is in (say a black and white version or a cropped version) using the stack menu or the shift-command-\ shortcut.
There are also short cut keys and menu options to promote or demote items within the stack order.
Also check out stack mode when looking at your images.
Check this out:
[Aperture Stack Mode|http://photo.rwboyer.com/2008/09/17/aperture-quick-tip-stack-mode>
There is a bunch of other stuff related under Aperture workflow as well.
RB

Syncing to iPad copies Master

I upgraded from iPhoto to Aperture recently. All seems good, and I'm getting to grips with the new application. Once problem I'm having is syncing photos to my iPad. I've created Albums in Aperture which are synchronised with my iPad. This works OK except that for some of the photos the original/Master photo as well as the edited/Version are copied to the iPad. I would only like the Version to be copied.
Am I doing something wrong? Is there a setting in Aperture which is incorrect if both Master and Version of the same photo is being synchronised to my iPad?
Thanks for any help you can offer. I'm using latest versions of Aperture, iTunes and iOS.

I upgraded from iPhoto to Aperture recently.
You seem to have migrated too early. You imported your edited iPhoto images as two separate images - one image for the original master, one for the edited version. Aperture stacks them at import, but does not create proper master-version pairs. This is wasteful, since you need twice the amount of storage, and if you unstack them, as Thomas suggests, the last connection will be lost.
If you did not yet invest too much work into the the transit from iPhoto, and if you have many duplicate iPhoto images, you might consider to do the import again. Since last week iPhoto and Aperture have compatible libraries, and if you import an iPhoto 9.3 library into Aperture 3.3, you will no longer have duplicate images for version and original. This will save space and make things easier in the long run.
Am I doing something wrong? Is there a setting in Aperture which is incorrect if both Master and Version of the same photo is being synchronised to my iPad?
What kind of albums are you syncing? If they are smart albums, did you check the "Stack Picks only" option?
Regards
Léonie

Delete a version --- what am I doing wrong?

Hello everyone. I'm using Aperture 1.5.1. I have a NEF file that I sent to Photoshop Elements 4.0 as a TIFF to do some editing. This was done through the 'Open with External Editor' command. Upon returning to Aperture, I found the file as edited stacked to the NEF. NO problems with any of that.
However, I decided I wanted to delete the TIFF file. So, I select File -> Delete Version. (or ctrl click -> Delete Version)
When I do that, I get a screen pop that is advising that I am about to Delete Master Image and All Versions.
I am assuming that this has something to do with the 'Open with External Editor' action that I did because I do not get this pop when I do Delete Version on an image that I manually created a Version on. It just deletes the version as usual.
What am I missing?? How is this supposed to work and how can I delete this 'Open with External Editor' version without deleting the master??
Regards,
Tom

Hi pvonk,
Gary2010 is right. I'll elaborate a bit further...
Your original master is a NEF. When you import it into Aperture you see the first version as a "window" of adjustments over the NEF. Originally, it has no adjustments so the window is "clear." When you adjust the version, you are seeing the NEF through the "window" of adjustments. If you create additional versions, then you are seeing the NEF through additional "windows."
Now, when you choose the command, "Open with External Editor," Aperture cannot send the NEF Master to the external editor, so it has to make a TIF file (or a PSD file if you have chosen that in Preferences). This isn't the same as the "window" of adjustment instructions, so it is not a Version in the same sense. It is actually a NEW PHYSICAL TIF (or PSD) file, and a new Master. The file is placed in the Aperture Library and becomes a Managed, even if your original NEF is Referenced. Any adjustments applied to the Version you clicked on when you chose the "Open with External Editor" command are applied to the new file, and it is opened in the external editor.
The confusion comes because Aperture stacks the new Master TIF file with the NEF file and its Versions. There is a difference though. The new file has the target badge showing it is an externally edited file (which I'm sure you've noticed).
However, make note of this: If you make additional Versions of the original NEF, they are stacked with the NEF, but also surrounded by a lighter gray box; sort of a stack within a stack. The lighter gray box shows you the Versions that all belong to one Master. You will notice that the new TIF file is not inside the lighter gray box. It is stacked together with the original NEF like any other Master file could be if you chose to stack them together. Aperture just figures that you want them stacked together because they are so similar.
I hope I explained this well enough. I also found it confusing at first. You've already crossed the first big hurdle of realizing that you are seeing a first Version and not the Master when you import an image.
- Karen

Aperture stacks

Similar Messages

Maybe you are looking for