Potential solution for the performance issues in C21 (focus window spinner, export)
As I was also effected by this, I filed a bug report. I got a helpful response in 24 hours (maybe I am just lucky). Whatever the reason, I always got reasonable fast response times in the past, your mileage may very.
The problem, in my case, got fixed by reinitializing the opencl driver pipeline for CaptureOne. Pretty easy to do, here is the complete support reply:
"As you describe, it appears that there may be an issue with the OpenCL pipeline of Capture One.
Try turning that off:
Under Preferences > General, about halfway down under OpenCL (Hardware Acceleration), set Display/Processing to Never. Then, restart Capture One to commit this change.
This will force Capture One to ignore the GPU when processing and generating previews. If it works fine with Hardware Acceleration disabled, try to rebuild OpenCL kernels as described in this article and enable Hardware Acceleration in Capture One: https://support.captureone.com/hc/en-us/articles/360002404937-Troubleshooting-OpenCL-in-case-of-viewing-processing-exporting-problems
For Windows users who may have recently installed driver updates, we recommend reverting back to the version prior to this update to avoid any driver compatibility issues.
You can find the driver versions for AMD here and NVIDIA's drivers can be found here"
Many thanks to Alice for the fast and competent reply. It's fast again (for now at last). There are still some redrawing issues (sometimes when selecting a picture for the viewer it's not 100% painted), but as i said before elsewhere, that can as well be a driver issue with the Nvidia card i am using. Hard to debug that, and not dramatic enough for now.
Hope this helps someone out.
Frank
-
The frequent interface freezing that started with C21 does not seem to be related to hardware acceleration or video drivers.
Whether it is on or off makes no difference to me. But thanks for sharing this information.
0 -
Sorry mate, i am not experiencing this at all, so no idea how to fix that. This is only about the performance issue related to viewing/processing.
Interface freezing is normally a deadlock on the main UI thread (programmer speak, probably useless to most) and is probably a combination of a bug + a special scenario - maybe related to the windows version, driver version etc. Did you file a support ticket with as much configuration detail as you have?
Frank
0
Post is closed for comments.
Comments
2 comments