Aperture 3 "processing"

When I launch aperture 3 it starts "processing" one of the rolls and never stops. I have restarted and reinstalled the software. Once the processing starts, aperture stops responding. Any ideas?

Have you tried the options listed on the Basic Troubleshooting page?
http://support.apple.com/kb/HT3805

Similar Messages

Selection in Aperture , processing in ACR ( Adobe Camera Raw )

I'm trying to figure out if there is some way to see my ratings from Aperture in finder - on original master files.
I understand "holy raw" policy and I have been following the threads about painfull renaming techniques
( obvious workarounds ).
Seeing my in Aperture rated raw files in finder is crucial for me because I want to use Adobe Camera Raw for processing .
I might also use DPP or Capture One for this in some situations.
(I prefere Aperture for selection work , I love loupe )
So is there som simple way to do it ?
One way would be for example if you could give a
color label ( visible in finder ) to selected master files .
That would be fine for me .
And as I understand wouldn't make any changes to the original file ( so it would stay "untouched" ).
Thanks for any suggestions.

Just re-read your first post and realised that you want to apply a Finder label to every RAW file based on rating. This is doable, but would require someone to write an app or script, like Adam Tow's app that moves metadata between Aperture and iView.
The rating for each image is held in the OriginalVersionInfo.apversion file next to each RAW file:
<key>mainRating</key>
<integer>0</integer>
If you are only grading into two categories and Bridge is doing what you want, then there is no reason not to use Bridge, it's likely to be faster for you, which is the main thing.
Time - setting up a hot folder takes about ten minutes, and I'd never done one before. On the other hand I know my way around Automator etc., as should anyone dealing with large numbers of images. Most of the extra steps are to bring the converted file back into Aperture, automatically linked with the RAW file as a version.
Here's to hoping that the conversion quality gets better fast!
Ian

Aperture processing images from new Canon 5D mark II

Hi, I'm wondering if anyone has attempted to process images from the new 5D mark II with aperture. It's my understanding that aperture cannot process the images as of yet.
Also, does anyone know if there is or if there will be a plug in available for aperture to process the images?
Thanks,
Trish

http://discussions.apple.com/thread.jspa?threadID=1809782&tstart=0

Aperture processing too long

Just bought a new MacBook Pro 15"
2.2 GHz i7
16GB DDR3
OS X 10.10
I was using Aperture to keep my photos...
And using a WD USB external drive to store the library...
Today I tried to open the library with the MBP...
Aperture started and processing...
I wait and wait... still running...
is the external drive failure?? I changed nothing in the setting of the WD drive.

May take hours??
So to have the MBP running for hours??
Will it go to sleep for long process??
No kidding - upgrading my largest Aperture library (close to 1TB) from Aperture 3.2.4 to 3.3 took one more than a day. I disabled the Powersaver to prevent it from falling asleep and connected to a power source.
You should be sure to have a backup of the library before upgrading and plenty of free disk space on the drive with the library and on your system drive.
Try again to upload the screenshot:

Aperture "processing" continually when opened

I open aperture and it continually is "processing" and I get the beach ball rotating. The only thing I can do is "force quit'. What does this sound like?

Deborah-
It sounds like Aperture is background processing and you should let it run.
-Allen
Some generic advice I posted in another thread is reposted below. Some of it (especially RAM comments) may apply to you, but we don't know your setup.
Aperture is a heavy pro graphics app that is very demanding of hardware. Your Mac's CPU, GPU and/or RAM are probably limiting to Aperture so we need to do what we can to optimize. Some steps:
• Set Previews to only be built manually, and only tell Aperture to build Previews when you are not otherwise editing in Aperture.
• Keep the internal drive underfilled for speed, which sooner or later usually requires using a Referenced-Masters-Library with Masters on external drives. Back up originals before importing into Aperture or any other images app.
• The Aperture Library should be on an internal drive.
• Turn off Share Previews with iLife and iWork
• Remember that HDs slow as they fill and keep the internal drive underfilled. Approx. 70% full maximum is a good guideline.
• If page outs increase significantly during operation, *max out RAM* and/or try to run Aperture by itself. On my C2D MBP with its max of 3 GB RAM I always did a restart prior to a heavy Aperture session to clear any memory leaks and make sure no other apps were open. Browsers in particular will often suck RAM Aperture would otherwise be using.
IMO all Aperture users who can should routinely bump RAM to at least 8 GB.
• Some users have observed that it can take a new Aperture installation time (weeks) to stabilize. So do not panic; and allow Aperture to continue background work by not fully shutting down the computer. Personally I never fully shut down Macs except during electrical storms.
• I recommend *always repairing Permissions* immediately before and immediately after every install of any kind.
Some folks consider it a waste of time but after years of listening to others have problems while I have had problem-free usage of heavy graphics apps (Aperture, Photoshop, Illustrator, InDesign, Dreamweaver, Painter, etc.) on multiple Macs I am fully convinced that although repairing Permissions is not a "fix" it is very useful maintenance for users of heavy graphics apps.
HTH
-Allen Wicks

