Output Does Not Match Preview

Comments

15 comments

  • NFGphoto

    I've found that if the output doesn't match the image seen in C1, then it's a matter of the colourspace being different somewhere.  Perhaps you're rendering from C1 using a different colourspace in the selected recipe, or the application used to view the final image is different (this threw me for a long time, my image viewer defaulted to its own colourspace selection, rather than what the OS' specified).

    Double check the ICC profile (under Basic, in the Process Recipe tool) and ensure that's the same as the rest of your workflow.

    0
    Comment actions Permalink
  • jgh

    Thanks. I keep checking the colorspaces since that is the common theme in these discussions, but i cannot find any discrepancies.

    Also, just to be clear, I see the difference between the preview and the output within CO, not in another application.  When compared side by side in the viewer, the difference between the preview and the output is clear.

    Thank-you again. I'm still open to other suggestions for a solution.

    Gordon

    0
    Comment actions Permalink
  • gb

    Deleted, please ignore previous.

    0
    Comment actions Permalink
  • gb

    Try turning off OpenCL in preferences - hardware acceleration.

    0
    Comment actions Permalink
  • jgh

    Thank-you for the suggestion.  I have turned off hardware acceleration in preferences, but that did not change the output.  The results are the same with or without acceleration.

    One thing that confuses me with this situation is the Proofing function.  When I select an Output Recipe that is created to produce an output that mirrors my adjustments in CO and enable Proofing, I see no change in the image in the preview window.  However, when I run the Recipe and compare the output to the preview (in CO in the preview window) the output and the preview do not match.  When I choose a different Recipe that I know changes the color space or adds other adjustments during processing, I can see those effects when I enable Proofing.

    Isn't Proofing supposed to show what affect the Recipe will have on the image in the Viewer?  If the Proofing view matches what I see in the Viewer, shouldn't the Output of that Recipe match the Viewer as well?  Or is my understanding of the Proofing function incorrect?

    Thanks again for any help.

    Gordon

    0
    Comment actions Permalink
  • gb

    "If the Proofing view matches what I see in the Viewer, shouldn't the Output of that Recipe match the Viewer as well?"

    Yes it should. Just note that it is the highlighted recipe that will be proofed. The tick boxes are ignored.

    You could check that some form of display preset is not being applied to the outputted files.

    Select an output image and check all the C1 tools that might affect contrast/exposure/color,
    Make sure all sliders are at their default positions.
    Check that the RGB, luma and separate color channels in the curves, level and color wheel tools
    are at default too.

    Are you seeing this just with B&W exports or color as well?

    0
    Comment actions Permalink
  • jgh

    Thank-you again for your suggestions,

    To start, yes I see a difference in both black and white and color.

    And I am proofing with the highlighted recipe.

    I cannot find any sort of display preset being applied.  And I am comparing them side by side in CO.  This is not a case of the output not displaying as expected on different devices or in different programs.

    As a test, I created a variant of one of the images that I am working with. With no adjustments applied (nothing at all, as is, out of camera), I used the same recipe that I used on the adjusted image, and the resulting output does match the preview.  Well, at least to eye it does.  Visually the preview and output look the same in CO. The only qualifier I add to that statement is that there is a very slight change in the histogram between the two, but it is not enough that would cause any concern if my adjusted images came out that close.

    I guess the next step is to start eliminating adjustments one by one from my image until I find the one that is affecting the output in a negative way?

    Thanks.

    Gordon

    0
    Comment actions Permalink
  • gb

    "This is not a case of the output not displaying as expected on different devices or in different programs."
    So it must be something C1 is actively doing to the output file and not something that has been "burnt" into the file during export .
    "The only qualifier I add to that statement is that there is a very slight change in the histogram between the two..
    Yes there are always some exposure/color changes happening as the color profiles are applied.

    0
    Comment actions Permalink
  • SFA

    Gordon,

     

    Are you comparing the output file, prepared with an output recipe/profile, side by side with the pre-output version using the same Recipe/profile?

    If so your output file will have the same recipe applied again. For some images that might not be very noticeable.  For others it might make a big difference.

    0
    Comment actions Permalink
  • jgh

    Again, I am so appreciative from the help and suggestions here.  I have reached out to CO for support, but I get nothing at all back from them.  Not even an acknowledgement that they have received my request for support.  Very frustrating. I am starting to wonder what other options I may have, but deep down, I do not want to leave Capture One.

    Anyway, SFA I have checked, and I am not double proofing, so to speak.

    The search goes on for a solution. Any help is welcome.

    Gordon

    0
    Comment actions Permalink
  • NFGphoto

    Good morning Gordon.  

    It's difficult to get a handle on the problem without being able to work with your setup directly, but if I had this problem, here's what I'd be checking:

    Make sure your camera's set to use the sRGB colourspace.  If it was set to aRGB, you'd get filenames that start with an underscore, if it's sRGB they won't.

    In Windows, START -> color -> Color Management (control panel).  Select the monitor(s) you're working with, and note the colourspace you're using here.  Since you're seeing differences -within- C1, this is more of a sanity check than anything else.  C1, as a rule, works with this OS-set colorspace for displaying images.

    I make sure the space I'm using (sRGB in my case) matches the output recipe.  So, within C1, select your recipe, and under the recipe's BASIC tab, make sure the ICC profile is what you expect.

    Also within C1, go to the main menu VIEW, and DISABLE 'enable recipe proofing'.  Since we're simplifying and working entirely within one colourspace here, we don't need to have C1 try and show us something we're not going to change.  

    That's how my system's set up, and I can't think of anywhere else that might harbour some confounding configuration.  I took an unadjusted raw from yesterday's session and ran it as a JPG and a TIFF, and viewed them all in C1, and:

    [images were removed at poster's request]

    0
    Comment actions Permalink
  • jgh

    Thank-you. I will check it all again.

    I know screenshots are not the best way to compare, but I don't know how to show the adjusted preview file any other way.  Anyway, here are screenshots of the adjusted raw file and the .psd output. Even in these I believe that you can see the shift between the two images.

    Gordon

    0
    Comment actions Permalink
  • NFGphoto

    That's really interesting, and not a little frustrating.  It's a very subtle difference, but when you flick back and forth the black areas of the stone (and the trees on the right background) show noticeable differences in black level.  

    Try as I might, I can't match your problem.  The only other thing I can think of, in this particular instance, is that some sharpening is having an effect.  Especially when scaled down, that sharpening on this particular high-detail, high-contrast image might be having an effect on the overall appearance.

    0
    Comment actions Permalink
  • jgh

    I agree. It feels like a sharpening or contrast adjustment has been changed or applied to the output, but I can't find where that is happening.  Thank-you anyway for your help.  If anything else occurs to you, please let me know.

    Gordon

    0
    Comment actions Permalink
  • SFA

    It looks like there is less sharpening in the PSD file output.

    PSD is not an output I use. However I have noted that the default for Output Sharpening on the Export and Output process recipes is "No output sharpening" and I think this is based on the idea that most PSD file creation activities are intended for use in PS and further processing that will take care of eventual sharpening. If further processing is intended then including any sharpening is, apparently, considered a poor approach to getting the best out of PS.

    Is this in any way likely to influence what you are seeing? Or have you already covered this and I missed in when reading the thread?

    0
    Comment actions Permalink

Please sign in to leave a comment.