The tutorial is extremely well-written and easy to follow. Please note that “in the shadows” is not a trivial part of the image as viewed on the screen.Īlso, it is possible to make a custom OCIO LUT that is customized to one’s actual monitor profile, instead of simply assuming the monitor is an sRGB monitor. Always some sort of compromise is required in the shadows: Same applies for printing assuming the display and OCIO configuration offered the correct variables.Īccording to Graham Gill, a pure 2.2 power function isn’t obtainable with a real display. This would require a native 2.2 power function ICC with REC.709 primaries akin to Elle’s in her GitHub. For example, rarely is the canonical sRGB transform applicable given displays are a pure 2.2 power function. Same applies for curves, etc.Īn ICC will work fine assuming the definition matches the OCIO output. This is one way, and the UI would convert to reference values. For example, it is sometimes desireable to have the UI roll linear values direct, while other times it may be useful to have an OCIO nonlinear technical transform. Offer transform control on the UI elements.Where possible, make them radiometrically correct. Make sure that the operations work under scene referred values.Add a power function with fulcrum for the view, where fulcrum is the value that the power function operates around.As a bare minimum, a view transform on the tail end of the data chain.Note all of these would operate at the tail end of the chain: I haven’t had a shred of time to look at Photoflow on a case by case basis, however I can give a loose outline.
Which tools are missing and/or not properly implemented with respect to scene-referred editing? Probably the best way to start will be to take the examples that will post in the other thread that focuses on Blender, and see how they can be adapted to PhotoFlow…
#Photoflow screen prints how to#
How to tweak/extend OCIO transforms when producing images for printing, possibly allowing the user to optimize the output for a specific printer/paper combination? Is OCIO needed in the scene-referred editing part, or is the current approach based on parametric and linear RGB ICC profiles adequate enough? I am ready to invest time to introduce OCIO in the pipeline, but I would like to clarify exactly what and where…
Instead, the choice of the color model and specific color space used for the editing is left to the user, and can be changed on-the-fly by inserting colorspace conversion layers anywhere in the processing pipeline. PhotoFlow differs from most of the other FOSS RAW editors in the fact that its pipeline is not based on the Lab colorspace.
Following the lively discussion that is ongoing regarding the advantages of scene-referred editing and OCIO-based processing pipelines, I would like to start a thread specific to my PhotoFlow editor, as I have the impression that it is already quite well equipped for this kind of approaches.
0 kommentar(er)
