CaptureCoreService.xpc issue (DB/Pro 8.3)
Some users have noticed a jumping services icon in their dock after starting/while running CO 8.3 (Pro/DB). It applies to the (new) CaptureCoreService. I have contacted Phase One on the issue with the following observations.
- seems to happen on Mavericks, not Yosemite
- can be mitigate by managing capture providers in the Preferences
Note that CO 8.3 seems to run just fine, despite the jumping icon.
Workaround
If you do not tether into CO8, just disable all providers in Preferences > Capture tab.
If you do tether, just enable only the provider needed. Limited testing from my side shows that in particular the Leaf provider in combination with Mavericks causes the jumping behaviour. As a result Leaf shooters should test the 8.3 update carefully although I have yet no reasons to believe that it is not working properly.
- seems to happen on Mavericks, not Yosemite
- can be mitigate by managing capture providers in the Preferences
Note that CO 8.3 seems to run just fine, despite the jumping icon.
Workaround
If you do not tether into CO8, just disable all providers in Preferences > Capture tab.
If you do tether, just enable only the provider needed. Limited testing from my side shows that in particular the Leaf provider in combination with Mavericks causes the jumping behaviour. As a result Leaf shooters should test the 8.3 update carefully although I have yet no reasons to believe that it is not working properly.
0
-
This worked for me. Then I tried just having Nikon enabled and this also worked without bouncing. 0 -
This post by Jim_DK confirms that it's a known behaviour in Mavericks only; and does not impair performance. 0 -
I have Mavericks and the icon just sits still in the dock. I would like to get it to quit (saves clutter) but it refuses to do that unless I quit Capture One from the dock (which I don't want to!). What does this CaptureCoreService.xpc do anyway? 0 -
It's part of the tethering module and should be a background process. 10.9 handles the plist for it differently to 10.10 so it shows in the dock rather than hidden (in 10.10 you can see it in the activity monitor).
We already have it fixed in the next service release due shortly.
It can be left to run and has no consequence to usability other than its a bit annoying.0
Post is closed for comments.
Comments
4 comments