Yosemite now released
With the release of Yosemite, do we have a time frame for compatibility with C1 8?
0
-
Is it not compatible? This has been the only other software that I am waiting to upgrade the OS. 0 -
C1 8 works perfectly with 10.10, I use it daily for several versions of Yosemite! 😄 😄 😄 0 -
I'm thinking "officially compatible".... 0 -
I think it has already been said here, it is not a communication site Official Phase one; but an exchange between users site. 😄 0 -
I upgraded yesterday and find CO8 runs better than it did on Mavericks. Seems to start up quicker and everything just feels faster. 0 -
I run CO8 on one of my Macs with various seeds of Yosemite since when CO8 was released and I have not found any incompatibility, so far. 0 -
I'm having all sort of weird display issues and several crashes since I've upgraded to Yosemite.
Check the black "blobs" next to toolbar input fields, happens when you click on one and the spot removal tool produces this yellowish overlay.
https://www.dropbox.com/s/6ijbxax74lqti ... 2.png?dl=00 -
Just upgraded to Yosemite 10.10, C1 works so far BUT if I process a picture to photoshop CC, bang the picture does not show as it should, grain at it´s worst and it has nothing to do with the picture worked on in C! in all aspects! What can I do? 0 -
And just checked... it also exports the image with these yellow overlays ☹️ Now that's a fail... 0 -
It cannot be said clear enough: If you are using CO in your daily flow, do not upgrade to 10.10 before it is officially stated that CO supports 10.10.
We have of course been running the various developer seeds, and fixed obvious compatability-issues along the way, but with new OSX-versions its always "exciting" to see how they change from dev seeds to final release.0 -
Well... it's too late for me now...
It's strange though how a couple years old CS5 I have here runs without hiccups on any OSX :/0 -
[quote="Christian Gruner" wrote:
It cannot be said clear enough: If you are using CO in your daily flow, do not upgrade to 10.10 before it is officially stated that CO supports 10.10.
We have of course been running the various developer seeds, and fixed obvious compatability-issues along the way, but with new OSX-versions its always "exciting" to see how they change from dev seeds to final release.
You mean 10.9 or later (or equivalent) that is specified on each release note... Instead of writing 4 lines of text, just say no (or yes)0 -
[quote="RonaldG" wrote:
Instead of writing 4 lines of text, just say no (or yes)
No or yes to what? A question that wasn't asked?0 -
[quote="RonaldG" wrote:
[quote="Christian Gruner" wrote:
It cannot be said clear enough: If you are using CO in your daily flow, do not upgrade to 10.10 before it is officially stated that CO supports 10.10.
We have of course been running the various developer seeds, and fixed obvious compatability-issues along the way, but with new OSX-versions its always "exciting" to see how they change from dev seeds to final release.
You mean 10.9 or later (or equivalent) that is specified on each release note... Instead of writing 4 lines of text, just say no (or yes)
Life isn't black and white, neither is the my comment on 10.10.0 -
[quote="roske" wrote:
I'm having all sort of weird display issues and several crashes since I've upgraded to Yosemite.
Check the black "blobs" next to toolbar input fields, happens when you click on one and the spot removal tool produces this yellowish overlay.
https://www.dropbox.com/s/6ijbxax74lqti ... 2.png?dl=0
Can anybody confirm, whether that is a 10.10/ C1P 8.0.1 bug? Does anybody have similar observations?0 -
Hi,
I would love to help and give you any conclusive answer, but it is hard to give one. There are so many variables in the equation, like hardware to start with.
I will be testing 10.10 release shortly on a system that is running 10.9.5 with CO8 on another volume. That is one way to differentiate and draw conclusions. That is an approach I like to advice to anybody who like to try Yosemite now while maintaining a solid setup at the same time.
Hope this helps.0 -
Hi!
Weird display issues here as well after upgrading to 10.10. Images are not displayed correctly and remain pixeled. Vertical or horizontal lines or dots appear immediately after selecting an image, which vanish after half a second or so. I observe the incomplete 'loading' of images with the pixeled phenotype preferentially with COLOR or EXPOSURE Tool Tabs chosen and the images load correctly if I swith to full screen mode (the new green butten with the two arrowheads which formerly used to be the + button). Maybe this helps a little to narrow down the problem.
My System: Mid 2010 MacBook Pro, 2.66 GHz Intel Core i7, 8 GB RAM, NVIDIA GeForce GT 330M 512 MB
C1Pro 8.0.10 -
C1 8.01 is running fine here with Yosemite.
MPB 17" early 2011, 2,2 GHz i7, 16 GB0 -
The biggest difference I notice with Yosemite is that drawing masks on adjustment layers is much slower than in Mavericks. I have an old MacBook, and the nice speed increase I noticed drawing masks in C1 8 compared to C1 7 in Mavericks is now gone in Yosemite.
MacBook Pro Mid 2010, 2,66 GHz Intel Core 2 Duo, 8 GB RAM, NVIDIA GeForce 320M 256 MB0 -
to avoid this noise in C1 and OS X 10.10 just disable the hardware acceleration in the preset of C1. This should work along we are waiting for some update from Phase One 😊
Best
Eric0 -
There is a known bug in Yosemite with the management of GL on MacBooks Retina. That is why some of you are experiencing problems and some are not 0 -
Tethering doesn't work well anymore with 10.10 and 8.01
Even with OpenCL disabled.
Really hope a update will arrive ASAP0 -
Upgraded to Yosemite yesterday and shoot 50 pics tethered today. No problems so far - but still on C1 8.0. Using a iMac ( not 5k ☹️ and a Nikon D7100.
Even CaptureOne Pilot worked great 😊
-- Magnus0 -
Good to hear Magnus.
Over here 8.01 and got 2 thudded image in using C1, after that connection gets lost with camera.
Also tried EOS utility but that doesn't even start up in 10.10.0 -
A small error: looks like I'm on 8.01 - can't remember updating… 🤭
-- magnus0 -
[quote="NNN635460641645477971" wrote:
Good to hear Magnus.
Over here 8.01 and got 2 thudded image in using C1, after that connection gets lost with camera.
Also tried EOS utility but that doesn't even start up in 10.10.
There you go (no offence). Canon has to update their software first (a.k.a. the SDK). Next, Phase One will update it in a maintenance release of CO8, and only then and hopefully Apple did not change relevant parameters in a point release (I am not making this up, happened more than once) and you'll have your tethered support.0 -
[quote="Paul_Steunebrink" wrote:
[quote="NNN635460641645477971" wrote:
Good to hear Magnus.
Over here 8.01 and got 2 thudded image in using C1, after that connection gets lost with camera.
Also tried EOS utility but that doesn't even start up in 10.10.
There you go (no offence). Canon has to update their software first (a.k.a. the SDK). Next, Phase One will update it in a maintenance release of CO8, and only then and hopefully Apple did not change relevant parameters in a point release (I am not making this up, happened more than once) and you'll have your tethered support.
As a Windows user I have never bothered too much about Apple issues but I keep an eye on things in the Mac section here out of interest and also on another forum related to some Open Source software I use.
So this older software - formerly a commercial product - works on Yosemite at it current official release level and has worked on 10.9 through several beta version updates. But as soon as people have allowed their machines to be updated to 10.10 the application no longer loads. Something to do with Java support it seems - but it could be something else.
I have this image of thousands of people around the world spending most of their lives trying to work out how to fix applications that once worked but are now broken because someone somewhere in Apple is either unconcerned about or has missed some legacy issues most likely unannounced. I'm not picking on Apple here - Microsoft and others can be equally as bad. The resource effort wasted must be huge and far more costly than dealing with it in advance at the source. Except that that would add to the costs at the source so throwing the problem out into the wild makes the perpetrators more profitable.
So much for "Free" "upgrades".
Grant
Edited to fix a couple of typos.0 -
Grant,
Have you ever been called a philosopher? 😉
You're doing a fine job in this respect, I would say.0 -
[quote="Paul_Steunebrink" wrote:
Grant,
Have you ever been called a philosopher? 😉
You're doing a fine job in this respect, I would say.
Thank you Paul. (I think .... ? 😲 )
I find it so frustrating to see the same issues coming around time and again, following the parallel but different sorts of issues that we could experience 10 years and then 10 years before that and so on back in computing time. It's really rather cyclical.
Today it is so easy to be "Agile" enough pass a problem on to others and have your PR and Marketing pushed so hard supported by smoke and mirrors that the source of a problem can be obscured all too easily. Of course the same comments also apply to other subjects far removed from computing.
Grant.0 -
I upgtraded to yosemite and CO crashes all the time and every time I hit the trash icon I was 5 mins away from buying this product but I think I will hold off until this issue is resolved. It also will NOT import Aperture library and will not read TIFFs whats with that???? 0
Post is closed for comments.
Comments
50 comments