theartofsaul

Any updates on this? I see 2.4 just released, but I do not see any mention of any fixes to the OCIO issues. Thanks.

Hey Chris, sorry about the double post. The first post I made was in the archived v1 forum section. This made me think maybe it would get lost in the v2 release noise. So I made this post to make sure it was visible. Thank you for passing this along and confirming the issue! Also really appreciate you hearing the feedback regarding LDR image exports. Thanks again and have great day!

Unfortunately, this is still not working. Also odd that the OCIO v1 config with any naming convention works fine. Please try the supplied OCIO v2 config rename it to config try it and compare it to the same output the OCIO v1 config gives from my previous post. They do not match when using ACES sRGB, the OCIO v2 config is outputting a purely sRGB output without the ACES ODT, aka Un-tone-mapped mode. I have also attached the EXR for your tests. It is working perfectly fine in Nuke/AE etc. As my previous example shows, the darker "contrasty" output is the correct output, but this is only working in OCIO v1 not the OCIO v2 config. This leads me to think that the built-in OCIO v2 transform for ACES SDR sRGB is not working correctly in the Affinity OCIO v2 implementation, as the other log spaces using the built-in functions are fine. Specifically this function `ACES-OUTPUT - ACES2065-1_to_CIE-XYZ-D65 - SDR-VIDEO_1.0` Thanks! config.ocio ACEScg_OCIO_Example.exr

Thank you for the new OCIO v2 support in the latest Affinity 2.2 release. I just gave it a quick test run, and unfortunately, I have to report that the ACES sRGB transform seems to be broken when using the built-in OCIO v2 ACES sRGB functions. You can try using this config which is OCIO v2 and works fine in Nuke/Fusion/Davinci Resolve and many other popular renderers. The Log, and Raw spaces are fine. But the ACES sRGB ODT looks identical to the un-tone mapped output. Which isn't correct. As a side note, it would be really nice if we had an option when using the file "export" into an LDR image format to apply or reverse a linear gamma to sRGB gamma. As exporting, say, a PNG or JPEG using OCIO adjustment layers will still output the linear gamma instead of returning it to sRGB Gamma. This washes out the output and makes the process a lot less user-friendly for artists. Whenever you change from 32-bit to 16/8bit in a Photoshop document or output to LDR you have an option to do this, as does the exporting of LDR image formats from an HDR image. This would make working with OCIO much better when users are ready for final export to an LDR image format after doing their color correction or compositing work in 32-bit. Example images and OCIO v1 + LUT folder config (working) and OCIO v2 config (not working fully), along with the LDR image export from HDR image format Gamma issue I mentioned above. Thanks! cong_ocio_v2.ocio OCIO_v1_Config_and_LUT_Folder.zip

Hey Ash, thank you for the new OCIO v2 support in the latest Affinity 2.2 release. I just gave it a quick test run, and unfortunately, I have to report that the ACES sRGB transform seems to be broken when using the built-in OCIO v2 ACES sRGB functions. You can give it a try using this config which is OCIO v2 and works fine in Nuke/Fusion/Davinci Resolve and many other popular renderers. The Log, and Raw spaces are fine. But the ACES sRGB ODT looks identical to the un-tonemapped output. Which isn't correct. As a side note, it would be really nice if we had an option when using the file "export" into an LDR image format to apply or reverse a linear gamma to sRGB gamma. As right now exporting say a PNG or JPEG using OCIO adjustment layers will still output the linear gamma instead of taking it back into sRGB Gamma. This washes out the output and makes the process a lot less user-friendly for artists. Whenever you change from 32-bit to 16/8bit in a Photoshop document or output to LDR you have an option for do this, as does the exporting of LDR image formats from an HDR image. This would make working with OCIO much better when users are ready for final export to an LDR image format after doing their color correction or compositing work in 32-bit. Example images and OCIO v1 + LUT folder config (working) and OCIO v2 config (not working fully), along with the LDR image export from HDR image format Gamma issue I mentioned above. Thanks! cong_ocio_v2.ocio OCIO_v1_Config_and_LUT_Folder.zip

Bumping this, years later it seems there is no way to import an HDR image "unmanaged" with zero ICC management. Odd considering it is an option in the 32-bit Preview but the file itself does not support a way to work with this.

Can we please get an update to the OCIO support in Affinity Photo? OCIO has been updated to OCIO v2 which supports a lot of cool new features including built-in transforms for ACES etc. Currently we cannot use OCIO v2 configs and this is rapidly becoming the standard as Nuke is beginning to integrate it, Maya 2022, Arnold Renderer, Redshift Renderer, both Photoshop/After Effects OCIO plugins and more. It would be great to have it upgraded to use OCIO v2 configs inside of Affinity Photo. Thanks! https://opencolorio.readthedocs.io/en/latest/upgrading_v2/_index.html#upgrading-to-v2

Going to throw in my +1 to more powerful painting workflows like those suggested here along with supporting some of the other commonly used workflow tools in Photoshop used by the concept art and matte painting communities who all are still heavily tied to Photoshop. While purely digital painting apps are great, one of the reasons the Concept Art and Matte Painting communities use Photoshop is also due to all the powerful Photo manipulation tools which are part of the average arsenal of digital painters in production nowadays. Adobe has mostly forgotten about this segment of its user base over the years and done next to nothing to fulfill their requests.

Bump, maybe the correct thing to do would be to have the Photoshop plugin support added? It would fill in all the missing gaps/features from the EXR workflow inside of Affinity Photo. They also have an interesting script to automate the Cryptomatte layering process which is a great workflow tool for 3D artists. please give it a look or maybe get in contact with the EXR-IO team? https://www.exr-io.com/ https://www.exr-io.com/autolayermaks-script-production-boost/

Clipping mask support +1 this is very useful for many digital painting techniques.

Just want to throw in the request for more EXR compression controls. For example when you use DWAA or DWAB it does not include any compression controls. Normally this is supposed to range from 0-100 with the typical default of 40. Right now I have no idea how much/little the EXR is being compressed when working with DWAA and DWAB. In general having more EXR controls would be welcome. EXR-IO the Photoshop plug-in does a great job with regards to all its options when dealing with EXR's. It would be nice to have similar options when dealing with EXR's. Also would be nice if you could expose the compression model "type" directly in the EXR export screen, right now you need to dig into its settings to even get to the compression models like PXR24, DWAB, etc. Thanks!

+1 this would be great to have, while EXR-IO is ok, having a full fledged integration similar to the one found in Nuke would be best.

Going to add my +1 to this request, would love to be able to use this in Affinity Photo in 32bit mode to tone map my renders. Thanks

Just wanted to mention that the latest beta update has fixed my issue. Thanks!

yep the issue is still there in the beta. Here is a screenshot showing the issue still happening in the latest beta 1.8.3.650. -Saul