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

problem with the displaying of previews

Jünjakob
Hello,

since I have installed C1 6 pro on my computer, I experience a strange mistake on my previews when I work on RAWs. It is not all the time ... but when it is, it is really annoying.

When I operate corrections like exposure (and most anything else) the preview turns to some scrambled picture for a few seconds, before the photo re-appears. It looks something like this:

http://www.kayjaydesign.de/images/C1_display-error_s.jpg

My current system:

Windows 7 - 64 bit
AMD Athlon 64 X2 Dual Core 6400+
8 GB RAM
GeForce GTX 260
128 GB Kingston SSD (system) + 2 TB SAT-A Disk (data)
Dell 3009 WFP with 2560x1600 (requires dual DVI)

Any ideas how I can get rid of this annoying problem?
Thx in advance for helping...!

Jay Evers
0

Comments

4 comments

Date Votes
  • Paul Steunebrink
    Turn OpenCL off in the Preferences and stay up-to-date with the latest release of CO6 (6.0.1 currently) if you have done so already.
    0
  • Permanently deleted user
    [quote="Paul_E" wrote:
    Turn OpenCL off in the Preferences and stay up-to-date with the latest release of CO6 (6.0.1 currently) if you have done so already.


    Paul,

    Turning "Open CL" off seems to be the standard solution here. Why is Open CL so buggy?

    It is very sad to keep hearing "Turning Open CL off". The CO 6.x needs all the performance boost it can get to keep pace with the CO 5.x. We need more speed, not less, especially the speed boost is one of the big selling points of the CO 6.x.
    0
  • Paul Steunebrink
    Nelson,

    I do not have knowledge about the why of bugs but the enormous diversity of video cards is probably part of the challenge. The suggestion to experiment the OpenCL setting is a way of trial-and-error which is not uncommon practice to help another user. If switching that setting does make a difference it is best to report the issue to Phase One so they can further investigate.

    It is paramount to stay up-to-date with the latest release, and I believe the 6.1 release was another milestone in the process.
    0
  • Lionel12
    Please update to 6.1, and this problem should have been fixed.

    -Lionel
    0

Post is closed for comments.