4 Replies Latest reply: Dec 21, 2012 6:46 PM by Hamper
Hamper Level 1 Level 1 (0 points)

There seems to be a hardcore persistent group of about 18 files on startup which Aperture keep regenerating previews for, it slows my system right down and I can't use Apeture until the operation is completed. I've tried all three option from Rebuilding the database to repairing it but the issue perists,I have a mostly managed Library and have read it can be down to consolodation, but those files had been consolodated long ago.


What is going on?

MacBook (13-inch Late 2007), Mac OS X (10.7.3), 4GB 667 MHz DDR2 SDRAM
  • léonie Level 9 Level 9 (79,490 points)

    As a work-around: Have you tried to launch Aperture with the "Shift" key held down? This will defer the generation of previews and you should be able to work.


    But try to find out, which images or videos are the ones, that Aperture is processing. Launch the "Activity window" directly after starting Aperture (Window > Show Activity). This window should display the version names of the images or videos that Aperture is processing. If in image is corrupted, or a video has an incompatible codec, then Aperture cannot create a preview, and will try over and over again. In this case remove the offending item from your Aperture library.

    You may see the same, if you have the 3ivx codec installed,

    see: Aperture 3: May be unresponsive or have slower performance with third-party video codec




  • Hamper Level 1 Level 1 (0 points)

    One thing that I noticed all the offending files had in common was that they were either videos or audio files (fly, mov, mp3) and not imagery. I exported the originals (I use a Managed Library) and converted them with QuickTime Player to MOV format and then imported and then replaced the file to which the problem then subsided.



    I think it might have been down to the software I originally used to convert the videos, as I mentioned some were .mov and there aren't a lot of those things flying about on YouTube, I know I would have converted it (especially when the original file name has "YouTube" in it), of which QuickTime 7 would have been used because I could embed metadata, this obviously the course I took before Aperture accepted video formats because I notice that Aperture cannot import existing (custom entered) metadata into it.



    What was really wired was that when importing files which were of the same name as the original (the one causing problems) that the file would disappear. I double checked by making a new copy of the file again and watching it import only to see it disappear before my eyes and nowhere to be found but in the Trash can, but why?



    The difference being, that I can tell, is that unlike the FLV files the MOVs were always going to be MOVs (I always output moves as MOVs) and so Aperture must be doing something automatic when the conditions are right i.e. the file name matches and sends them strait to the Trash!



    Even if I change the name of the video before importing the file it will keep doing this, not only that but the file cannot be traced back to it's location on my HDD, it just gets sucked in a lost inside Aperture, turning into a muffled (what seems to be unprocessed) image thumbnail of the video.



    But it gets even weirder as I place those files into a folder for inspection (as the Trash can won't allow for metadata inspection, for some reason the pane is greyed out and inaccessible) those videos (still registered as such) turn out to be fuzzy pictures, not pliable at all.



    However those conventions were with QuickTime X, using QT7 I was able to create (and then rename) a copy of the movie file (at almost exactly the same size in MB and so nothing was real changed!) and it imported okay. Now you might be thinking it was the way it was encoded, but one of those MOVs was always a MOV and came from QTX as a screen recording!



    I don't know what's going on?! It seems to be that Aperture still has issues with other formats other than imagery, which was a major feature of the third release.



    Now there are only two audio files that process and are done in the blink of an eye, I can live with that, thanks for your insight leonieDF.

  • léonie Level 9 Level 9 (79,490 points)

    Good to know, hat you could stop Aperture from continuously processing, but I do not yet see, what the difference is between the new video format that you are using now and that is working, and the previous video format. MOV is not like MOV, as you probably know. A Quickime movie consists of the Quicktime wrapper and a media fork containing the actual video file, and probably your Qicktime X encoded quicktime movies were using a codec for the embedded video different from the one you are using now.

  • Hamper Level 1 Level 1 (0 points)

    Err, I forgot about that but yea it's true isn't it, I just thought that them both being Apple software releases there wouldn't be much difference. There have been other videos (I'm sure?) that wern't a problem when being generated from QTX when inside Aperture, and like I said there were FLVs playing up too, I think it's Aperture at fault as well.


    I've mentioned it to them.