Aperture 'processing'

Since about a month every time I open Aperture the activity window says it is processing 878 pictures. I can see it is the same set of pics again and again. Afterwards Time Machine makes a back-up, which is always the same size. I am on Aperture 3.1.3.
What is going on? How can I stop it?
Hope you can help!

Have you let the processing run to conclusion or have you quit Aperture before the processing has completed?
Open up the Activity window in Aperture and don't quit the program until the window shows no more activity.

Aperture processing gear will not stop spinning

using aperture 3.5 on a macbook pro retina 15 inch with OS X 10.9.5. Made adjustments to a photo and gear will not stop spinning. I have done the three repairs shut down and restarted. problem persists.

Hey there johnfromnorth andover,
I see that you are experiencing an issue with Aperture and have attempted some troubleshooting steps to address this issue. I have an article that outlines a few more troubleshooting steps that you may wish to take in order to address this:
Get help with Aperture 3 - Apple Support
http://support.apple.com/en-us/HT201289
Take care, and thanks for visiting the Apple Support Communities.
Cheers,
Braden

Aperture 3 Hanging after upgrade and possible solution

In advance, sorry for the long post:
As many have reported already, I was also a user of Aperture staring at the beachball and finding my computer hanging completely up to the point I was ready to give it flight lessons for free. I might have done this to my MacBook Pro if I was not leaving for an overland trip to Capetown from the Netherlands in a Toyota Land Cruiser in 2 days. If you want to read about the trip: www.africaminded.com.
How did I solve the issue in my case? I hope it helps some of you.
*My aperture setup*
Before you go through all the steps below let me explain how my Aperture workflow was set up:
1. Projects in Aperture correspond to folders on my harddrives. The project folders in Aperture contain reference files to the fils on my harddrives. The folders on my harddrives have the same name as the projects in Aperture. Using the same name does not really matter much, except I find it easier to find images from aperture back on my harddrive without having to use aperture to find the images.
2. I do not have the images imported into an Aperture library because this alllows me to access the images with other applications than Aperture (Photoshop etc).
Preparations:
*Actions I took before I started with a clean Aperture:*
1. Launch Aperture with holding the shift key. This defers Aperture from processing images in the library. Tip from Apple website: http://support.apple.com/kb/HT3805
2. Show Keywords HUD and export the keyword list in a separate file onto the desktop
3. Create folder on desktop called "Exported Projects"
4. Drag project by project to the just created folder. Yes this is a painstaking long process and one I would have liked avoided but I did not find any other solution and needed one. Luckily I only had 44 projects to go through.
5. Close Aperture
6. Delete the user preferences
1. Quit Aperture if still running.
2. In the Finder go to ~/Library/Preferences. (The tilde "~" represents your Home folder).
3. Remove the "com.apple.Aperture.plist" file from the Preferences folder.
7. Move the user created presets, keyword lists, and so on...
1. Quit Aperture.
2. In the Finder, go to ~/Library/Application Support/Aperture.
3. Move the contents of this folder to your Desktop
8. Delete your old Aperture Library or move it to another harddrive. If possible do not empty the bin of your computer (just in case you need the library again - I did not after following all steps below).
9. Reinstall Aperture; Note: Make sure that you have your installation discs nearby before starting this.
1. Open the Applications folder.
2. Drag the Aperture application to the Trash.
3. Insert your Aperture installation disc and install Aperture.
4. When finished, choose Software Update from the Apple () menu to update your software to the latest version.
*Now your computer has a clean install of Aperture*
1. Launch Aperture
2. Show Keywords HUD and import the keyword list that you saved in a separate file on the desktop
3. Move the following files back into ~/Library/Application Support/Aperture:
1. Adjustment Chain Presets.plist
2. FileNamingPresets.plist
3. Metadata Presets.plist
4. MetadataSets.plist
4. Close Aperture and go to
Following the steps below allows you to keep all you metadata and rating as well. It is possible in Aperture 3 to read and import sidecar files containing metadata but this will not include the rating! So if you want to keep your metadata and your ratings, follow the steps below:
(*A) Importing Project*s
1. Launch aperture
2. File > Import >Library / Project
3. After selecting the exported project you want to import, confirm you want to merge the project
4. Which library should be used when a conflict is detected? Choose current library (and not the library/project you are importing).
5. Let Aperture take its time to merge the projects (depending on the size of the project you import this can take longer and you might see the famous beach ball for a few seconds). In the beginning it will look like Aperture does nothing or hangs again.
6. After merging the libraries are completed Close Aperture.
7. Launch Aperture and immediately select Window > Show Activity from the menu. Let Aperture process new previews (this should start automatically after opening Aperture). Show activity will give you an idea how far Aperture is when processing the images so you don't have to stress and stare at the spinning wheel in the bottom left corner.
8. After the processing has finished Close Aperture again to save the new previews and share them with iLife and iWork.
9. Repeat the above until you have imported all your projects. Remember to keep repeating step 6 to 9. This allows you to find out which project contains corrupted images or is corrupt and to deal with it separately. Importing all projects at the same time and then processing all pictures at the same time does not give you the opportunity to figure out how to get rid of the beachball!
*(B) What to do when images are corrupted in a project?*
In case you imported a project that was corrupted or contains corrupted images that causes Aperture to hang completely and slow down your computer to a complete halt:
1. Force quit aperture
2. Reopen aperture and immediately press the shift key after launching the program. Pressing the shift key stops Aperture from rendering/processing the images you imported from the "corrupted project".
3. Select the last imported projected (the one that contains 1 or several corrupted images and gave you the beachball again).
4. Delete the project and empty the trash in Aperture as well. Do not delete the master files associated with you referenced images.
5. Move the corrupted project into a folder called "Corrupted projects". Do not throw the corrupted project away - we will deal with this one later. Just make sure they are not part of the main library you are building.
6. Quit and launch aperture. Aperture should not be processing any images anymore as you already completed that with step 8 above.
7. Complete the importing of your projects following the exact steps above, skipping the corrupted project.
Ps. In my case I found 1 project with corrupted images.
*(C) What do you do with the corrupted projects?*
1. Make sure that Aperture is not yet running.
2. Double click the corrupted project and press the shift key to defer the processing of images. This will launch aperture and treat the project as an individual library.
3. Select all thumbnails and export masters to a new folder and select "Create IPTC4XMP Sidecar File" in the pulldown list where it says "Metadata" in the export window. You should now have all master images of this corrupted project and the sidecar files containing the metadata of these images in the same folder.
4. Quit Aperture
5. Press the Alt-Key/Option-Key and Launch Aperture. Aperture should now ask you which library you want to open. Select your Main Library that contains all the projects you imported following step 1-9 above.
6. Create a new project for the images you are going to import from step 3 of section C.
7. Import the images and move them to where you want them to have. Aperture should import the non-corrupted images including their metadata (as the sidecar file of these images is in the same folder as the images). All you have lost in this case is the rating and possibly the adjustment of these images. The IPTC data will be imported by Aperture in step 9 Section C. You could survive having to redo the rating manually. Redoing the adjustments is a bit of more work, sorry.
8. Quit Aperture.
9. Launch Aperture with pressing the alt-key or option-key and select your main library as in step 5 and select "Show Activity" from the menu. You are now back into step 7 of section A. Complete step7, step 8 and 9 of section A.
*D. Congrats*
1. When all projects have imported correctly delete the projects from your harddrive to gain space.
2. Delete the temporary Aperture library created in section C step 2.
3. Re-install plug ins that you might have moved in the preparation phase (if possible 64-bit versions if available)
Congrats. You now have a completely new and well functioning new Aperture 3 library that offers you all the new features and is very fast I should say. My machine: MacBook Pro 2.93GHz with 4GB Ram.
After you think you can trust Aperture again empty your bin to gain space on your computer.
How long did this take me? All in all about 3 days but not full time luckily. How many real corrupted images? None - something else in the project data was messing everything up.

