Phase One 8.0.1 OpenCL Bug?
Hi,
I just updated to 8.0.1 and noticed that under C1 > Preferences > General > Hardware Acceleration
By default both Display and Processing is set to Never (I thought it turns on by default?), so I changed both to Auto but this is what I experience next
https://copy.com/thumbs_public/UTKvtb4FnJ4xZccx/Screen%20Shot%202014-10-18%20at%2010.58.43%20AM.png?size=1024
These black stuffs that look like noise will appear whenever I scroll to different photos or scrolling through the different presets, so I guess this is OpenCL at work? But does it suppose to display small black spots all over the image during preview?
I just updated to 8.0.1 and noticed that under C1 > Preferences > General > Hardware Acceleration
By default both Display and Processing is set to Never (I thought it turns on by default?), so I changed both to Auto but this is what I experience next
https://copy.com/thumbs_public/UTKvtb4FnJ4xZccx/Screen%20Shot%202014-10-18%20at%2010.58.43%20AM.png?size=1024
These black stuffs that look like noise will appear whenever I scroll to different photos or scrolling through the different presets, so I guess this is OpenCL at work? But does it suppose to display small black spots all over the image during preview?
0
-
I am experiencing the same issue on my Mac Pro when I enable OpenCL. The 'noise' is of a different colour though. It also appears on the exported files. The results are unusable. 0 -
Are you guys happen to use OS X 10.10? 0 -
Not sure about the other guy, but I've upgraded to Yosemite. I thought the 0.1 update is for Yosemite 😂 0 -
[quote="NNN635468147870723611" wrote:
Not sure about the other guy, but I've upgraded to Yosemite. I thought the 0.1 update is for Yosemite 😂
Not yet, maybe 8.0.2 or later... (just guessing, not suggesting) 😄0 -
http://i.imgur.com/ATWEx5u.jpg?1
This is pretty bad. Yosemite and Capture One Pro 8.0.1 are useless together.0 -
I had to turn off Hardware acceleration which was by default on "auto". 0 -
This is where you get blamed as the dumb consumer -- for upgrading your operating system without knowing this would happen... And the excuse that even 3 GM Seeds of Yosemite weren't enough to prepare an e-mail to said customers that upgrading might be worth avoiding in the mean time. 0 -
If you subscribed to our (Digital Transitions) newsletter or followed our blog you would have seen a clear-as-day indication that we do not recommend upgrading to 10.10
http://www.digitaltransitions.com/blog/ ... nouncement
That said, I don't think you should really need anyone to warn you that upgrading an Operating System immediately upon first availability is a nearly guaranteed way to have some headaches with existing software.
If you really want to live on the cutting edge of OS's you will get cut. Otherwise wait a month or two and life will be much smoother all around.
Regarding the GMs... It's one of Apple's terrible habits to make last minute changes, even between the supposed "gold master" and the final downloadable customer version. So even if it works on the GM there is no guarantee it will work upon actual public release.0 -
Hi Doug,
Thanks for providing the valuable service of educating customers on Capture One. Your company plays a pivotal role in closing the gap between the software and the consumers, I applaud you for that.
I'm fully aware of the GM Seed issue. It's a debate/excuse that gets tossed around year-in-year-out as this cycle continues. Sure, it's the crazy one's that update blindly without fear of the worst but it really would be a good idea for the kind folk at Phase One to send out an e-mailer prior to the release of a major OS, warning newer users of the pitfalls of upgrading.
Thanks!0 -
[quote="photoGrant" wrote:
Hi Doug,
Thanks for providing the valuable service of educating customers on Capture One. Your company plays a pivotal role in closing the gap between the software and the consumers, I applaud you for that.
I'm fully aware of the GM Seed issue. It's a debate/excuse that gets tossed around year-in-year-out as this cycle continues. Sure, it's the crazy one's that update blindly without fear of the worst but it really would be a good idea for the kind folk at Phase One to send out an e-mailer prior to the release of a major OS, warning newer users of the pitfalls of upgrading.
Thanks!
Maybe the mail would be useful although why it would have to be repeated each time in a high tech business in the modern world is something to wonder about.
I doubt Apple would be too enthusiastic either - they are more than capable of creating their own havoc (ref. the recent iPhone challenges) without without feeling a need to tell people there might be a problem.
Moreover, as a Windows user, I would be somewhat amused (to start with) and then perhaps dismissive and annoyed, of getting mails that were meaningless to me. Filter by user's OS perhaps? But then who is to know who uses which OS, who uses both and who might be about to switch?
But I would guess that the biggest risk would be Apple disliking the underlying message being made so publicly.
They like to do things their way or no way. I mean, soldering RAM onto boards to make sure they are almost impossible to upgrade? I guess it means they avoid, um, "quality issues" that might occur should people attempt their own upgrades as their needs change.
Grant0 -
What machine are You guys who have this issue running ? 0 -
I'm not so sure this is solely due to Yosemite. I have a similar issue (for which i've raised a ticket) with CO 8.0.1 and Mavericks. OpenCL on or off, doesn't seem to matter. They're working on this. [quote="NNN635464713054817659" wrote:
http://i.imgur.com/ATWEx5u.jpg?1
This is pretty bad. Yosemite and Capture One Pro 8.0.1 are useless together.0 -
[quote="Christian Gruner" wrote:
What machine are You guys who have this issue running ?
The problem occured on an iMac 27" with an i7-870 2.93 GHz, 16GB RAM, ATI 1GB Radeon HD 5750 Graphics.0 -
[quote="NNN635464713054817659" wrote:
[quote="Christian Gruner" wrote:
What machine are You guys who have this issue running ?
The problem occured on an iMac 27" with an i7-870 2.93 GHz, 16GB RAM, ATI 1GB Radeon HD 5750 Graphics.
Using a mac with the sam specs and was getting the same weird result.
The fix with turning off the hardware acceleration really saved me!0 -
i already mentioned this BUG in the 2 latest developer Version from 10.10 to Phase One. They told me, its still beta so no worry 😊 Not 10.10 is out and even after updating with C1 8.01 the Bug is still there. So i am pretty sure, Phase One is working on this and we get some Update soon. As long this takes, i just use it without hardware acceleration on my brand new MAC PRO, and still wait 😊
Best
Eric0 -
[quote="Christian Gruner" wrote:
What machine are You guys who have this issue running ?
Base Mac Pro (Late 2013)
And yes, turning off any hardware acceleration will eliminate any of that OpenCL related issue.0 -
[quote="Fotosight" wrote:
i already mentioned this BUG in the 2 latest developer Version from 10.10 to Phase One. They told me, its still beta so no worry 😊 Not 10.10 is out and even after updating with C1 8.01 the Bug is still there. So i am pretty sure, Phase One is working on this and we get some Update soon. As long this takes, i just use it without hardware acceleration on my brand new MAC PRO, and still wait 😊
Best
Eric
The bug is due to Apple changing/breaking in the AMD-drivers for 10.10. They usually do that, and fix it again in the betas. This was not the case this time. The released version of the drivers remains broken. We will circumvent this in an upcoming release, but if Apple decides to actually fix their bug, CO will very likely have another bug, because of the patching for the broken driver.
This is very typical story of new OSX releases, sadly.0 -
[quote="Christian Gruner" wrote:
[quote="Fotosight" wrote:
i already mentioned this BUG in the 2 latest developer Version from 10.10 to Phase One. They told me, its still beta so no worry 😊 Not 10.10 is out and even after updating with C1 8.01 the Bug is still there. So i am pretty sure, Phase One is working on this and we get some Update soon. As long this takes, i just use it without hardware acceleration on my brand new MAC PRO, and still wait 😊
Best
Eric
The bug is due to Apple changing/breaking in the AMD-drivers for 10.10. They usually do that, and fix it again in the betas. This was not the case this time. The released version of the drivers remains broken. We will circumvent this in an upcoming release, but if Apple decides to actually fix their bug, CO will very likely have another bug, because of the patching for the broken driver.
This is very typical story of new OSX releases, sadly.
Christian, I am sorry but I have to ask. OpenCl has never really worked well. The forum is full of people that are complaining about it, and PO answers have all been either is Apple's fault or the hardware is not up to par. Even you guys most time suggest to leave it off. Be as it may dosent any one there had the though that perhaps it is time to scrap it all together? I mean every time apple changes something we go through months and months of painful crashes, you guys pull your hair out, while other programs like PS6 and LR5 keep working fine. We all love the product that is we we are so adamant and passionate, but I think it is time you guys perhaps take a close look at cleaning the code and moving on, perhaps without OpenCl0 -
processing nikon d800 files in 8.0 on mac os 10.9.4 with openCL set to auto gave me big black squares on my processed files.
On a MacPro 8 core D700 GPU0 -
[quote="alececco" wrote:
[quote="Christian Gruner" wrote:
[quote="Fotosight" wrote:
i already mentioned this BUG in the 2 latest developer Version from 10.10 to Phase One. They told me, its still beta so no worry 😊 Not 10.10 is out and even after updating with C1 8.01 the Bug is still there. So i am pretty sure, Phase One is working on this and we get some Update soon. As long this takes, i just use it without hardware acceleration on my brand new MAC PRO, and still wait 😊
Best
Eric
The bug is due to Apple changing/breaking in the AMD-drivers for 10.10. They usually do that, and fix it again in the betas. This was not the case this time. The released version of the drivers remains broken. We will circumvent this in an upcoming release, but if Apple decides to actually fix their bug, CO will very likely have another bug, because of the patching for the broken driver.
This is very typical story of new OSX releases, sadly.
Christian, I am sorry but I have to ask. OpenCl has never really worked well. The forum is full of people that are complaining about it, and PO answers have all been either is Apple's fault or the hardware is not up to par. Even you guys most time suggest to leave it off. Be as it may dosent any one there had the though that perhaps it is time to scrap it all together? I mean every time apple changes something we go through months and months of painful crashes, you guys pull your hair out, while other programs like PS6 and LR5 keep working fine. We all love the product that is we we are so adamant and passionate, but I think it is time you guys perhaps take a close look at cleaning the code and moving on, perhaps without OpenCl
Removing OpenCL is simply not an option. For the vast majority we know for a fact that is working, working nicely, and working very fast. Mind you, a forum will always be full of people with issues (which is partly what it is there for). All the people where it just works don't post in the forum, as they are busy making pictures and editing in CO.
PS uses OpenCL for some limited amount of features and LR does not use GPU acceleration at all. OpenCL gives CO a huge performance-boost in many operations, and we see no reason to remove it.
There are clearly issues for some, especially for the first-movers to a new Operating system or new hardware. We are always trying to solve these issues as quickly as we can, but if using CO as a critical tool in your business, you should be conservative when it comes to OS-/Hardware updates.0 -
[quote="dale11833" wrote:
processing nikon d800 files in 8.0 on mac os 10.9.4 with openCL set to auto gave me big black squares on my processed files.
On a MacPro 8 core D700 GPU
Please contact our support, and they'll get you sorted.
Here's the link: http://www.phaseone.com/SupportMain.aspx0 -
using a mac pro and other open gl applications I have to say the only program with a problem is capture one pro 8.... ☹️
wondering if it is an apple problem, why all the other applications using open gl work just fine with yosemite....0 -
[quote="NNN635143378405515920" wrote:
using a mac pro and other open gl applications I have to say the only program with a problem is capture one pro 8.... ☹️
wondering if it is an apple problem, why all the other applications using open gl work just fine with yosemite....
OpenGL has been around, according to Wikipedia, for over 20 years.
OpenCL - as used by C1 when switched on - since August 2009. 5 years.
One needs to differentiate between the two.
The more recently defined standards may as yet not be so stable or well executed by all the parties involved (Wikipedia - It has been adopted by Apple, Intel, Qualcomm, Advanced Micro Devices (AMD), Nvidia, Altera, Samsung, Vivante, Imagination Technologies and ARM Holdings.) as is the more mature OpenGL but clearly it promises a lot and needs to be actively used in order to gain experience that will refine the usability and consistency of what it offers.
Wisely the C1 developers have provided a facility to turn it off when a combination of circumstances means that it does not, currently, provide benefits in some cases. So no gains there ... but perhaps no real long term losses either.
For an OpenCL free application LightRoom would seem to be the way to go. Or just turn it off in C1 until your combination of OS, application, camera files and hardware all gel with the ever developing capabilities of the OpenCL concept.
These choices are open to all of us.
The GPU in my current Laptop of choice is not powerful enough to justify using its OpenCL capability. No problem, I can still process things using C1 quickly enough for my purposes. I look forward to the day that a machine upgrade makes things even faster ... but meanwhile I can get along fine without OpenCL.
That said I use Windows V7 so I can't comment on whatever the Mac effect might be, nor Win V8.
Grant0 -
[quote="NNN635143378405515920" wrote:
using a mac pro and other open gl applications I have to say the only program with a problem is capture one pro 8.... ☹️
wondering if it is an apple problem, why all the other applications using open gl work just fine with yosemite....
As SFA says, CUDA and OpenGL is different from OpenCL.0 -
[quote="Christian Gruner" wrote:
All the people where it just works don't post in the forum, as they are busy making pictures and editing in CO.
you have a rather shifted point of view, i think most users have capitulated long time ago (v4) and learned to use c1 with all the handicaps.0 -
[quote="Horseoncowboy " wrote:
[quote="Christian Gruner" wrote:
All the people where it just works don't post in the forum, as they are busy making pictures and editing in CO.
you have a rather shifted point of view, i think most users have capitulated long time ago (v4) and learned to use c1 with all the handicaps.
Why would that be a shifted POV? It is exactly the way internet forums behave, not just this one provided by Phase One. I assume you know dpreview.com, go on there and choose any forum and you will find b@tching about nearly anything but hardly any good word for the topic at hand (be it cameras, lenses, software etc.). Feel free to go on any other open forum and you will find the same, similar on open review sites.
I also believe that anything not made by yourself or strictly only for yourself will always require "learn to use with the handicaps", as someone else developing will not have the same view on the same subject as you have. This is not only true in the photography domain, as a matter of fact, it may actually be worse in other domains. I'm designing software and systems for businesses (think SAP and the likes) and in here it's not half as bad 😄0 -
[quote="HCS" wrote:
I'm designing software and systems for businesses (think SAP and the likes) and in here it's not half as bad 😄
True. Bad, but not so bad.
I think that is because the people who sign off the deals (and therefore must always have made the "right" decision), have mostly no understanding of what is required and no desire to become involved with forums about the products.
The people who understand what their business requirements are have no authority to influence purchases (or even specifications very much) and so have to get on with what they are give. The are unlikely to want to waste any of their life venting on forums and they may not even have such an opportunity should they desire it.
Hence things can be much calmer ... but probably for the end user, personal or corporate, less productive since everyone is removed from the very personal involvement one gets when buying software for one's own use.
Just my opinion of course.
Grant0 -
I see what you mean Grant. However, in my company we also have a user forum, if not on the internet. It's called a change control board and it involves end users, not business managers.
Other than that, since i'm one of the architects of our business applications of course my email inbox is also a venting place 😄
That's what i'm comparing to. And the personal involvement here is much higher (at least i think so), but the performance of the systems (software plus hardware plus support plus user/operator) is much better than what i'm used as described above.0 -
[quote="HCS" wrote:
I see what you mean Grant. However, in my company we also have a user forum, if not on the internet. It's called a change control board and it involves end users, not business managers.
Other than that, since i'm one of the architects of our business applications of course my email inbox is also a venting place 😄
That's what i'm comparing to. And the personal involvement here is much higher (at least i think so), but the performance of the systems (software plus hardware plus support plus user/operator) is much better than what i'm used as described above.
Ah yes, a properly managed User Group where the members were all existing customer representatives (or sometimes important nearly customers we had come to know well) could be a very powerful forum that in general would be of benefit to everyone - or at least those who could turn up. I think today it could be supplemented with video conferencing for those unable to justify the travel required but there is something to be said for getting people "around a table" to discuss experiences and future direction and to learn a little about each other during the days.
But that was a corporate world and only a corporate world.
Here we are a range of interested parties ranging from people working for relatively large photographic agencies and so on through to serious hobbyists. Maybe a few not so serious hobbyists as well. From Corporate to very personal with quite widely varying needs I would expect. Some different challenges to manage compared to a User Group of paid employees enjoying a day out of the office representing their employer's interests. 😉
Grant.0 -
Sorry to say this so clear, as a pro working with the IQ 180 you can imagine i produce many pics and i need to work on this high performance equipment, and his is not only relevant for the Camera but also for the Mac. So there is no room left for excuses to be honest. Phase One announced the Version 8 of Co exactly with this amazing speed, without any warnings about it will not work on Yosemite. I payed money for the Upgrade from 7 to 8 and now P1 told me to turn off the OpenCl? Not really, Photoshop CC2014, Blender, and all the rest of this program work fine, really fine.
Really i hope it will not be a nightmare like the USB3 Support on the IQ backs. This took around 1,5 Years to be fixed.
Can you provide some workaround like other Drivers or what ever to get a kind of hotfix?
Best
Eric0
Post is closed for comments.
Comments
42 comments