Let's stop using Hex / HTML colour codes. "The Nightmare" Part 3

แชร์
ฝัง
  • เผยแพร่เมื่อ 10 ก.ย. 2024

ความคิดเห็น • 8

  • @RomixV
    @RomixV ปีที่แล้ว +5

    A new part from my favorite series! Thanks bro 😎

  • @unstablejamil
    @unstablejamil ปีที่แล้ว +2

    This one of the best design series in youtube, not so many channel has covered color management. Thank you very much. But I need to know how to minimize off color for device that has a low sRGB percentage, is it enough to avoid "out of web" and "out of gamut" color.

    • @StudioPetrikas
      @StudioPetrikas  ปีที่แล้ว +1

      Most of the digital image editors have a "gamut clipping" overlay/tool that informs and indicates whether you are within a certain gamut. That might be of some use to you.

    • @unstablejamil
      @unstablejamil ปีที่แล้ว

      @@StudioPetrikas thanks for replying, I'll look it up

  • @GencoUney
    @GencoUney ปีที่แล้ว +2

    (ColorSpace)(R, G, B) carries colorspace info but how about gamma? Also its hard to imagine wat the actual color would end up becoming for different spaces as their white points differ too.
    Or perhaps we can actually make it so that it is like a "code". It could be 3 values, CIE XY coordinates for chromaticity and Linear Value (X, Y, V). Then RGB or CMYK conversion could be handled by the software for any colorspace or gamma. Creating an absolute "Code" for color.

    • @StudioPetrikas
      @StudioPetrikas  ปีที่แล้ว

      Well, technically, a Colour Space is only a Colour Space if it defines 3 things:
      1. Primaries
      2. Transfer function
      3. Whitepoint
      So all the info is already included.
      CSS has included a way to specify 'linearity', if necessary - just add -linear to the Colour Space. I'm sure people can come up with other ways to specify something in greater detail.
      Remember "colour" exists only in your head. And it's incredibly dependent on context. It's basically impossible to reliably match colour by matching tristimulus values. It is likely this is a "problem" that cannot be "fixed".
      I thought about the absolute values, but a lot of issues arise. Once again we lose the intuitive part of the value triplet. As well as automatic gamut traversion. (I.e. What happens to an sRGB document if I paste a "laser green" value?). Or a value that fits into no colour spaces? This creates a gamut mapping issue that we still don't have a robust solution to.
      I thought that the Colour Space(RGB) solution was a bit more elegant and already, somewhat, almost being adopted.

  • @MrSofazocker
    @MrSofazocker 8 หลายเดือนก่อน +1

    why would I ever want to define my color in terms of the end viewing/display transform?
    the color is abstract and has no units, tone mapping should take care of things to display the same color across monitors, the returned light, the color will be different for each colorspace. Not really sure hwat you meant there.