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

Issue with image preview

Comments

3 comments

  • dredlew
    The issue is not the software, the issue is oversharpening. This may (have) be(en) necessary, more on that later.

    The smaller version of the file will look different as it has been scaled/compressed down and extra/unnecessary information gets thrown out. How else would you fit the same amount of pixels/information, from like a large 4000x3000px into a small 1000x750px image? Physically impossible, so something has to go and it will be sharpness (that includes noise) first. The scale algorithm has to get rid of information while trying to maintain the overall appearance. The end result will be that it is similar but not the same as the original.

    Whether you zoom out in the viewer or export a resized version, in either case a smaller version of the file needs to be rendered for display. In order to achieve a certain output sharpness, the original or 100% size has to be sharpened more to make up for the resulting loss. This is usually fine, as it's unlikely that the original will ever be seen by anyone at 100%. All that matters is the output size and sharpness.

    Another way would have been to keep the sharpness in check on the original at 100%, export to output size and re-sharpen that smaller version after the fact. But that's a bit a convoluted process IMHO.

    Fortunately, C1 v10 now makes this easier with specific output sharpening (). You can keep the 100% at normal sharpening levels and add more sharpening just for the output. However, a zoomed out viewer still has to render a smaller image on the fly which will have less sharpness than the 100%. As I mentioned above, this is inherent to the compression process and is the way it is supposed to work. This is not unique to C1, any other application that displays images does the same, with varying results. This is expected and not an issue.

    Having said all that; from your images it looks like really heavy oversharpening, if you see that much white. This should generally not be needed if your focus is accurate and the lens is (micro) adjusted properly. I would give the camera setup a once-over first to make sure that's in good order. I rarely ever would have to sharpen that much, unless my focus clearly went off on the wrong focal plane and I really wanted to salvage the shot.

    HTH
    0
  • NN635992461021583172UL
    Hi dredlew, thanks for your reply.

    [quote="dredlew" wrote:

    ...
    The smaller version of the file will look different as it has been scaled/compressed down and extra/unnecessary information gets thrown out. ... This is usually fine, as it's unlikely that the original will ever be seen by anyone at 100%. All that matters is the output size and sharpness.
    ...

    That is a good explanation as to why a single image would look different when scaled.

    I understand that perfectly, and to that extent I wrote that:
    [quote="NN635992461021583172UL" wrote:

    ...
    At first, this kind of behavior doesn't seem like a bug - after all, the same image viewed at different zoom levels will look different, albeit very unlikely in my opinion, to show the differences I'm seeing.
    ...



    However the problem I'm describing is different, more specifically:
    [quote="NN635992461021583172UL" wrote:
    ... this behavior is not consistent across file formats. ...

    Put another way: two files (a Sony arw, and and a 16bit uncompressed tiff) that look identical at a 100% zoom level in the viewer, do not look the same when viewed at a 'Fit' zoom level.
    Moreover, as the non raw file is a 16bit uncompressed tiff, it's not only supposed to look the same to the naked eye, it's supposed to actually be the exact same color pixel-by-pixel at 100%, if I understand correctly.
    So for files that are identical at 100%, I'd expect the viewer to show the exact same preview at a 'Fit' zoom level.



    [quote="dredlew" wrote:

    ...
    Another way would have been to keep the sharpness in check ... Fortunately, C1 v10 now makes this easier with specific output sharpening ... will have less sharpness than the 100%.
    ...

    These are all workarounds for a problem with how the viewer works with Sony raw files.
    I could also for instance export the original to a tiff and work on that, as its preview representation is more accurate.
    However, at this point I'm not yet looking for cumbersome workarounds but rather to either actually solve the problem if possible (e.g. by ticking some checkbox I'm unaware of somewhere in the settings), or if not at least have the phase one development team be aware of this issue.

    Cheers.
    0
  • Sasha
    Same problem here. Raised a ticked and PhaseOne's response today was truly awful: "it's by design".

    At 100% my subject's skin colour is accurate and pink. At 50%, the subject instantly turns ill with clear signs of jaundice.

    Also working with Sony A7ii RAW files at high ISO.

    One thing which DOES significantly reduce (but not remove) the yellow colour cast is to change the ICC Profile under Base Characteristics tab to "sRGB Color Space Profile" (you need to select "Show All" first).

    But this approach is completely inconvenient as it's on a per-image basis. This definitely feels like an issue with the use of colour profiles (possibly linked to camera/raw file type) for rendering images in the preview/editing window.

    I don't hold much hope as I see the forum littered with this same problem, dating all the way back to CO7.
    0

Post is closed for comments.