Opening a clip in an external editor

It's my understanding that I can open a clip from the FC Pro timeline in an external editor like Motion or After Effects. However, whenever I try to do this in Final Cut I end up with the WHOLE clip (not just the portion of it as designated by in and out points). Motion, on the other hand brings in just the piece of the clip to be affected. I'm still learning Motion and know After Effects really well so I'm trying tp figure out if I'm doing something wrong.
Also, once I'm done in Motion or After Effects do I have to EXPORT the movie or is there a way to for the FC Pro timeline to recognize the changes done to it in the external editor without EXPORTING A quicktime movie.
Thanks for your help.

You are going about it the wrong way.
For Motion, you mark IN and OUT and go to the FILE menu and select EXPORT. EXPORT TO MOTION will be an option.
Unfortunately it doesn't work like that for AE. Motion and FCP work together in a very unique way...a way that Apple designed its Suite to interact. For After Effects you need to export your clip as a self contained QT Movie, import that into AE, then export the changes as another self contained QT file...and import that into FCP.
Shane
"There's no need to fear, UNDERDOG is here!"

Similar Messages

Why can I not open a file in lightroom to an external editor?

I have recently restored my photo library on an external drive via time machine and all has been good. Now I have updated lightroom to 4.4 and cannot open any files to an external editor... photoshop cs4 or any nik software program. I am running OS X.6.8. Any ideas as to what has happened and how to fix?
It comes up with "Lightroom was unable to prepare the selected file at.... for editing. It will not be opened."
Cheers

Not sure what the problem is..... When I originalte an email, or reply to one, I have the paperclip icon that I use to attatch files that need to be sent.
Do you not have the paperclip icon? If not, when you initiate a new outgoing email, go to the VIEW menu, and make sure Show Toolbar is checked....

Changing color space when opening in external editor

Hi
Is it possible to have aperture open a raw file in Photoshop in a colourspace other than Adobe RGB and also in 8bit rather than 16bit.
Also I notice that it only saves as PSD or TIFF if you want to have the retouched file linked to the original master. Is there a work around to change this to jpeg but maintain the link to the master file.
Thankyou

OK
I understand why, in the interest of maintaining max file integrity that apple restricts exporting to 16bit and PSD or TIF.
However Adobe 98 is'nt always the best or most convenient colourspace to open a file with an external editor. What i'm looking is the option to change the export colourspace.
PS: I'm only looking for the option when using the 'Open In External Editor' option. I know when exporting files out of aperture that there are many more options.
Thanks

Can't open image in external editor, can't export images

Greetings helpful Aperture experts,
I've just finished transferring aperture from one computer to a replacement unit. Except for being slow on my previous g5, it worked flawlessly at every level. However, now that I've xferred, I can't open Aperture images with an external editor, nor can I export the images to my desktop. Any help along these lines will be gigantically appreciated.
gaylon

Thanks, ok, here is the info step by step:
When I try to pick any raw image, I am not able to export from Aperture. When I go into the finder and select "show master" then I am able to export from aperture. However, it seems that I am not able to export an image full size. I selected export image to full size jpg to my desktop. Nothing happens except that the window that indicates the image is exporting is open and it says estimated time less than a minute. Yet, there is nothing happening. Additionally, before I transferred Aperture over to my new g5, I could right click an image and had the option to open an image with external editor. Now, no such menu item is apparent. An update, the menu box that lets me know that my image is exporting is still open but there has been no progress. It will just sit there forever, or until I force Aperture to quit. Here's another strange goings on: One of my folders of raw images appear to be pixelated and of very poor quality, even when viewing the masters. The images have already been published by the client in their annual report, so I know that what I am seeing on the screen is not reality. Should I just uninstall Aperture and reinstall? Also, what will this do to the thousands of images in my libraries? Thanks so much for your input and help. In no way am I an expert, but I've been successfully using Aperture since it came out. That was on my G5 dual processor mac with pre intel configuration. Now, these strange things are happening with my new replacement G5 with the Intel processors. Thanks again.
gaylon wampler

Open untagged JPEG with external editor, then be attached with sRGB profile

Hi there,
I wonder why I open untagged JPEG with "external editor" (Photoshop CS) , then the JPEG will be attached with sRGB profile. Of course my color setting on photoshop is "Use the embedded profile".
I think sRGB is the default RGB space of colorsync utility , because the profile is also sRGB when you check "Add Colorsync Profile" on iPhoto 6.
Anyway , I want to set up total Adobe RGB workflow , so does anybody know how to change sRGB profile to Adobe RGB profile when opening untagged JPEG directly with external editor?

Thank you for your reply , Lloyd.
I am sorry , but I noticed my misunderstanding message.
As you know , you can change raw and other image files to tiff or psd for external editor. You can select that on the preference. At this situation , if you pass nontagged image file to external editor , then automatically sRGB profile is attached.
I don't think this is related to export preset for JPEG file.

