Aperture 2 Thumbnail Building - KILL ME!

so i'm using aperture 2, and i've got prob 30,000 shots to are referenced within the program...they're all located on my external drive.....anyway, LATELY, every time i launce aperture, it builds thumbnails, and it takes forever...1300, 1800, 2300 photos at a time.....it NEVER used to do this...i'm seriously about to jump ship and go to lightroom....even though i hate it....this is really killing me....aperture used to run fine, and then lately it's just getting bogged down a lot, and runs like crap...any suggestions???

Thanks for your reply. I have automatic generation of previews turned off, share previews with iLife and iWork turned off, and use embedded JPEGs turned on. Aperture 2 works at reasonable speed for a while after starting, then slows down more and more with longer use. Then the Viewer blackouts start, with an occasional yellow screen instead of a black screen. The SBOD may start before or after the Viewer blackouts start.
Since my original post, only hours ago, I've also now seen the Viewer image appear upside down and distorted side-to-side (once). As with all the Viewer weirdnesses, the Viewer image looked normal again after restarting the application. As reported earlier, the SBOD and Viewer appearance problems increase in frequency after multiple restarts of Aperture, until I am forced to reboot my Mac.
I'd classify these abnormalities as bugs.
The Radeon 9650 graphics card was bought as an upgrade when I purchased my PowerMac G5. It is not the fastest graphics card, to be sure, but no other applications, including Photoshop CS3, have the least problem with it. Slowness is not the most serious issue I'm having. Having to restart the application repeatedly, then eventually reboot the OS, is the big issue.
The upgrade from Academic is not related to the problems I'm having with Aperture 2. As I wrote previously, I will pay for the full version - I WANT to buy the full version because I love Aperture 2 when it works - but I would feel like such a dummy to spend my money on an application that is so buggy that it interferes with my workflow. If anyone knows of a way to make Aperture 2 work on my Mac, I will be delighted to learn it.

