Hardware acceleration not working

Comments

11 comments

  • Thierry Girard

    Same bug, last version of studio driver, Win 10 last updates, i7-6700k - 64 gb - gtx 1080ti

    0
    Comment actions Permalink
  • SFA

    I think you would need to look at the log files for the GPU assessment process as a starting point for working out what happened during the process.

    Have you already tried restarting C1? 

    In the past (with Win V7)  I have known situations where the kernel build for the Intel software GPU in the processor failed and that terminated the assessment for the independent GPU as well. Re-assessment worked after a restart.

    The log file provided the clues about what was happening.

    Also, once in a while, the latest driver may not be the best thing to have. I might be worth reverting (if there is an option to do so) to an earlier driver to see if that allows things to work. But check the log file first.

    0
    Comment actions Permalink
  • David Tavan

    I've found this in the log file :

    [2021-06-24 11:41:37.487][159][ID:028, ]{CAMCO} | Enabling OpenCL with: 'C:\Users\david\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin' and 'C:\Program Files\Capture One\Capture One 21'
    [2021-06-24 11:41:37.497][009][ID:043, ]{PLUG } | Reading Manifest - C:\Program Files\Capture One\Capture One 21\Plugins\OpenWith ...
    [2021-06-24 11:41:37.500][002][ID:043, ]{PLUG } | Manifest OK
    [2021-06-24 11:41:37.538][037][ID:043, ]{PLUG } | Init plugins
    [2021-06-24 11:41:37.760][221][ID:028, ]{CAMCO} | Set OpenCL to True returned: Missing OpenCL BenchMark

    0
    Comment actions Permalink
  • FirstName LastName

    I have the same proble, the GPU is not working with capture one.

    2021-06-25 16:18:50.568> Found 1 OpenCL platforms
    2021-06-25 16:18:50.568> Found 1 OpenCL devices on platform 0 (NVIDIA CUDA)
    2021-06-25 16:18:50.568> OpenCL Device 0 : NVIDIA GeForce GTX 1660 Ti
    2021-06-25 16:18:50.568> OpenCL Driver Version : 471.11

    2021-06-25 16:18:50.684> OpenCL : Loading [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] started
    2021-06-25 16:18:50.684> OpenCL : Loading [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] OK
    2021-06-25 16:18:50.684> (ERROR) bin file failed parse [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] (verificationCode=7)
    2021-06-25 16:19:58.057> OpenCL Device 0 : NVIDIA GeForce GTX 1660 Ti
    2021-06-25 16:19:58.061> (Message delayed 67.484s to prevent duplicates.)
    2021-06-25 16:19:58.061> OpenCL Driver Version : 471.11
    2021-06-25 16:19:58.061> (Message delayed 67.484s to prevent duplicates.)
    2021-06-25 16:19:58.061> OpenCL Compute Units : 24
    2021-06-25 16:19:58.061> (Message delayed 67.484s to prevent duplicates.)
    2021-06-25 16:19:58.061> OpenCL Nvidia Compute Capability : 7.5

    THIS IS THE PROBLEM:(ERROR) bin file failed parse [C:\Users\XXXX\AppData\Local\CaptureOne\ImageCore\14.2.0.48\ICOCL.bin] (verificationCode=7)

    but this is how I set up the NVIDIA control panel:

    but still the problem is there!

    0
    Comment actions Permalink
  • SFA

    David,

    If the process, as in your case, did not create a Benchmark assessment (or did not find a previous indicator to use) then there would seem to be a problem in the process that prevents C1 creating the required "kernels" of Windows/Nvidia driver and C1 code.

    Are you using an Intel-based system? If so was the Intel built-in Software base GPU discovered and assessed successfully?

    My Older Win 7 system had a repeating problem with that in that for some reason the Intel assessment (Device 0) would fail catastrophically at about 93% complete and stop the entire assessment process. Thus the NVidia assessment was killed off at the same time and so never completed.

    Usually a restart would try the assessment process again, spot the failed Intel test and skip to Device 1 whereupon it would usually be successful, but not always.

    Your log file sample does not provide any reference to any Intel analysis or device number so I'm guessing somewhat here.

    0
    Comment actions Permalink
  • David Tavan

    Yep windows 10

    Intel I9 10900K

    64 Go RAM - NVidia RTX 3090 FE 

    I've made a clean install, start, re start and always the same issue

    0
    Comment actions Permalink
  • SFA

    @Firstname

    Do you have an Intel based system with its own software-based GPU?

    Your screen grab seems to suggest you have forced the card to use OpenGL rendering for Capture One rather than Open CL.

     

    FOr what it is worth the Driver for my T2000 NVidia card is version 462.30. It seems to be working fine. 

    It might be worth trying a rollback on the driver to see what happens?

    Your error message was what I sometimes saw on my older Win 7 machine related to something about the Intel GPU. See my previous post for some details of that experience. 

    That said, unless you are really asking a lot of the system and perhaps output-processing several thousand files you might not see much real difference in human measurable performance whether processing is passing through a GPU or just the CPU. Especially with older hardware, if that is what you have.

    0
    Comment actions Permalink
  • SFA

    David,

    Does the i9 have the usual Intel built-in GPU software? If so does C1 see it? 

    Is the 3090 quite new? (I don't attempt to keep up with the numbers!)  If so it may be worth checking the 'net for stories of driver problems or similar, even if only satisfy yourself that are no widely reported compatibility issues. 

    My problem with the old machine seemed to resolve once after a Win 7 update, then unresolved for a longer period and finally resolved again - but I could not rely on staying resolved. Quite why the Intel kernel build failed at 93% complete I have no idea. Bad data somewhere in the stuff from Intel or Microsoft I suspect.

    The most annoying thing was that C1 would always reject the Intel device for lacking compute power anyway. The Nvidia only just about justified its existence doing just enough to make it worth having, sometimes, to assist the CPU's efforts.

    0
    Comment actions Permalink
  • FirstName LastName

    My apologies if I did not post a complete log file, but the integrated intel GPU 630 has been recognised by C1 and it is the only drive used by C1. The NVIDIA GPU is not used. Than what I did is to disable the intel GPU from the “device manager”, I’ve delated the C1 core file in order to rebuild them, but still C1 in the rebuild process show the error message in the log file.
    Please @ SFA could you check how big I are your file in the core folder of C1? They should be in this folder AppData\Local\CaptureOne\ImageCore\ I have something like 4 or 5 file but only one is 61MB (the one related to Intel GPU), the one related to NVIDIA is only 45KB.
    This is my hardware config:
    Intel i7 9750H, NVIDIA 1660 Ti, 16GB RAM.
    Sorry but now I’m writing from my mobile phone

    P.S. I’m the one who posted the recipe in this thread

    https://support.captureone.com/hc/en-us/community/posts/360013722838--WIndows-10-2004-C1-13-1-3-13-introduces-new-bugs-in-windows-management?page=2#community_comment_360003281757

    0
    Comment actions Permalink
  • Robert Hartl

    It seems to be a problem with the latest NVIDIA driver. After switching back to 466.77 everthing works fine

    0
    Comment actions Permalink
  • Nathan Allworth

    I'm running 471.11, and have similar issues. In fact if I delete the ImageCore folders and let it attempt to rebuild, it fails with 'ptxas fatal : Unresolved extern function '__nv_fast_exp2f''.

    PhaseOne support confirmed that the issue is with the Nvidia driver version 471.11 and that Nvidia is aware of the problem. They indicated that it's likely to be fixed in the next Nvidia driver version. I am rolling back this evening to see if that works.

    0
    Comment actions Permalink

Please sign in to leave a comment.