Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Artifacts in highlights/shadows with new GPU

Sacher Khoudari
Hi,

I am using C1 since beginning of this year and so far had no issues with it. Some days ago I upgraded my GPU and started experiencing some graphic artifacts while applying highlight/shadow recovery, and all images where I applied some highlights/shadows showed the same artifacts after they were processed. The artifacts look like some heavy clipping, maybe the correction was applied in the opposite direction.

These artifacts were gone after I disabled Hardware Acceleration in the preferences.

My previous GPU was an AMD Radeon RX 560 with 4GB, the new one is an AMD Radeon RX 5700 with 8GB. My AMD Radeon drivers are the newest recommended ones (19.9.2).

I'm using latest Capture One 12.1.4 on Windows 10.

You can find two sample images here:
https://my.hidrive.com/share/2id-nww0pd
One has no shadows and highlight recovery applied, the other has highlights:100 and shadows:22

Is this a bug? Or a misconfigured GPU? Anything I can do?

Thanks
Sacher
0

Comments

3 comments

Date Votes
  • SFA
    There are a few possibilities here.

    C1 will build a machine configuration specific kernel for each usable GPU in a system (up to 4).

    It is possible that this has, for some reason, not completed successfully, is still using the old kernel for the previous GPU or is using the new one but the latest driver installed may have some problems. (There are time when the latest driver may not be the best one to install for some reason.)

    Firstly try this.

    Open C1, open the Activities floating window so that is displayed permanently and then close C1. I normally use File > Close Window (If you have more than one window (i.e. more than one catalog or session) close all of them.

    Then restart C1 and observe what happens in the Activities Window. You may see some indication that the GPU assessment is being repeated. If it is and the progress bar seems to start part way across but eventually finishes (it may only progress to something over 90% but not reach 100%) go back and re-enable the Hardware Acceleration in Preferences and see how that affect the processing.

    If that re-assessment does not provide any resolution I would suggest the first you go here

    C:\Users\[User Name]\AppData\Local\CaptureOne\Logs

    and have a look at the ImgCoreOCL.log file.

    Open it in Notepad or Wordpad to see what it says.

    If you are relatively familiar with reading Log files you will spot a lot of lines that just record processes but it should be possible to see the lines that identify the GPU options discovered, what happens when each possible OpenCL device is assessed and whether the result seems to be successful.

    Note also the date and time stamps at the start of the lines.

    If the log file suggests any sort of issues there may be some rectification steps to identify.

    To force the GPU kernel build process to re-run go here AFTER you have closed Capture One.

    C:\ProgramData\Phase One\Capture One\ImageCore

    And delete the ICOCL named files. (If that worried you create a folder and copy/move the files into that folder first.)

    Now restart C1 and observe the Activity monitor again.

    Does it get over 100%?

    Check the newly created log file. Are the any problems reported?

    If it looks like the process was only partly completed, close C1, leave it a few seconds (to finish any tidying up) and then restart it. Observe the Activity bar again.

    If it looks like all is well check that the preferences are set to Auto for Hardware acceleration. Recheck what happens when you edit and process the problem images.

    If it is still the same (or at least still a problem) then it is probably time to go looking for an alternative GPU card driver to see if that makes any difference.

    If that does not lead to any obvious resolution or possible direction to investigate then create a Support Case and have the Capture One Support Team come up with some suggestions after they have looked as the log files.

    All of that sounds very complicated but it really is not. Apart from finding and installing a different driver should you need to go that far, the rest will only take a few minutes.

    HTH.


    Grant
    0
  • Sacher Khoudari
    Hi Grant,

    thank you your help!

    I'm very familiar with reading log files (as software developer), but unfortunately I couldn't find anything special in there. There are some errors but seam to be unrelated.

    I deleted the GPU kernels, they were rebuild (and reached 100%) but still the issue persists. BTW, is it normal that this takes almost one hour?

    I will try with another GPU driver, or contact C1 support. Should I rebuild the kernel again after installing another driver?

    Best regards
    Sacher
    0
  • SFA
    No it should not take an hour. The guidance suggests up to 5 minutes.

    Something not right somewhere.

    How many devices were found and reported in the log file.

    My (old) notebook presents a built in Intel HD4000 (which is assessed and currently, for some reason, fails after taking some time to attempt to create a kernel. In earlier versions of C1 it was simply ignored) and an NVidia which is processed and used but is very marginal in terms of providing useful processing.

    The log file reasonably clearly shows both potential GPUs being processed although there is overlap in the logged lines being written.

    On my system the Intel (Device 0) section takes a while before failing due to a read error - so something Windows related I think. Can't pin it down.

    I run a second time and it skips the HD4000 since it knows it failed previously, and runs the NVidia in a few seconds.

    I think C1 will spot the the new driver BUT, given the 1hr you mentioned previously, I think I would dive in and delete the kernel files after having Windows install the new driver and before starting C1 again.

    Save a copy of the current log file as well - for reference and comparison to see if anything changes.

    If a revised driver (maybe try one or two back if you have the latest already) does not work you should certainly create a Support Case.

    Grant
    0

Post is closed for comments.