Similar Messages

  • Thumbnails building on launch, impermanent and missing several years

    When I open it, Aperture always wants to generate thumnails (70,000+, for a library of 190,000 referenced files).
    I'm working with a fresh install of 3.4, a new plist.
    If I let the thumbnails build until done, it apparently makes no difference the next time (after quitting and relaunching Aperture).  The same thing happens.
    Looking at the package contents, I see that although I have pictures in my referenced library going back to 2005, the Thumbnails folder shows folders beginning at 2008.  So several years of thumnails are evidently missing.  (That's probably around the time I switched from iPhoto to Aperture as my photo organizer and editor.  That might be a red herring, or is there something qualitatively different about those former-iPhoto Masters?)
    So how do I make a permanent set of thumnails for those missing years, so that I don't have to either wait a long time for the program-slowing activity to complete, or manually cancel the 70,000+ temporary rebuild every time I launch Aperture?
    Thanks for any advice.
    Patrick

    Leonie,
    Thank you again! 
    The 2008 thumbnail folder appears to include only the normal monthly activity, but inspect files numbers in each (using command-i to look at numbers of items in each folder, in each month) I do indeed find one day in 2008 that includes multiple-thousands of thumbnails.  I conclude that it must be the date I imported a huge iPhoto library. 
    That explains why I appear to have a thumbnail for each picture, going back to the first photo by date (2005), in spite of the (redundant) rebuild that wants to happen automatically with each launch of Aperture.
    I intend to do your recommendation:  to manually highlight all photos prior to 2008 and generate thumbnails.
    However, while waiting (expecting a long delay before I received an answer--I was wrong about that--thanks again!), I highlighted those same photos, and did a "reprocess from masters".  That will take me a long time.
    Then I will try the generate thumbnails.
    Then I will report back!
    Even on a blazing fast machine--MBP retina, with 750G flash drive, and Masters stored on 6TB raid via thunderbolt-eSata--these things take time!  And I'm mindful to try (to change) *one thing at a time* to see if it fixed the problem, so that I can benefit from (and share with others) a simple cause-and-effect confidence that I fixed a problem.
    FYI:  I have been stalled in my editing now for almost 48 hours.  Two days ago, my formerly reliable Aperture editing procedure began to freeze (spinning beach ball) while I tried so fairly routine edits on pictures.  I'm not sure the editing problem still exists, because I have allowed myself to become side-tracked by this rebuild issue, thinking I might solve my editing problem in the process.  However, the two might be completely unrelated.
    I'm still trying to figure out what I changed (if anything) that might have caused the spinning beach ball.  I can think of only one thing, and it has to do with previews--but I had better put that aside for now, until I can move ahead with this thumbnail issue (or just ignore it, if I can't fix it, as I was doing before the problem occurred, without apparently affecting the editing efficiency, prior to 48 hours ago).
    I have customers waiting patiently, but Aperture is stalling my ability to generate income.
    Were it not for this community--and particularly your help over the last 24 hours--I would be much more anxious!
    Cheers,
    Patrick

  • Aperture 2 thumbnail quality grainy on imports

    I am migrating to Aperture because it is lightning quick in managing with 1000s of images. I am particularly pleased with how it allows quick access to high-quality thumbnail images of photos in a large project. I should note, that my imports are referenced to folders elsewhere on the DB. I do not copy masters into the vault.
    My issue: Aperture has variable/flaky treatment of imported project thumbnails. If I choose the Import icon arrow, the chosen imported folder photos show high-quality thumbnails. Conversely, if I chose the file menu option "Import Folder as Project", imported folder photos get grainy thumbnails--but then become high-quality IF I select individual photos, which then get properly rendered.
    I generally like the "Import Folder as Project" method for importing folders because it is quick and it properly named the aperture project with the title of the referenced photo folder. The Import icon button requires several additional steps and is cumbersome for importing 100 photo folders from the HD, but it at least has the virtue of giving me what I want-which is high-quality thumbnails a la iPhoto.
    Does anyone have an explanation for the different treatment of thumbnails? Program preference settings are same for both approaches, yet the thumbnails spit out by the imports are qualatatively different.
    I suppose a variation on the above question would be, how to get Aperture to automatically generate high-quality thumbnails involving multiple photos? Currently the only option would be to manually select each photo one-by-one, which is impractical.

    I just installed Aperture 2 on a PB G4 and 10.4.11:
    it works and manage D300 and D3 raw...
    The only problem is that trial version will not convert your previous 1.5 library (there is no option yet to upgrade in the Italy store).

  • Aperture Library Thumbnails

    I have a problem I cannot figure out. I have 155,000 photos in 1120 projects in A3 (ver 3.2.4). My photo files are referenced on external hard drives, and the Aperture library folder resides on my imac hard drive in the pictures folder.
    I started to remove previews in the Aperture library to make space because my 500GB internal hard drive is almost full. When I got into the Aperture folder I found this:
    My preview folder is 39GB for 488,000 items and my thumbnail folder is 173GB for just 4504 items. What is happening here?
    I don't understand 488,000 previews, and how can I have 173GB of thumbnails for only 4504 items?

    First off going into the library like that to remove anything is a bad idea. You should be using the Aperture command delete previews. In addition you need to turn off previews not just in the Preferences but also in the projects or else Aperture will juts regenerate them.
    As for the sizes issue. The Aperture library is a database, even though you can open it up and see some regular files and folders the entire package acts as a database. Taking the size of different pieces of ti is usually not vert helpful.
    Each image can have multiple thumbnails as you will see if you look in the folder. In addition in order to speed ip operation there are two actual database files in the Thumbnails folder in which Aperture  caches recently used thumbs (at least as near as can be figured out trying  to reverse engineer it).
    As for the item count remember each of the folders contain more then just a collection of  image files. Every preview is stored  in its own subfolder.
    Again you should not be managing the Aperture library as if it was a regular folder of images or data. If your short of space on the library drive you can delete the previewss from within Aperture and set Aperture up to not regen them and also not to create new ones. Remember this will have some negative consequences especially with referenced originals.
    regards

  • Aperture 2: Thumbnails are squished

    I have an existing project which I have not modified for some time. All of a sudden some, but not all, of the thumbnails for a particular project that you see in the browser are "squished". The people in them are, well, short and wide.
    These are referenced files. My Lumix DMC-LX2 takes a 16 x 9 picture. The "squished" files are those which were shot at 2360 x 4208 with the camera rotated 90 degrees to get maximum height and minimum width, such as when taking a picture of the Grizzly Giant in the Mariposa grove of Sequoias in Yosemite.
    If I look at the Pixel Size in Aperture it shows 4224 x 2376 instead of the correct 2360 x 4208. It is shortening and widening a tall picture to fit into a wide box.
    The original files look fine in Finder. I have tried to regenerate the thumbnails, but get the same result. I tried the edit the pixel size field to switch the numbers but it can't be edited.
    How do I get thumbnails to show correctly?
    Thanks!

    I discovered the solution, if you import the folder as a library, it converts it to the new format with no problem

  • Aperture Import thumbnails not clear

    I'm importing uncompressed raw from a Nikon D300 into Aperture 2.1 on a Mac Pro, Leopard. The thumbnail images prior to import are not clear and actually appear jagged if I view large. Images are fine after import. Was wondering if this is normal or if I need to correct something in my process. Thanks for any help.
    Tom

    Aperture generates the "real" high-quality thumbnails. Whatever's on the camera as thumbnails are grab-bag. Don't worry about it

  • Any solutions to the thumbnail building yet?

    Every zoom, sharpen, brush stroke I do requires AP3 to build a new thumbnail taking 5 to 10 seconds or more. Why?

    Every zoom, sharpen, brush stroke I do requires AP3 to build a new thumbnail taking 5 to 10 seconds or more. Why?

  • Aperture movie thumbnails bug

    Hi,
    Aperture fails to show thumbnails for all videos from my Samsung NX10 that I import into Aperture. Rebuilding thumbnails doesn't help. The weird thing is, the thumbnails are not just black, but noisy or distorted versions of other (non-Samsung) videos that are in the library. When I resize the Aperture window, the thumnails change randomly.
    Screenshot:
    Has anyone seen something similar?
    Also, iMovie hangs when trying to browse the Aperture video library, might that be related?
    Thanks
    Andy

    This still happens to me, even in the final version of Aperture.
    The way I get around this for video is I do a cmd-shift-O to open the video in QuickTime Player 7. (I have QT Player 7 as my video editor.) Aperture will create a stack and make a duplicate version of the video and open the video in QT Player. I then save and close all of the videos and return to Aperture. I deselect all the selected videos. You will then see that all of the duplicated videos now have a proper thumbnail.
    You can then delete the original with the scrambled thumbnail, the duplicate is exactly the same as the original in size, so I'm not losing any resolution. The only caveat is that the duplicate won't be in any project folders, light tables, etc. So you will want to add the video duplicate to the projects that the video is a part of, if you care.
    I know this is an old thread, but I just thought that I'd throw this hint in before this discussion gets archived.
    I sure beats rebuilding your Aperture database; the time involved and the possibility that it doesn't get fixed anyhow.
    P.S. If you get a message that the video doesn't open in QT Player because it is not a supported format; quit and relaunch Aperture.

  • CS6 E Bridge Slow to load thumbnails, 'building criteria'

    When Bridge opens on the folder it was last opened/closed in, it takes a long time to load, constantly 'building criteria' as if all the images are newly imported. I've searched the forums, have tried all the tweaks and settings, but it's still iceberg slow.  Bridge CS5 is noticeably quicker, as if the cache info is being read immediately. CS6 is behaving as if the cache file has been deleted. It hasn't. I have tried the "flush the cache" to see if maybe it's corrupted. No joy. I have boosted cache size. No joy. I've compacted, automatically exported cache to folders, everything... Nothing seems to fix the snail slowness.
    All Adobe updates have been applied.
    i7-2600s @2.80GHz
    8 gb DDRw ram
    Nvidia GeForce GT420 1gb DDR3
    6+ tbs hd space.

    I could understand the glacial slowness if the beta version had also been so slow. Or if CS5 Bridge was also as slow.
    Did not read this whole (long) thread but in general when a previous version of Bridge did work faster then the following this almost certainly is related to your system itself.
    While building criteria in filter panel has a mind of its own and especially when opening a second window to fast (when first window is just finished caching or building filter panel) it may take ages. closing this window and open a new one usually succeeds.
    However when this always takes a long time the problem seems related to the cache (most Bridge problems are...)
    Purging cache using preferences or menu commands is not always the correct solution. Using Bridge CS5 and PS CS6 is also not the perfect solution.
    If you can spare the time you should consider a proper back up of custom settings, actions tools, keywords, templates etc. and a complete reinstall.
    I don't have the correct info for Windows and searching on Adobe.com isn't easy anymore. Here are some old Knowledge base articles (it's about CS4 but changes are locations are still the same)
    http://helpx.adobe.com/photoshop/kb/move-actions-presets-workspaces-photoshop.html
    http://helpx.adobe.com/photoshop/kb/preference-file-functions-names-locations-1.html
    and also read about the Adobe Cleaner Tool and decide if this is an option for you.
    http://www.adobe.com/support/contact/cscleanertool.html
    If you decide to reinstall:
    Deactivate the software and use the official uninstaller that comes with the application itself and then use the clean tool for Adobe:
    Double check if your Cache folder has been deleted (I'm on Mac, don't know the location for Windows but on Mac it is in the user library caches folder)
    Install CS6 again. Obvious you have to set your custom preferences again and also need to recache your files but if you have a main folder with many subfolders containing the files just select the main folder and in the menu View select 'show items for subfolders' and let it do it's caching overnight.
    In my experience every new version of CS has been faster and more stable (well, except the disaster CS3 version for Bridge...) then its predecessor.

  • Why doesn't Aperture rembmer thumbnail size when turning on/off viewer?

    I noticed that when I turn on/off the viewer by pressing V, the thumbnail in the browser will go back to the smallest size. Do I have a corrupted preference file or something like that?
    Am I the only one experiencing this annoying behavior?
    Thanks for any input.
    Chris

    Thanks for these suggestions.
    I have added the sites to the trusted sites in IE and that didn't help.
    Things are a bit more complicated with the global security settings of the flash player. When I click your link, I see the note (Note: The Settings Manager that you see above is not an image; it is the actual Settings Manager itself.), but no settings manager, so I cannot click any tabs. I can rightclick to go to global settings, but I can find no global security settings. A complicating factor is that I'm located in Poland and even though the installer correctly notes that I'm running an English language Windows system, it will only install flash player in Polish - and translations are usually not so good. So I have an "advanced" tab in the settings manager and I added my secure sites to the trusted sites, even though it says this is for programmers only. Anyway - this didn't help either.
    Please help, as this problem has cut me off from my bank account!

  • Cannot Import Photos. Fails at Thumbnail Build

    It worked with Beta, but not with version 1. I delete the DB (My Pictures\Lightroom), start up Lightroom, and select Import. Whichever type of file that I choose, jpg, psd, nef, or dng, I get the message that Lightroom has encountered a problem and needs to close.
    System is Thinkpad a31p, 1.7GHz, 1GB RAM, XP-SP2, C: 60GB, d: 80GB, ATI MOB FIRE GL 7800, 1600x1200 at level 8.133.2.1.1-061116a.
    It happens when I set the res to 1280x1024, happens when I boot into safe mode (I'm impressed that Lightroom starts up in 640x480).
    Any ideas?
    John Gregson

    I got it working. I uninstalled the ATI drive and used the generic VGA driver, but still experienced the xC0000005 in kernel32.dll. But when I reinstalled the ATI driver, it now works. Baffling.
    John Gregson

  • 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 to build thumbnails on import?

    I am new to Aperture, and have just imported my photo library of 19000 photos into Aperture as referenced files. I know they are referenced because I have the little arrow bottom right.
    I have the preview pref set to not build previews for new projects. I also have the "maintain previews for this project" unchecked.
    The actual import took an hour or so during which it said "importing" next to the cog wheel at the bottom of the window.
    Now it says "thumbnails" in the same place, and has been doing this for a couple of hours now.
    At this point the library is 8 Gb in size but I have no idea how far through the thumbnail building it is.
    I am a bit surprised at the size, since there shouldn't be any previews, and also how long it is taking to build just thumbnails.
    Does what is happening sound correct? How big should a 19K library with no previews be? and how long would you expect the thumbnail building to take?
    I am doing this on my Mac Pro, BTW.
    Thanks for any input.
    PS (edit). When I scroll through the entire 19000 by having the cursor on the top project level in the projects window, the thumbnails appear extremely quickly.
    Also, I assume that if it is building previews instead of thumbnails, it would say "previews" next to the cogwheel?
    Message was edited by: Mike Boreham

    Just discovered the "show Activity" window, which shows that it is building thumbnails (not previews) and that it has 6000 more to do.
    So that probably answers my own questions, unless anyone has any insights, for which I would be very grateful.

  • How do I stop Time Machine from backing up Aperture thumbnails?

    Hi,
    My 2TB backup drive recently became full, and I became curious as to what was filling it up. I wrote a perl script to analyze the Time Machine backups, and I noticed that over 50% of my backup was filled with AP.Thumbnails and AP.Minis from the Aperture project directory. In particular, the AP.Thumbnails files in the backup consumed 737 GB of disk space!
    The problem with the thumbnails files is that they are a single file that contains all of the thumbnails for all of the 40,000 photos I have in Aperture and it is now 20gb in size. Every time I add a new file to Aperture, the thumbnail file changes, and I get a new 20gb of data added to my backup. I add photos often which means that most of my backups have 20gb of Aperture files (which are easy to rebuild and don't need to be backed up).
    I decided to try and stop Time Machine from backing up these files, and there seems to be no way of doing so (without telling Time Machine to skip backing up my entire Aperture project which I don't want to do). In Finder, you can do a "show package contents", but the Time Machine GUI doesn't allow this.
    I tried to tell Time Machine to exclude the files via the GUI, but Time Machine sees the Aperture Library as a single package and won't let me exclude individual files from within the package.
    I googled around, and found the attribute that Time Machine puts on files to exclude them from the backup. I used xattr to set the attributes:
    xattr -w com.apple.metadata:comapple_backupexcludeItem com.apple.backupd <filename>
    I also used this command on the iPhoto thumbnail files.
    I used spotlight to find all of the files with this attribute using this command:
    sudo mdfind "comapple_backupexcludeItem = 'com.apple.backupd'"
    This command returned the iPhoto files, but did not return the Aperture files.
    However, if I run "xattr" on the Aperture files, the attribute does exist!
    During my next time machine backup, the iPhoto files were skipped as I wanted them to be, but the Aperture thumbnails were backed up again
    I thought that maybe time machine was looking at the aperture package as an atomic unit, but iPhoto is stored as a package as well, and the attributes worked there on files inside the package.
    Does anyone have any idea why time machine is still backing up these files? Is there any way I can get around this?
    It seems to me to be an incredible oversight on Apple's part since both tools are Apple. The thumbnails files are very expensive to backup, and they are not necessary for backup since the are easy to rebuild from the original photos which are also backed up.
    Thanks,
    Ron

    Shadow99999 wrote:
    Hi,
    My 2TB backup drive recently became full, and I became curious as to what was filling it up. I wrote a perl script to analyze the Time Machine backups,
    No need to write your own script for that. there are a couple of already made nice GUI tools for this - TimeTracker http://www.charlessoft.com/ and BackupLoupe http://soma-zone.com/BackupLoupe/
    and I noticed that over 50% of my backup was filled with AP.Thumbnails and AP.Minis from the Aperture project directory. In particular, the AP.Thumbnails files in the backup consumed 737 GB of disk space!
    The problem with the thumbnails files is that they are a single file that contains all of the thumbnails for all of the 40,000 photos I have in Aperture and it is now 20gb in size. Every time I add a new file to Aperture, the thumbnail file changes, and I get a new 20gb of data added to my backup. I add photos often which means that most of my backups have 20gb of Aperture files (which are easy to rebuild and don't need to be backed up).
    I decided to try and stop Time Machine from backing up these files, and there seems to be no way of doing so (without telling Time Machine to skip backing up my entire Aperture project which I don't want to do). In Finder, you can do a "show package contents", but the Time Machine GUI doesn't allow this.
    I tried to tell Time Machine to exclude the files via the GUI, but Time Machine sees the Aperture Library as a single package and won't let me exclude individual files from within the package.
    I don't have aperture but I think most people exclude the whole thing from TM backups and back it up separately. but if you want to exclude a subfolder in a package that's easy too. just select the package in finder, control-click on it and select "show package contents". in the resulting finder window drill to the folder you want to exclude and drag it to the TM exclusion list in TM system preferences->options.
    I googled around, and found the attribute that Time Machine puts on files to exclude them from the backup. I used xattr to set the attributes:
    xattr -w com.apple.metadata:comapple_backupexcludeItem com.apple.backupd <filename>
    I was not aware of this method for excluding stuff from TM backups. could you provide a link to where you found this?
    I also used this command on the iPhoto thumbnail files.
    I used spotlight to find all of the files with this attribute using this command:
    sudo mdfind "comapple_backupexcludeItem = 'com.apple.backupd'"
    This command returned the iPhoto files, but did not return the Aperture files.
    that's because Spotlight never looks inside packages unless you start a search inside a package directly. iphoto seems to be the only exception. I don't know how it's done.

  • Aperture thumbnail generation forever

    Hello
    I like to have all my pictures in one place to share them with apple tv, so I decided to give aperture a try.
    I imported all images (about 36000 from 12 years) into one aperture library.
    Before importing I switched off face detection and preview generation.
    After finishing I had a 236 GB library, but aperture starts to generate some thumbnails.
    Problem is, it freezes on generating them.
    I used the activity window to hunt down what is happeing and found out that it stops when it comes to a specific picture.
    So I managed to
    1) start aperture
    2) open activity window
    3) stop the thumbnail generation when it starts
    4) delete the picture where the aperture have problems
    This way I managed to get from about 5700 thumbanisl to do to a number of 3500 thumbnails to do, but aperture keeps freezing at a single pic (the bad one)
    But now, aperture starts thumbnail generation so quickly that I cannot open activity window and stop the progress before it reaches the bad one.
    @Apple: could we have an option like "safe start" that won't schedule any processes for thumbnails before the user wants it?
    So, any ideas out there? I tried everything I found like repairing, rebuilding, no help.
    Is there any kind of log to look into? I am a newbie in mac os and aperture.
    Regards
    Klaus

    This "bad" one is a video, some of the former bad ones were videos too, so does aperture have a problem in general with video files? Maybe its a good idea to just import all pictures and do the videos in a separate step afterwrds? Otherwise with 36000 pics (and about 300 videos between them) this is tedious...
    Klaus,
    Aperture may have a problem with videos, if you have a problematic video codec installed, if the video is corrupted, or incompatible with Aperture. What kind of videos did you import?
    If you can, delete the whole project, so that you do not need to select the video and reimport only the image files.
    Check, if you have the 3ivxVideoCodec installed - if yes, remove it,
    see: Aperture 3: May be unresponsive or have slower performance with third-party video codec
    This codec could have been installed for example by FlipForMac.
    If you do not want to delete all of your last import, you could try to delete the bad video directly from the Aperture library package:
    Quit Aperture. Ctrl-click the Aperture library and select "Show Package Content" from the pop-up menu. Open the "masters" folder and navigate to the Year-Month-day of your last import. If you can find the video there, remove it, but don't change anything else. Afterwards the video should show as missing. Delete the version from the library. The dates in the Library package are based on "Import session", not capture dates.
    Before manipulating the Library, make sure you have a current backup.
    Regards
    Léonie
    A list of supported videos is here, but it is not exhaustive:
    Aperture 3: About Video and Audio formats in Aperture

Maybe you are looking for