![]() ![]() He couldn't see beyond its current utility. A few years back, I showed my then 12-year-old nephew some historic tech that was ahead of its time when it was made, but was now verging on being a museum-piece. I'd probably want Color Depth to get its own shortcut key so that I can use it with the Photos extension but that's about it.Ī regards the language in the video, I think it says a lot about perspectives and the constraints of technology. In other words, I'd call my feature request not only met but also exceeded. What's more likely is that when I need to apply a Gaussian Blur, I may also need access to a brush that work in the same way, so it makes sense that I switch to using a linear colour-space up-front when I think I am going to need it. There might be occasions that I want to work in sRGB and still have access to a perceptual Gaussian Blur but those occasions will be few and far between. I ask for a new effect to be applied to *one* tool as a variant and you let me know that there's a whole method of working that no only supplies the effect that I want that that one tool but lets me use it with every tool at my disposal. It is important to do 16 bits first, otherwise you will loose lots of color information at converting to ACES, because ACES requires 16 bit to work properly (we are going to improve this user experience). → Advanced → ACES CG Linear (Match to Profile). → 16-bits per channel Ģ) Image → Color Profile. You just need to use linear color space, because in linear color space numerical color processing corresponds to perceptual color processing. The most important thing is that you can get perceptual processing for everything you want. Grain and sharpness are currently (as of version 1.4) are numerical, but we will redo them in a perceptual way. Numerical color adjustments are following: RGB Levels, RGB Curves, RGB Channel Mixer, Inversion (Luminance Levels and Luminance Curve are perceptual). are implemented numerically, not perceptually.Ģ) Color Adjustments are implemented perceptually, except RGB adjustments (to not surprise users). ![]() So, we come to the following compromises:ġ) All filters, brushes, gradients, blending, etc. Even things like RGB color model are numerical detail of implementation and very remotely related to the way we see colors, but everyone still wants to have tools like RGB Levels and Curves in image editor. If we did everything perceptually, then minimum required color depth will be 16 bits per channel, and all the results will differ from those in other software, so users will be surprised. This extends to everything, and the software should be completely implemented in perceptual color processing way. Thus, we need perceptual layer blending in order to not contradict to single-layer painting. But then layer blending should also be implemented perceptually, otherwise your will still have dark edges if you paint by red brush on separate transparent layer over another green layer. If we implement brush smoothness perceptually, then you will get good-looking yellow edges when painting on single layer. You will have these «ugly» brown edges around brush strokes (between red and green colors). ![]() For example, you paint red color over green background via smooth brush in single layer. If we mix perceptual and numerical approaches, we will come to contradictions. ![]() We either should make the software completely color-space-agnostic (compute everything perceptually) and consider color spaces only at import and export, or should do all operations numerically. The problem is that perceptual color processing should be implemented in «all or nothing» way. When designing Pixelmator Pro architecture, we were carefully considering all the stuff mentioned in the video (and all other stuff also), and came to the conclusion that we should do color processing numerically, as in older software (opposed to perceptually). Thank you for your question this topic is really interesting.įrankly speaking, I don't like the title of the video («Computer color is broken»), and phrases in it like «wrong», «ugly», etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |