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

Poor image rendering, usually when opening C1

Comments

6 comments

  • Paul Steunebrink
    I think it is good you opened a support case. This issue can have several causes, but working with the latest update often helps a lot. So are you on CO 8.0.2 already?

    Next, you can go to your preferences (Edit menu) > General tab and set OpenCL hardware acceleration off (Never it is named).

    In addition to these suggestions it is best to follow-up with your case. Maybe we read the solution here later.
    0
  • NN635468391227852789UL
    Thanks, Paul.

    Do you recommend turning off hardware acceleration for both display and processing? As far as I understand, my graphics card should be able to offer some help (low specced again, GT520), but that is based on it helping with video rendering in Premiere. I don't know if it actually the case with C1.

    Also, I had forgotten to update to the latest version, which I'm doing now.

    Edit: How can I change my crazy username??? Don't see how I can.
    0
  • NN635468391227852789UL
    Now on 8.0.2. I don't see the issue presently, but not confident anything has changed.
    0
  • Paul Steunebrink
    [quote="NN635468391227852789UL" wrote:
    ...
    Edit: How can I change my crazy username??? Don't see how I can.

    Change user name is currently and temporarily not possible by the user itself, but through a support case only. The website design will provide this functionality in the future, I am told, again.
    0
  • SFA
    [quote="NN635468391227852789UL" wrote:
    Now on 8.0.2. I don't see the issue presently, but not confident anything has changed.


    I noticed some minor strange anomalies using OpenCL in 8.0.1. Not the same as your problem but peculiar things happening behind the scenes. 8.0.2 seems to have fixed them so something has changed. Whether that is in the code or simply some sort of working or temporary file being replaced and "fixing" a data anomaly I cannot say. Either way the problems I saw I no longer see.

    I think C1 tries to take as much performance benefit as it can from the available technology the machine can offer. This means that it may be working very close to the limits of capabilities some times for some activities. The target is for high speed performance with large files. There will almost certainly be occasional stability risks in the early times of development in such a process and some people have seen quite a few problems. Personally I have observed almost none so there are clearly many factors involved both for computing hardware and the camera and file technologies.

    At least you are running on Windows - there seem to be fewer externally introduced problems with windows than with Macs.



    Grant
    0
  • NN635468391227852789UL
    Thanks to everyone for chiming in.

    Going back to the original images I had raised a ticket about still showed the problem. I forgot to mention that, in those early images, it was a case of recovering severely underexposed areas that had a lot of noise. It is a bit of a torture I believe for that to be rendered well at such a zoomed out state, but again, it isn't happening in other software.

    Otherwise, with my latest image that the problem appeared with, I haven't seen issues again there, or with any other image (it really happened almost every time I opened C1). Hopefully any funky rendering will be limited to images with severe noise (what support said the issue was previously), and I can think of that terrible rendering as a feature; letting me know, "Hey! Buddy! You've got a lot of noise to deal with here!" 🙄
    0

Post is closed for comments.