WOW!
I'm REALLY impressed by your exhaustive and detailled description!
How long did it take to write? Sure longer than the import itself...
Thank you so much. I got a working import of Ap2 lib before but your description have me various hints for handling problematic or faulty projects.
Matt

Aperture not building thumbnails

Having a problem right now with generating thumbnails in Aperture 3.5.1. Originally had another issue with iMovie seeing very few movies in my Aperture library. I was able to import all files from all cameras into iMovie, and can see them if I import a sampling of them into another library. Apple support suggested I rebuild my library, which revealed a few more, but still less than 5% of the total.
Apple then suggested I create a new library and import my existing library. I was watching the progress bar near the end when Aperture crashed at completion. I repaired the library and it began building thumbnails. The process has been slow, with Aperture running at 100% CPU (one core--single thread?) and very low I/O on the disk.
The status freezes on one image when Aperture processes roughly 1000 thumbnails. It says "Generating Thumbnails for [image]" "35,323 Remaining". At first I thought Aperture may still be processing in the background, seeing how Aperture's CPU utilization remained in the 100% range and disk usage continued. But when I quit Aperture and restart, it shows barely more progress than what was indicated in the status before quitting Aperture. The particular images listed are fine, and the thumbnails are generated when Aperture is launched.
At this point, Aperture will not quit cleanly, or with a Force Quit. Occasionally I've been able to use this suggestion:
https://discussions.apple.com/docs/DOC-3881
In other cases, Aperture seems to quit, but the entry remains in the Activity Monitor, with all accumulated stats, but 0% CPU. I'm unable to launch Aperture at this time and must restart. If I try to kill the process, the OS says it can't find it. Could this be a Mavericks eccentricity?
When restarting the OS and Aperture, thumbnail generation continues from where it left off, and processes another 1000 images or so. I did try repairing the database, and thumbnail generation continued, but eventually failed.
Occasionally, the com.apple.MediaLibraryService stops resonding in the Event Viewer. This had not always correlated with the frozen progress bar. In fact, thumbnails have continued to process when I've seen that hang in Event Viewer. But it always has meant I need to take Aperture down forcefully. Oddly, I do not have sharing previews enabled (set to never for now).
There are a few early articles, but they don't seem to offer any suggestions I have not tried, except to persist and restart Aperture each time this happens. Could take 2-3 weeks at this rate if I need to restart every time the progress bar stops. I have also tried clearing user and system cache a few times.
Apple second level support has been slow to respond, and I'm over 9 days into this process. Has anyone experienced anything similar, or can offer any suggestions?

