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

After updating C1 random images show up all black

Comments

8 comments

  • Jim_DK
    I vaguely remember a bug in a version where WB values were not updated properly when migrating.

    What build are you using? Check you have the latest (8.3.4)
    0
  • NNN634665269316987988
    Thank you for the reply, James.

    Yes, I am using the latest build (8.3.4). Any ideas?
    0
  • Christwo
    Had the same issue with the windows version on 8.3.4, had to reset and process again.
    0
  • NNN634665269316987988
    Thanks for the input. How do you go about "resetting"?

    Tried resetting adjustments for the black images but that doesn't seem to change anything.
    0
  • Jim_DK
    Try resetting the WB tool (using the local reset on the WB tool's tool bar)

    http://help.phaseone.com/en/CO8/Optimiz ... aspx#item5

    Contact support if it doesn't resolve and they will dig deeper into the issue: http://support.phaseone.com
    0
  • Christwo
    "Reset adjustments all all selected variants" the back arrow pointing at the vertical line key. Hope it works for you!
    0
  • SFA
    [quote="Christwo" wrote:
    "Reset adjustments all all selected variants" the back arrow pointing at the vertical line key. Hope it works for you!


    If that works then at a guess it might suggest that there is something amiss in the internal indexing of the catalog (or session) database that is perhaps the result of a corruption (cause probably unidentifiable) in one of more of the edit files related to the affected images.

    I had something like that once a couple of years ago with a session. It kept crashing when try to scroll through using the browser. 2000 images that visually seemed OK - until I stumbled across one that showed a corrupt (in my case) thumbnail and preview. Re-generating the preview made no difference to the corruption. So I deleted the edits for that image (basically what Christwo is suggesting), re-edited the problem image and all was well.

    I never did find out why the edit file was problematic. I have not seen the problem again.


    HTH.



    Grant
    0
  • NNN634665269316987988
    Thanks to all for the replies.

    Unfortunately I have tried all suggestions and have not found a solution. Going to file a support case and see what happens. Will report my findings.
    0

Post is closed for comments.