Hi TStrolia,
TStrolia wrote:OCIO Config File : (routed to blenders config.ocio file)
It is recommended to avoid using the default Blender3D color management folder and instead, download it from the official source:
https://sobotka.github.io/filmic-blender - long story short, the Blender3D developers made some changes to the naming convention - the files are the same, so is the result.
TStrolia wrote:(here's where it gets particularly dicey) OCIO view : Filmic (if enabled, highlights get a green glow in the highlights and shadows turn a bit magenta. Also, obviously gets even more washed out in compression because it is adding filmic to ACES. I basically just have to set OCIO View and OCIO Look to blank in order to get an image that resembles the colors I might expect to see)
I am confused about this part. Filmic by Troy Sobokta has nothing to do with ACES - In very short, ACES is a color encoding system, Filmic is considered to only be a "view transform" - the difference
mostly lies in the rendering-working-space, Filmic uses the default sRGB/BT.709 primaries, while ACES uses ACEScg AP1 primaries for rendering. In the case of Octane, a rendering-working-space is absent as Octane is calculates the scene
spectrally but encodes the rasterized result of the rendered image in a linear-scene-referred or display-referred sRGB color space, by default. Filmic is being applied "on top" of the default linear-sRGB (scene-referred)output/image file (unclamped 16-bit beauty EXR).
TStrolia wrote:My only thought is that its going out and going in ACES but perhaps I should switch to Linear but then things get super dark and the gamma is definitely off
"Linear" is not a color space. I strongly suggest reading my post:
https://www.elsksa.me/blog/understanding-linear-in-digital-imagerykabakZ wrote:x24 was updated to OCIO 2.0, which also requires an updated 2.0 config file.
Filmic uses an older configuration file, that's why the colors are not displayed correctly.
Dangerous misleading information - .ocio configuration files from previous versions are readable.
kabakZ wrote:I really wish there was a "normal" color manager by default. Highlight compression looks outdated and makes the image look washed out and less attractive.
A built-in advanced tone-mapping/color-processing is not only difficult to engineer, but also costly and time-consuming. At the moment, it is not a number one necessity since solutions (in post, packages like Filmic or custom proprietary ones, etc) are available, and that has been the case for many years.
kabakZ wrote:Still wondering how Daz3D(IRAY) solved this problem with the highlights, since they use linear, and it's very hard to achieve overbright and burn image there, which you have to deal in Octane all the time
I have never used Iray, besides a few times in Substance Painter but "linear" is meaningless in this formulated sentence. I have two blog-posts that explain about the meaning of linear in digital imagery, color management fundamentals and some more:
https://www.elsksa.me/blog/understandin ... al-imagery and here
https://www.elsksa.me/blog/cgi-color-ma ... rvival-kit.
TStrolia wrote:No, all I had to do was run it on auto and as long as it was set to linear aces I was set and good to go. No change in the scene at all unless I explicitly set the OCIO settings in the camera or override. Now it just straight up is always on.
I am not sure to correctly follow this thread - are you setting Octane's Intermediate OCIO color space to ACES 2065-1 while using Filmic OCIO by Troy.S? If yes, then you should let it on auto, it will use Linear-sRGB as default and is the only correct way.
TStrolia wrote:EDIT: Upgraded to OCIO 2.0. This is definitely a lot better. The colors look a lot cleaner. More correct. Filmic isn't a thing anymore which sorta sucks a little but its all good. At the end of the day as long as my view transform matches in all my editing software then I guess we are good. I only work on film compositing renders like 20% of the time so I think it will be ok... I guess I am gonna have to just play around until I figure out which OCIO view I like the most but out of the gate it is a lot more flat than even OCIO 1 with x23. Definitely good headroom.
The one from Troy Sobotka? If yes, then it is still viable. Beware that not a single online solution such as Filmic and ACES, are perfect. They respectively have their set of issues and improvements to do. Explaining it here would not be appropriate and very lengthy to write and read. I do plan to do so via on my website.
TStrolia wrote:Whites are a lot brighter and dont have as much detail unfortunately but I may just have to tinker. Do you happen to have any suggestions of which view/look to use?
Filmic OCIO By Troy.S did not change at all. If you had a working setup before, I assume a correct one, it did not change. It is still scene-referred linear-sRGB to Filmic Log to display-referred with contrast looks (in short).
TStrolia wrote:I will say, though, I am still sure I am doing something wrong because like I said, whites are right back to blown out with OCIO 2
There seems to be an enormous confusion here. OCIO is a color management
framework, it does not make sense that OCIO 2.0 allows for better or worse highlights or any drastic different result. OCIO allows for importing external color encoding/management solutions, OCIO itself without anything loaded to it, does strictly nothing.
kabakZ wrote:Also, don't forget to change "white light spectrum" to legacy in kernel settings. This is set to D65 by default which gives a warmer tint (bug).
It is not a bug. "D65" is referring to the CIE Standard Illuminant D Series D65.
TStrolia wrote:Comparison of filmic or ACES would be a bit hard because as it turns out, I seem to not have filmic anymore.
If I understood correctly, you made your own OCIO configuration file containing both ACES and Filmic by Troy.S?
kabakZ wrote:Well, as far as I know OCIO 2.0 support is on Blender's to-do list, so Filmic config will be updated to 2.0 too, but that could take a very long time, about a year or so...
I suggest to read my answer relating to OCIO configuration readability.