Aperture won't export

since yesterday i encounter the same problem as some described before.
Aperture 'refuses' to export my foto's.
It keeps saying 'exporting' in the bottom of the screen and quitting the program is not posibble, the only solution is to perform a forced stop.
When i open the program afterwards there's a message where the prog advises to repair the library.  (which is not the solution to the problem)
any ideas how to fix this irritating bug? my OS is V 10.2.8 & i have the latest version of Aperture 3.4.1 (which appears to be useless now)
thx for the feedback !

my OS is V 10.2.8
You mean Mac OS 10.8.2, right?
Does Aperture hang when exporting any image, or does it only happen for some of your images? Are you trying to export versions or original images?
Sometimes Aperture hangs, when it is processing a single, corrupted image.
If the problem only occurs with certain images, remove them from your library, but if you are having this problem with all images, try the Aperture 3: Troubleshooting Basics
I'd start with removing Preferences and presets, and then try the other options.
Regards
Léonie

Similar Messages

  • Aperture won't export all photos to Mail

    Most of the time, Aperture won't export all my chosen photos to Mail. If I chose 8 photos, it may only export 4 of them and no matter what I do, nothing changes. Tried it on Entourage and it was exactly the same. Size is not the issue, I'm sending them in small sizes and the total attachment is about 1 MB. Anyone had this issue and know what to do? I do have NIK plug ins installed if that helps any.

    I would suggest you do a library repair to see if that clears it up.
    See Aperture 3: Troubleshooting Basics

  • Aperture won't export work copies (apparently after OS X update to 10.6.6)

    Hi folks!
    I'm really stuck. Some weeks ago (maybe since the 10.6.6 update) Aperture is behaving strange. As I do not use Aperture every day these problems were not discovered in one day. So first I thought maybe some cache or whatever is "irritated" and a reboot would fix everything. Then I thought back and now think that all these problems started after the 10.6.6 update.
    - Can't import from the harddrive (some folders open, others won't) - no spinning beachball but no import either.
    - Can't export work copies (exporting "originals" works) - sometimes the spinning beachball appears instantly, other times no reaction after right-clicking on a thumbnail or photo to export-work copy and a spinning beachball shows up on the third attempt(!)
    - and some other things (for example I get a spinning beachball when I click on the "import" tab in the preference
    What did I try? After sucking out google and this forum for these problems I did the following in this order:
    - Repaired permissions in Apertures library with Aperture-tool (command-option during Aperture start up) - no success
    - Repaired database in Aperture library with Aperture-tool - no success
    - Recreated database in Aperture library with Aperture-tool - no success
    - Reinstalled Aperture from DVD and 3.1.1 update - no success
    - Removed .plist files as described in a KB-article - no success
    - Moved away all installed plugins - no success
    - Moved Aperture to the trash, made OS X "forget" Aperture and reinstalled Aperture and 3.1.1 update - no success
    - (Re-)installed 10.6.6 combo-update as suggested in this forum - no success
    - Played with 64- and 32-bit options - no success
    I must say I am pretty p*ed-off at the moment as I can' export pictures that I really really need to prepare my honeys invitations-cards for her 40th birthday!
    Any other ideas than switching to light room an photoshop?
    Please help! Any hint is welcome!

    Assuming your machine is within recommended specs and there is at least 15% HD space available, I am leaning towards a bad 10.6.6 or Aperture install.
    You mention having run the 10.6.6 combo and re-installing Aperture, so not sure what route you would want to go:
    1 - Try removing all trace of Aperture (manually) and installing again.
    2 - Try booting to safe boot mode (although, I have noticed sluggish performance on my machine after doing this a couple times, so am reluctant to recommend).
    3 - The time consuming clean install of 10.6.6 which is a last resort - IMHO.
    Other than that, I can only hope someone else has a better option for you.

  • Aperture won't export : Retina MacBook Pro

    I've been struggling with getting all sorts of basic stuff to work on my supposedly top spec 15" Retina MacBook Pro, the latest is that it can't seem to export from  Aperture.  Finder really slow, attaching files to emails takes ages to open etc - so wondering if it is part of this problem.
    Has anyone else experienced this.  Obviously being a Pro App I'm going to be charged handsomly to talk to anyone at apple.
    Occasionally it can export a single image at a time, the export folder location takes ages to open.  Select multiple images and select "Exprt Versions" and absolutely nothing happens.  Export originals, and it crashes Aperture. I'm begining to wonder just how far you can throw a MacBook Pro.
    It really is the most disapointing Mac I have ever bought, lovely display, but if the computer behind it doesn't function its all a little pointless.
    Done the usual reboot, disk permissions etc.
    Thanks for any pointers
    Stephen

    Stephen,
    It is new (ish, about 90 days, and covered by Applecare) but calling Apple help - as I have previously - as soon as you mention it is Aperture they want to charge money - a lot of it and with no guarantee of results - to talk about any issues as it is a Pro App - pity it doesn't behave like one!
    Finder really slow, attaching files to emails takes ages to open etc - so wondering if it is part of this problem.
    I'd really let the Apple Store sort out the system and hardware issues, as long as your Applecare lasts.
    Make a backup of your system, best a bootable clone on an external drive (so you can easily revert back to your current state, or run your apps  by booting into the clone) and reinstall the system without any third party apps and without Aperture, only the basic set of applications.
    Then test your mail and Finder, and if issues remain, go back to AppleCare and present them with the proof, that it is the hardware and not the software.
    You may find, that it is not Aperture at all, that is causing the problem, but an incompatible plug-in, kernel extension, "helper" applications, duplicate fonts, problems in the Aperture library inherited from iPhoto, incompatible videos in the Aperture library, an unsuitable drive hosting your Aperture Library. Where is the library located, btw? On an external or internal drive?
    Regards
    Léonie

  • Aperture won't export to photoshop

    I keep getting an error message when exporting from aperture to CS4, it is totally random, any clues greatly appreciated.

    Sharing the exact text of the error message would save us the step of posting this reply.
    What do you mean by "exporting from aperture to CS4"?  Are you using the Aperture command "Edit with Adobe Photoshop ... "?

  • Aperture won't export full-size jpegs

    I'm trying to export full-size jpegs, but Aperture is sending out 24 KB images. I'm selecting the edited versions I want, then going File>Export>Version. I have the dialog set to JPEG - Original Size. Still, what comes out is a thumbnail.
    Aperture 3.4.5
    OSX 10.8.5
    MacBook Pro
    2.4 GHz Intel Core 2 Duo
    4 GB Memory

    Check, if your export preset "JPEG - Original size" is still set correctly.
    In the "Export" panel set the "Export Preset" pop-up to "Edit".
    In the "Edit" panel make sure, that "Size to" is set to "Original Size", and the quality to a high value, at least 10.

  • Aperture won't export images despite preset modification

    I've just downloaded Aperture as an App to enable me to export my photos to a photo library. They have very specific criteria ... 300ppi/image size at least 1750 x1750/level 12 Jpeg or TIFF/1MB-100MB file size etc. I have entered this criteria in Aperture presets but they still fail ... any ideas what I'm doing wrong.
    The error message on their site says that the file is only 753KB instead of 1024kb (1mb) even though the info on the image says it is over 1mb/ the size isn't the same as in the preset and that it is only 180ppi - though I realize that the preset asks for dpi which isn't the same as ppi.
    Sorry, complete beginner and really need help.

    Hi Bob
    I tailored the preset to fotolibra's criteria so I put in:- JPEG - image quality 12 - fit within pixels - width 3000 height 2400 and various amounts in the dpi - I've tried 180/300/320 - all trying to get 300ppi (but the fotolibra error message always says the image reads 180ppi!)Everything else I've left but I must say I have changed these boxes many times trying to find the right combination. I've tried TIFF and different sizes - so far nothing has been right.
    After tailoring the preset I then went to fotolibra and used their upload engine which asks me to select the image which I choose from Pictures as it doesn't give me the option to choose from Aperture. The metadata for the image I have been trying to upload to them says it is 4000x3000p (12mp) and 6.52mb which should fit in with fotolibra's requirements but by the time the image gets there the data had changed to 753kb and the dimensions have also changed and are too small on the shortest side.
    So the image has somehow become compressed in transit - unless it ignored my customised preset altogether?
    Hope this is understandable! Any help gratefully received, Bob
    Thanks
    Angie

  • Aperture 3.4.1 won't export photos OS 10.8.2

    Aperture 3.4.1 won't export photos OS 10.8.2. ?? Just sits there, no spinning globe, just nothing.

    I have 10.8.2 and Aperture 3.4.1.
    No problem to export originals and versions.

  • Aperture 3 won't export at all: images held hostage

    Complaining about Aperture 3 is almost pointless now with the mess the program is obviously in, but I encountered a rather distressing problem I hadn't seen reported yet.
    I can't export anything. All of my photos are locked into Aperture. If I select any export option (say, Jpeg 50%) Aperture will start exporting it and never finish. It will sit there for hours if I let it. The file will never export. Activity viewer just shows Aperture attempting to export the image and never finishing. Basically, it's holding my images hostage.
    The crashing and hangups I can deal with (for now), but if I can't export a photo the program is literally useless to me. If anybody knows a way to fix this issue, please help.
    Message was edited by: Padriac

    I have now solved my problem, and it only cost me a day :-|
    I had a few corrupted master files. Aperture was running a task to process a lot of pictures, and whenever it was reaching such a corrupted file, the task would hang, and it would not be possible to start other tasks like exporting pictures.
    That rebuilding the library helped temporarily was just because after a rebuild Aperture would spend some time updating Places information, before it would start the processing task that would then eventually hang.
    I identified and deleted the corrupted pictures, which solved my problem. Finding the pictures was something that I had to do by hand, though.
    Since the problem is usually not with the pictures that one is working with at the moment, but with completely unrelated pictures, one possibility is to export the current project as a library and then work with just that library.
    So the problem was with corrupted files that I had in my library. Still I think that Aperture should handle a situation like this more gracefully. If a task hangs, it should be possible to learn which picture it is currently working on and to kill the task.

  • Some photos won't export as versions

    A proportion of photos from various projects won't export as versions, either JPGs or TIFFs. The files themselves aren't corrupt as I can open them in Photoshop and then save them as JPG or TIFF files or whatever I want. I though it might be library that was corrupt but I rebuilt the library and the probem still persists and with the same photos.
    I have my library stored on a RAID system. I've stored it before on a RAID setup but always using Apple's formatting software to RAID the HDs together. This is a hardware RAID system so the computer reads it as 2TB when it's really two 1TB drives together. It is then formatted with the standard Apple DIsc Utility. This is the only difference from before and I've never had the problem until now.
    Could this be the problem? Could fragmented files on this drive be the problem? Any suggestions welcome.

    The way you have described your issues sounds like you are running a referenced library where you have easy access to the files through the finder. Is it possible that in the process of accessing files through the finder that some have been moved or had attributes changed? The way to identify this is by the badges that Aperture displays on an image, pg.291 of the manual see below.
    To display badge overlays on images in the Viewer:
    1 Do one of the following:
    Â Choose View > Metadata > Customize (or press Command-J).
    Â Choose Aperture > Preferences, then click Metadata.
    2 Select the Viewer checkbox.
    3 From the Viewer Set 1 pop-up menu, choose a metadata view that includes badge
    overlays. Some examples are General and Ratings, as well as Viewer-Basic and
    Viewer-Expanded.
    4 Close the Preferences window.
    Badges are now visible in the Viewer.
    Tony

  • Podcast won't export from Garageband to iWeb

    Hi all
    Help appreciated with this. I do a two hour music podcast (www.whatyouwantradio.com also available at http://soundcloud.com/whatyouwant-radio) which is created in Garageband and then exported to iWeb for uploading to my website. I've been running this, with few problems, since April 2009.
    Recently the garageband podcast won't export to iWeb. It's random, and I seem to have been able to bypass it by changing the filename slightly, or adjusting the quality at which it is exported (I like to export at 320mps for best quality - big files but no complaints from the 100 or so listeners. Could be more - who knows as I can't get stats from iTunes. But I digress). However, the most recent podcast, which is already available on Soundcloud, just won't export. It goes through the motions (mixdown etc.) but nothing appears on iWeb on the other side. No error message, nothing. I know that memory has also been an issue in the past but right now there is plenty to spare (5.37GB at last glance).
    I'd really be grateful for some help on this, I'm at a bit of a loss - no error message, no clue. As I say, this podcast has been going for nearly three years and it's only recently I've had this problem.
    Cheers,
    Stuart
    Mac OS X 10.6.8
    Garageband '09 5.1
    Model Name:
    MacBook
      Model Identifier:
    MacBook5,1
      Processor Name:
    Intel Core 2 Duo
      Processor Speed:
    2.4 GHz
      Number Of Processors:
    1
      Total Number Of Cores:
    2
      L2 Cache:
    3 MB
      Memory:
    4 GB
      Bus Speed:
    1.07 GHz
      Boot ROM Version:
    MB51.007D.B03
      SMC Version (system):
    1.40f2
      Serial Number (system):
    W8912A098QT
      Hardware UUID:
    CE258311-95FB-5BB2-BF43-DC494598B584
      Sudden Motion Sensor:
      State:
    Enabled

    Just a further note on this. I tried a couple more times yesterday to export the file. Starting out with over 5GB of memory, by the time I had tried twice this had gone down by a couple of GB. Still no export. This morning I noticed some new files in the trash that were from around the time of the failed exporting:
    Note sure if you can see that, but I'm guessing the files are something to do with the failed export? Does anyone have any thoughts? Either way, this problem is still annoying the **** out of me...
    Stuart

  • Aperture won't open, library won't load. Please help!!!

    My Aperture won't load. My Safari doesn't work either, but I care more about recovering my Aperture photos. I can do without Safari. Here is the problem report:
    Process:         Aperture [14235]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.5 (3.4.5)
    Build Info:      Aperture-320090000000000~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [181]
    Date/Time:       2014-01-17 15:24:36.725 -0800
    OS Version:      Mac OS X 10.7.5 (11G63)
    Report Version:  9
    Interval Since Last Report:          76427 sec
    Crashes Since Last Report:           1
    Per-App Crashes Since Last Report:   1
    Anonymous UUID:                      74929CF4-B435-4C2D-875E-596F2DDB8E2C
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: @rpath/iLifePageLayoutCore.framework/Versions/A/iLifePageLayoutCore
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: image not found
    Binary Images:
           0x1012e6000 -        0x101a43fff  com.apple.Aperture (3.4.5 - 3.4.5) <C0ED95AC-8B39-380E-91E4-6B7BB3DD013F> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x101c66000 -        0x101c6fff7  com.apple.PhotoFoundation (1.0 - 20.12) <9E3EA726-0AE7-3A40-AF03-EA7BDF21C099> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
           0x101ce5000 -        0x102243fff  com.apple.RedRock (1.9.4 - 321.3) <4685E533-6C92-372F-8F28-83BDD4AF5082> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
        0x7fff60ee6000 -     0x7fff60f1abaf  dyld (195.6 - ???) <C58DAD8A-4B00-3676-8637-93D6FDE73147> /usr/lib/dyld
    Model: MacBook3,1, BootROM MB31.008E.B02, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB, SMC 1.24f3
    Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
    Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.15)
    Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST9120822AS, 120.03 GB
    Parallel ATA Device: MATSHITADVD-RAM UJ867PD
    USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0229, 0x5d200000 / 3
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
    What can I do to get my Aperture library back?
    Thanks!

    My Aperture won't load. My Safari doesn't work either, but I care more about recovering my Aperture photos. I can do without Safari. Here is the problem report:
    Process:         Aperture [14235]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.5 (3.4.5)
    Build Info:      Aperture-320090000000000~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [181]
    Date/Time:       2014-01-17 15:24:36.725 -0800
    OS Version:      Mac OS X 10.7.5 (11G63)
    Report Version:  9
    Interval Since Last Report:          76427 sec
    Crashes Since Last Report:           1
    Per-App Crashes Since Last Report:   1
    Anonymous UUID:                      74929CF4-B435-4C2D-875E-596F2DDB8E2C
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: @rpath/iLifePageLayoutCore.framework/Versions/A/iLifePageLayoutCore
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: image not found
    Binary Images:
           0x1012e6000 -        0x101a43fff  com.apple.Aperture (3.4.5 - 3.4.5) <C0ED95AC-8B39-380E-91E4-6B7BB3DD013F> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x101c66000 -        0x101c6fff7  com.apple.PhotoFoundation (1.0 - 20.12) <9E3EA726-0AE7-3A40-AF03-EA7BDF21C099> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
           0x101ce5000 -        0x102243fff  com.apple.RedRock (1.9.4 - 321.3) <4685E533-6C92-372F-8F28-83BDD4AF5082> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
        0x7fff60ee6000 -     0x7fff60f1abaf  dyld (195.6 - ???) <C58DAD8A-4B00-3676-8637-93D6FDE73147> /usr/lib/dyld
    Model: MacBook3,1, BootROM MB31.008E.B02, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB, SMC 1.24f3
    Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
    Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.15)
    Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST9120822AS, 120.03 GB
    Parallel ATA Device: MATSHITADVD-RAM UJ867PD
    USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0229, 0x5d200000 / 3
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
    What can I do to get my Aperture library back?
    Thanks!

  • Aperture Won't Open (tethered shooting error?)

    Aperture won't open, I was shooting tethered and it bogged down on importing images. After waiting a few minutes I forced quit the application. Since then I get this error. I have deleted the file from my Applications and reinstalled from the App store.
    Process:         Aperture [276]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.2.2 (3.2.2)
    Build Info:      Aperture-201096000000000~2
    App Item ID:     408981426
    App External ID: 5333832
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [121]
    Date/Time:       2011-12-19 22:11:16.598 -0500
    OS Version:      Mac OS X 10.7.2 (11C74)
    Report Version:  9
    Interval Since Last Report:          406994 sec
    Crashes Since Last Report:           49
    Per-App Crashes Since Last Report:   37
    Anonymous UUID:                      DB4F401E-4CC2-4F7A-9DAF-E8F1F045CAD1
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: no suitable image found.  Did find:
              /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
    Binary Images:
           0x100000000 -        0x10078bfef  com.apple.Aperture (3.2.2 - 3.2.2) <AD96E4EA-580B-3585-8783-6A2458AEA857> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x100975000 -        0x100e25fef  com.apple.RedRock (1.8.2 - 231.95) <15582067-FB9A-3057-988F-85AB51721A33> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
           0x101096000 -        0x101099ff7  com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <FED42410-3DB7-3CF4-BF3B-AE1650576C9D> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
           0x10109f000 -        0x1010affff  com.apple.iLifeAssetManagement (2.0 - 2.33) <B7102C48-4455-313B-9D2B-14A3DE14D5B8> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
           0x1010c1000 -        0x10116fff7  com.apple.MobileMe (11 - 1.0.3) <50A10074-AB15-39EE-952B-30D6E5CEB395> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
           0x200000000 -        0x20000aff7  com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <E8A0F472-C8AA-3F5F-9F85-BDC6F9E260CB> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
        0x7fff6948b000 -     0x7fff694bfac7  dyld (195.5 - ???) <B372EB7D-DCD8-30CE-9342-E06CADD7CACA> /usr/lib/dyld
        0x7fff82bfa000 -     0x7fff82bfafff  com.apple.Cocoa (6.6 - ???) <7EC4D759-B2A6-3A99-AC75-809FED1500C6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
        0x7fff831d8000 -     0x7fff831d8fff  com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
        0x7fff833f5000 -     0x7fff835f7fff  com.apple.AOSKit (1.01 - 87) <E00ACA45-14A4-3894-9001-DDD39667B107> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
        0x7fff84b03000 -     0x7fff84b6dfff  com.apple.framework.IOKit (2.0 - ???) <87D55F1D-CDB5-3D13-A5F9-98EA4E22F8EE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
        0x7fff84e8c000 -     0x7fff84e9bff7  com.apple.opengl (1.7.5 - 1.7.5) <2945F1A6-910C-3596-9988-5701B04BD821> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
        0x7fff85943000 -     0x7fff8598eff7  com.apple.SystemConfiguration (1.11.1 - 1.11) <F832FE21-5509-37C6-B1F1-48928F31BE45> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff86f7c000 -     0x7fff86f7cfff  com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
        0x7fff87eb2000 -     0x7fff8803cff7  com.apple.WebKit (7534.52 - 7534.52.7) <D858B247-71C2-395A-9A44-A0B8B0713E3A> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
        0x7fff89d8a000 -     0x7fff89d8afff  com.apple.Carbon (153 - 153) <C1A30E01-E113-38A0-95CA-99360F92A37A> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
        0x7fff8a133000 -     0x7fff8a133fff  com.apple.ApplicationServices (41 - 41) <89B6AD5B-5C75-3E83-8C2B-AA7F4C55E400> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
        0x7fff8a42a000 -     0x7fff8a5c9fff  com.apple.QuartzCore (1.7 - 270.0) <E8FC9AA4-A5CB-384B-AD29-7190A1387D3E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
        0x7fff8b3a9000 -     0x7fff8b57dfff  com.apple.CoreFoundation (6.7.1 - 635.15) <FE4A86C2-3599-3CF8-AD1A-822F1FEA820F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff8b57e000 -     0x7fff8b856ff7  com.apple.security (7.0 - 55010) <93713FF4-FE86-3B4C-8150-5FCC7F3320C8> /System/Library/Frameworks/Security.framework/Versions/A/Security
        0x7fff8c18b000 -     0x7fff8c191fff  com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
        0x7fff8ce65000 -     0x7fff8cef7ff7  com.apple.PDFKit (2.6.1 - 2.6.1) <33A0A777-8CF4-3F36-BB1A-78F8A3D7E8C2> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit

    Looking at the crash dump you posted it appears as if one of the apllication libraries got messed up.
    This entry from the dump:
    Dyld Error Message:
    Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: no suitable image found.  Did find:
    If you have a TM backup of the OS volume you could get the PluginManager file out and just copy that  but probably the easiest and quickest thing to do would be to reinstall Lion.

  • Aperture won't launch on 15" Retina MBP

    I recently moved to a Retina 15" MacbookPro. Installed Aperture (app store), and it worked fine with Lion. Upgraded to ML, and now Aperture won't launch. I read the thread having to do with a conflict with Final Cut Express. That's not me. No FCE (or and Final Cut apps) loaded on this machine.
    I've removed all existing Aperture libraries (to force the creation of a new library on launch).
    I've re-downloaded Aperture from the app store, to make sure I have a nice clean version.
    It won't launch.
    Anyone else out there having this problem?
    I suppose I could try re-installing OSX 10.8, but that seems extreme.
    Thanks in advance,
    Chris

    More info. Some good. Some not so.
    Right-clicked iPhoto library in finder and chose Aperture as app to luanch, and Aperture opened it right up.
    Tried switching to an Aperture library. Crash.
    Repeated launch of iPhoto library.
    Tried creating new Aperture library. Crash.
    Right-clicked an Aperture library and chose Aperture as app to open, and Aperture opened it up (I think I'd tried this prior to posting, without success, but can't be 100% sure of that)
    At any rate, the library I want is now open, so I should just go get some work done, but I'd appreciate any insights into what might be going on.
    Thanks,
    Chris

  • OMF won't export out of final cut pro.

    Exporting a 93min 1920x1080 HD timeline to OMF
    5 second handles tried 2 second handles as well.
    OMF won't export out of final cut pro. Get error message there is a 2 gb limit.
    Final cut 6.0.6
    Have deadline. Didn't see it on any forum. Help!! Thanks!!

    Seems like a weird thing to not be able to do since it's called final cut PRO...
    Bagging on Final Cut Pro for OMF? HA! OMF has been around LONG BEFORE FCP was introduced. It isn't an FCP issue...OMF technology is VERY old. Over 20 years I believe. I used it on Avid...and it always had a 20GB limit.
    You cannot deliver 1 track via OMF. You can ask the audio person. I know that Avid now allows you to export an AAF...but FCP doesn't do AAF. For embedded audio I think that OMF is the only way. SO you have to work within the limitations of that format.
    Shane

Maybe you are looking for