Is it only your current Aperture library, that is causing this trouble?
Or do you see the same problem, when working with a new test library?
Although otherwise operationally sound, some video in my original library was not viewable in the Media Browser (including iMovie), even after a repair and rebuild.
I created a new, empty library and imported my original library. I described that process. Aside from the crash near the end, it appears to have all my assets. The project and image counts are the same.
The issues described about building thumbnails is in this new library. Upon importing my original library, the new library began generating all new thumbnails.
If the thumbnail generation is only hanging for your current Aperture library, you may have imported corrupted media - image files, videos that cannot be processed, sound files.
I know exactly what you're talking about, and this was my first assumption as well. As an Aperture 3 early adopter, I saw this issue countless times from failed imports. But I have examined over 8 files that it has apparently hung on. The thumbnails are fine! I look at the assets, directly, and they are in perfect condition. I expected to find corrupted TIFF files or bad thumbnails. Neither were true. If I request to generate it again, it works just fine.
Have you tried to remove the images from your Apeture library, that are shown in the message? Inspect them in the Finder and check the media type - jpeg, raw, video and check, if other Applications can open it.
Yes.
I do not have previews generated for nearly 2/3 of the images in my library, although I haven't seen reports about how this could be a problem.
UPDATE
Since my first post, I found a suggestion to regenerate all new thumbnails. Days of time lost, but I restarted. Still had a crash after about 1000 thumbnails. com.apple.qtserver or something was hung. Seemed only to launch occasionally after I restarted. Thought this might be responsible for generating thumbnails for video. So I did a search for all video files and let Aperture build these as I browsed through, page by page.
Since that time, Aperture has been building thumbnails for 10 hours, the longest run yet. Thumbnails are still generating VERY slowly, but I haven't seen a crash since.
Could it be the back and forth between images and video as it's generating thumbnails?

Time zones being re-written when files are processed from refernced files

I'm having a problem where photos with time zones set are being re-written automatically to whatever time zone my mac is currently set at when Aperture processes them for viewing regardless of the time zone they were set to. This happens as the photos load for viewing (i.e. not on the browser thumbnail view). It does this one at a time and eats up processing time. This seems to only happen (I think) for referenced files stored on my external drive and not those stored in the Aperture library. If I re-set the photos back to the proper time zones using Batch Change, it still happens next time it has to load the photo into memory, again "processing" and again the time zone reset to whatever time zone I'm now in.
Here's the exact situation:
- I've imported several photosets from a Canon 50D. The camera was set to the time zone of the country in question. Let's use India at GMT +5:30 as an example.
- When I import the photos, I also use the time zone presets, setting both the Camera Time and the Actual Time to GMT +5:30.
- I'm importing the photos as referenced files, storing them on an external hard drive.
- So when I first view the photos, the time and date show correct. Again using a real example IMG_0001 shows the date 6/10/10 1:43:31 PM GMT +05:30.
- Now I close Aperture and re-open.
- I open the folder and view the photo. The "loading" message appears at the time and the "processing" message appears on the bottom. (and during this unnecessary processing, it is very slow flipping to the next photo, a serious annoyance in browsing).
- After processing, the photo IMG_0001 now shows the date as 6/10/10 1:43:31 PM GMT +03:00 (the time zone I'm currently in and the one my Mac is currently set to)
- If I close it again and re-set my Mac to say I'm in London at GMT, and re-open, the photo is re-set instead to GMT.
- I can re-set all the dates to the proper time zone using the Batch Change where I again set both the Camera Time and Actual Time to the correct time zone. But when the photo re-loads, it again re-processes and goes back to the date of the Mac. So changes don't seem to stick.
- This appears to happen only to files that are referenced and stored on my external drive, not those stored in the Aperture library.
Has anyone had this problem? Is it a bug or some hidden setting I'm missing? Is there some way to tell Aperture "don't change the dates, ever, unless I do it via batch change"? The problem turns into a major inconvenience in reviewing and editing photos with it taking the extra processing time every photo and messing around the order.

maybe you try this question also in the dedicated Adobe Illustrator Forum, not many inhere (including me) have much experience with Illustrator nor live trace I'm afraid.

Images Disappearing in Aperture

Hi Everyone,
I run a little Aperture advisory blog in Hungarian, for my Hungarian readers.
I often get questions that I can answer, and the users are satisfied.
Now I’ve received a difficult question about disappeared images that I followed up with some research and an exchnage of messages with the user, but I can not find the answer.
This is a commercial (wedding photography) use of Aperture, with serious time commitments to deliver images, so it is critical to find a quick solution.
Here come the details:
Issue One:
Small network with one iMac and one MBP and with one Synology DS211J NAS with 2x2TB disks in a RAID1 array.
All assignments are given an individual .aplibrary that is placed in a separate folder, which also holds the RAW masters.
A couple of weeks ago my reader was working around the MBP, but not touching it. After a period of inactivity he could see from a distance, that the Preview images, one-after-the-other were being replaced by gray triangles with exclamation marks. As if a wraith had been invisibly fiddling with his files.
Some of the images were changing, being replaced by tiny, rectangular, cropped images from another library (!!!).
He quickly quit Ap, then restarted with Option-Cmd and went through all the repairs and the rebuild. After the maintenance and rebuild the situation remained the same. He gave up work with the MBP.
Issue Two:
We are now on the iMac, in the Library of an assignment with 2000 masters and 200 adjusted/finished images, a part of them, luckily, already exported.
Again, apparently without any human action, the images, seen in Browser view, one after the ather, spectacularly changed:
- Some turned by 90 degrees and got distorted - these later were possible to recover by Generate Thumbnails.
- Most of them changed to a camera-icon (though these are photos), and in the bottom-right corner „The referenced image’s master is offline” badge appeared.
In the “Locate Referenced Masters”-dialog all images are shown as existing in their correct location.
When clicking at such a thumbnail, the preview of the adjusted version appears with the “Loading…” message then, after it has been loaded, a translucent gray layer comes over it and the bricks in the Adjustments inspector get grayed out.
In some cases the preview finishes loading nicely, but the master is still shown as offline. When my reader attempted to export full sized JPG versions - you won’ believe: the result of the export was a copy of the RAW master!
After confirming that all standard repair processes have been completed (permissions, repair- and rebuild database, relocate referenced masters, etc) I suspected that the RAID might cause the problem, as it is using 2 disks and I know that Aperture links each image to the UUID of the disk which holds the image. I thought while the logical path is unchanged, the physical location - and hence the UUID - might change. But we tested this, moving a Library to a new external HD and then locating and reconnecting masters. In the result the images showing a camera-icon still could not be found.
I’m getting rather desperate with this case, and would appreciate any advice that might bring us closer 1) to find the cause of the issues 2) to solve it.
Many thanks.

So the libraries are on a NAS?
I hate to point this out but Aperture libraries don't so well in such a configuration see: Aperture: Use locally mounted Mac OS X Extended volumes for your Aperture library
Also with the libraries on the NAS there is the danger that two separate Aperture processes could have a library open at the same time.
regards

Quick preview looks better than processed raw image...??

Hey all, probably a bit of a "newb" question here... so forgive me, and thank you...
Using a D7000 and often times when I shoot - the preview image on the camera looks BRIGHT, VIVID and ROBUST ... after import however - when reviewing my shots, JUST as I arrow over to the next shot - many of the preview images tend to look better than the processed image that aperture displays once it's done spinning it's wheels.
Perhaps I've messed up a Raw Fine Tuning setting?
When I click on quick preview and browse through an import, the pictures truly look nicer to me than the when aperture processes them.
Without question, the display on my acer monitor is a far cry from the miniature compressed image on the back of my nikon, however the more i shoot, the more I realize a disconnect between what I think I should see, and what I'm ultimately seeing in Aperture.
Are their specific settings to fine tune the import of raw d7000 shots?
Thanks much.. gk

I take it you're shooting and processing RAW images?
It's worth remembering that if you have a picture style selected (i.e. vivid etc), your camera might be applying extra contrast and saturation etc to the image you see on the back of the camera. Camera manufacturers do this so that we can give our pictures some extra punch and colour automatically.
I'd also be wary of comparing what you see on your camera to what you see on your monitor. Unless both are calibrated, you shouldn't trust either of them 100%. The best example of monitor calibration is going to look at TV's in an electronics store. You'll probably notice that in a wall of TV's, some pictures will be darker, some lighter, some more vivid, some more saturated. Using a calibration tool adjusts the picture your screen and monitor displays so that it is 'accurate'.
It's a bit like having a room full of scales and adjusting them so that they all read 1 kilogram when a 1 kilogram weight is placed on each of them. Calibrating monitors will mean that when you display an image on it, it will always look the same rather than getting the some light/some dark problem you saw in the TV store.
It's a tricky subject to explain (don't worry if it doesn't make sense), but you might like to have look around YouTube for videos on the subject.

