Slow Aperture 2

Hi,
I have the quad G5 with 5g ram, however when i start using it as raw processor for my canon 5D mark II files which are 24mb in size, aperture became so slow it a frustrating way. do you think its time to upgrade to a better machine or it has nothing to do with it.
also in preference I set my preview size to unlimited does it have to do with my problem?. the defualt is 1/2 the size.
thanks

Hi,
I might as well put my two-cents in since this seems to be a common problem. I just recently purchased an 8-core Mac Pro with the stock configuration (6gb memory/Nvidia card). I am coming from an iMac 24" 2.4Ghz. After transferring all my files and programs from my iMac to my new beast, I quickly opened Aperture and was expected to be blown away. Not so fast...
The Mac Pro, with it's 2 quad processors and 6GB memory was having a hard time keeping up with my adjustments. I tried rebuilding the library, reinstalling Aperture and searching high-and-low on the internet as to the cause of this problem. I also singled out Aperture as the only program on my Mac Pro that was running like a dog. So I contacted Aperture support and he helped me figure out the problem, which is much more simple then upgrading your whole system. The answer is breaking up your library into multiple libraries.
If you shoot a lot photos (especially RAW), then your library is probably pretty big. He explained that any computer would have a hard time going through a library that was 160 GB (the size of my current library). So, we did a test. I created a new library and imported a couple master images from the old library. I then went through and applied tons of adjustments to the image without lag, beachballing or lock-ups. It really made a huge difference!
So, if you are finding that Aperture is acting unusually slow or freezing while making your adjustments, I suggest you begin managing multiple libraries to keep the size down. Below are a few threads on creating and managing multiple libraries.
http://www.apertureprofessional.com/showthread.php?t=1483
http://www.johnthawley.com/journal/2009/5/11/managing-multiple-libraries-in-aper ture.html