Images won't open in Adobe external editor

I can't get my images to open up in Photoshop eventhough it is set up as my external editor. When I select a picture to open with via the chosen external editor, a second version of my original is made within Aperture(with the external editor badge on it), Photoshop proceeds to open, but the image does not open in Photoshop to allow for edits.
Can someone recommend a fix?

Are you using CS2 or CS3? There might be something weird going on with the emulation if you're using CS2.
Barring that, I'd open up Aperture, set the external to nothing, quit Aperture, reopen, then reset it to PS again. Kind of a pain, but stuff like that has worked in the past for me. Also, do you have the latest version of Aperture (1.5.3)? If not, update.
You might also want to try pointing it to a different external editor – if it works on the alternate one, then it might have something to do with your Photoshop installation, which then might necessitate a reinstall.
My last (well, 2nd last to uninstalling and reinstalling Aperture) suggestion would be to repair permissions and cross my fingers.

File opened in external editor not stored with referenced files

If I open a referenced raw file in an external editor (CS2) and work on the image adding layers etc., the image is not stored where I have all the other referenced files. It gets stored in the Aperture Library. Is there a way around this. I want to keep all my files together. This can be done in Lightroom, but I am trying to make Aperture work for my workflow.
Thanks,
gary
mac book, G5 Mac OS X (10.4.7)

Well, here's the feedback I submitted to Apple:
With the introduction of Aperture 1.5, you offered users the ability to manage their own libraries, and for Aperture to work with 'referenced' images. In fact, because of this very reason, many of us consumers decided to buy Aperture 1.5.
Most of us photographers also use Adobe Photoshop routinely.
But there is a huge problem/bug for us users who manage our own library (force Aperture to work with 'referenced' images) AND use Photoshop (or any external editor for that matter). When we open a file in an external editor via Aperture, Aperture creates a new 'master' for editing -- but does so in its own 'managed' library! When we save from Photoshop, the image remains in the 'managed' library! So now we have one 'master' in our own directory, and the externally-edited 'master' in Aperture's 'managed' library! This is very CONFUSING and renders external editing via Aperture USELESS... no one in their right mind would want one version of their image in an organized directory, and an edited version in Aperture's managed library (where it is difficult to find manually)! No, it makes much more sense to create the edited 'master' in the same location as the original 'master'!
PLEASE fix this bug ASAP! Aperture already has a good method for automatically renaming files by adding (1) or (2) or (3) or so forth when it is relocating files and finds a file with the same file-name. The same logic can be applied when creating a new 'master' for external-editing: that is, it should just create another .tiff (or .psd, or what have you) file with the same name but with a (1) or (2) tagged on. For example, if my master image is \Pictures\Seattle\SpaceNeedle.tiff, then when I open this image in an external editor, Aperture should automatically make the file: \Pictures\Seattle\SpaceNeedle (1).tiff, and open that file in the external editor... rather than create SpaceNeedle.tiff in its own managed library where I can't even find it using Finder or Windows Explorer, etc.
Many of us have this complaint (just search Apple discussions)... PLEASE rectify this problem ASAP as it is completely messing up our workflows by requiring us to manually save through the external editor and then having to manually remove every 'managed' file that Aperture makes. This is really a pain and seriously makes me want to switch to a different image management program... though I love Aperture thus far and would love to stick to it as I believe it is visionary and shaping the future of how photographers will manage their digital workflows!
Many thanks in advance for your time!
Best,
Rishi

Open in External Editor

I would love it if Aperture would leave the Version name the same when you open a picture in an external editor. Right now it reverts back to the filename. Which means that after I'm done saving it, I have to copy the version name from the "original," and then type "Version x" after it for every picture I edit in Photoshop.
Toine

Hi Nige,
It is a Photoshop problem and probably because it is missing files.
this is an old copy/paste from MacFixit it.
Try this suggestion I copied and pasted from MacFixIt first
"Photoshop CS: Fix for file opening problem Yesterday we reported that since installing Mac OS X 10.4, Photoshop CS refuses to open any new files or create any new documents, reporting a "program error" when one tries to do so. Our previously reported workaround involved re-installing Photoshop CS, but MacFixIt reader Bryan Schappel now offers a faster solution:
"This happens because the Archive and Install option does not copy over a necessary folder for Photoshop. The critical folder is called 'ScriptingAdditions' and is stored in the main Library folder. This folder contains one file 'Adobe Unit Types' that makes Photoshop open files that have been double-clicked or dragged to the PS icon in the Dock.
"Simply move this folder (and file) from the 'Previous System' backup to the Library folder, relaunch Photoshop and all is well again. No need to completely re-install.""
I copied an pasted instead of putting the link in because it is not on the front page and you would have to search around to find it. Hope it is ok to do that here. If you don't still have the folder then you have to reinstall PhotoShop.

Aperture and external editor

