Terminology

Home Forums Help and Support Terminology

  • This topic has 2 replies, 3 voices, and was last updated 10 months ago by MW.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #144117

    Roger Breton
    Participant
    • Offline

    I confess I’m not a color management “newbie” but it took me a while to wrap my head around some of the terms used in DisplayCAL “Calibration” tab.

    I was especially confused with terminology around “Black”. I confess I read the online documentation more than once. That’s usually how it is for anything “new” and “unfamiliar”. I know I don’t have an IQ of 220.

    So, “Black level”. And by extension, “White level” and “White point”. I understand they need to live in separate menus.  The choices are either “Custom” or “As measured”.

    Perhaps this has long been mentioned by other DisplayCAL users but I thought I would bring it up in the interest of “clarity”.

    In a future release, would it be possible to add the qualifier “Native” to the right of the “As measured” menu option?

    White point (Color appearance) = “As measured (native)”
    Whille level (Luminance) = “As measured (native)”
    Black level (Luminance) = “As measured (native)”

    There is plenty of space in the interface to implement these “improvements” in my opinion which would go a long way towards adopting widespread terms in displays color management.

    Attachments:
    You must be logged in to view attached files.
    #144125

    Vincent
    Participant
    • Offline
    #144133

    MW
    Participant
    • Offline

    Some thoughts on modifying the labels. On one hand it might be easier to understand at a first glance. On the other hand it’s not directly clear that for example the white point setting is overridden by the individual application CM engine regardless, or that you even can set it to “as measured” and still be shown a corrected source color white point  if you configure the color aware app that way(I’m pretty sure that’s what happened when I tested this  condition a some time ago).

    Ultimately it requires the users desire to keep learning, not assumptions that things are what they appear to be and just work.
    Optimizing labels can only go so far. Maybe tooltips could help in tandem but it’s still easy to confuse a new user with vague language, or overload them with information, which already is an issue.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS