Open CL Issue
After adjusting 20-50 photos, additional adjustments will cause the screen to black out for a second before the display returns. At times it will washout gray with full screen flickering to back and white. Heavy use of local adjustments seems to be the biggest culprit. Turning off open CL display will stop this but of course compromises speed. I use an NVIDA 660 Ti with current drivers on an Intel i7 3930k 6 core with 32g ram.
Fix is to close Capture One and re-open.
I have never seen this with 8.xx. Has anyone else seen this on 9.x?
JOHN
Fix is to close Capture One and re-open.
I have never seen this with 8.xx. Has anyone else seen this on 9.x?
JOHN
0
-
Yes, this sounds very similar to the problem I reported: viewtopic.php?f=62&t=21340
I have not upgraded to v9 due to this issue.0 -
I have noticed the exact same issue (on a mac) and opened a support case for this among other things. 0 -
Thanks, will wait for service release for the fix...I hope.
JOHN0 -
Yes - I've had this same issue. A mixture of a washed out screen combined with losing the screen altogether.
Using Canon RAW files.0 -
It is confirmed that something wrong happens while importing Canon Raw files happens on NVidia cards, switching off, OpenCL should solve your issues. 0 -
[quote="Andriy.Okhrimets" wrote:
It is confirmed that something wrong happens while importing Canon Raw files happens on NVidia cards, switching off, OpenCL should solve your issues.
The problem with the Canon files leaking are not related to OpenCL in any way.0 -
I hope they fix this - one of the main reasons I`ll be upgrading to 9 from 7 is because 7 crashes using Open-CL with the latest NVidia Drivers and I have to run with old ones which I doubt will work with Win10 making Pro-7 instantly useless as its unusably slow without open CL even on a fast machine ..
It`s about time Phase one got the software to run at decent speed without shaky Open-CL .. Pro V5 ran without OpenCL faster than 7 does with it on the same machine and was 100% Rock stable .0 -
[quote="John7" wrote:
After adjusting 20-50 photos, additional adjustments will cause the screen to black out for a second before the display returns. At times it will washout gray with full screen flickering to back and white. Heavy use of local adjustments seems to be the biggest culprit. Turning off open CL display will stop this but of course compromises speed. I use an NVIDA 660 Ti with current drivers on an Intel i7 3930k 6 core with 32g ram.
Fix is to close Capture One and re-open.
I have never seen this with 8.xx. Has anyone else seen this on 9.x?
JOHN
John, have you filed a support ticket? What's the answer/solution?
Cheers,
BeO0 -
Is anyone still getting this problem with 9.0.1?
I have made lots of edits (far more than was previously needed to trigger the problem) and can't get it to re-occur.
I didn't see anything in the release notes for 9.0.1 on Windows that would address this issue. However, I have also upgraded my Nvidia driver to 359.06 so maybe that is responsible?0 -
I have not filed a support case yet. I will check out 9.01 and wait for a new Nvida driver update first. 0 -
I spoke too soon - the problem does still occurs with 9.0.1.
I was using the White Balance dropper tool on several images when it started happening.0 -
I've noticed that the log file C:\Users\<username>\AppData\Local\CaptureOne\Logs\ImgCore.log
contains thousands of error message like these:2015-12-19 17:46:18.019> (ERROR) Execution of Resize failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.019> (ERROR) Execution of Resize failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.019> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.019> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.021> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.021> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.021> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of LocalToneMappingV8 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Structure2012 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Filter1D failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Filter1D failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Structure2012 failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Resample failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of Resample failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyExposure failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.022> (ERROR) Execution of ApplyLevels failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.023> (ERROR) Execution of ApplyLevels failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.023> (ERROR) Execution of ApplyLevels failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.023> (ERROR) Execution of ApplyLevels failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.023> (ERROR) Execution of FilterLumaH failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
2015-12-19 17:46:18.023> (ERROR) Execution of ApplyUSMLinear failed : CL_MEM_OBJECT_ALLOCATION_FAILURE
That is just a small sample - there are over 11700 similar entries for today alone.
From the CL_ prefix, I suspect CL_MEM_OBJECT_ALLOCATION_FAILURE is related to OpenCL.
The first entry of this type in the log file occurred on 30/11/2015 which was the day I installed CO 9.0 and first noticed this problem.0 -
You really should open a support ticket, providing your information and logs.
Cheers0 -
Well after spending several hours, carefully crafting a support case, including log file and screen recordings of the problem happening I don't seem to be able to upload the case to Phase One ☹️
I have tried two different browsers and in both cases I get dumped to an error page that says:Form Error
Sorry there was a problem sending your form submission.
The security challenge (anti-spam) field was entered incorrectly.
Please go back and try again.
I did not see any security challenge?0 -
[quote="RichardT" wrote:
I did not see any security challenge?
hhm, that's a real challenge then, and very secure 😂
cheers
P.S. I don't see it either, at least not on the first page with all the dropdowns...0 -
I'm seeing the same log file entries as well.
I have a Surface Book with the NVidia GPU.
Capture One started mis-rendering files with OpenCL enabled for "Processing" - garbled JPG and TIFF output, green specs all over the output files.
I have to close and open C1 to keep working, but after a while brush strokes on Adjustment Layers stop working, and the screen blacks out too often to actually work.
If you have success posting log files, let us know.
9.0 and 9.0.1 both did this.
So far the only option is to disable OpenCL.0 -
I had suddenly issues with exporting images from RAW (sony) - The exports showed green bands in the output. First I reinstall C1 and the problems seem to be solved. After a while Its shows up again. After realising what i had changed since then, I finally discovered that changing preferences -- USE OPENCL FOR PROCESSING TO AUTO - was responsible for the failure. If I put it back to never then it will not occur.
So I also think that OpenCl is responsible for these issues with corrupted output.
C1 v9.01
I7 6500 processor / 8gb
NVIdia GeForce GTX950M
Regards Bert0 -
It is impossible to work in version 9 (9.01, 9.02 etc) OpenCL was terribly buggy. And without it, everything is slow! I have the Palit 660GTX
Now I have to work in version 8 ((0 -
I confirm the issue too.
I t is not fixed with 9.03 version.0 -
Hi guys,
Please post you VRAM amount of your GFX card, but only if you see this message in the ImageCore.log or ImageCoreExternal.log:
CL_MEM_OBJECT_ALLOCATION_FAILURE (it doesn't matter what is in front of it)0 -
After the problems with submitting a support case noted above, I was finally able to submit one for this issue on 29th December (see viewtopic.php?f=62&t=21704 for the cause of the problem submitting the case).
In their initial response, Phase One support pointed out that, although my Graphics card (NVIDIA GeForce GTX 550 Ti) was listed as supported for Capture One V7 (GTX 500 series), it was not included in the list for V8.
See https://www.phaseone.com/en/Search/Arti ... nguageid=1 (note this article has not yet been updated for V9).
Despite not being officially supported for V8, I did not observe the OpenCL problems described in this thread while using that version.
The graphics card has 1024 MB VRAM.
Phase One support added:However, due to your good description of the issue, and due to that I see or know of no reason why your card should not be supported, I have created a bug regarding this issue and forwarded it to Image core R&D.
The reference for the bug id is CO-9120. Lets hope they will acknowledge this as a bug and fix it.
Since then (30th December) the support case has not been updated.
I have been mostly using V9 with OpenCL switched off. I did test V9.0.3 with OpenCL enabled a few days ago and it is still generating lots of CL_MEM_OBJECT_ALLOCATION_FAILURE, CL_INVALID_EVENT etc errors.0 -
Thank you.
It is being looked into.
With regard to the support-cases, the Support team cannot respond to everyone once the problem has been solved. However, an issue like this will be mentioned in the Release notes, if it has been fixed, so please read these, when a new version comes out. The release notes can also contain important information on known issues, so one more reason to read them.0 -
I can add, that i have similar Open CL problems with NVidia Quadro K620 (2Gb VRAM). PC has 16 Gb RAM. With Open CL set to auto after while redrawing becomes erratic. Having Open CL disabled everything works. 0 -
[quote="Urmas Tartes" wrote:
I can add, that i have similar Open CL problems with NVidia Quadro K620 (2Gb VRAM). PC has 16 Gb RAM. With Open CL set to auto after while redrawing becomes erratic. Having Open CL disabled everything works.
Do you see the error-line I posted in a previous post?0 -
[quote="Christian Gruner" wrote:
[quote="Urmas Tartes" wrote:
I can add, that i have similar Open CL problems with NVidia Quadro K620 (2Gb VRAM). PC has 16 Gb RAM. With Open CL set to auto after while redrawing becomes erratic. Having Open CL disabled everything works.
Do you see the error-line I posted in a previous post?
Just upgraded to 9.0.3. Having worked for a while and it seems, that my problems with Open CL have gone! It is definitely more responsive with Open CL enabled. Will keep my eye on that, but so far seems good.
Thanks for taking care and keep on good work!0 -
[quote="Urmas Tartes" wrote:
Just upgraded to 9.0.3. Having worked for a while and it seems, that my problems with Open CL have gone! It is definitely more responsive with Open CL enabled. Will keep my eye on that, but so far seems good.
Thanks for taking care and keep on good work!
I have been running 9.0.3 today with OpenCL enabled and, after a few hours, the problem is definitely still happening for me.
I have uploaded a new screen recording and log files to my support case.
Richard0 -
[quote="RichardT" wrote:
[quote="Urmas Tartes" wrote:
Just upgraded to 9.0.3. Having worked for a while and it seems, that my problems with Open CL have gone! It is definitely more responsive with Open CL enabled. Will keep my eye on that, but so far seems good.
Thanks for taking care and keep on good work!
I have been running 9.0.3 today with OpenCL enabled and, after a few hours, the problem is definitely still happening for me.
I have uploaded a new screen recording and log files to my support case.
Richard
After while I could get Open CL error with C1 again. The error appeared, when I used C1 and Adobe CS6 simultaneously (switching between them) having video card usage enabled in both programs. However, there are no errors when I work with C1 alone (No Photoshop running at the same time).
Even disabling computation acceleration and Open CL in Photoshop did not remedy the problem. So, it seems, that there is conflict between Adobe and C1.0 -
hey, very interesting! So who is the bad cop, PS or C1? Doesn't matter too much as long as C1 works if PS is not runnning... 😕 0 -
The problem is occurring for me without having CS6 running.
One thing I have noticed recently is that if I reduce the size of the main Capture One window then the problem stops happening. With the size down to 1674 x 913 pixels, I didn't see the problem. When I then increase the size back to near full screen (1920 x 1080), it started happening again. I've not found where the transition point is yet.0 -
Yeah, I have 9.0.3 now and OpenCL is still busted on my Surface Book i7 + dGPU (NVidia).
FastPictureViewer seems to work alright, and CS6 may benefit - it's hard to tell.
FastPictureViewer used to crash and now it's working. So I think the new Surface Book NVidia drivers have helped.
I just wish they helped Capture One 9.0
Post is closed for comments.
Comments
33 comments