Introducing color calibration module (formerly known as channel mixer rgb)

How about keeping the word invalid, making people ask about it again and again until

becomes folk wisdom and people will keep saying something “i didn’t knew too, but then i read the manual and i recommend you do so too” :stuck_out_tongue:

1 Like

That’s completely wrong and also this is the origin of the whole problem.

Many people are still confused that color is somehow related to temperature when it comes to white balance, even in the classical software and interface (just browse your average photo forum). So, as of now, either they built some practical notion of the temperature <=> color mapping (as some arbitrary amber-red → blue axis) with no understanding of the theory, or they had to learn how light spectrum correlates to temperature of a planckian radiator (whether they call it planckian radiator or not).

In this context, I don’t see how much worse it is to just warn about the wrongness of the temperature. There is no need for physics if you don’t want them, you only have 3 things to understand:

  • if daylight-ish illuminant, then color <=> temperature by some physical law you don’t need to understand – just know there is a link,
  • if not daylight-ish illuminant, then color is whatever. Typical software offers color <=> (temperature, tint) but that is piling up shit on top of wrongness, so we simply offer color <=> (hue, chroma) with no further assumption – it’s robust and generic,
  • in our classical transparent way, we tell you if your illuminant is daylight-ish or not, and let you decide how you want to proceed from there.

That’s all.

A lot of photographers/artists/tech-shy people know when to use a polarizing filter and what it does to picture, yet very few of them understand the principle of filtering light waves depending on the orientation of their electric field. If you don’t understand it, you take the word as an arbitrary label, learn the result obtained with the technical apparatus labeled so, and learn how to control said apparatus to obtain said results.

Just because I strive to publicly expose the reasoning and the inner technicality doesn’t mean everyone has to go to M.Sc to use the thing. There are 2 use cases (daylight-ish or not), and a label that tells you which one you are in, just follow the recipe.

Besides, talking about color temperature without ever saying the name “illuminant” is also part of the misunderstanding, because the illuminant is the thing which (equivalent) temperature is measured. So people will have zero chance to understand what’s going on with temperature as long as they are prevented from conceptualizing a real-life object that is actually hot/emits radiations.

3 Likes

Thank aureliene. Thank you a lot for your time and efforts for trying to make us understand these concepts. Not all developers (few of them, indeed) take such an effort.

I think i more or less understand what you mean, and as often i am sure you are right.

I don’t meant temperature and tint is the correct model.

I meant they are concepts people have managed to ‘u dertand’ even no in depth or being a not completly correct model.

But literature and tutorials have simpkified this concepts enough in a way that comon users can manage them.

I undertand more or less what is temperature as the temperature of a black bpdy that radiates a given light wave seen as a precise color.

But tint us not as easily understood. Many colors are not possibleusing just a radiation body.
So tint is a kind of deviation from the locus? Of the radiatong body, something like the distanxe from the nearest color that can be emited with it.

I don’t know if that is exactly what tint is, but i think it is a working model for not technically people.

It seems quite an artificial model, by the way.

I would be glad to change it for another one. You say chroma and hue.

But we will need a better understanding of what chroma and hue is.

I have seen previous links to very good books and online tutorials.
But reading almost 300 pages would be a bit hard to begin with.

I will try to read them slowly and see if i can understand part of them and improve my knowledge.

Meanwhile i would need a working definition of what chroma and hue is.
I have read this terms in many places but used in a loose way.

I had thought hue and chroma were similar, but it is obious they are not.

I have read dtdoc about color concepts, but not fully understood what hue and chroma is, will need to find more examples about it. And read it slowly and in a big screen and not in mobile to see if I can understand it.

Just replace invalid with see manual :slight_smile:

4 Likes

It’s not darktables purpose to widen audience; main purpose is to widen capabilities useful for those that are limited by simplified tools

5 Likes

I’m going to chime in here and say that darktable is too powerful to not expect people to read the manual.

1 Like

The manual is useless when it gets too technical for most peopke, but the ones who understand the color science.