Similar Messages

  • Problem with Maverics: Can not sign in to App Store, Mac slow, Aperture not working

    I was using a Mac Book Pro 15" supplied with Snow Leopard. I have created an ID and used it to purchase apps such as Aperture. After buying an iPhone 5S, I wanted to share the contacts and was suggested by the seller to upgarde the Snow Leoprad to Maverics and use the iCloud. After installing the Maverics following happened:
    - I can use iCloud and share the contacts, mission completed
    - the Mac is running slow, really slow (as an old pc)
    - Aperture can not be used, a major problem since all of my photos are stroed on an external disk via Apeture
    - I can not sign in to App Sore to refresh my purchases and see if there is an update for Aperture
    - I tried to sign in by clicking the forgot password and entering my ID (e-mail address) but have received no mail - total mistery
    - I also see that the HP 7610 printer icon is not active and assume that will also be a problem
    What should I do? I need a fast running computer. I need Aperture, all of my private and business photos are accessible only via Aperture. I can sign in with the same ID/password on an iPad. The problem is obviously due to installing the Maverics. I do not have a time machine/capsule.
    Urgently need support, please help.
    Lanika

    LousyFool wrote:
    ... I enter my e-mail address and Apple ID ...
    Just for the record, you should enter your Apple ID ([email protected]) and password...
    Provided you did that and it doesn't work:
    You're using an account with parental control active?
    Do other logins with your Apple ID work? E.g. icloud.com, iTunes, ...?
    Correction: I did correctly enter my Apple ID and its password. And there are no parental controls.
    But I found a fix: I went to the Featured page and it showed me as logged in. I clicked the Account link and in the pop-up for that entered my Apple ID and Password. Now I can once again see my Purchases.
    It would seem to have been some undue delay or glitch at the Apple server end.

  • Very slow Aperture on MacBook Pro 2.16 Duo

    Hi All,
    This is most likely a topic that has been covered before but Ive looked and cant find the answer. Ive got a 1.5 yr old MacBook Pro 2.16 intel duo with 2GB RAM (its maximum )
    I bought Aperture 2 a few months ago, and its now started to run very, very very slow. I store my referenced files on a Lacie Drive (USB 2), however the issue seems to be that when I start browsing, exporting, editing and generally moving around the program, it gets to a point when the beach ball is on spinning overload. My Mac's fan is wizzing round like mad, It sounds like the things going to take off! Im really starting to lose faith and seriously looking at lightroom, but I love the structure on aperture. I have taken my Laptop to a mac store and even they have had a look over it, and cant understand why it runs slow. Its really disappointing that if its a hardware issue I cant do anything about it, plus I easily surpass the min specs to run it. Its holding up my workflow and costing me money in delivering files to clients!
    Any help what so ever would be great,
    Cheers Guys
    Matt

    I'm running the same model Duo with a 120GB drive and an external LaCie. It does not support the 800 Firewire, just the 400.
    Aperture runs adequately fast, although after two months I'm still learning a lot about the features. The search HUD seems a bit slow, but I do have alot of pictures.
    My Aperture Library is 14GB, 13,000 files, 90% are jpegs. All picture files are referenced and take up an additional 17GB.
    I found Aperture (and Parallels) choking whenever the free space on my internal drive gets down below 6-8GB. Some non-Apple forums recommend keeping at least 10GB free for working with media intensive apps like Aperture. I also find that even when I quit Aperture, it doesn't free up the temp space on the disk drive it had used. Restarting regularly recovers the 1.5GB or so that Aperture was leaving behind after quitting.
    I'm slowing breaking the big project I had with 11,000 files into several smaller projects and migrating the referenced files to an external LaCie. File management, renaming files, finding duplicates, etc., is not an Aperture strong point, (Expression Media is better at file and metadata management, but has limited editing and integration features with iLife, etc.) but over all I'm satisfied with performance on the Core Duo with an external monitor attached.
    Cheers,
    Flack

  • Will imprting my iPhoto library slow Aperture down?

    My current Aperture library is 20GB and my iPhoto library has 11,000 images and is 32 GB. If I bring my iPhoto library into Aperture (and store it in the Aperture Library, i.e. non-referenced), will this cause Aperture to slow down considerably? I know I can always have multipule Aperture libraries, but I'd rather not.
    I presume that using Smart Albums would be slower as there are more images to search through, but other than things like that what is your experience?
    Thanks!
    P.S. I'm looking for first hand experience, not theoretical
    24" iMac 2.33 Ghz, Powerbook G4 1.5Ghz   Mac OS X (10.4.7)   Aperture 1.5.2

    Yes it will slow it down, in my experience the stacks that are created by the iPhoto import for all the iPhoto photos that had modifications applied to them (of which I had a lot (since it did that for all my portrait photos automatically)
    will cause major slow downs, so after import first try to reslolve all those stacks, remove duplicates (if you want to keep the master but also the modifications try to mirror the modifications made to the photo in Aperture and then toss the iPhoto edited..)

  • 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!

  • Changed the pace of aperture (slow to normal fast)...

    HI ALL...
                       I UPDATED TO LION A FEW WEEKS AGO...YES APERTURE WAS SLOW WIHT 4 GB RAM...
                        BY PUTTING AN OTHER 4 GB RAM...TOTAL 8 GB RAM...IT'S WORKING WELL NOW...
                       FOR THOSE WHO HAVE THE SAME PROBLEM  "SLOW APERTURE WITH LION"  IT'S
                       WORTH  CONSIDERING  UPGRADING YOUR RAM...
                       THANKS... J Charles

    OWC does a good job of keeping track of max RAM amounts for Mac models.
    It appears that you should be able to get at least 6 GB in your 2011 White MacBook.  Well worth getting to 8 GB (or 6 if that's the limit), imho.

  • Aperture getting slower and slower

    When I first got my Mac, and installed Aperture it was lightening fast. The sliders worked in real time, I never got the spinning wheel, every reason I wanted a Mac in the first place had come true. Fast forward to today - about 6 months into owning the Mac and using Aperture, the software is running slower and slower. Even clicking on an adjustment often takes time for the adjustment to load. Brush HUD's don't show up right away; adjustments don't show in real time - all of this makes tasks with brushes painful if not sometimes impossible. I've read the posts and threads related to slowness - faces is off; I'm not sharing photo's with I-life or I-work; all other apps and software are closed and shut down; my HDD is under 60% utilized; my library resides on my computer. Why is the system getting slower, and what can I do? Obviously, I can add RAM, but my question would be why would it have worked so fast previously and work so slow now with the same RAM? Any suggestions for adjustments, or suggestions. Anybody else experience progressively slower Aperture?

    How much RAM do you have?
    In any case:
    Repair your Library.
    Then:
    Copy your repaired Aperture Library to an external drive.  Rename the version on your system drive.  Run Aperture from the external drive and confirm that the copy is whole and working.  Delete the re-named version on your system drive.  Empty the system trash.  Just for giggles, using Disk Utility, repair your system drive.  Then copy your Aperture Library back to your system drive.
    How does it run?
    (This will repair your Library, possibly clean up your disk, and defragment your Aperture Library (many of which contain hundreds of thousands -- even millions -- of files).)
    There is one other thing to do -- PRAM flush? -- I'll see it I can turn it up.

  • Aperture reprocesses previews for all videos every time I open it

    Hello,
    I use Aperture to organise all my videos shot on Canon 7d and an old HD Cam (705 vids, 381GB). Whereas my stills are stored in the aperture library, the videos are imported into eparate folders named after each project inside one master video folder.
    I do this because it is an easy way to work with all of them in FCP (X), importing them without moving them, keywords from the folders coming across (and also because  FCP used to incorrectly display the meta data- date and time imported shown as the file's creation details, when accessed via the aperture library menu from FCP, this bug has probably since been corrected)..
    After restoring from a time machine back up recently, Aperture now reprocesses previews for all 705 movies every single time I open it, reboot or not. It doesn't hang on any particular file or crash but (as it's a mid 2010 MBP) simply slows Aperture down below useable for a few mins until they are done.
    Post import processing set to camera previews, new projects always create previews ticked.
    What am I doing wrong please? Should I attempt to fix the database?
    Best
    Ben

    As a work-around -  hold down the shift-key, when launching Aperture. That will defer the generation of Previews, so you can start working immediately.
    What is your Aperture version and MacOS X version?
    After restoring from a time machine back up recently, Aperture now reprocesses previews for all 705 movies every single time I open it, reboot or not.
    Was Aperture the only thing you restored from a Time Machine backup? Or did you restore more of your system? If you reinstalled or upgraded the system, there may be now video codecs missing. In that case check, if reinstalling additional video codec (Perian, Flip-4-Mac, or similar) may help.
    If the reinstalled aperrture library has been created on a different mac, there may be permission problems after restoring from Time Machine. Check the permissions and ownership on your video folders.
    Are you touching the videos in any way, when using them in Final cut? Using stabilize or something? If the " last modiied " date is changed by Final Cut, this might prompt Aperture to recreate the preview.
    -- Léonie

  • Help - can't see Aperture library in iPhoto

    I'm following the directions outlined on
    http://docs.info.apple.com/article.html?artnum=304446
    but not seeing the Aperture library.
    Sharing is turned on in Aperture, and I have the latest versions of both software.
    A follow-on (probably answered when I get this worked out):
    I am assuming I can create a Photocast in iPhoto of files I have modified in Aperture (not the masters). If that happens and I continue to tweak the modified photo within Aperture, will that automatically update the iPhoto Photocast?
    Or does iPhoto in essence import a file from Aperture, so its not really dynamic? (or just reference the master or the top of the stack)?
    Thanks so much!

    Answering the second question first: You get a media browser with Aperture photos - if you use them in iPhoto you'll have imported them and thus created copies, so no, the changes won't go through to the photocast.
    In addition to turning on sharing, you might have to force previews to be generated for your Aperture library. I don't have Aperture but I believe the steps were to hold down Option and choose Generate Previews, forcing Aperture to create previews. I read this on a discussion that was in essence complaining about how slow Aperture is to generate previews - I guess if you didn't notice, then no previews were actually created. I think the preference you set might have been to apply it to newly imported photos, not existing ones.
    There's a task progress window or something that tells you it's generating previews. I'm not sure if it appears automatically or you have to bring it up.

  • Stability and Performance Issue With Aperture 3

    I'm running Aperture 3.0.3 on my iMac. This is a switch from Adobe products and I'm having a ton of stability and performance problems.
    Environment:
    * My library is about 32,000 images, about 1/3 of which are 21 megapixel, the remainder are 10 megapixels or smaller.
    * I have no smart albums.
    * All images are referenced and live on an external FW800-connected RAID5 array. The library lives on my internal drive.
    * I have an Apple Cinema display connected through the mini-DVI port.
    Here's what's happening. Initially, Aperture starts up fine and things are peachy. After a few adjustments -- particularly cloning or patching, rendering becomes slow. It becomes slow as in a minute or more. On a 21 megapixel file, this is an incredible productivity killer. Here is what I've tried to make Aperture go faster (not all at the same time):
    - Log in holding the shift key to make sure nothing but core system stuff is running
    - Rebuild Aperture library
    - Defragment internal hard disk using iDefrag
    - Export a subset of images to a separate library and work on them there
    None of these has had the desired effect. Worse, if I switch to full-screen mode, the whole interface becomes balky and can become unresponsive to the point where the only way out is to cold reboot the computer. Cmd+TAB doesn't even work.
    I can't imagine this is an experience shared by many users of the screaming would be deafening. Lightroom and Photoshop are insanely fast by comparison so it can be done -- and on this computer.
    What are the best practices for speeding up Aperture?
    Thanks,
    Steve
    Message was edited by: films-so-last-year

    Have you tried the Bergsma BAsh?
    Many of us who have upgraded our library's over time have cleaned out caches using a technique discovered by Matthew Bergsma . It cleans out some obsolete files that significantly slow aperture 3 down.
    Here's what you should do:
    Quit aperture
    Navigate to your aperture library.
    Ctrl click library and select show package contents
    Open the thumbnails folder and drag contents to trash.
    Then delete the entire contents of the following cache folders:
    Hard Drive/Library/Caches
    Hard Drive/System/Library/Caches
    Hard Drive/Users/Your username/Library/Caches
    You may also like to delete the preferences file but that's up to you.
    ~/Preferences/Library/com.apple.aperture.plist
    Open Aperture:
    Rebuild Thumbnails click library - photos
    Then select one photo and apple(command) A to select all.
    Then go to the photo menu and choose generate thumbnails.
    It'll take a while to go through them all but once it's all done Aperture 3 should zip along
    You can read Matthew's original post:
    here http://discussions.apple.com/thread.jspa?threadID=2359859&start=0&tstart=0
    Hope this is of help!
    M.

  • Bringing 8 years of work into Aperture 2?

    Any suggestions on bringing 8 years of work and approx 40,000 images into Aperture 2? I have consolidated all the 300GB of images on to single drive. And they are separated into two main directories called Job Files and Personal Work.
    Job Files is further divided in to folders for each year and then into dated job folders. Personal Work is divided by categories such as Lifestyle and Sports, Family and Friends, Mexico, etc.
    I would like to use referenced images and keep all past and future work on the existing hard drive.
    Can I just import the whole drive into a single project, or should I create separate projects for Jobs Files and Personal Work? Or do I need even more projects?
    I've been searching for tutorials on importing large volumes of images like this, but I haven't found much.
    Any advice would be much appreciated.
    Thanks,
    Andrew

    Definitely separate personal vs. work into separate projects.
    Be aware that you can disable/enable Aperture's function of automatically creating previews on import. The default setting is enabled, and that makes importing take much longer. Also, automatically updating the previews after every adjustment adds to background processing, which can slow Aperture's performance. Previews are only necessary for slide shows and for sharing photos with other iLife and iWork applications via the system-level media browser. For those reasons, many of us disable automatic preview generation. You can selectively generate previews at any later time, which is what I do when I need to use photos in iWeb or another app.
    Go to Bagelturf.com and read through his library of Aperture articles, if you haven't already done so. He has several articles about importing photos.
    You seem to have a pretty good start with your current folder hierarchy. As a general rule, don't use projects to "organize," that's what albums are for. Use Aperture's "Import Folders Into A Project" function which will convert your folder hierarchy into an album hierarchy. Although Aperture 2 is faster and the number of photos in a single project has been increased to 100,000, I would still use some multiple projects, just to be safe. Your work is already divided by year, so perhaps you could have a separate project per year.
    This is a big subject to summarize quickly, but I suggest that you create a keyword to correspond to every unique category that exists in your current folder hierarchy. After you have imported all of your photos, you can assign those keywords to your photos by selecting an album and keywording them all at once. It helps to setup keyword button sets. The point of all this is that once you have setup a keyword system, as you bring new photos into the library, you can put them into your organization structure by assigning them the keywords you've setup. And the big payoff then is to create library-level smart albums based on those keywords. This probably doesn't make sense until you actually start doing it, but just keep in mind the goal of using albums, smart albums and keywords as tools to do amazing things with organizing your library.

  • Aperture not returning RAM

    Hi, it seems that I am the first one to post this.
    I have been using Aperture a lot this week adding keywords to loads of photos taken in the last 4 months (had been slack and it was time to get on with it).
    Since I have started I have noticed that my machine was running slower and slower....
    I have now realised after monitoring my machine that Aperture seems to be causing this.
    When I spend a long time on Aperture, and when I quite it, my RAM goes up to 4.5Gig used when Aperture is sharing the previews, but when Aperture is finished and quit, My Ram usage doesn't go back down...
    Anyone else had that problem to confirm this before I send feed back to Apple?
    Let me know

    I have a one year old Intel iMac with 2Gb and the 256Mb X1600 card and i have to say i'm becoming increasingly disappointed with just how slow Aperture is making my machine run.......
    not being able to jump between various images quickly defeats the whole purpose of Aperture! and having to close Aperture to complete semi-power hungry applications almost defeats the whole purpose of switching from a cheap PC to £1500 iMac
    I had the extras to make life smooth and painlesss, are Apple living up to there own hype? I'm begining to think not.
    20" Intel iMac   Mac OS X (10.4.9)   256 X1600 Card / 2Gb RAM
    20" Intel iMac   Mac OS X (10.4.9)   256 X1600 Card / 2Gb RAM

  • 600 GB Library with 200,000 images OK for Aperture?

    Hi everyone,
    I'd like to ask whether anyone has experience with very large libraries (not only size-wise, but also by the number of itmes included) slow Aperture down. I'm considering merging my year-by-year libraries into one huge library to get a better overview of the photos and to be able to work with all (use them for other projects, books, etc.).
    Thanks for your ideas,
    Roman

    Roman1 wrote:
    Since I often move around with my laptop, I'd love to have all in one huge library with 90% referenced to an external HDD. This would create an awful lot of items with their respective previews, thumbnails and database entries in the end slowing down Aperture. The question is how much and how robust Aperture is when used in this way.
    Aperture is very robust with a single Referenced-Masters Library on an internal drive kept less than 70% full. A Referenced-Masters Library does not get overly large in GB of mass storage even with hundreds of thousands of images referenced.
    Another worry is, that while I can have my backup process very transparent if I keep organized libraries with their respective vaults, all would change when referenced files are added to the mix. Not that it would get complicated, but simple is beautiful and I like beautiful.
    First, Libraries plural is almost always bad workflow, defeating the benefits of modern digital files management. Once in a single Library, images can be keyworded and easily managed.
    Second, *I very strongly recommend that back up of original Master files be performed BEFORE importing into Aperture* or any other app. Once that key step is the start of a workflow, the backup process using Referenced-Masters is simple and beautiful:
    • Copy from camera card to the hard drive folder where the originals (Masters) will live.
    • Important: eject and physically remove the camera card from the card reader at this point. The original images are still on the card.
    • Back up that folder.
    • Import from the folder into Aperture.
    • Verify image count, etc.
    • Reformat the card in-camera.
    • Make regular Vault backups of the Aperture Library.
    The Library will remain a manageable size for a single drive and Vaults will be created much more quickly and easily, which means one is more likely to frequently create Vaults, a good thing. And backing up originals before entering Aperture means originals are not exposed to the risk of catastrophic failure that sometimes occurs with complex heavy graphics apps.
    I import each Project separately and name each originals folder by the project name and add _mstrs to the end of the folder name (e.g. 100815Jones_Wedmstrs). That way even if Aperture lost linkage to the Masters (which has never happened to me) a simple search on the Project name would easily find originals and backups of originals.
    -Allen Wicks

  • Aperture 3 performance with the new MacBook Pros?

    I'm loosing my mind using slow Aperture 3 with 2007 MacBook Pro 2.4GHz C2D 4gig mem.
    If someone has upgraded from similar setup to a newer model, please report if the performance has gotten significantly better, because I will start saving money if it does.

    I've managed to get the performance passable by turning basically everything unnecessary off and using Quick Preview most of the time. Still when editing and Quick Preview is turned off, I get the beach ball way too much and simple things like WB changes take a lot of time to refresh. The editing is everything but smooth and flowing. Stamping multiple adjustments qualify for a coffee break.
    Any new experiences on Aperture 3 with MacBook Pro 2010's? I found one review on Leica forum saying upgrade from 2008 to 2010 gave a significant boost in performance and reduced a lot of beach balling.

  • Aperture 3.6 locks up on lunch under Yosemite

    Aperture 3.6 locks up when lunched, I see the Aperture desktop (minus all photos) and the only thing happening is the spinning colour wheel.
    I have to do a force quite to exit the program.  I am running Yosemite 10.0   Any ideas would be appreciated, thanks. --Brian

    How long are you waiting before for quitting Aperture? Aperture needs to upgrade the library, and that can take a long time. Let it run.
    Also, the first few times after the upgrade it will take longer before you can access the menus.
    Several users reported that they had to wait at least 40 seconds after each launch, after the initial library upgrade completed. And that background processing will be done, slowing Aperture down.
    Let Aperture get the background processing done without interrupting it.
    From Aperture's Release notes:  Aperture 3.6 Release notes
    Keep in mind that fully upgrading a very large library is a one-time process that can take a long time; the process may take many hours or even overnight, depending on the size of the library.  Once the initial database upgrade is complete, you can begin working with your Aperture library. However, post-upgrade processing will continue in the background for some time, as face detection and preview generation are performed. (A progress indicator and the word "Processing" will appear in the status line of the Viewer or Browser to indicate these operations are underway.) While you can work with Aperture while these operations are performed, you may experience temporary slow-downs. Optimal performance will return when all post-upgrade processing is complete.

Maybe you are looking for