When opening a file with the external editor (I think most of you using PS like me), then saving it and go back to aperture, the file size is much greater than the original RAW file (roughly 58Mb in my case).
I guess that's because PS opens the files either in PSD or TIFF 16bit format.
So my questions are:
1. After editing with PS, Is there a way to go back to Aperture and maintain the same file size?
2. Why can't PS manage the file in a RAW format rather than PSD or TIFF?
3. Are these files stored in the Aperture library?
Thank you in advance!
Guido

Hi Guido,
in addition to Adam's correct reply:
1.
Nope (see 2.). It doesn't matter from where the RAW file comes (Aperture, Finder, ... ).
2.
It does manage the RAW file (else it wouldn't be able to open it
But no program can save a RAW file (it's also called "Digital negative", as in the analog world this negative exists once only).
PS is a destructive editing application, whatever you do changes the original you send over. That's why you copy the original (background) layer first thing when applying filters and/or use adjustment layers.
Layers can only be saved as PSD or TIFF - and those are big, that's the way it is.
3.
Yes. But you can make it referenced like any other image.
Hope it helps,
chris

External Editor in Sun Studio 8 IDE

When I invoke any external editor (Gvim or Xemacs) via File->Open File, a note dialog comes up which says:
Waiting for connection from external editor...... If you want to cancel external editor support and use the built-in editor instead, click Cancel
The external editor never comes up and the dialog box stays there until I click "Cancel".
While this might occur for a number of common reasons, which hopefully I've considered, while trying to troubleshoot, the solution was very strange. When my unix prompt contained a carriage return as in the following:
"413:sc:/home/server_k55/rbuckwa
as defined by:
PS1='!:$Hostname $PWD
the above described behavior occurred.
However, when the unix prompt did not contain a carriage return as in:
"sc{413}$"
defined by:
PS1="$Hostname{!}$ "
the IDE opened the file and the external editor successfully.
Does anyone have any explanation or experience with this strange behavior. BTW I'm running Solaris 8.
thanks,
rick

This sounds like a bug. We probably don't test with a prompt
containing a carriage return. You can file this bug using
http://bugs.sun.com if you like. Look for the "Sun Studio" categories.
--chris

External editor file naming question

This topic was covered about a year ago, with 1.1, but I am wondering if there is a solution with1.5:
When I open a file in an external editor (CS3), the file name reverts to the master file name, not the version name. Is there any way to get Aperture to use the version name?
I typically shoot multiple bird species on a single card, so when I download them, I am unable to get my preferred file name for each file on import.
Any suggestions would be appreciated,
Thanks,
Steve
MacPro Mac OS X (10.4.9) 2G Memory, Aperature 1.5.2

No, there's still no way to rename Masters short of exporting them with the version name and re-importing.
The only way 'Save As' is going to work from an external editor is if you use exactly the same file name - that is the only file Aperture has sent out and it's the only file that Aperture is expecting back.
Saving with a different file name is functionally the same as copying a new file into the Library using the Finder - Aperture has no way to expect it. You'd have to save to somewhere outside the Library and then import it as a new Master, maybe setting up a hot folder in Automator for automatic importing.
Ian

External Editors file format- choose more than one:i.e. either tiff or psd

External Editors file format- would like to be able to choose more than one OR I'd like to be able to easily change between opening a file in an external editor in either psd format or tiff. i.e. PSDs to photoshop, or TIFFs to one or more other editors like Topaz Labs, FX Photo Studio Pro or Snapseed.
While when editing in PhotoShop, one would like to edit in psd format, other plug-ins will not take a psd format, they need tiff. There is only one choice for external editor in Aperture. is it possible to set up a work around for this?
This issue is also discussed on http://www.apertureexpert.com/tips/2012/1/25/using-3rd-party-apps-with-aperture. html

Here's my thoughts...
1. You are a bit confused and I wonder how you can determine a file is a PSD or a TIF by looking at it? Not all print drivers can recognize PSD's, but can recognize TIF ( this means almost all output devices can interpret TIF's no problem ). That said, PSD's can manage layers better than TIF's which add to file size each layer you include in the TIF.
2. Never say never. This all depends on the file's use. Layered TIFs can add complexity in which a print driver can or cannot deal with. As you work on an image, you may want to merge layers for whatever reason(s) and you always have the option to flatten whenever you feel like it. However, It is also a good idea to dupe the file as you move along. That means you always have a layered version to fall back on should you need to edit later on. I also Place transparent PSDs in Illustrator files with no problems. But, I save as EPS in Illustrator and when I do that, then the file is automatically flattened. This is perhaps what the internet was talking about.
3. Yes, see number 2 above. There's no such thing as automatic flattening of TIFFs. Again, this all depends on the printer and whether or not it can print while retaining original layers. Some do, some don't. Most of the time, I edit in PSD with layers intact. Then, when I prep the file for printing, I will save a copy as a flattened TIFF so the file streamlines through the RIP and Print process.
4. Makes no difference. Use 'em if you've got 'em.
Try to get some good resource material at a library or college bookstore or barnes & noble. Also, get Adobe's Print Publishing Guide. This is a good reference guide.
Message was edited by: John Danek

IPhoto 9.1.5 crashing when going to external editor

I have iPhoto set to open Photoshop as the external editor. But it keeps crashing my mac when I instruct iPhoto to open a pic in the external editor, not every time, but enought that it's so annoying, it causes a complete crash so I have to do a complete restart.
It's driving me nuts, any answers anyone?
Thanks
Kate

OK had a big crash which has trashed an iPhoto library completely, if anyone can help will appreciate it. Crash report below.
Process:
iPhoto [392]
Path:
/Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:
com.apple.iPhoto
Version:
9.2.1 (9.2.1)
Build Info:
iPhotoProject-628000000000000~3
Code Type:
X86 (Native)
Parent Process: launchd [107]
Date/Time:
2012-01-10 06:38:15.193 +0000
OS Version:
Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report:
111972 sec
Crashes Since Last Report:
6
Per-App Interval Since Last Report: 29380 sec
Per-App Crashes Since Last Report:   4
Anonymous UUID:
EA04266D-AE09-4438-A92C-B42D0BA5B080
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   com.apple.iLifeSQLAccess
0x0182863a sqlite3VdbeExec + 7306
1   com.apple.iLifeSQLAccess
0x0182662c sqlite3_step + 2812
2   com.apple.iLifeSQLAccess
0x018588b9 -[HgKResultSet next] + 265
3   com.apple.iLifeSQLAccess
0x0185a1b4 -[HgKDatabaseManager(Utility) numberForQuery:] + 420
4   com.apple.iLifeSQLAccess
0x01859ffb -[HgAdminDataEntity numberPropertyForArea:propertyName:] + 123
5   com.apple.RedRock
0x01eff38d -[RKDatabase isTMSyncUpToDate] + 317
6   com.apple.RedRock
0x01d31d2f -[RKDatabase openDatabaseWithOptions:] + 8831
7   com.apple.RedRock
0x01d2eab6 -[RKDatabaseComponent openDatabaseForLibraryPath:options:] + 742
8   com.apple.RedRock
0x01d2e574 -[Godot startupDatabase] + 916
9   com.apple.RedRock
0x01fd4488 -[Godot startWithLibraryPath:inAppStoreMode:] + 184
10 com.apple.iPhoto
0x0003fa38 0x1000 + 256568
11 com.apple.iPhoto
0x0003c40f 0x1000 + 242703
12 com.apple.iPhoto
0x000393ef 0x1000 + 230383
13 com.apple.iPhoto
0x000386bc 0x1000 + 227004
14 com.apple.iPhoto
0x00036098 0x1000 + 217240
15 com.apple.iPhoto
0x00035e50 0x1000 + 216656
16 com.apple.iPhoto
0x000356c1 0x1000 + 214721
17 com.apple.iPhoto
0x00033a4f 0x1000 + 207439
18 com.apple.Foundation
0x9978adb3 _nsnote_callback + 176
19 com.apple.CoreFoundation
0x91537763 __CFXNotificationPost + 947
20 com.apple.CoreFoundation
0x9153716a _CFXNotificationPostNotification + 186
21 com.apple.Foundation
0x9977fc50 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
22 com.apple.Foundation
0x9978d05d -[NSNotificationCenter postNotificationName:object:] + 56
23 com.apple.AppKit
0x95f06216 -[NSApplication _postDidFinishNotification] + 125
24 com.apple.AppKit
0x95f06126 -[NSApplication _sendFinishLaunchingNotification] + 74
25 com.apple.AppKit
0x9605d339 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274
26 com.apple.AppKit
0x9605cf59 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101
27 com.apple.Foundation
0x997c01f8 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
28 com.apple.Foundation
0x997bffbc _NSAppleEventManagerGenericHandler + 228
29 com.apple.AE
0x90006f5c aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
30 com.apple.AE
0x90006e5b dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
31 com.apple.AE
0x90006d65 aeProcessAppleEvent + 197
32 com.apple.HIToolbox
0x96a03197 AEProcessAppleEvent + 50
33 com.apple.AppKit
0x95ed67d2 _DPSNextEvent + 1420
34 com.apple.AppKit
0x95ed5dd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
35 com.apple.AppKit
0x95e981f3 -[NSApplication run] + 821
36 com.apple.AppKit
0x95e90289 NSApplicationMain + 574
37 com.apple.iPhoto
0x0001159a 0x1000 + 66970
38 com.apple.iPhoto
0x00010a29 0x1000 + 64041
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0   libSystem.B.dylib
0x981e9382 kevent + 10
1   libSystem.B.dylib
0x981e9a9c _dispatch_mgr_invoke + 215
2   libSystem.B.dylib
0x981e8f59 _dispatch_queue_invoke + 163
3   libSystem.B.dylib
0x981e8cfe _dispatch_worker_thread2 + 240
4   libSystem.B.dylib
0x981e8781 _pthread_wqthread + 390
5   libSystem.B.dylib
0x981e85c6 start_wqthread + 30
Thread 2:
0   libSystem.B.dylib
0x981e8412 __workq_kernreturn + 10
1   libSystem.B.dylib
0x981e89a8 _pthread_wqthread + 941
2   libSystem.B.dylib
0x981e85c6 start_wqthread + 30
Thread 3:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 4:
0   libSystem.B.dylib
0x981c2afa mach_msg_trap + 10
1   libSystem.B.dylib
0x981c3267 mach_msg + 68
2   com.apple.CoreFoundation
0x915192df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x915183c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x915181f1 CFRunLoopRunInMode + 97
5   com.apple.Foundation
0x997c51b3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
6   com.apple.proxtcore
0x0175caed -[XTRunLoopThread run:] + 509
7   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
8   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
9   libSystem.B.dylib
0x981f0259 _pthread_start + 345
10 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 5:
0   libSystem.B.dylib
0x981c2afa mach_msg_trap + 10
1   libSystem.B.dylib
0x981c3267 mach_msg + 68
2   com.apple.CoreFoundation
0x915192df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x915183c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x915181f1 CFRunLoopRunInMode + 97
5   com.apple.Foundation
0x997c51b3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
6   com.apple.proxtcore
0x0175caed -[XTRunLoopThread run:] + 509
7   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
8   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
9   libSystem.B.dylib
0x981f0259 _pthread_start + 345
10 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 6:
0   libSystem.B.dylib
0x981e8412 __workq_kernreturn + 10
1   libSystem.B.dylib
0x981e89a8 _pthread_wqthread + 941
2   libSystem.B.dylib
0x981e85c6 start_wqthread + 30
Thread 7:
0   libSystem.B.dylib
0x981f0aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x9821c9c5 nanosleep$UNIX2003 + 188
2   libSystem.B.dylib
0x9821c903 usleep$UNIX2003 + 61
3   com.apple.AppKit
0x9603fe2d -[NSUIHeartBeat _heartBeatThread:] + 2039
4   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
5   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
6   libSystem.B.dylib
0x981f0259 _pthread_start + 345
7   libSystem.B.dylib
0x981f00de thread_start + 34
Thread 8:
0   libSystem.B.dylib
0x981e8412 __workq_kernreturn + 10
1   libSystem.B.dylib
0x981e89a8 _pthread_wqthread + 941
2   libSystem.B.dylib
0x981e85c6 start_wqthread + 30
Thread 9:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 10:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 11:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 12:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 13:
0   libSystem.B.dylib
0x981c2afa mach_msg_trap + 10
1   libSystem.B.dylib
0x981c3267 mach_msg + 68
2   com.apple.CoreFoundation
0x915192df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x915183c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x915181f1 CFRunLoopRunInMode + 97
5   com.apple.Foundation
0x997c51b3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
6   com.apple.proxtcore
0x0175caed -[XTRunLoopThread run:] + 509
7   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
8   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
9   libSystem.B.dylib
0x981f0259 _pthread_start + 345
10 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 14:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 15:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 16:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 17:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 18:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 19:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 20:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 21:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 22:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 23:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 24:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 25:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 26:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 27:
0   libSystem.B.dylib
0x981c2b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x981f06e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x9821f5a8 pthread_cond_timedwait_relative_np + 47
3   com.apple.Foundation
0x997c78e8 -[NSCondition waitUntilDate:] + 453
4   com.apple.Foundation
0x997803b1 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5   com.apple.Foundation
0x99780294 -[NSConditionLock lockWhenCondition:] + 69
6   com.apple.proxtcore
0x0175b702 -[XTMsgQueue waitForMessage] + 50
7   com.apple.proxtcore
0x0175a6b0 -[XTThread run:] + 416
8   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
9   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
10 libSystem.B.dylib
0x981f0259 _pthread_start + 345
11 libSystem.B.dylib
0x981f00de thread_start + 34
Thread 28:
0   libSystem.B.dylib
0x981c2afa mach_msg_trap + 10
1   libSystem.B.dylib
0x981c3267 mach_msg + 68
2   com.apple.iLifeSQLAccess
0x0184df41 -[RALatchTrigger wait] + 81
3   com.apple.iLifeSQLAccess
0x0184ddc9 -[RAOperationQueueImpl _workThread] + 217
4   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
5   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
6   libSystem.B.dylib
0x981f0259 _pthread_start + 345
7   libSystem.B.dylib
0x981f00de thread_start + 34
Thread 29:
0   libSystem.B.dylib
0x981c2afa mach_msg_trap + 10
1   libSystem.B.dylib
0x981c3267 mach_msg + 68
2   com.apple.iLifeSQLAccess
0x0184df41 -[RALatchTrigger wait] + 81
3   com.apple.iLifeSQLAccess
0x0184ddc9 -[RAOperationQueueImpl _workThread] + 217
4   com.apple.Foundation
0x9978b4c4 -[NSThread main] + 45
5   com.apple.Foundation
0x9978b474 __NSThread__main__ + 1499
6   libSystem.B.dylib
0x981f0259 _pthread_start + 345
7   libSystem.B.dylib
0x981f00de thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x039d5a7c ecx: 0x00000000 edx: 0x00000001
edi: 0x00000000 esi: 0x1f2e18c8 ebp: 0xbfffe198 esp: 0xbfffdce0
   ss: 0x0000001f efl: 0x00010202 eip: 0x0182863a   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x1000 -   0xd1afeb com.apple.iPhoto 9.2.1 (9.2.1) <68601E93-E4CF-3B4C-AFFD-4781A92DD58B> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0xe83000 -   0xf6afef org.python.python 2.6.1 (2.6.1) <4FFD855C-1C5A-9206-A695-8C9904F1DA84> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
0xfb5000 - 0x1155ffb com.apple.geode 1.5 (151.51) <28D29759-F356-3608-B9CF-3031F3299B1B> /Applications/iPhoto.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x11f5000 - 0x11f7fff com.apple.iLifePhotoStreamConfiguration 2.2 (2.2) <4FA61CE9-1718-3E07-9896-0023A2A49699> /Applications/iPhoto.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fram ework/Versions/A/iLifePhotoStreamConfiguration
0x11fd000 - 0x120cfff com.apple.iLifeAssetManagement 2.0 (2.33) <8346DE35-5F86-3338-9913-B035B3EE5435> /Applications/iPhoto.app/Contents/Frameworks/iLifeAssetManagement.framework/Ver sions/A/iLifeAssetManagement
0x1219000 - 0x1241ffb com.apple.iPhoto.Tessera 1.1 (60.10) <7BA9184E-0A00-3083-8322-772ECBDD30C9> /Applications/iPhoto.app/Contents/Frameworks/Tessera.framework/Versions/A/Tesse ra
0x1252000 - 0x1279ffb com.apple.iPhoto.Tellus 1.3 (60.10) <4AABB0BC-AC97-3EE4-BF0F-D8499DDB57C0> /Applications/iPhoto.app/Contents/Frameworks/Tellus.framework/Versions/A/Tellus
0x128e000 - 0x1298fff com.apple.iphoto.AccountConfigurationPlugin 1.2 (1.2) <3B68F126-D783-3F86-AF04-A0F6A459BE67> /Applications/iPhoto.app/Contents/Frameworks/AccountConfigurationPlugin.framewo rk/Versions/A/AccountConfigurationPlugin
0x12a3000 - 0x12baff7 com.apple.iLifeFaceRecognition 1.0 (21) <AD53D7A2-F0B2-FF76-5C6D-C23B234AB50E> /Library/Frameworks/iLifeFaceRecognition.framework/Versions/A/iLifeFaceRecognit ion
0x12c9000 - 0x12f4fff com.apple.DiscRecordingUI 5.0.9 (5090.4.2) <3E6CC284-2F1B-9EDB-0B56-872F962669A2> /System/Library/Frameworks/DiscRecordingUI.framework/Versions/A/DiscRecordingUI
0x130c000 - 0x1317fff com.apple.UpgradeChecker 9.2 (9.2) <2040F6E1-7E77-3C64-8B2C-F3B9503C7402> /Applications/iPhoto.app/Contents/Frameworks/UpgradeChecker.framework/Versions/ A/UpgradeChecker
0x131f000 - 0x131ffff com.apple.iLifeSlideshow 2.3.0 (847) <E98D197B-DAE9-3728-A2DA-C66966ABC6EF> /Library/Frameworks/iLifeSlideshow.framework/Versions/A/iLifeSlideshow
0x1322000 - 0x1598ffb com.apple.iLifePageLayout 1.3 (150.37) <F71F8978-B7FE-3E7A-91E7-C79862B7E827> /Library/Frameworks/iLifePageLayout.framework/Versions/A/iLifePageLayout
0x1662000 - 0x16fdff7 com.apple.MobileMe 11 (1.0.3) <BCE66DE5-97D5-3E78-AC9C-17353AFA6A34> /Applications/iPhoto.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mobi leMe
0x1757000 - 0x17b7fff com.apple.proxtcore 1.3 (140.57) <37B97974-E262-3CA8-AF41-2A522C849E82> /Applications/iPhoto.app/Contents/Frameworks/ProXTCore.framework/Versions/A/Pro XTCore
0x1809000 - 0x18e8ff3 com.apple.iLifeSQLAccess 1.6 (30.12) <C59BE368-DD76-3E91-8F89-2A97E99FE282> /Library/Frameworks/iLifeSQLAccess.framework/Versions/A/iLifeSQLAccess
0x1916000 - 0x1942fef com.apple.ProUtils 1.1 (120.14) <44F86ACC-A361-3837-9068-B3B8802E6B39> /Applications/iPhoto.app/Contents/Frameworks/ProUtils.framework/Versions/A/ProU tils
0x195d000 - 0x19b0ff7 com.apple.iLifeKit 1.3 (90.16) <607E7C33-6A90-39A3-96F2-6C4C8160A4DC> /Library/Frameworks/iLifeKit.framework/Versions/A/iLifeKit
0x19e1000 - 0x1c19fff com.apple.prokit 7.0.1 (1331.1) <327AFA15-E955-02EF-3E57-E2558B645698> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x1d21000 - 0x215efe3 com.apple.RedRock 1.8.1 (231.89) <6217B083-7AD4-355E-8ED3-53318A609015> /Applications/iPhoto.app/Contents/Frameworks/RedRock.framework/Versions/A/RedRo ck
0x22ef000 - 0x22f6ff7 com.apple.MediaSync 1.1 (130.12) <3E7E1340-C3C8-3F1A-BB4B-E8C3A3EE7777> /Applications/iPhoto.app/Contents/Frameworks/MediaSync.framework/Versions/A/Med iaSync
0x22fe000 - 0x22fffff +eOkaoCom.dylib ??? (???) <2DE16B47-23E7-73DB-1297-C928E40DFC31> /Library/Frameworks/iLifeFaceRecognition.framework/Versions/A/Resources/eOkaoCo m.dylib
0x2303000 - 0x2328ff2 +eOkaoPt.dylib ??? (???) <831D49D0-43A0-21A0-2662-2207E3BE0FF6> /Library/Frameworks/iLifeFaceRecognition.framework/Versions/A/Resources/eOkaoPt .dylib
0x232f000 - 0x2363fe7 +eOkaoDt.dylib ??? (???) <5693A28E-8C94-0F5F-150E-3B17CF753F64> /Library/Frameworks/iLifeFaceRecognition.framework/Versions/A/Resources/eOkaoDt .dylib
0x2369000 - 0x24d0fff +eOkaoFr.dylib ??? (???) <E355FB47-C5EF-50CF-621A-9B17A50E2850> /Library/Frameworks/iLifeFaceRecognition.framework/Versions/A/Resources/eOkaoFr .dylib
0x24d4000 - 0x24fdff7 com.apple.iLifeSlideshowCore 2.3.0 (233) <AFEB793C-AB48-3FEC-BE49-393824CB92F9> /Library/Frameworks/iLifeSlideshow.framework/Versions/A/Frameworks/iLifeSlidesh owCore.framework/Versions/A/iLifeSlideshowCore
0x2510000 - 0x261ffef com.apple.iLifeSlideshowProducer 2.3.0 (613) <160187AE-D805-3479-887E-B5A5FBE96F44> /Library/Frameworks/iLifeSlideshow.framework/Versions/A/Frameworks/iLifeSlidesh owProducer.framework/Versions/A/iLifeSlideshowProducer
0x266d000 - 0x27cbfe3 com.apple.iLifeSlideshowRenderer 2.3.0 (676) <76D67C6D-9148-380F-A356-ADF82550500E> /Library/Frameworks/iLifeSlideshow.framework/Versions/A/Frameworks/iLifeSlidesh owRenderer.framework/Versions/A/iLifeSlideshowRenderer
0x2829000 - 0x2842ff7 com.apple.iLifeSlideshowExporter 2.3.0 (252) <923A15E3-2BB3-35C6-AD09-36E1D8318BC6> /Library/Frameworks/iLifeSlideshow.framework/Versions/A/Frameworks/iLifeSlidesh owExporter.framework/Versions/A/iLifeSlideshowExporter
0x284f000 - 0x2878fe3 com.apple.audio.CoreAudioKit 1.6.1 (1.6.1) <7FFBD485-5251-776A-CC44-4470DD84112B> /System/Library/Frameworks/CoreAudioKit.framework/Versions/A/CoreAudioKit
0x2889000 - 0x290aff7 com.apple.NyxAudioAnalysis 12.2 (12.2) <278C9474-A560-4CCD-0414-DCAC5F2E2BB1> /Library/Frameworks/NyxAudioAnalysis.framework/Versions/A/NyxAudioAnalysis
0x2929000 - 0x2950fff com.apple.ExpressCheckout 1.0 (1.0) <F2DB3C97-F03F-3152-B436-B2DCB6100857> /Library/Frameworks/iLifePageLayout.framework/Versions/A/Frameworks/ExpressChec kout.framework/Versions/A/ExpressCheckout
0x296a000 - 0x29a5ff3 com.apple.iLifeImageAnalysis 3.0 (3) <87BA0439-1AA8-321A-844A-35A5D1B7898D> /Library/Frameworks/iLifePageLayout.framework/Versions/A/Frameworks/iLifeImageA nalysis.framework/Versions/A/iLifeImageAnalysis
0x2f61000 - 0x2fb101f +com.DivXInc.DivXDecoder 6.0.5 (6.0.5) /Library/QuickTime/DivX 6 Decoder.component/Contents/MacOS/DivX 6 Decoder
0x4d5b000 - 0x4fb3fe3 +com.elgato.mpegsupport EyeTV MPEG Support 1.2 (build 56) (1.2) <852AEA3A-1F5D-D964-F35A-6C8194090784> /Library/QuickTime/EyeTV MPEG Support.component/Contents/MacOS/EyeTV MPEG Support
0x526a000 - 0x532afff +net.sourceforge.webcam-osx.common 0.9.2 (0.9.2) /Library/QuickTime/macam.component/Contents/MacOS/macam
0x155a3000 - 0x155a7ff7 libcldcpuengine.dylib 1.5.6 (compatibility 1.0.0) <EF10CD42-F20F-EB7B-FC29-2AA973D5758D> /System/Library/Frameworks/OpenCL.framework/Libraries/libcldcpuengine.dylib
0x155d4000 - 0x155d6ff7 libclparser.dylib ??? (???) <F1C02810-AEEA-F661-FCED-DEA4EB7524D7> /System/Library/Frameworks/OpenCL.framework/Libraries/libclparser.dylib
0x1e44a000 - 0x1e5c3ff7 GLEngine ??? (???) <64C74F67-44B5-7DEF-CCA6-C8A9FF9BB60A> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x1e5f5000 - 0x1ea08fef com.apple.ATIRadeonX2000GLDriver 1.6.36 (6.3.6) <257CAA1D-6573-2932-E344-E96F6C9CDA84> /System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRade onX2000GLDriver
0x1ea3a000 - 0x1ea5efe7 GLRendererFloat ??? (???) <AD081A9B-1424-1F17-3C68-9803EBA37E8D> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x1f032000 - 0x1f0ccff7 unorm8_argb.dylib 1.5.6 (compatibility 1.0.0) <F486B4F7-B6B0-88F5-8A0C-570566F74618> /System/Library/Frameworks/OpenCL.framework/Libraries/ImageFormats/unorm8_argb. dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <749D24EE-54BD-D74B-D305-C13F5E6C95D8> /usr/lib/dyld
0x90003000 - 0x90

"Rebuild Library" option leads to external editor problems

Due to an issue with the Aperture internal tray I used the option "rebuild library". After the rebuild is completed it is not possible to open the images with an external editor or plugin anymore.
The message says that the image could not be handled as it has an unsupported format. Sorry, I cannot post the exact message as I use the german version of Aperture.
After getting the old Aperture library from my backup I tried it again. Before "rebuild library" everything works fine (except for the tray), after the rebuild I receive the message.

My affected images are masters inside the library and referenced ones - that doesn't matter. Images imported after the faulty rebuild work as usual. But it is still not possible to edit the older ones - those imported before the crash and rebuild. I couldn't find a workaround until now, except exporting and reimporting every single master, adjusting everything new and edit this new one with a plugin or the external editor.
I tried to export a project as a whole and reimport it, it dosen't change anything. If I open the package of the aplibrary I see that the TIFF or PSD is created by the command "edit in external editor" and I can open this in photoshop, but Aperture isn't able to hand it over to the external editor or the plugin. It seems to be a database problem not a problem of image rendering.
I also tried to rebuild the library again and repaired the user permissions of the database (CMD ALT during aperture start) - Doesn't help.
I imported an affected mediabase into another Aperture installation on my notebook which was not affected before. But the imported images inside the project won't open with the external editor or any plugin too. So I think it has nothing to do with the general installation of Aperture. For sure it is an error inside the database caused by the automatic rebuild of the database after a crash.
For all aperture users I can give the following two hints:
1) Backup your Aperture database carefully.
2) After a crash of Aperture and an automatic or any other rebuild of the database, check FIRST if your database is infected by our problem. Open some images with a plugin or the external editor. If this doesn't work, go back to your vault version.
My mistake was to backup RIGHT AFTER the crash, without checking everything including the external editor command. Because of this I infected my vault version with the error too.....
Apple is needed for solving this issue. It should be possible for the programmers to find the error inside an exported project/mediabase, which is affected with the problem. I would provide such a file to Apple for examination.
Wolfram

Can't open iphoto file to edit in Elements 10 even though external editor is set

Right clicking on iphoto file, selecting "edit in external editor" resullts in spinning beach ball. Each attempt at opening a file initiates a reopening of Elements even though it is already opened.

Can you open images normally in Photoshop Elements? I would recommend including this information as well as which verson of iPhoto and Mac OS you are using to the Photoshop Elements forum. It might also possibly be a problem with iPhoto but the users in the Photoshop Elements forum should better be able to determine where the problem lies.

Opening a clip in an external editor

Similar Messages

Maybe you are looking for