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. ⚠️

Edit window not updating

Comments

6 comments

  • NN102528UL12
    Started to look into the problem myself... un-installed and reinstalled older version, still same problem. Then I downgraded the graphics drivers and re-installed old ones from last year.

    Bingo, now the edit/zoom do update automatically.
    Not sure why an old driver would work better than Microsofts new video driver.
    0
  • SFA
    Strange sort of problem but unhappily such things seem to occur all to readily in computer world.

    I had something similar with graphics card drivers last year where an alleged update, or a series of updates (OEM not Windows) broke more of the functionality I used on that machine than it 'fixed'.

    All sorts of reasons are possible inculding the obvious 'just a poor update' syndrome but we could hope that by the time it is released as a Windows update it should be quite resilient. Of course it is also possible that the update failed to install correctly but no obvious warning was given or that it relaies upon some other update which is not in place for some reason.

    What can happen with code from all soruces, not just video drivers, is that end user application vendors have coded around previous problems, some of which can be very old indeed. Suddenly someone fixes the old problems. This may make them work as originally intended or it may just change the problem. The fix might have been intentional or could simple be itself an error.

    This means that a new problem is created either because it is indeed a new problem or because it breaks the fixes and workarounds that had been employed to overcome the original problem. And so the cycle repeats ...

    Very annoying no matter what the cause may be but I doubt it could be avoided completely even if all developers had completely unlimited resources to throw at quality issues.

    Of course your problem may have a different root cause but my first guess would be something from the above suggestions.

    Grant Perkins
    0
  • Marbla
    I have the same issue with the most recent Intel grapics drivers (v. 3071) also running a 3rd gen i5 with an HD4000 graphics. I initially wondered if the move to opencl 1.2 led to problems, but it seems that the issue is not dependent on opencl settings.
    *Edit* Went and got the last drivers before 3071 and everything is working again. Hopefully this will be solved either by phase or by intel.
    0
  • NN102528UL12
    Good to know I'm not alone 😄
    Just made some tests for the Intel HD4000 Graphics...
    Graphics: 8.15.10.2598 Works!
    Graphics: 9.17.10.2963 Works!
    Graphics: 9.18.10.3006 Fail!
    Graphics: 9.18.10.3071 Fail!
    0
  • Lionel12
    I believe Intel has this one covered - I have been testing Intel drivers, and driver 3186 has fixed this issue for HD5200 Iris Pro. Should also fix the issue for Intel HD4000, but let's make sure once the driver becomes public.
    Once OpenCL is off, the display for Capture One is treated as a generic Windows device.

    On a side note, OpenCL for Intel HD4000 is internally disabled due to lack of resources (processing power). This will change once you get to Haswell Intel Iris Pro 5200.

    -Lionel
    0
  • Marbla
    Thanks for the info Lionel. Figures that OpenCl would not really do anything with the HD4000. It should be interesting with the next processor generation coming out from intel and amd. Since the new AMD chips should have GCN parts integrated they might actually amount to something. I guess the infos from intel should be coming pretty soon.
    0

Post is closed for comments.