I can understand what hue is, everybody has used the color wheel.

Chroma is not as easy to understand.

I love aureliene explanations about color concepts, anyway.

I have to read it more carefully to see uf i can understand it, but some .ore graphucs with the color wheel and may be some graphic about what chroma is may help.

Results are great, we just need get used to the interface and new concepts.

The manual tries to keep everything straight in constant terminology without making it hermetic.

If you don’t understand chroma or hue or both there’s https://darktable-org.github.io/dtdocs/special-topics/color-management/color-dimensions/ :slight_smile: specifically made to explain terms used.

see https://darktable-org.github.io/dtdocs/special-topics/color-management/color-dimensions/#illustrations :stuck_out_tongue:

As you can see - the manual is SUPERB.

3 Likes

I would agree, the manual is great and I use it almost daily.
But I can see why some parts are not always easy to understand for some. This is partially because some of the concepts are inherently hard to understand. But I have also noticed some terminology from the world of mathematics and physics used, which can further cloud comprehension for those without this kind of background. I’m not sure if the manual still includes such words, but two that come to mind are “orthogonal” and “abscissa”. Layman’s terms for these would be something like “at right angles” and “x axis” respectively. The manual’s attempts at being very precise and technically accurate are one of its many strengths, but keeping it in plain English as much as possible should be a goal in my opinion.

I’m an editor by trade and have previously offered to contribute to the manual if more volunteers are needed…

2 Likes

http://www.huevaluechroma.com/ This is a great site with some nice explanations and examples…

1 Like

contribute as much as you can :slight_smile: Including huevaluechroma stuff.

3 Likes

Thank you all.
I have read it but not fully understood it.

Hue i think i understand it, it us the classuxal color wheel.

Chroma has a definition that is not all that simpke… What do we understand for colorfullness compare to gray?

It is not so simple to understand
I thonk of it as some kind if aaturation, but not in the perceptive world but in physucal world.
O us gray 100% full color corresponding to hue.

I have to study the graphs, but in the mobile i cannot see the well, will havd to wait for a pc screen.

The explanation about saturation and chrima sounds very inyeresting.

The link would help too, thank you.

Will do, thanks!

Agreed. You don’t need an invitation. All pull requests to dtdocs are considered. If you want to make major changes, best to raise an issue for discussion first though.

1 Like

I doubt I would be making any major changes; more likely changes of a proofreading/editing nature for consistency/clarity.

2 Likes

I have read manual and the provided link. Thank you, I think i have a better undertanding of chroma, hue and other concepts.

Manual explains perfectly what invalid means in color calibration module and that it does not invalidate color correction, just that the used illuminant does not fit plankian model.

I have sime doubts about chrome, may ve i have misunderstood it.

But in the link and concepts definition in manual talks about chroma as a perceptive property: how close or distant are we from a gray with the same lightness as seen by a human observer, so perceptually as we see it with our eyes and brain.

But in many of the recent modules talk about chroma as scene referred, thus physical or at least phisiologically, after using cone filters in our eyes.

May you explain this a bit more?

VñBy the way, may be i can help in translating parts of the manual to spanish.

Is there a way of doing it without installing git and hugo?
Some kind of online page were you can paste the translation?

Right now i am not easy accesd to my computer, after summer i will get more involved.

We have a spanish speaker forum about dt that can help in polishing my translation, or privide more translators.

Please see here for details. All translations are done online in weblate so you don’t need to use git/hugo at all. Edit: looks like Spanish is currently at 100% translated, though weblate is not currently entirely up-to-date with the English version of the manual. We’ll look to get that updated within the next few days.

Yes, it’s translated even so fresh eyes could be great.

@ariznaf I encourage you to work in the translations :slight_smile:

1 Like

Sometime all the explaining the world may not resolve the issue…If you pull up a color wheel esp one that has also a saturation gradient and use extreme slider adjustments you can visually see what it does to primary and secondary colors…then you can apply the observed behaviour to your images.