Several questions regarding aperture 1.5.2

hi.
I am a new mac user (just started using several days now), and apparently Aperture.
One of the reason why I switched to Apple is Aperture and future CS3. In any rate, I have these questions if anyone can answer.
First, my spec is as follows.
Mac Pro/2.66Ghz/5Gb/250GB+320GB HD/ATI X1900 Video Card.
1. I have imported about 4000 images into Aperture library. I liked the idea of vault and backing up to another device/hd for safety. Now that I have about 4000 images, the photo editing has SLOWED down dramatically. What I saw the changes immediately, now I have to wait 1 or 2 seconds before I see the result. Is this normal? I am worried that if I import another batch of photos from another HD, it'll slow down even more. How can I improve the overall responsiveness and performance of Aperture?
2. Is there a way to export entire library/project/folder from Aperture Library back to hard drive? I tried export, but it seems to export only individual photos. I wouldn't want to repeat the process 4000 times in order to export the master files back to the external HD in its original format. Is there any way?
I can't seem to locate the color management/profile setting. Is it default to AdobeRGB or Proofing is what it is?
Thanks for any response in advance.

Hi and welcome.
1) Is Aperture processing previews? This takes a long time after import (hours), and it will slow the overall responsiveness of the machine down. If you don't need the previews, you can turn them off. Be aware you have to do this in more places than just the preferences, you have to click the "action" gearwheel and disable them. See if Aperture is burning CPU cycles generating previews.
2) Yes. Select a project and export it. Perhaps you have some photos selected and not a project. Ensure you don't have photos selected, and click specifically on a project in the list. Under the Export menu item there should be a "Project" option.
3) The default color space used by Aperture is "large." It is larger than Pro Photo RGB according to Joe Schorr. When you export a photo, only then is a color space applied (this is in general a good thing -- artificially limiting the color space to something as small as Adobe RGB could cause banding during editing).
I would suggest you not use onscreen proofing except for when you plan to print -- it often has some strange effects which will show definite posterization.

Aperture horribly slow on retina 16gb

