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

export or process variant results in black image

LotusO
Some images (D800 nefs) in session cannot be exported or processed as a tif from the edited variant (Jpegs are fine and I can process an unedited variant). The resulting tif shows up in the thumbnails momentarily then goes black. The tif also displays black when opened in photoshop cc 2015.
I have read previous threads and tried, as suggested, changing the tiling option to 128. I have tried exporting at 50% to reduce the resultant tif size. All makes no difference. Other images in the session can be processed just fine. I would think the file was corrupt, but Lightroom has no problem with the image - exporting successfully as a full size tif from an edited nef.
Hoping someone can shed some light on this.

Cheers
0

Comments

2 comments

Date Votes
  • Justin Katz
    First, check your process recipes and see if it is happening with one or many or all. If one, recreate the recipe with a new one. It could be that the Process Recipe is corrupted or has invalid settings (like trying to output to a location or drive that isn’t available). The best approach is to simply create a new recipe from scratch and trying again.

    If you are getting weird processing errors in your processed images, for example, you are only getting black frames when you process, it may also benefit to toggle your OpenCL settings for processing in your Capture One Preferences (Preferences > General > Hardware Acceleration). If it’s set to Never, try setting to Auto, or vice versa. Often times it will be set to Auto, and changing to Never will prevent any stored information in the Graphics card’s memory from being used to help process. Restart Capture One for changes to take effect.

    If this does not solve it, please create a support case at http://support.phaseone.com
    0
  • LotusO
    Thanks Justin, turning open GL off seemed to do the trick. I now have it back on and still working fine.
    Cheers
    0

Post is closed for comments.