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

Bugs introduced in 10.0 still not fixed in 10.0.2

Comments

10 comments

  • VirtualRain
    I'm afraid this video is analogous to the defect fixing at Phase One...
    https://www.youtube.com/watch?v=B4JRLS58nyQ

    😂
    0
  • Permanently deleted user
    Hi Russ,

    I didn't update to 10.0.2, I have only 10.0 at this time, but selecting CMYK profiles gives me % in CMYK, while selecting RGB profiles displays RGB values (0-255).
    I didn't observe any lag or local adjustments issue when using OpenCL display on.
    I haven't tried the uniformity values in the Color Editor.
    Cheers,
    Robert
    0
  • Russ Khabal
    Hi Robert,

    That's really interesting that you don't seem to have an issue with CMYK readout. On my end, the readout does look like CMYK, but the values are incorrect - skin mid-tones show Cyan value of ~80%. 🤓



    Which CMYK ICC profile are you using?

    Best,
    Russ
    0
  • Permanently deleted user
    Hi Russ,

    I have also, sometimes, for some skin colors, C around 80%, but with M and Y high as well. As I don't know exactly what should be the values, I can't make my mind. The best solution would be to open the RAW with Photoshop and measure with a CMYK profile (Lightroom can't do it)....
    I use the CMYK profile of my book editor, i.e. Blurb.
    Cheers,
    Robert
    0
  • Permanently deleted user
    Hi Russ,

    Yes, I've done it, and you are right !! The values measured with Photoshop CS6 are far better and much closer to the reality.
    I don't use very often CMYK profiles, but I think it would deserve to put a case.

    Regards,
    Robert
    0
  • HansB
    It seems like RGB and CMYK both behave additive, while CMYK should be subtractive.

    RGB is correct, but I expected white to be C=0%, M=0%, Y=0%, K=0%, not C=99%, M=99%, Y=99%, K=99%.


    Regards,
    Hans
    0
  • Permanently deleted user
    Perfectly right, Hans !!
    0
  • Permanently deleted user
    Hi,

    I have just suggested the P1 team a correction for a next update (case #243322).
    Cheers,
    Robert
    0
  • Permanently deleted user
    Hi,

    This is the answer I just got:

    "This is a known issue and will be addressed an upcoming service release for Capture One."

    Cheers,
    Robert
    0
  • Russ Khabal
    Thanks for all the support, Robert and Hans! Good to hear that this will be patched soon! 😄

    Cheers,
    Russ
    0

Post is closed for comments.