IPhoto and Aperture cannot browse one another's libraries
When I go to File>Show iPhoto Browser in Aperture, there is nothing there, and just says "Missing Content Library."
And vice-versa, with iPhoto, there is nothing when trying to browse the Aperture library.
I am coming from a Lightroom background, new to using the Mac apps, but everything is in its newly installed default mode, on a brand new MacBook Pro.
And yes, I have already images to both. I've even done adjustments and tagging and faces, etc..
Cannot find the answer to this issue ANYWHERE on the web.
Another user has this problem with iPhoto over on that forum, so it suggests an issue with the iLife Media Browser, which is what this feature is called.
As it works in the other account, it suggests that a third element is blocking the process. It may be another plist file some where.
Have a look at this thread:
http://discussions.apple.com/thread.jspa?threadID=1945835&tstart=0
Particularly Old Toad's method for troubleshooting Preferences in Leopard.
Regards
TD
Similar Messages
-
How does one transfer Files from an old MacBook Pro to a new iMac?
10.5.3 is at least part of the problem. You need to apply the latest updates to that mac.
See How do I set up a new Mac from an old one, its backups, or a PC? Select the appropriate link and follow the instructions carefully. -
Cannot open apps iPhoto and Aperture after updates
Cannot open apps iPhoto and Aperture after updates. I'm operating ML on mbpro. Now apps will not open. Simply that.
Not simple, if as ML implies you are running Mountain Lion! If you only mean Lion, then it would be useful for you to open another User Account, and as that User test to see if either app will launch?
Ernie -
I cannot afford an iMac, can anyone recommend a widescreen Monitor for my 15" MacBook Pro. It will be used mainly for iPhoto and Aperture. TF
Pair a wireless KB with the laptop and all should be well when you attach the laptop to the iMac and invoke TDM. But as Denny mentions, it does seem like the waste of a good iMac to use it in just this configuration. Why is the laptop primary?
-
Use both iPhoto and Aperture with one library-best practice?
I'd like to use both iPhoto and Aperture, but have both programs use/update just one photo library. I have the latest versions of both programs, but was wondering if the optimum approach would be to:
a)point Aperture to the existing iPhoto library and use that as the library for both programs
or
b)import the entire iPhoto library into a new Aperture library, delete the iPhoto library, and point iPhoto to use the Aperture library.
I should point out that up to now I've been using iPhoto exclusively, and have close to 20K photos in the iPhoto library, tagged with Faces, organized into various albums, etc; if that makes a difference...
Appreciate any advice!
Thanks,
DaveThanks Frank! I'll try it that way.
Appreciate the help! -
i cannot sync photos to iphone 5 or iPad , since updating to new iPhoto and
Aperture Sync option no longer availableSorry for lack of info
i usually sync photos from Aperture on MacBook Pro to iPhone 5 and iPad
using iTunes (all latest updates) . Sync worked perfectly
but
since last update of OS X and migration from aperture to new "PHOTOS"
icloud turned off, sync won't put any photos onto devices
I have restored both devices , leaving sync photos option off(to delete any previous photos)
then try to sync photos and nothing happens
i I can sync folders but that isn't how I want it??
hope this is a little clearer -
Hey there, Apple Support Communities.
To start, I'm working on a MBP Retina 15" with a 2.3GHz i7 processor and 16 GB of RAM. 10GB free on a 256GB SS HD. Attached are two external HDs - one 1TB Western Digital portable drive from 2011, one 2TB Porsche LaCie non-portable drive from 2013; both connected via USB. All photo libraries in question are on the external drives.
I have Aperture 3.5.1 and iPhoto 9.5.1. I prefer to work in Aperture.
The Issue(s)
Over the years, I have accumulated a number of iPhoto libraries and Aperture libraries. At one point, I thought my WD drive was dying so I purchased the LaCie and copied all libraries over the the LaCie drive. (Turns out, there's probably an issue with my USB port reading drives, because I can once again see the WD drive and occasionally I can't see the LaCie drive.)
So now I have old version of some libraries on the WD drive, and new versions on the LaCie drive.
When I was moving things, I ran the software Gemini to de-dupe my iPhoto libraries. Not sure what effect that may have had on my issues.
In my main Aperture library and in some iPhoto libraries, I get the image-not-found badge or exclamation point. I've dug through the hidden Masters folders in various libraries to find the original image. In some cases, I have been able to find the original image, sometimes in a different version of the iPhoto library.
My Question(s)
1. For Aperture libraries that have missing originals, is there some magical way to find them, or have they just disappeared into the oblivion?
2. For iPhoto libraries that have missing originals and I have found the original in another iPhoto library, what is the best way to proceed?
3. Are there quirks to merging iPhoto and Aperture libraries (by using the Import->Library) feature that I should be aware of?
TL;DR: Too many iPhoto and Aperture libraries, and not all the original pictures can be found by the libraries anymore, though some originals still do exist in other libraries. Steps/process to fix?
Thank you! Let me know if you need add'l info to offer advice.
With appreciation,
ChristieThat will not be an easy task, Christie.
I am afraid, your cleaning session with Gemini may have actually removed originals. I have never used this duplicate finder tool, but other posters here reported problems. Gemini seems to replace duplicate original files in photo libraries by links, and this way, deleting images can cause the references for other images to break. And Aperture does not follow symbolic links - at least, I could never get it to find original files this way, when I experimented with this.
1. For Aperture libraries that have missing originals, is there some magical way to find them, or have they just disappeared into the oblivion?
You have to find the originals yourself. If you can find them or restore them from a backup, Aperture can reconnect them. The reconnect panel can show you, where the originals are supposed to be, so youcan see the filename and make a Spotlight search.
For iPhoto libraries that have missing originals and I have found the original in another iPhoto library, what is the best way to proceed?
Make a copy of the missing original you found in a folder outside the iPhoto library. You can either open the iPhoto library in Aperture and use "File > Locate Referenced file" to reconnect the originals, or simply reimport them. Then Lift&Stamp all adjustments and metadata to the reimported version.
See this manual page on how to reconnect originals: Aperture 3 User Manual: Working with Referenced Images (the paragraph: Reconnecting Missing or Offline Referenced Images)
Are there quirks to merging iPhoto and Aperture libraries (by using the Import->Library) feature that I should be aware of?
References images will stay referenced, managed will remain managed. You need to unhide all hidden photos in iPhoto - this cannot be done in Aperture.
and not all the original pictures can be found by the libraries anymore, though some originals still do exist in other libraries. Steps/process to fix?
That is probably due to Gemini's replacing duplicate originals by links, and your best cause of action is to fix this before merging the libraries. Reconnecting can be done for your iPhoto libraries in Aperture. -
Print quality difference between iphoto and aperture...?
when ordering books, is there a print quality difference between using iPhoto and Aperture? or are they sent to the same lab?
it's possible i may have some setting wrong, but when i order a book using iphoto, i never really feel the quality is that great. it's good, i just feel it could be a lot better. the print quality sort of reminds me of newsprint, albeit high quality newsprint. similar sized prints made at home on my basic 3-in-1 printer look better.
thanks...Previews are what you view on your display. When you import a photo into Aperture (and I'm pretty sure iPhoto as well), your computer automatically generates a preview for quick viewing. The original images are stored in your library, but it is the preview that you see.
In Aperture, you are able to set the size and quality of these previews. When sharing photos between Aperture and iPhoto, the process is as follows:
Let's say that your images are stored in Aperture, but you also want to be able to view them in iPhoto without taking up too much room on your hard drive. Essentially, if you were to import the originals into iPhoto as well, you would be storing two exact, yet separate copies of the same image on your hard drive. As you are aware, with large images (whether JPEG's, and especially RAW) this would put quite a tax on your storage capacity after not too long.
So, you have your images in one or the other (in this case Aperture), but you want to play around with them in iPhoto. What you can do, is open iPhoto, go to the File menu and then select, Show Aperture Library. This will open a window with all of the contents of your Aperture Library. You can then drag any images you want into iPhoto . The only thing is, you are not dragging the original JPEG's, but rather, the previews of those images. If you have those previews set to a lower quality (again for capacity concerns), you will only have lower quality and lower detailed images in iPhoto. These images might not be ideal, or even suitable for printing high quality prints. The previews that you generate in Aperture though can be adjusted to be extremely high quality with no size limits.
My thinking was that since you mentioned Aperture, it sounded like you had experience with working with it and with ordering a photo book through Aperture. I guess you were saying that you ordered via iPhoto, weren't happy with the quality and were wondering if Aperture created books were better.
Anyway, if this is the case, I cannot answer that for you. I have never ordered a book through Aperture. If the quality of your images is good, you should be able to get a decent product no matter where you order it from. There is not doubt that the materials used and the print shop that does the work makes a difference, but if your images are good, you should still get a decent product through iPhoto. Perhaps iPhoto isn't the way to go though if you have had poor experiences with them.
If you haven't used Aperture yet, I would highly recommend it though aside from the photo book aspect of this thread. It is a stellar product.
I hope this helps.
Message was edited by: macorin -
How do I add photos to photo stream from BOTH iPhoto and Aperture
I use Photostream for displaying photos I have taken on my DSLR on my iPad. I take the photos, download them into iPhoto and then add them to Photostream. They then appear on my iPad for display to friends and family. But some of my photos are now being manipulated in Aperture. I'd like to display these in the same Photostream, but so far, because I have to choose either the iPhoto libray or the Aperture library - but not both - for the photostream, the only way I can do this is to export the photos from Aperture into iPhoto (which doubles up my photo files). Is there a simpler way to do this?
OK. But let's say you are in iPhoto and you switch libraries so that you are now looking at your Aperture library. In order to add photos to your photostream you have to activate iCoud/photostream again in your iPhoto preferences for the new library. Then you get a message up which says: "iCloud Photos for [my iCloud email address] is being used with another library named "iPhoto Library". Switching iCoud Photos to this library will turn it off in iPhoto library."
In other words this does not solve my problem of how to have one photostream which contains photos from BOTH iPhoto and Aperture.
Is it perhaps possible to merge the iPhoto and Aperture libraries so that you only have one library for both applications? -
Is it possible to keep both iPhoto and Aperture on the same Mac
I would like to use both IPhoto (for day by day pictures) and Aperture (for pictures made with my SLR in Raw format).
Is anybody able to advice me about this opportunity?You can keep both Applications (iPhoto and Aperture) on the same computer and separate libraries for iPhoto and Aperture; images from both libraries will/should be available in other Applications from the Media Browser. In the long run, after you get accustomed to working Aperture, you will find it more convenient to migrate all your images to Aperture. Aperture has the more efficient storage strategy, you need less disk space to store multiple versions of the same image in Aperture than in iPhoto, and Aperture is the more versatile tool.
It is easy to migrate iPhoto libraries to Aperture, but that is a one way road, if you want to export back to iPhoto, you can export your images, but not all of your library structure. -
Using both iPhoto and Aperture workflow help
I am using both aperture 3 and iPhoto 9 to edit and keep track of images
I imported images to iPhoto the have Aperture import the iPhoto library this way I have i library..I know if something happens to it I am screwed
1) I know that Aperture is non destructive, is iPhoto?
2) will changes ( like GPS location) in aperture be applied to iPhoto images
3) looking to see if I can make changes made in one program appear in the other
4) or it it better to import the images in from my external drive (how they were before iPhoto), and have a separate library for each programHere's the best advice for using both iPhoto and Aperture:
Pick one horse and ride it. They both do the same job. If you're shooting Raw or high volumes of Jpeg, then definitely go with Aperture. If you're doing family snaps with a point and shoot stick with iPhoto. Using both adds unnecessary complexity to everything, and with complexity comes the risk of error and data loss.
1) I know that Aperture is non destructive, is iPhoto?
Yes. In a wholly different way, mind you, but yes. WHen you edit an image in iPhoto it creates a new file called the Modified Version. You can always revert to the Original photo. If you edit only with iPhoto then you can also avoid generational loss.
2) will changes ( like GPS location) in aperture be applied to iPhoto images
No.
3) looking to see if I can make changes made in one program appear in the other
You can't.
4) or it it better to import the images in from my external drive (how they were before iPhoto), and have a separate library for each program
It makes no sense to use both programs.
Aperture and iPhoto are entirely different applications that work in very different ways.
The only communication between the two is as follows:
Aperture is able to parse the iPhoto Library to allow it to import the contents while stacking the Originals and Modified versions, preserving metadata and so forth.
Aperture can share its Previews with the iLife apps, including iPhoto.
That's it.
So, specifically, what interaction there is between the two is designed to facilitate migration from iPhoto to the more powerful app. After that, iPhoto has exactly the same relationship to the Aperture Library as, say, Pages or iMovie.
iPhoto has no knowledge of, and knows nothing of how the Aperture Library works. It cannot read the Aperture library.
What are you hoping to achieve by running both?
Regards
TD -
IPhoto and Aperture sharing a library
I want to use Aperture 3 while my wife uses iPhoto on the same computer. We have a gazillion photos in the library and I want both programs to be able to access the same photos. I've imported the iphoto library to Aperture and everything's fine.
The question is: when I import new photos into the library (via iphoto), will both programs recognize the new imports, or do I need to constantly re-import the library into Aperture for it to recognize new additions to the library?The relationship between iPhoto and Aperture is not dynamic. Updates to one library are not available to the other.
So, yes, if you add to the iPhoto Library you will also need to add to the Aperture Library, and vice versa.
If you use a Referenced Library in iPhoto (which I do not recommend) and Referenced masters in Aperture then you might be able to automate the process somewhat with Automator and a watched folder system.
For updating Aperture with new imports to iPhoto you can drag the new Events over to Aperture using the File -> Import -> Show iPhoto Browser command. Note that this will always mean Managed Masters.
Regards
TD -
IPhoto and Aperture crash on launch, iPhoto and Aperture crash on launch
Hi everyone.
Recently when I launch iPhoto it crashes immeadiately and I have to 'Force quit' the application. I haven't been able to use it for weeks! I decided to purchase Aperture and when I open it I get the same problem! Both iPhoto and Aperture don't seem to want to work...
I recently bought a new Nikon camera and imported some pictures and videos from that, so was wondering if that was causing the problem. I haven't been able to sync any more photos to my library since the problem happened- I have to manually drag and drop from Finder.
Can anyone help? Here is a crash report from iPhoto.
Thanks
Jon
Date/Time: 2012-05-29 15:37:39 +0100
OS Version: 10.7.4 (Build 11E53)
Architecture: x86_64
Report Version: 9
Command: iPhoto
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Version: 9.2.2 (9.2.2)
Build Version: 2
Project Name: iPhotoProject
Source Version: 629040000000000
App Item ID: 408981381
App External ID: 6836991
Parent: launchd [145]
PID: 15946
Event: hang
Duration: 3.20s
Steps: 33 (100ms sampling interval)
Pageins: 1
Pageouts: 0
Process: iPhoto [15946]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Architecture: i386
UID: 501
Thread 0x3c762
User stack:
33 ??? (in iPhoto) [0x10269]
33 ??? (in iPhoto) [0x10dda]
33 NSApplicationMain + 1054 (in AppKit) [0x99b48bd9]
33 -[NSApplication run] + 911 (in AppKit) [0x998b7cb1]
33 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113 (in AppKit) [0x998bb942]
33 _DPSNextEvent + 678 (in AppKit) [0x998bc0d8]
33 BlockUntilNextEventMatchingListInMode + 88 (in HIToolbox) [0x965078fa]
33 ReceiveNextEventCommon + 168 (in HIToolbox) [0x965079b6]
33 RunCurrentEventLoopInMode + 318 (in HIToolbox) [0x96500723]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1112 (in CoreFoundation) [0x912a19c8]
33 __CFRunLoopDoSources0 + 440 (in CoreFoundation) [0x91277bb8]
33 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15 (in CoreFoundation) [0x9127813f]
33 __NSThreadPerformPerform + 503 (in Foundation) [0x92ac5e0c]
33 -[NSObject performSelector:withObject:] + 65 (in CoreFoundation) [0x91300d11]
33 -[RKInvoker _invokeTarget:] + 33 (in RedRock) [0x1d71771]
33 -[NSInvocation invoke] + 137 (in CoreFoundation) [0x913039d9]
33 __invoking___ + 29 (in CoreFoundation) [0x91303a9d]
33 ??? (in iPhoto) [0x29cf50]
33 ??? (in iPhoto) [0x8be1f]
33 ??? (in iPhoto) [0x8bfea]
33 ICACopyObjectPropertyDictionary + 24 (in ImageCapture) [0x9ac7c236]
33 ICACopyObjectPropertyDictionary_Deprecated + 89 (in ImageCapture) [0x9ac7c297]
33 ICACommand::ProcessCommand() + 74 (in ImageCapture) [0x9ac7b100]
33 ICACommand::SendSync() + 62 (in ImageCapture) [0x9ac7b204]
33 ICAAESendMessage + 58 (in ImageCapture) [0x9ac7b4ce]
33 AESendMessage + 4116 (in AE) [0x9531c24f]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1428 (in CoreFoundation) [0x912a1b04]
33 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x912989da]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c7a6 DispatchQueue 1701273966
User stack:
33 _dispatch_mgr_thread + 53 (in libdispatch.dylib) [0x91b1885f]
33 kevent + 10 (in libsystem_kernel.dylib) [0x9ae5990a]
Kernel stack:
33 kqueue_scan + 416 (in mach_kernel) [0xffffff800053a660]
Thread 0x3c7a8
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7aa
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTRunLoopThread run:] + 509 (in ProXTCore) [0x176f9cd]
33 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273 (in Foundation) [0x92a7d4af]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1428 (in CoreFoundation) [0x912a1b04]
33 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x912989da]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c7ab
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTRunLoopThread run:] + 509 (in ProXTCore) [0x176f9cd]
33 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273 (in Foundation) [0x92a7d4af]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1428 (in CoreFoundation) [0x912a1b04]
33 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x912989da]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c7f9
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7fa
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7fb
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7fc
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7fd
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTRunLoopThread run:] + 509 (in ProXTCore) [0x176f9cd]
33 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273 (in Foundation) [0x92a7d4af]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1428 (in CoreFoundation) [0x912a1b04]
33 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x912989da]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c7fe
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c7ff
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c800
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c801
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c802
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c803
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c804
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c805
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c806
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c807
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c808
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c809
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80a
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80b
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 416 (in ProXTCore) [0x176d590]
33 -[XTMsgQueue waitForMessage] + 50 (in ProXTCore) [0x176e5e2]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80c
User stack:
33 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x9329e42c]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80d
User stack:
33 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x9329e42c]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80e
User stack:
33 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x9329e42c]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c80f
User stack:
33 pthread_cond_timedwait$UNIX2003 + 70 (in libsystem_c.dylib) [0x9329e3e0]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c812
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[RAOperationQueueImpl _workThread] + 217 (in iLifeSQLAccess) [0x1860dc9]
33 -[RALatchTrigger wait] + 81 (in iLifeSQLAccess) [0x1860f41]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c813
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[RAOperationQueueImpl _workThread] + 217 (in iLifeSQLAccess) [0x1860dc9]
33 -[RALatchTrigger wait] + 81 (in iLifeSQLAccess) [0x1860f41]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c82e
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 438 (in ProXTCore) [0x176d5a6]
33 -[XTThread handleMessage:] + 1285 (in ProXTCore) [0x176ee35]
33 -[XTDistributor distributeMessage:] + 726 (in ProXTCore) [0x176f2e6]
33 -[XTSubscription postMessage:] + 181 (in ProXTCore) [0x176fb95]
33 -[NSObject performSelector:withObject:] + 65 (in CoreFoundation) [0x91300d11]
33 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166 (in ProXTCore) [0x1778506]
33 -[NSObject performSelector:] + 58 (in CoreFoundation) [0x913091aa]
33 -[RKAsyncImageRenderer _backgroundRenderThread:] + 177 (in RedRock) [0x1d4f331]
33 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x92ac96a6]
33 -[NSConditionLock lockWhenCondition:beforeDate:] + 294 (in Foundation) [0x92ac97d2]
33 -[NSCondition waitUntilDate:] + 427 (in Foundation) [0x92b033c3]
33 pthread_cond_timedwait_relative_np + 47 (in libsystem_c.dylib) [0x932edf7b]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c847
User stack:
33 start_wqthread + 30 (in libsystem_c.dylib) [0x932ed6fe]
33 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9ae5902e]
Kernel stack:
33 workqueue_exit + 1616 (in mach_kernel) [0xffffff80005a4200]
Thread 0x3c84c
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378 (in Foundation) [0x92add0c4]
33 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x912a1088]
33 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x912a11dc]
33 __CFRunLoopRun + 1428 (in CoreFoundation) [0x912a1b04]
33 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x912989da]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c84e
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __select + 10 (in libsystem_kernel.dylib) [0x9ae58b42]
Kernel stack:
33 wakeup + 992 (in mach_kernel) [0xffffff8000555010]
Thread 0x3c851
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[RAOperationQueueImpl _workThread] + 217 (in iLifeSQLAccess) [0x1860dc9]
33 -[RALatchTrigger wait] + 81 (in iLifeSQLAccess) [0x1860f41]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9ae56c22]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x3c857
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 __NSThread__main__ + 1582 (in Foundation) [0x92ad0dd5]
33 -[NSThread main] + 45 (in Foundation) [0x92ad0e25]
33 -[XTThread run:] + 438 (in ProXTCore) [0x176d5a6]
33 -[XTThread handleMessage:] + 1285 (in ProXTCore) [0x176ee35]
33 -[XTDistributor distributeMessage:] + 726 (in ProXTCore) [0x176f2e6]
33 -[XTSubscription postMessage:] + 181 (in ProXTCore) [0x176fb95]
33 -[NSObject performSelector:withObject:] + 65 (in CoreFoundation) [0x91300d11]
33 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166 (in ProXTCore) [0x1778506]
33 -[NSObject performSelector:withObject:] + 65 (in CoreFoundation) [0x91300d11]
33 -[RKInvoker _invokeTargetWithPool:] + 68 (in RedRock) [0x1d82fd4]
33 -[RKInvoker _invokeTarget:] + 33 (in RedRock) [0x1d71771]
33 -[NSInvocation invoke] + 137 (in CoreFoundation) [0x913039d9]
33 __invoking___ + 29 (in CoreFoundation) [0x91303a9d]
33 ??? (in iPhoto) [0x8b6e5]
33 ??? (in iPhoto) [0x8b794]
33 ??? (in iPhoto) [0x8b88f]
33 ??? (in iPhoto) [0x8bad6]
33 ??? (in iPhoto) [0x8c29c]
33 _CF_forwarding_prep_0 + 50 (in CoreFoundation) [0x912fdaa2]
33 ___forwarding___ + 894 (in CoreFoundation) [0x912fde8e]
33 -[RKInvoker forwardInvocation:] + 133 (in RedRock) [0x1d71585]
33 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 160 (in Foundation) [0x92ac5286]
33 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 1236 (in Foundation) [0x92ac57f0]
33 -[NSCondition wait] + 304 (in Foundation) [0x92ad2be8]
33 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x9329e42c]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3c865
User stack:
33 thread_start + 34 (in libsystem_c.dylib) [0x932ed6de]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x932e9ed9]
33 _ZL13startIOThreadPv + 160 (in CoreVideo) [0x92f3fd05]
33 CVDisplayLink::runIOThread() + 945 (in CoreVideo) [0x92f400cd]
33 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x9329e42c]
33 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9ae5883e]
Kernel stack:
33 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059daa0]
Thread 0x3cade
User stack:
33 start_wqthread + 30 (in libsystem_c.dylib) [0x932ed6fe]
33 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9ae5902e]
Kernel stack:
33 workqueue_exit + 1616 (in mach_kernel) [0xffffff80005a4200]
Binary Images:
0x1000 - 0xd28fe7 com.apple.iPhoto 9.2.2 (9.2.2) <169B41B1-53E9-39E5-8154-43D2B0805600> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0x176a000 - 0x17cafff com.apple.proxtcore 1.3 (140.59) <6C899840-6789-3A2A-A090-BF368536C5EE> /Applications/iPhoto.app/Contents/Frameworks/ProXTCore.framework/Versions/A/Pro XTCore
0x181c000 - 0x18fbff3 com.apple.iLifeSQLAccess 1.6 (30.14) <2CBF1F57-610A-33B8-9607-30C38DF4155B> /Applications/iPhoto.app/Contents/Frameworks/iLifeSQLAccess.framework/Versions/ A/iLifeSQLAccess
0x1d29000 - 0x2170fe3 com.apple.RedRock 1.8.2 (233.28) <798E41E3-815E-3D30-B885-7C53F38A7A8A> /Applications/iPhoto.app/Contents/Frameworks/RedRock.framework/Versions/A/RedRo ck
0x91266000 - 0x9143dfe7 com.apple.CoreFoundation 6.7.2 (635.21) <4D1D2BAF-1332-32DF-A81B-7E79D4F0A6CB> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x91b17000 - 0x91b25fff libdispatch.dylib ??? (???) <2F918480-12C8-3F22-9B1A-9B2D76F6F4F5> /usr/lib/system/libdispatch.dylib
0x92a71000 - 0x92d7bff3 com.apple.Foundation 6.7.2 (833.25) <4C52ED74-A1FD-3087-A2E1-035AB3CF9610> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92f3e000 - 0x92f61fff com.apple.CoreVideo 1.7 (70.3) <4234C11C-E8E9-309A-9465-27D6D7458895> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x9328d000 - 0x93358fff libsystem_c.dylib ??? (???) <52421B00-79C8-3727-94DE-62F6820B9C31> /usr/lib/system/libsystem_c.dylib
0x95304000 - 0x9533aff7 com.apple.AE 527.7 (527.7) <7BAFBF18-3997-3656-9823-FD3B455056A4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x964fe000 - 0x96844ff3 com.apple.HIToolbox 1.9 (???) <409E6397-0DCB-3431-9CCC-368317C62545> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x998b2000 - 0x9a347ff6 com.apple.AppKit 6.7.3 (1138.47) <D8CD06D7-F18C-39BE-BC68-B343F87F0469> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x9ac79000 - 0x9ac8eff7 com.apple.ImageCapture 7.0.1 (7.0.1) <1C8933A9-C7C6-36E9-9D8B-0EF08ACA3315> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x9ae40000 - 0x9ae5eff7 libsystem_kernel.dylib ??? (???) <3705DE40-E00F-3E37-ADB0-D4AE5F9950F5> /usr/lib/system/libsystem_kernel.dylib
Process: AELWriter [12294]
Path: /usr/sbin/AELWriter
Architecture: x86_64
UID: 0
Thread 0x2defd DispatchQueue 1
User stack:
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x2defe DispatchQueue 2
User stack:
33 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff902d531a]
33 kevent + 10 (in libsystem_kernel.dylib) [0x7fff864317e6]
Kernel stack:
33 kqueue_scan + 416 (in mach_kernel) [0xffffff800053a660]
Binary Images:
0x100000000 - 0x100001ff7 AELWriter ??? (???) <60FDC042-2449-A0E5-D11A-B7D7AD0D3447> /usr/sbin/AELWriter
0x7fff8641a000 - 0x7fff8643afff libsystem_kernel.dylib ??? (???) <1DDC0B0F-DB2A-34D6-895D-E5B2B5618946> /usr/lib/system/libsystem_kernel.dylib
0x7fff902d3000 - 0x7fff902e1fff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
Process: AirPort Base Station Agent [241]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
Architecture: x86_64
UID: 501
Thread 0x8f9
User stack:
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x910
User stack:
Kernel stack:
33 kqueue_scan + 416 (in mach_kernel) [0xffffff800053a660]
Thread 0x916
User stack:
Kernel stack:
33 wakeup + 992 (in mach_kernel) [0xffffff8000555010]
Binary Images:
0x10b003000 - 0x10b01afff com.apple.AirPortBaseStationAgent 1.5.5 (155.7) <0D37CC05-D1C6-3C6C-BACD-A88D4BD4C3CD> /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
Process: aosnotifyd [54]
Path: /usr/sbin/aosnotifyd
Architecture: x86_64
UID: 0
Thread 0x149 DispatchQueue 1
User stack:
33 start + 52 (in aosnotifyd) [0x10e21b0b4]
33 main + 74 (in aosnotifyd) [0x10e2229ec]
33 -[AOSNotificationDaemon startup] + 1294 (in aosnotifyd) [0x10e2227b3]
33 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267 (in Foundation) [0x7fff90ca5f7b]
33 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff87ec5486]
33 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff87ec5c74]
33 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff87ebd50c]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8642f67a]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x31a DispatchQueue 2
User stack:
33 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff902d531a]
33 kevent + 10 (in libsystem_kernel.dylib) [0x7fff864317e6]
Kernel stack:
33 kqueue_scan + 416 (in mach_kernel) [0xffffff800053a660]
Thread 0x37e
User stack:
33 thread_start + 13 (in libsystem_c.dylib) [0x7fff8a121b75]
33 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8a11e8bf]
33 __NSThread__main__ + 1575 (in Foundation) [0x7fff90cf46a2]
33 -[NSThread main] + 68 (in Foundation) [0x7fff90cf472a]
33 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 335 (in Foundation) [0x7fff90cfffd7]
33 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff87ec5486]
33 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff87ec5c74]
33 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff87ebd50c]
33 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff8642f67a]
Kernel stack:
33 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x887
User stack:
Kernel stack:
33 wakeup + 992 (in mach_kernel) [0xffffff8000555010]
Binary Images:
0x10e219000 - 0x10e25afff aosnotifyd ??? (???) <5287944C-EDF3-3175-81A3-CC1BEF4E43F7> /usr/sbin/aosnotifyd
0x7fff8641a000 - 0x7fff8643afff libsystem_kernel.dylib ??? (???) <1DDC0B0F-DB2A-34D6-895D-E5B2B5618946> /usr/lib/system/libsystem_kernel.dylib
0x7fff87e8d000 - 0x7fff88061ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8a0d0000 - 0x7fff8a1adfef libsystem_c.dylib ??? (???) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff902d3000 - 0x7fff902e1fff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff90c9a000 - 0x7fff90fb3fff com.apple.Foundation 6.7.2 (833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
Process: AppleMobileDeviceHelper [11170]
Path: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/MacOS/AppleMobileDeviceHelper
Architecture: i386
UID: 501
Thread 0x24a52
User stack:
33 ??? (in AppleMobileDeviceHelper) [0x2ace]
33 ??? (in AppleMobileDeviceHelper) [0x49fd]
33 ??? (in AppleMobileDeviceHelper) [0xdb11]
33 __select + 10 (in libsystem_kernel.dylib) [0x9ae58b42]
Kernel stack:
33 wakeup + 992 (in mach_kernel) [0xffffff8000555010]
Thread 0x24a58 DispatchQueue 1701273966
User stack:
33 _dispatch_mgr_thread + 53 (in libdispatch.dylib) [0x91b1885f]
33 kevent + 10 (in libsystem_kernel.dylib) [0x9ae5990a]
Kernel stack:
33 kqueue_scan + 416 (in mach_kernel) [0xffffff800053a660]
Thread 0x24c11
User stack:
Kernel stack:
33 wakeup + 992 (in mach_kernel) [0xffffff8000555010]
Binary Images:
0x1000 - 0x17ff7 com.apple.SyncServices.AppleMobileDeviceHelper 5.0 (837) <E5568885-1F2A-3621-B2E3-E0EE18C4A10D> /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/MacOS/AppleMoIf it also hangs in another account then the issue is systemic. You'll need to reinstall
To re-install iPhoto
1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
2a: On 10.5: Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
2b: On 10.6: Those receipts may be found as follows: In the Finder use the Go menu and select Go To Folder. In the resulting window type
/var/db/receipts/
2c: on 10.7 they're at
/private/var/db/receipts
A Finder Window will open at that location and you can remove the iPhoto pkg files.
3. Re-install.
If you purchased an iLife Disk, then iPhoto is on it.
If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
If you purchased it on the App Store or have a Recent Mac you can find it in your Purchases List.
If that fails you'll be reinstalling the OS.
Regards
TD -
IPhoto and Aperture referenced library issues
Hi,
For the last couple of days I've been busy trying to get my iPhoto/Aperture library to work properly. I recently created a referenced library using Aperture because of lack of space on my internal ssd. I can see all of my Projects, thumbnails, metadata etc. in both iPhoto and Aperture when my external drive is disconnected. However, there are two major issues:
1) Most of the video thumbnails are broken, both in Aperture and iPhoto. By double clicking a thumbnail of a video (.mov, .avi etc.) it sometimes starts playing (with the external drive connected), sometimes it doesn't, totally inconsistent. I can export the video and it works just fine.
2) While using iPhoto with the external drive disconnected, all Events are there, the thumbnails are there, everything looks ok, but I can only view some of the previews/photos after double clicking the thumbnails. A dialogue opens up saying "The volume for [imagefilename] cannot be found. Insert the disk or connect to the server volume..", but I can actually see the full size preview behind this dialogue. By clicking "Cancel" the photo dissapears and is replaced by a black screen with a grey exclamation mark. This does not occur while using Aperture, I can see all of my previews in full glory when the external drive is disconnected. However, with the external drive connected everything works in iPhoto (except above mentioned issue with videos).
Please boys and girls, I need your help on this one!
System information
OS: Maverick 10.9.1
Aperture: 3.5.1
iPhoto: 9.5.1
Thanks!
//Michel1. Are these videos different formats? Or the same?
2. See my answer to your duplicate post. -
I like iphone for the fact that i can easily access my photos, look at them, and create calendars, books, ect, from them very easily, and i also enjoy the interface.
i purchased aperture to be able to get more control out of editing some of my RAW files.
What is the best way to have iPhoto and Aperture coexist in the same world on my computer? Or do you think I need to just move everything from iPhoto into Aperture and just use Aperture to manage my photos as well?
I noticed that in Aperture I can't even make a calendar, it's very odd.
I wish i could keep everything in iPhoto, and when i want to edit a photo, i could send it to Aperture, edit it, and have it just update in iPhoto.
is that possible?I wish i could keep everything in iPhoto, and when i want to edit a photo, i could send it to Aperture, edit it, and have it just update in iPhoto.
is that possible?
No, you cannot sync an Aperture Library with an iPhoto Library. You will have to make up your mind, which Application of the two you will want to use primarily.
I use Aperture because of its superior organizational tools and more elaborate image processing options, and when I need a calendar, I export the images from Aperture and import them to iPhoto.
But if you are happy with iPhoto, by all means stay with iPhoto. Aperture has a steep learning curve, and if iPhoto is sufficient for your needs, why give it up for something more complicated?
You can always import selected images or events from iPhoto to Aperture for processing by using the iPhoto Browser in Aperture. After processing in Aperture you can export the image again and reimport to iPhoto.
Regards
Léonie
Maybe you are looking for
-
I am looking for is trying to figure out what am I doing wrong for this compile time error message to appear when I try to deploy the BPEL service. The BPEL diagram indicates no errors. Error: [Error ORABPEL-10902]: compilation failed [Description]:
-
Data transfer from dma to raid disk
Hi, I am new at device drivers. I have a problem and I cant solve it. We have pci express card, it writes data to dma, I wrote user app, there I allocate buffer and give adress and size to dma and dma writes data to that buffer and I try to write da
-
I have a Cisco aironet 1040. On my Accespoint i have 2 vlans: 1 for my wifi phones and 1 for my network. Wifi Lan has the SSID LAN with WPA enterprise authentication to a radius server(ms server 2008). Wifi Phone has SSID PHONE and vlan 50 with local
-
"ORA-12222 TNS no such protocol adapter" When running Forms after installing Portal
We have a Forms 6i (web) application running on 9iAS. This worked fine. But after installing Portal on the same 9iAS, we got the following error when starting the WebForms application: ORA-12222 TNS no such protocol adapter Who knows a solution? Conf
-
Mac OS Chrome browser - Muse Photoshop buttons not visible
Photoshop buttons are not visible on Chrome on Mac OS X, but show up fine and work properly on Mac OS X Safari browser.