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

Strange dark overly on some images.

NN635217262769005787UL
I've spent some time trying to figure this out I'm baffled.

I'm not using any layers, presets or styles. I come across some images that have this dark sort of overlay on them. Streaky lines, Like I used some kind of filter in a new layer. Sometimes I can see like a dark outline from another image on the current image. I have edited an image and its fine, only to edit a few other images come back to it and its got this overlay or whatever on it.
I try regenerating previews, does nothing. If I export the image the strange dark overlay isn't there.
sometimes going back to the images after a while it will be gone, or if I close and reopen it will be gone. but then it just randomly starts on other images.
I had previously edited this folder of images with version 10 with no issues. (I started over with a new catalog)


Here is a screenshot i uploaded to drop box
https://www.dropbox.com/s/q2c06a3y2o38j ... M.jpg?dl=0

Any help is appreciated this is driving me nuts


Jim
0

Comments

17 comments

Date Votes
  • HansB
    It looks quite like an issue I had with v10. Some areas only received highlight recovery, the rest only shadow recovery. It usually happened in combination with a slight rotation and/or cropping. It didn't happen always, it suddenly appeared when I returned to an image. Not there on the exports, exactly as you described it. It created stripes, blocks, checkerboard patterns, and sometimes almost double-exposure-like ghosts. It wasn't caused by OpenCL, it happened with and without. Even on a MBP without OpenCL support in CO. And it was usually, but not always, gone after a CO restart. I filed a support case about it, and I thought it was solved.

    So...
    ...do you have highlight/shadow recovery on this image?
    ...if yes, does it disappear when you remove the recovery?


    Regards,
    Hans
    0
  • NN635217262769005787UL
    [quote="HansB" wrote:


    So...
    ...do you have highlight/shadow recovery on this image?
    ...if yes, does it disappear when you remove the recovery?


    Regards,
    Hans



    Yup, you are exactly right, I remove them and its gone. I had meant to mention that , but its been a few days since I attempted to edit. One of C1s best features, and I cant use it? 😭
    0
  • HansB
    [quote="NN635217262769005787UL" wrote:
    ...
    Yup, you are exactly right, I remove them and its gone.
    ...


    I was hoping not to read that.

    It took a while before I was able to pinpoint the recovery. Support wasn't able to reproduce it.

    Please file a support case on https://www.phaseone.com/SupportMain.aspx. Describe your findings as you did here, including screenshots and image.

    I'll dig up my old images and see if it's back here, too. If yes, I will re-open my old support case.


    Regards,
    Hans
    0
  • HansB
    Could you try using an older engine? It only happened to me in early v10 (it was 10.0.2). I used v9 on the same images without problems. Maybe it was carried over from v10 to v11, maybe it was fixed in a later v10 and returned in v11.
    (Set your default engine in 'Preferences' - 'Image' - 'Editing' - 'Default processing engine', then create a new variant. It will have the chosen engine.)


    Regards,
    Hans
    0
  • Ian Wilson
    Moderator
    Top Commenter
    I had a similar thing (using v10, still) with a couple of images while I was away on holiday the last couple of weeks. I reimported one of the images and it was OK. The other one I think I deleted the layer with highlight recovery and tried again, and that was OK too.

    Ian
    0
  • NN635217262769005787UL
    [quote="HansB" wrote:
    Could you try using an older engine? It only happened to me in early v10 (it was 10.0.2). I used v9 on the same images without problems. Maybe it was carried over from v10 to v11, maybe it was fixed in a later v10 and returned in v11.
    (Set your default engine in 'Preferences' - 'Image' - 'Editing' - 'Default processing engine', then create a new variant. It will have the chosen engine.)


    Regards,
    Hans


    If I do this within ver 11 and change the process engine to 10, new variant, it stays the same. Messed up.
    however i just reinstalled version 10. I can't use the same catalog,(won't let me use ver11 catalog in ver10) but I created a new one and loaded about 150 pictures in, they are all fine.

    I just submitted a support ticket. See what they say.

    EDIT: oh no, I take it back, it IS doing it in version 10 now also. I went through those 150 pictures and not a single one, now its doing it randomly again!!! So strange I had never had this in version 10, now after using 11 its going to do it in 10???? weirddddd.
    0
  • SFA
    I would suggest checking for any uncleared temporary files and maybe check the drivers for the GPU (if you can and despite HansB's observation that he could not point any blame as OpenCL because despite that opinion - which I fully respect - the symptoms shown are quite similar to the sort of things that a driver problem can produce and of course correlation and causation are not necessarily related! Sadly. If only things were always that easy.

    When you updated the catalog to V11 C1 will have saved a copy of your V10 catalog. You can get that back by renaming the saved file.

    I'm not a MAC user so will defer to others for the location of the file but it should be possible to search the forum and find relevant information or wait for a MAC resource user to respond.

    HTH.


    Grant
    0
  • HansB
    I looked up my old support case and my notes.

    I've tried a number of things without success that time:
    - clean uninstall/install of CO
    - created new sessions to edit the images
    - loaded fresh copies from memory card and opened new sessions
    - toggled CO preferences between auto and never
    - forced OpenCL off using Phase One's script
    - manually switched graphics cards in my Macbook Pro
    - reverted the monitor color profile to Apple's original
    - downgraded CO fro 10.0.2 to 10.0.1 and 10.0.0
    - clean install of El Cap 10.11.6

    I was able to clear the patterns (temporarily) by:
    - restarting CO
    - moving the white balance slider a tiny little bit

    I finally ended up downloading and installing CO v9 from the archive and edited all images from that shooting without any problem.

    So maybe you can do two things:
    - move the white balance slider a tiny little bit to see if it temporarily clears the pattern in v10 and/or v11
    - use CO v9 with the images from that shooting to see if there is the same issue


    Regards,
    Hans
    0
  • HansB
    Here's a worst-case example from what I saw when I filed my support case.
    https://www.dropbox.com/s/towgorvjhmx1r ... m.mp4?dl=0

    Jim,

    Does it look familiar?


    Regards,
    Hans
    0
  • NN635217262769005787UL
    [quote="HansB" wrote:
    Here's a worst-case example from what I saw when I filed my support case.
    https://www.dropbox.com/s/towgorvjhmx1r ... m.mp4?dl=0

    Jim,

    Does it look familiar?


    Regards,
    Hans



    yup, exactly like that. I will try some of the things mentioned don't have time at the moment. I did just remember, Mac had an update a week ago, and I DID have to install new video drivers for my nVidia 1070. I'm really thinking that is the issue somehow
    0
  • Jerry C
    I have had this artifact with occasional imported images (Canon RAW). Sometimes it affects 5% of the images in an import. It appears only with one of my memory cards and not the other.

    It appears to result from a link to another image created during import manifested only when adjusting highlights and shadows in a preview. It is not seen if these adjustments are removed. It does not appear with any other adjustments. The artifact appears to be derived from the luminance of an image imported at the same time and appears in the same album. Of note, it only affects the preview. Regenerating the preview has no effect. If I use the magnifying loupe, zoom in on the image, or display the image full screen, the artifact is not displayed.

    I have not encountered this artifact before version 10. I have no explanation for the artifact, but if I discard the image and reimport it from the memory card, it virtually never reappears. Another fix that lasts for a while was to reformat the memory card.

    I reported this as a case, but the tech folks had no explanation.

    Jerry C
    0
  • NN634700652925553223UL
    I am experiencing this same issue. I have tried everything and can't get free and clear of the issues. I started another thread before I was directed to this one. How can we get some answers from Phase directly. I find it hard to believe they have not run into this over the last year. It is happing in shoots that I shot directly into Capture One while tethered as well as shoots where I shot to card and downloaded files later.
    0
  • Benjamin Liddle
    [quote="NN634700652925553223UL" wrote:
    I am experiencing this same issue. I have tried everything and can't get free and clear of the issues. I started another thread before I was directed to this one. How can we get some answers from Phase directly. I find it hard to believe they have not run into this over the last year. It is happing in shoots that I shot directly into Capture One while tethered as well as shoots where I shot to card and downloaded files later.


    As this is a user-to-user forum, you can get answers from us directly by creating a case via the link in my profile, or the support page at www.phaseone.com
    0
  • Staticmemories
    i say uninstall and reinstall that's weird
    0
  • HansB
    I did

    - a full uninstall/reinstall of CO according to Phase One's how-to,
    - formatted the disk, installed OS X, only added CO to the installation.

    Nothing changed.

    But using CO v9 on the same images works without issues. Using CO v10 or v11, even with engine 9, the problem is there. Did a code change in screen rendering introduce it? Just guessing.


    Regards,
    Hans
    0
  • Jerry C
    I wrote previously about this. In my case, the artifact only affects the preview when the HDR sliders are adjusted. Then, it is not seen on the thumbnail or when the image is displayed full screen. The only thing I have found to reduce the incidence of this is to reformat the flash drive in the camera. SSDs have only so many write cycles before they lose bits. For me, the incidence of the artifact goes way down to virtually nothing for images recorded as the flash drive becomes about half full, perhaps because it is writing to a less used portion. These observations may be relevant, but it would take an engineer to explain the mechanism.

    I also found that reimporting the image almost always eliminates the artifact. All of my attempts to fix the problem as if it related to Capture One were unsuccessful. The actual source of the problem might be an interaction between the Capture One code relating to previews and importing images recorded on an aging flash drive. Of note, copying the images to a hard drive before importing does not seem to make a difference.

    This is a case where simply reimporting the affected image may be the only viable choice if reformatting the flash drive does not work.

    Jerry C
    0
  • FH Photo
    EDIT: oh no, I take it back, it IS doing it in version 10 now also. I went through those 150 pictures and not a single one, now its doing it randomly again!!! So strange I had never had this in version 10, now after using 11 its going to do it in 10???? weirddddd.



    To me they only happen when I'm under some tool tabs.

    Like Exposure or Color, but it never happens when I'm under the library tab.

    //Frank
    0

Post is closed for comments.