Since a few days i am using my new macbook pro retina i7 2.3 16gb ssd. and i am surprised how slow aperture is.
i used it on a ssd macbookpro 13" i5 with 8gb for 2 years and always was ligtning fast.
its not useable at all right now. when i scroll to photos (without preview mode) each photo takes up to 1/2 seconds which is just to slow. when i dodge and burn cursor gets choppy, and when i adjust levels it takes 2/3 sec to take any effect.
Just noticed that when i only browse the cpu goes up to 113%+
Since i just used it as temp library (later i will import that in my full archive) the library is only a 2.000 to 4.000 images large.
Here some other information
Macbook Pro 2.3 i7 16gb ram and 265GB SSD.
Clean new install mountain lion (only adobe suite, chrome, aperture, dropbox and skype are installed)
Turned off faces, and geo location in aperture, and also set previews to quality 6 and half size. no other apps running.
by the way not only aperture gets slow, but when i just did some changes to a image and i command tab into a other app. its slow as well..
getting crazy
current activity monitor stats
ram 12.7 gb used 3.2 free
1.8 gb swap used
disk activity small peaks of around 900kb so nothing exciting here
network almost not used. (so no backup or anything is on
for cpu with a idle aperture in the background is just normal
93% idle
skype uses some 3%
chrome 2%
photoshop 1.2%
my other system is a i5 8gb macbook pro 13" with 8gb of ram and also a SSD and a lot of **** on it, and harddisk for 95% full and that one is lightning fast.
so im really stuck here :-(

I did a couple of things to resolve this issue and it was very succesful for me from what I can tell so far.I would like to share this information with everyone. For the record, I recently bought a standard MBP with the i7 2.6GHz CPU, discrete GT650M GPU with DDR5 1GB, and the Hi-Res AG screen. I dropped in 16GB RAM from Crucial and a Samsung 830 512GB SSD. So technically, my MBP with the exception of the retina screen should be pretty identical to the tech inside the rMBP. The SSD I installed also uses the same ATA controller as the Apple OEM NAND in the rMBP.
Thanks to Linc Davis I used his suggestion to look for memory leaks within the Aperture application and my findings so far seem to dictate that he's probably right. I did some comparison with other editing software that I use and none of those exhibited the same behavior. The leaks detected with the "Aperture" process were exponentially higher than say "Photoshop" or "Elements." I think Apple has some code repair to do with Aperture. They rushed 64-bit and Retina support and somewhere the code got sloppy. As Linc also stated, it's tough to track a memory leak, but I find it strange that Aperture reports more leaks than other similar applications?
After doing quite a bit of research, because I do like Aperture a lot as a workflow engine, I had to try my best to fix this. Personally, I don't think this has anything to do with our hardware. Everyone on this thread has the maximum amount of memory supported by their MBP's, so there's not much more that can be done here. Also, the rest of the tech is high-quality IMO. The problem I believe is the order that things have flowed with OSX updates, released, the most recent Aperture update, and the move to 64-bit forced by Mountain Lion. That said, here's what I suggest:
Make sue that you have all of your updates for OSX, Aperture, and iPhoto if you're using a shared library.
Backup your machine with TM. When this is done, moved on to #3.
Download "Rember" and test your RAM just to make sure it passes all the checks.
Check SMART status and make sure your SSD is not reporting any I/O errors. If all is good, continue.
Download and install the latest version of ONYX 2.6.7.
Using ONYX, go to the "Cleaning" tab and do a generic cleanup of all the crap on your machine.
Using ONYX, go the "Maintenance" tab and repair permissions, run all the Scripts, and most important - rebuild Launch Services and the DYLD shared cache.
Reboot your machine.
Start Aperture holding down the OPTION and COMMAND keys. You will get prompted to REBUILD the database. Do this, not REPAIR (that does't really help). After the rebuild is complete, launch Aperture.
Within Aperture, go into PREVIEWS tab, and set "Share previews with iLife and iWork" to NEVER.
Go ahead and try... what do you think? For me, it runs much better, more reliable for sure.
Now for the last and most controversial topic that has to do with TRIM. Problem is, people with an rMBP can't disable TRIM support on their SSD from what I can tell. Maybe I'm wrong? However, call me crazy, but when I had the TRIM hack enabled for my SSD, I saw some screwy things happening with I/O during Aperture use. According to everything I read from extremely knowledgeable people of the subject, TRIM is one of those uncertain grey areas. In theory the tech sounds logical, but in reality, I'm not sure if it's impacting I/O by making it unreliable? After all, those commands between the OS and the ATA controller have to be perfect in every way possible - otherwise it will create problems. In the case of Apple usage with there OEM NAND, it seems to be engineered. Can't say the same for Trim Enabler?? Just use caution IMO. Like I said, for me, I saw some weirdness, mainly beachballs. As soon as I disabled the TRIM patch, they went away. If you have a quality SSD like a Samsung or Intel, just rely on the firmware's GC. Do what I do, just let your system sit at the login prompt idle once a week.
Another suggestion; use the PMSET command and change the default values for 'standbydelay" from 1600 to 86400 (24 hours). This will tell your MBP to stay in standby mode longer and only after 24 hours will it execute 'Standby' mode (which will write memory contents to the SSD - this just burns NAND P/E cycles unnecessarily). Don't know about you, but who the **** leaves their MBP in stanby mode for 30 days (based on Apple's logic)? I use it daily, so 24 hours fof sleep for me is fine. And, the MBP battery is great and can easily stay in sleep mode for at least 7 days untouched. Point is, less hibernation is better. The command is >>
> sudo pmset -a standbydelay 86400
Good luck!

Finding a place for Aperture in our workflow

Hi All.
I've used it since Sunday. I've attended the demo in San Francisco and I've had discussions with other photographers who would like nothing better than to incorporate Aperture into their lives. I share that desire. This is where I am personally in my relationship with the application:
There are two distinct targets for which my images may be purposed, depending upon the kind of project and the stage of that project. Those processes are of course Proofing and Publication.
For Proofing, wether for a commercial client, corporate PR or a wedding, Apertures RAW engine is perfectly adequate. It's editing tools are brilliant. It's correction tools are crude, but convenient, and again, for the purpose of presenting proofs for selection (but not final publication) adequate.
But in terms of preparing images for publication Apertures RAW engine is not as refined as ACR's and it's color and tonality correction tools are crude by comparison with Adobe Camera RAW.
So the work flows might look like this:
Product Photography:
-Shoot.
-Review in Bridge as versions are created
-Process with color correction in ACR
-Refine for publication in Photoshop
-Deliver
In my opinion, putting these images through Aperture is bad policy because:
1) The RAW engine is going to create artifacts, sharpening, color and contrast problems resulting in an inferior file.
2) Color/tonality, noise reduction, sharpening tools available in Aperture are too crude for reproduction-quality images. Those available in ACR by comparison are more precise, consistent and trustworthy.
3) Layered files are treated and flattened on the fly in a cavalier fashion within Aperture.
4) File management in Aperture is confusing when trying to deal with a number of versions of the same image. I can't tell at a glance which version is which, either by name or other obvious tag.
Event, Wedding, Portrait, Editorial, Journalism:
-Shoot
-Review entire take in Aperture
-Edit and make preliminary selections in Aperture
-Make proof-quality color and tonality corrections in Aperture
-Process out to proofs for print, disk or web delivery to client
-Client makes selections
-Export uncorrected masters of selections to hard drive
APERTURE ENDS
Remainder of processing takes place in Bridge/ACR/Photoshop for preparation and delivery of final images.
Because Aperture should not, in my opinion, be used to produce Reproduction-Quality RAW conversions and because it is confusing, inconvenient and dangerous to use to manage layered PSD versions of files, it is currently not suitable as a one-stop Digital Asset Management application for all of my images.
I Soooo don't want to sound like I'm knocking Apple here. This is an application with amazing potential and when it's risen to the needs, standards and expectations of the professional community it may become indispensable.
Regards,
Frank
G5 2.3 Mac OS X (10.4.3)

