Aperture 2 Preferences
I recall generating previews in AP 1.5.6 to display images in iLife apps. Now that there is the option in preferences to check the "Display images in iLife and iWork" option, why would we need the checkbox for "Generate Previews"? What would be the reason to generate previews?
Jerry
The embedded JPEG in the RAW file is generated by the in-camera RAW processor. Depending on the camera, these range from poor to very good. BUT, even the very best in-camera RAW processor is not going to make the same decisions that Apple's own RAW processor does.
Consequently, the embedded JPEG preview is a reliable tool for judging content and composition, but an Aperture-generated preview is the only reliable way to visualize the color and tonality you will get from processing the RAW in Aperture.
Embedded previews are great for quick-pass editing. But, for example, if you've narrowed it down to two very similar images and want to know which one is a better candidate for some highlight-recovery and tonal adjustments in Aperture, then the Aperture preview is going to be a more reliable basis for making that decision.
Horses for courses...they each have their uses, and it's nice to finally have the option to use either one.
Similar Messages
-
Aperture Preferences - Mobile Me
For some reason when I selected the MobileMe tab in Apertures Preferences the software hangs (spinning rainbow circle) and I have to force quit. When I relaunch the application and select preferences, it still got MobileMe selected and then hangs without giving me time to deselect. Anyone had this problem??
This nagging should have stopped by now, since Mobile Me is no longer available.
Press "Learn More" once again.
Then open the Aperture Preferences, go to the "Web" tab in the "Preferences" panel, and remove the "Mobile Me" account. This should stop the alert.
If it doesn't, quit Aperture (and if you are running Mac OS 10.7. or later, log off and on again) and clear the Aperture Caches: remove the file
~/Library/Caches/com.apple.Aperture/mmsunset.plist
from your User Library. This file contains the information on the end of MobileMe and when to stop nagging.
If clearing the caches did not do the trick, remove the Aperture Preferences; see the "Aperture 3 Trouble Shooting Basics" on how to do this.
Regards
Léonie -
Aperture Preferences: can't access under Leopard
Hi,
I've recently upgraded to Leopard and Aperture 1.5.6 appears to be working fine for me after a brief test (nothing exhaustive as yet).
However, if I try to access the Preferences window from the Aperture application menu, Aperture dies 100% of the time. I choose the menu option, the beachball cursor appears for a bit, and then Aperture just quits. So at present I can't alter anything in the preferences.
I haven't managed to discover whether some other software is causing this to happen or whether it's something to do with Leopard itself. Does anyone else see this behaviour?It's solved!
I suddenly realised, after spending ages looking at the Aperture crash reports and doing other testing, that I'd completely forgotten to see if there was any useful Console output when Aperture crashed. So I had a look and found a very revealing line associated with each crash, saying:
"Custom ColorPicker class with name .DS_Store could not be loaded."
I wouldn't have expected colour pickers to be involved when merely opening preference windows that apparently don't use them, but removing the custom pickers seemed the obvious thing to try, and did indeed cause the crash to go away. So I narrowed down the search and have identified the culprit as the RCWebColorPicker which can be obtained from here:
http://www.rubicode.com/Software/RCWebColorPicker/
I had version 1.0 installed and found that a 1.1 update had been issued, so I attempted to download it. It turns out that the link to version 1.1 is actually broken and just leads to a 'not found' page, but after a brief experiment in editing the URL, I found that the following works:
http://www.rubicode.com/Downloads/RCWebColorPicker-1.1.dmg
However, version 1.1 suffers from the same problem as 1.0 (i.e. it upsets Aperture), so I mention the above just in case anyone's interested in investigating further. Obviously I wouldn't recommend installing it at present! Source code to the picker is actually available on the site, and I'm going to email the author to let him know about the problem.
The interesting thing is that I've had this picker running fine under Tiger since last year and it hasn't caused a problem with Aperture in the past, so the problem behaviour is new to Leopard.
My thanks to everyone who offered help here, and to the Apple programmer who emailed me privately. -
I can open Aperture now, but since it says Welcome Aperture, I just want to make sure my old Library is there still. I don't want proceed until I know my photos are safe. They are backed up on Time Machine and a Cloud service, too, if I need to retrive them. I had a problem where my computer shutdown during a rebuild/repair, but when I re-boot, I couldn't open Aperture. Any advice will help.
I have looked in my Picture folder and see "Aperture Library", but not "Aperture Library.aplibrary". Are they the same?
Have you set the Finder to hide the filename extensions? Then enable the extensions to be shown in the Finder Preferences (Advanced tab):
You could also have hidden the extensionin the "Get Info" panel for the Aperture Library:
Can I open this new "Aperture Library"? If I do open this new "Aperture LIbrary," will my old photo library be there?
If that library only has been created yesterday, it is unlikely, that it will contain your photos. How large is this "Aperture Library"? If it is very small, only a few MB, then it is probably a default library, that Aperture has created, when it could not find your regular library. But if it has several GB, than it can be your Aperture Library - then double click it to open it and see.
If your old "Aperture Library" is not in your Pictures folder, enter ".aplibrary" in the Spotlight searchfield in the upper right corner of your screen.
Does that turn up more libraries? -
Aperture resetting preferences on launch
My Aperture preferences are constantly being reset when launching Aperture. For example, the following preferences:
View > Inspector > Swap Position
Preferences > General > Automatically stack new versions
View > Hide Toolbar
Aperture > Commands > Custom Command Set
Preferences > Export > External Editor > CS6
Preferences > Export > External Editor File Format > TIFF16BIT
And more. Whenever I launch Aperture I must reset every one of these, every time : ( Any ideas?
Graham
grahamclarkphoto.comGraham,
this looks, like Aperture is unable to write the preferences file or your presets.
See the Aperture 3: Troubleshooting Basics on how to remove the com.apple.aperture.plist file from the Preferences folder and how to remove the command presets.
You did not say, what your Aperture version and your MacOS X version are. In MacOS X 10.7.x your user library is hidden. You open it best from the Finder's "Go" menu, from the main menu bar:
Go > Go to folder then hold down the alt/option key until the library appears in the drop down menu. Select it to open.
Also, with the new process model in Lion and Mt. Lion I'd log off and on again, before removing preferences files. Quitting an application alone will not always suffice to terminate the processes.
Regards
Léonie -
Problem with Aperture 3.6 Can't open Preferences
I had a problem with Aperture 3.6; opened a new Library from the Vault, now cannot open Aperture Preferences. When I attempt to open preferences I get a very thin vertical line about 1 ½ inches long?? Any fixes for this/ Thanks, Vic
Try to delete the Aperture preferences as described here at this link:
Get help with Aperture 3 - Apple Support
Steps to reset preference settings
To reset your Aperture user preference settings to their original state, do the following:
Quit Aperture.
In the Finder choose "Go to folder" from the Go menu.
Type ~/Library/Preferences in the "Go to the folder" field. Press the Go button.
Remove the "com.apple.Aperture.plist" file from the Preferences folder.
Restart your computer if you're using OS X Mavericks.
The locations of your Aperture libraries are stored in the preference file listed above. If you have stored your library outside the default location of ~/Pictures/Aperture Library, make a note of where the library is before deleting the Aperture preferences file. If you have more than one library, you can bring up a dialog to choose which one to load by pressing Option immediately after you open Aperture. -
Aperture strips GPS from Sharing to Flickr despite Preferences
Exporting images ("Sharing" them) from Aperture to Flickr (and also to Smugmug) strips the GPS data so that in Flickr and Smugmug no location is shown. Aperture Preferences are set to Include location info in exported photos. Exporting photos to files on my Desktop retains the GPS data.
Sharing to Flickr from iPhoto also retains the GPS - the problem is with Aperture only.
And only on my iMac. Sharing photos to Flickr /Smugmug from Aperture on my MacBook Air retains the GPS, so there's a workaround, However, I do most of my photo work on the iMac and would like to be able to figure this out.Yes, I have the same problem.
My objective was to get a few photos with geolocation onto my iPhone.
Putting them in Dropbox and downloading them from the Dropbox app worked for me.
Oddly, Google Drive seems to also strip geolocation data. -
When I export photos from Aperture to desktop or iphoto I lose pixels. The pixel dimensions are halved, despite setting the export preference to export at original size. Anyone know why or how to correct this?
Dragging an Image from Aperture exports the Preview. Preview parameters are set on the Previews tab of Aperture preferences.
Are you seeing the same results when you export using one of the export commands?
Is so, confirm that the settings in the selected Image Export Preset ("Aperture➞Presets➞Image Export") truly represent those in the Image Export Preset's name.
HTH,
--Kirby. -
Aperture 3.1.2 Preferences gone
I was making adjustments to a image and wanted to see if there was a setting in Preferences to make a common adjustment permanent. The Preferences no longer comes up, or is a narrow vertical rectangle. What happened? And, how do I fix it?
I have a similar problem, Aperture 3.6, when I try to open Aperture Preferences, I just get a very slim white line about 1 ½" long appearing on the screen. I tried what you suggested , but this didn't work for me. Victor
-
"Aperture (3.2) cannot be opened because of a problem." on MBP Core 2 Duo, 10.7.2
I recently upgraded to 3.2 from the App Store and was able to run the program until today. I am now completely unable to open it. I have tried the standard troubleshooting, including moving the application support files to the desktop, deleting the com.apple.aperture preference file, opening while holding CMD and option, and reinstalling. I have also tried moving my Aperture Library to start the program fresh. Nothing has worked; the same "cannot be opened" error persists.
I have read about other users having issues with the program constantly crashing, but that specific problem appears limited to Intel Core Duo processors, while mine is an Intel Core 2 Duo running on a MBP 3,1. I am starting this thread to find out if any with similar specs have had the same issue and known how to resolve it. Thank you in advance for your help!
For any who understand error reports, here it is:
Process: Aperture [3286]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.2 (3.2)
Build Info: Aperture-201088000000000~1
App Item ID: 408981426
App External ID: 4372644
Code Type: X86-64 (Native)
Parent Process: launchd [158]
Date/Time: 2011-10-25 08:13:23.285 -0600
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 151592 sec
Crashes Since Last Report: 16
Per-App Interval Since Last Report: 1263 sec
Per-App Crashes Since Last Report: 15
Anonymous UUID: F8A6AE56-E17C-4836-A475-FBC72F4C6A5D
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 - 0x10078bfff com.apple.Aperture (3.2 - 3.2) <0FC0DA68-CE13-3BCF-A2AE-700EA0C524CA> /Applications/Aperture.app/Contents/MacOS/Aperture
0x100975000 - 0x100975fff +GlimsLoaderMinimal.dylib (??? - ???) <3BAA9682-DD18-8442-D38A-7160FC8F7EAE> /Library/Frameworks/GlimsAdditions.framework/Library/GlimsLoaderMinimal.dylib
0x100978000 - 0x100e26fe7 com.apple.RedRock (1.8.1 - 231.89) <794D7315-0A6F-351C-B77A-D4E50D50DE26> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x101097000 - 0x10109aff7 com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <536AF147-2FB0-3EAF-AB65-F83E8EC63936> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
0x1010a0000 - 0x1010b0fff com.apple.iLifeAssetManagement (2.0 - 2.33) <4796FD8D-8F37-3F9D-B989-23E21D5B2487> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
0x1010c2000 - 0x101170ff7 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) <5ADCB983-167A-3DD4-BA21-0C81E9FAFA07> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
0x7fff62520000 - 0x7fff62554ac7 dyld (195.5 - ???) <4A6E2B28-C7A2-3528-ADB7-4076B9836041> /usr/lib/dyld
0x7fff8b2db000 - 0x7fff8b2e1fff com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff8c5ab000 - 0x7fff8c63dff7 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
0x7fff8c6f1000 - 0x7fff8c8f3fff com.apple.AOSKit (1.01 - 87) <E00ACA45-14A4-3894-9001-DDD39667B107> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
0x7fff8d218000 - 0x7fff8d218fff com.apple.Cocoa (6.6 - ???) <021D4214-9C23-3CD8-AFB2-F331697A4508> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff8e368000 - 0x7fff8e53cfff com.apple.CoreFoundation (6.7.1 - 635.15) <FE4A86C2-3599-3CF8-AD1A-822F1FEA820F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8ecd5000 - 0x7fff8ecd5fff com.apple.ApplicationServices (41 - 41) <03F3FA8F-8D2A-3AB6-A8E3-40B001116339> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x7fff8faa0000 - 0x7fff8fc2aff7 com.apple.WebKit (7534.51 - 7534.51.22) <A52AF4EF-A2AA-3718-AB96-576A5E0A1CB8> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff8fd48000 - 0x7fff90020ff7 com.apple.security (7.0 - 55010) <93713FF4-FE86-3B4C-8150-5FCC7F3320C8> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff90021000 - 0x7fff90030ff7 com.apple.opengl (1.7.5 - 1.7.5) <2945F1A6-910C-3596-9988-5701B04BD821> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff90ca3000 - 0x7fff90ca3fff com.apple.Carbon (153 - 153) <895C2BF2-1666-3A59-A669-311B1F4F368B> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff91990000 - 0x7fff919dbff7 com.apple.SystemConfiguration (1.11.1 - 1.11) <F832FE21-5509-37C6-B1F1-48928F31BE45> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff9232d000 - 0x7fff92397fff com.apple.framework.IOKit (2.0 - ???) <87D55F1D-CDB5-3D13-A5F9-98EA4E22F8EE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff927bc000 - 0x7fff927bcfff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff930c4000 - 0x7fff93263fff com.apple.QuartzCore (1.7 - 270.0) <E8FC9AA4-A5CB-384B-AD29-7190A1387D3E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff93a6b000 - 0x7fff93a6bfff com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.2 GHz, 4 GB, SMC 1.16f11
Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x4F5743353343344444523253324742000000
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x4F5743353343344444523253324742000000
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416: 2.1.14.9
Bluetooth: Version 4.0.1f4, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: TOSHIBA MK1655GSXF, 160.04 GB
Parallel ATA Device: MATSHITADVD-R UJ-857E
USB Device: Mass Storage Device, 0x1307 (USBest Technology Inc.), 0x0330, 0xfd100000 / 3
USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd400000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x021a, 0x5d200000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2@Frank: I did read through the article shuttersp33d posted. Unfortunately, for my scenario, the support doc redirects me to a page for OSX Lion reinstallation and recovery:
If you purchased Aperture from the Mac App Store and are running OS X Lion:
See the article OS X Lion: About Lion Recovery for instructions about how to reinstall OS X Lion.
That seems overkill and very inconvenient. Can I resolve this issue by restoring PluginManager files from before I installed FC, or something like that?
Thanks again. -
Aperture 3.1 takes incredibly long time to start
Since after the upgrade from 3.0.x to 3.1 Aperture takes a long time to start up. I click on the Aperture icon in the dock, the icon bounces for almost a minute, then it stays still for more than a minute, doing nothing and without the "light bulb" indicator that the app is running. It's just sitting there in the dock. After a total of 2-5 minutes, the Aperture window opens and I can start working.
I tried many things suggested in the forums to speed up Aperture:
I turned off Faces
I turned off sharing of previews with iLife and iWork
I turned off using embedded JPEGs from camera
I deleted all Aperture preferences as I thought there might be a corruption after upgrade
I removed all plugins from Aperture plugin folder to make sure nothing is interfering
I used the Aperture rebuild and repair options on the library
I created a new Aperture library and imported my photos from the old library into a fresh one
I downloaded and installed the Aperture 3.1 update again to make sure nothing got corrupted during update installation
Nothing helped. Aperture takes 2-3 minutes to fully start.
Plugins in use: NIK Software's Viveza 2 and HDR Efex Pro, Tiltshift for Aperture. That's it. And, as I said, it doesn't help if I take them out of Aperture's plugin folder so they don't get loaded. Problem still remains.
My library isn't that big: 29GB in 8230 items. Is 2-3 minutes a normal startup time?
Has anyone experienced a similar problem after upgrading? As I literally exchanged everything underneath Aperture (deleted preference files, created new library and imported photos from old lib) I don't know what else I could try. Totally uninstall Aperture and re-install it again?
Any suggestions what this could be?
On a sidenote, interestingly Logic Pro takes about the same amount of time to start. The icon bounces in the dock for almost 1 minute, then I hear the harddisk working for another minute until the splash screen finally appears. Logic Pro is loaded after 2 minutes and 20 seconds. I could boot my whole Mac 4x in that timeframe.To everybody having this problem. I found out what the culprit was. As a documentation here is what it was.
I read some posts here on the forums that mounted USB sticks or flash cards would make Aperture super slow while importing photos. I have Boot Camp installed and have a Windows 7 partition on the same drive as my MacOS. So, out of curiosity, I forced it to unmount as the partition automatically gets mounted by the OS.
Voilà! That seems to have been the culprit! Now both Aperture and Logic (which also had to think 2 minutes before it decided to start) display the splash screen in seconds and start like they are supposed to.
Make sure you have no drives mounted when starting these applications. This helped bringing down the starting time from 2 minutes and 20 seconds to just a few seconds. Of course, if you have your library on another drive you have to have it mounted. Maybe it only takes so long when you have Boot Camp and an NTFS partition. But if you experience lags starting these apps, try unmounting what you don't need. -
How do I stop Aperture consistently crashing when attempting to reconnect a few referenced files?
Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process: Aperture [29772]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.1 (3.4.1)
Build Info: Aperture-301039000000000~2
App Item ID: 408981426
App External ID: 11130653
Code Type: X86-64 (Native)
Parent Process: launchd [177]
User ID: 501
Date/Time: 2012-10-25 08:47:06.464 +1300
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 122141 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff897cf250 objc_msgSend + 16
1 com.apple.Aperture 0x0000000106f2ce46 0x106e03000 + 1220166
2 com.apple.Aperture 0x0000000106f2cf32 0x106e03000 + 1220402
3 com.apple.AppKit 0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4 com.apple.AppKit 0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5 libdispatch.dylib 0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6 libdispatch.dylib 0x00007fff8b42e0b6 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8 com.apple.CoreFoundation 0x00007fff899b30fe __CFRunLoopRun + 1614
9 com.apple.CoreFoundation 0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox 0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox 0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox 0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit 0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit 0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture 0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit 0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit 0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture 0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture 0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit 0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit 0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture 0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit 0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit 0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit 0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit 0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit 0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox 0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process: Aperture [29772]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.1 (3.4.1)
Build Info: Aperture-301039000000000~2
App Item ID: 408981426
App External ID: 11130653
Code Type: X86-64 (Native)
Parent Process: launchd [177]
User ID: 501
Date/Time: 2012-10-25 08:47:06.464 +1300
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 122141 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff897cf250 objc_msgSend + 16
1 com.apple.Aperture 0x0000000106f2ce46 0x106e03000 + 1220166
2 com.apple.Aperture 0x0000000106f2cf32 0x106e03000 + 1220402
3 com.apple.AppKit 0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4 com.apple.AppKit 0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5 libdispatch.dylib 0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6 libdispatch.dylib 0x00007fff8b42e0b6 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8 com.apple.CoreFoundation 0x00007fff899b30fe __CFRunLoopRun + 1614
9 com.apple.CoreFoundation 0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox 0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox 0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox 0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit 0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit 0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture 0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit 0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit 0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture 0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture 0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit 0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit 0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture 0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit 0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit 0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit 0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit 0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit 0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox 0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206 -
Aperture 3 keeps asking for my serial numbers every time I launch it.
I'm writing this not because I have this problem (though I did have it) but because I couldn't find a direct answer here in Apple Support Communities but did eventually solve it.
After purchasing a new iMac to replace an aging MacBook Pro, I tried copying the original ProAppsSystemID file in /Library/Application Support/ProApps from the old to the new system, hoping that would transfer my Aperture license. That didn't work (for me), though Aperture continued working on the old MacBook Pro. I went digging and found my original Aperture activation keys (original and upgrade), entered those on the new iMac, and was finally able to launch Aperture 3 on the iMac.
My problem was that Aperture kept asking me for my serial number every time I launched it. I had originally purchased Aperture 2 and then purchased the Aperture 3 upgrade. As it should, when I supplied my Aperture 3 activation key, it noted that was for an upgrade and prompted me to enter my original key. After supplying my original Aperture 2 (full license, not an upgrade) key, it would continue and launch.
I could then use Aperture just fine, as before, however, its "About" window showed that it was "unlicensed". The next time I'd re-launch Aperture (after quitting it, obviously), I would have to go through the same process, supplying first my Aperture 3 upgrade key and then my Aperture 2 key, before it would finish launching.
I tried everything I could think of: uninstalling and reinstalling Aperture 2, upgrading again to Aperture 3, deleting Aperture preference files, and so on. I tried logging in as root and repeating everything. I tried "repair disk permissions". Nothing helped!
What seemed to fix my problem was going back into /Library/Application Support/ProApps and renaming "ProAppsSystemID" to "ProAppsSystemID xxx", relaunching Aperture 3, and entering the activation keys one last time. At that point, the "About" box properly indicated my version was licensed, and I was able to exit and re-launch Aperture without being prompted!
Although my problem is solved, I'm still a but mystified, however, because the file named "ProAppsSystemID xxx" is still there, its modification date is unchanged from when I renamed it, and a new "ProAppsSystemID" file has not appeared in that directory.
Also, it's a shame that Aperture's licensing is so fragile that this problem should arise at all. If there was something wrong with my system ID file, Aperture should have opened an error dialog or at least noted something in the system log. (It didn't, I checked.) Apple really should fix that. And here I thought only Adobe shipped egregiously stupid upgrade/licensing logic...Thanks - this worked for me too - you saved me alot of heartache and wasted time :-)
-
How do I use iCloud with Aperture?
I want to synchronize the photos I shoot and load on my MacBook in Aperture to my desktop iMac. I've never used iCloud, but the setup instructions says this should work for Aperture users. The instructions say:
"Open iPhoto or Aperture and click the Photo Stream icon in the left column. Then click Turn On Photo Stream."
Well, there is no Photo Stream icon in the left column or anywhere in my Aperture program. What am I missing? Thanks for any help.
MariaMaria, have you enabled Photo Stream in the System Preferences > iCloud tab and in Aperture's Preferences?
Does your Aperture version support iCloud? You need at least Aperture 3.2.3
See: iCloud: Photo Stream FAQ
Choose Apple () menu > System Preferences. Click iCloud, then select Photo Sharing.
Turn on Photo Sharing in one of these applications:
iPhoto: Choose iPhoto > Preferences. Click iCloud, then select Photo Sharing.
Aperture: Choose Aperture > Preferences. Click iCloud, then select Photo Sharing.
Léonie -
The dropdown list "Store Files" in the "Import Settings" section of Aperture 3.3.2 displays the history of the entries previously added to the list. Some of the entries are no longer valid and I'm trying to delete them but I can't find a way to do this. This is a screenshot. Does anyone know how to do this?
Once again - the Jive system ate my bullet points and messed up the formatting
Is the MacOS X version in your signature correct? Then you cannot be using Aperture 3.3.2?
You should not be seeing duplicate entries in the "Store Files" pop-up menu. This looks like your Aperture Preferences file is corrupted and needs fixing.
Quit Aperture (and log off and on again, if you are running MacOS X 10.7 or later)
Then reveal your User Library (from the Finder's main menu bar, the "Go" menu. Hold down the options-key until the library apears in the drop-down menu)
In the Library folder select the "Preferences folder and locate the file "~/Library/Preferences/com.apple.Aperture.plist"
Now you can either
remove the com.apple.Aperture.plist file to the Desktop, to force Aperture to create a new one, but you will have to set again your Preferences from the "Preferences" panel,
or make a backup copy of the file and edit it, if you are an experienced programmer and have Xcode installed. To fix the drop-down list you need to edit the item "RecentReferenceFolders" and delete the redundant folder names. Enter "recent" into the search field to find it quickly. If you click an item in the list, plus/minus buttons should appear. But only try this, if you know how to edit property lists, otherwise it will be much safer to delete the faulty list and to set your preferences again from the "Preferences" panel.
Regards
Léonie -
I have had several issues so far with my new aperture program, and this is the fifth time i have tired to collect all of my images (or nearly all) onto a single drive and be able to file them from my mac notebook...obviously one huge problem is that every timie the dog walks buy he knocks the cord out and i basiclaly have to start over again...
but i have taped the cords in an managed to fly across country while keeping the whole import running---up near 24 hours constant now...
anyway, i ahve a bunch of questions but my main one is, i think from reaeding up here that it could take a fulll week to finish this transfer (even though i beleieve i made it very clear that i only want to index the fiels from their current location and not to move any of them around at all....
the only rush really is that i have my daughter's graduation pictuers and everyone wants to see htem but i don't really want to cancel this transfer after i have already spent 24 hours!!!
sorry to write so much...
thanks for any ideas....
MaxMax,
It really can take very long to import and process so many images - I would not dare to make a prediction.
Can you open the Activity Viewer?
From Aperture's main menu bar: Window > Show Activity.
This window will tell you the filename of the image that is currently being processed.
if you are seeing, that the import is still far from being finished, you might to pause certain tasks directly from this panel, like the generation of previews or scanning for faces. I'd let the import run, if you see that it is making progress.
Have you enabled very time-consuming options, like the generation of high resolution previes or scanning for faces and places? if yes, and the import is not making any progress at all, I'd disable thes options in the Aperture preferences for the initial import. You can add these later for the projects where you want to use these features.
Regards
Léonie
Maybe you are looking for
-
Sales /Outgoing Excise Invoice number Range for J1IIN
Dear Gurus, We are doing STO from excisable plant 1000 to plant 1100. We created a PO with document type UB ( STO) and created delivery with reference to PO and created billing document ( delivery challan). Against billing document number we created
-
Report to display material master data changes
Hi, Is there a standard report available to display all changes to material master data over a specified time frame i.e all changes made alst week,all chnages made today. Please suggest. Thanks in advance.
-
How to get result in comma separated
I have the follwing query with simple join select c.f_category_id,c.f_category_name,sc.f_subcategory_id,sc.f_subcategory_name from mcp_adv_category c join mcp_adv_category_trans ct on c.F_CATEGORY_ID =ct.F_CATEGORY_ID join mcp_adv_subcategory sc on c
-
Alot of Lockups from numerous OS X Applications
I'm getting a lot of lockups from different applications on my MacBook Pro. It's not that it happens all the time, but any time you throw something at it that's processor intensive it just halts. If you try to cancel the action you just get the spinn
-
Screenshots and dual screen logic in macbook
Ive got a problem, everytime i safe screen settings i worked on in a song, they wont reload. When i have for instance arrangement view on the macbook screen, and the matrix edit on the monitor on key 1,,,,, the setting gets lost when saving the song.