D
Deleted member 16349
Guest
It has long been known theoretically that one can not get accurate colour values from RGB values. That has not stopped developers in the graphic arts to imply they can.
An interesting blog post by John Seymour of QuadTech covers this issue and provides interesting tests to highlight this problem. He also talks about his years dealing with this problem and his final conclusions. It is clear he spent a lot of time and frustrating effort with this issue, which frankly could have been avoided if just understanding and accepting that theoretically it was not so workable.
His interesting blog is at this site.
John the Math Guy: RGB into Lab
But what does this mean? It means that RGB workflows can not accurately describe colour. Many developers might claim that it is good enough but this is foolish. The reason it is foolish is because when one tries to solve a problem with an approach that conflicts with known theory, one can not know the magnitude and location of the errors that will result.
For years I have discussed the problem issues in the press which cause the lack of consistency and predictability. There has been no real interest to get these issues fixed. The RGB problem is just as important and I expect there will be no interest to get it fixed either.
From the recent rant by Frank Romano about colour management and other related issues on an Enfocus webinar, he clearly showed his frustration but of course he had no solutions. His frustration stems from the lack of action by the industry to understand the core issues and properly address them.
The industry lives in two worlds. One where publications, associations and suppliers state how well things are being done with new technology and the other world where every day problems continue to stress people due to the lack of consistency and predictability.
Systemic problems are the worst because they will constantly be a source of frustration and waste.
An interesting blog post by John Seymour of QuadTech covers this issue and provides interesting tests to highlight this problem. He also talks about his years dealing with this problem and his final conclusions. It is clear he spent a lot of time and frustrating effort with this issue, which frankly could have been avoided if just understanding and accepting that theoretically it was not so workable.
His interesting blog is at this site.
John the Math Guy: RGB into Lab
But what does this mean? It means that RGB workflows can not accurately describe colour. Many developers might claim that it is good enough but this is foolish. The reason it is foolish is because when one tries to solve a problem with an approach that conflicts with known theory, one can not know the magnitude and location of the errors that will result.
For years I have discussed the problem issues in the press which cause the lack of consistency and predictability. There has been no real interest to get these issues fixed. The RGB problem is just as important and I expect there will be no interest to get it fixed either.
From the recent rant by Frank Romano about colour management and other related issues on an Enfocus webinar, he clearly showed his frustration but of course he had no solutions. His frustration stems from the lack of action by the industry to understand the core issues and properly address them.
The industry lives in two worlds. One where publications, associations and suppliers state how well things are being done with new technology and the other world where every day problems continue to stress people due to the lack of consistency and predictability.
Systemic problems are the worst because they will constantly be a source of frustration and waste.