In either process, you could do the sorting and
picking in aperture. You could possible produce web
or paper contact sheets for clients. Export the
master files (these are the original RAWS) to
Photoshop and deliver. You can always reimport the
finished files to Aperture in the same project, where
they would remain as Masters, and therefore unedited.
Richard,
I could use Aperture to sort product work, but there is no reason to.
My clients don't want proofs of product shots. I sort between only a handful of brackets to choose the frames I'm going to work on for each image at each stage. Bridge is more than adequate for this task, ports right to the superior RAW converter of ACR, maintains the file names I choose when I save versions of the file back to the working folder, behaves predictably, allows me to view multiple windows and their previews easily and (are you listening Apple?) respects the way I work.
At this point Aperture is only useful for editing and sorting large projects and creating proof-quality output. At this it is brilliant. BUT It's organizational fascism, inferior output, marginal control and capricious behavior with layered files makes it far, far more trouble than it is worth to incorporate into any part of a product photography workflow at present.
And in any case I would not want to keep finished files in Aperture anyway. If I need recourse to a file it is usually to a Layered version of that file because my client has asked me to make some change to it. If I import a layered PSD into Aperture I have to export it back out of Aperture before I can open it up again in Photoshop. Aperture will only send a flattened version of a file to Photoshop if that file was not originally saved in Aperture in the first place. Aperture only allows me access to layered files that have been savedinto Aperture, not files that were imported into Aperture.
-Import RAW into Aperture
-From Aperture, open that RAW into Photoshop, create layers and do a straight save, NOT a save as,
-Under these circumstances Aperture will allow you to then open that file into Photoshop again with it's layers.
(NOTE that it must be a straight Save. Save As will not let you save into the Aperture Library. You cannot create distinct and useful version names as you save the file.)
But if you
-Import a Layered PSD into Aperture, Aperture will ONLY send a flattened version of that file back out to Photoshop.
So I can see no advantage and very many pitfalls in allowing Aperture to touch any of my product photography at any stage. Its severe limitations mean that it can function only as a sorting table for my event, editorial and portrait work. Import Project, sort, export selects, proof, delete Project.
Like you, I desperately hope that Apple will take these concerns seriously.
Cheers,
Frank

Aperture 2 vs Photoshop CS3

I'm currently looking to upgrade to a Mac and I use CS3 on a Windows XP Pro machine now. I don't know much about the Macs, but I've been impressed with in store demos and online discussions with ease of use.
What I'd like to know from other users is "does Aperture 2 provide any value in a workflow set up?" Since a cost of moving to the new platform will bring some other costs (new software in various areas), I'm trying to limit my investment costs. Does Aperture (at least the way I understand) only provides a light table type approach with basic editing capability? How powerful are the editing tools?
How easy is it to set up a Mac on a home LAN that contains several other Windows machine (my thought here is a "sharing" between the Mac where I'll download and do Aperture processing of files and use the Windows CS3 machine for the "heavy" post processing - since I rarely get an exposure that doesn't need post processing).

>Can I suppose that Aperture is better integrated with the OS, and Lightroom is better integrated with Photoshop?
Not really. Both integrate well with the OS and with Photoshop.
Photoshop and Aperture/Lightroom are totally different apps. For advanced image editing one needs an app like Photoshop or Photoshop Elements. If one does substantial DSLR image capture an image management app like Aperture or (less good) Lightroom are invaluable. Aperture requires strong MacIntel hardware but LR will run on PCs and weak Macs.
I strongly recommend that every digital photog with adequate computer hardware first spend $33 and work through the tutorial CD
i Apple Pro Training Series: Aperture 2 (Apple Pro Training Series) by Ben Long, Richard Harrington, and Orlando Luna
(Paperback - May 8, 2008), Amazon.com. Step one with Aperture is to have at least 3-4 GB RAM on a MacIntel box. After adequate RAM is on board do the free Aperture trial
Note that the value is in diligently working the tutorial, not in using the book as a manual. The time spent learning modern digital image capture workflow via the tutorial is invaluable.
IMO a cursory examination of Aperture usually turns out to be mostly a waste of time, or leads to bad workflow habits or folks simply do not get it. Carefully working the tutorial is by far the best way to learn this new killer app category.
Good luck!

Aperture 3 "processing"

Similar Messages

Maybe you are looking for