|
|
|
|
|
by Dylan16807
1711 days ago
|
|
Yes, it has to be injective from the real world to the file format. It doesn't have to be bijective. > As soon as you manipulate values of your image in your color space, you run the risk of falling outside the color domain. If your manipulation could go outside the domain, then your manipulation is incorrect. Like, if I have a number from 0 to 99 that I store in a byte, it's fine that a byte is not bijective to those numbers, and if I end up with a byte representing 105, then I did something wrong that corrupted my byte. If I'm doing incorrect math, a bijective color space doesn't fix the problem, it just guarantees that I get an incorrect color out the other end instead of possibly getting an incorrect color or possibly getting an error value. |
|
https://upload.wikimedia.org/wikipedia/commons/a/a9/Visible_...
Good luck representing that with only 3 channels, without using "bytes representing 105" (aka imaginary colors), and trying to stay percepetually uniform !
It gets even worse : the real color space is non-Euclidean : it stretches out, parallel lines drift further apart, etc.