Thanks for pulling that list together JF! Your list was correct relative to the Autodesk products. (Flame and 3dsMax do not currently support OCIO.) From: <ocio-dev@...> on behalf of

Probably should add Flame then as well, right? What about 3DS Max? Thanks! JF

On Sun, Feb 23, 2020 at 05:04 PM, Jean-Francois Panisset wrote: Autodesk Maya got OCIO support in version 2016 (I believe Autodesk SynColor color management system can read OCIO configurations?), May

El 23/02/20 a las 16:16, yashagrawal048@... escribió: Please add mrViewer which is a professional flipbook player, hdri viewer and video/audio playback tool. It supports OCIO

A few apps in no specific order: Unreal Engine got OCIO support in version 4.22, released in April

I am the developer of PhotoFlow (https://github.com/aferrero2707/PhotoFlow), and editor for RAW image files. It supports OCIO via a dedicated tool that can load a given configuration and apply the

Some softwares have added OpenColorIO support which are not being reflected in https://opencolorio.org/CompatibleSoftware.html . Can anyone suggest me all the softwares, libraries and DCCs which

Cancelled: OpenColorIO TSC meeting (weekly) This event has been cancelled. When: Monday, 17 February 2020 9:30am to 10:00am (UTC-08:00) America/Los

Hi Doug, Thank you for the info. I tried P3D65 from ACES1.1, but it uses a gamma of 2.6, rather than the sRGB gamma of the iMac P3 displays, so in the end, I modified the ACES configs, creating a new

This is perhaps more of a question for ACESCentral, but here is some info that may help you: 1) MacOS uses ICC color management for the display. OCIO is not integrated with that. So to some

I am starting to adopt ACES1.0.3, and have a question about the iMac P3 displays. Most people seem to use ACES sRGB for viewing, but this is quite different from the display P3 color space. What

Cancelled: OpenColorIO TSC meeting (weekly) This event has been cancelled. When: Monday, 30 December 2019 9:30am to 10:00am (UTC-08:00) America/Los

Cancelled: OpenColorIO TSC meeting (weekly) This event has been cancelled. When: Monday, 23 December 2019 9:30am to 10:00am (UTC-08:00) America/Los

Okay, I found out what magic it is.  The R3DSDK has an ImageProcessing struct and I was not setting it.  Once I set it to the camera settings, everything started to match.  Note that besides the

Okay, here's a crazy one.  If I decode the R3D clip as 16 bit, and I set the input color space to Output - Rec.709 and set the view to Rec.709, I get a matching picture to the one you saved out from

Glad to know. Currently, I cannot get the same result with the sRGB/rec709 of ACES.  I get a close to good, but darker  and more saturated image, as I got with exrs.  This is the issue with the

Hi Gozalo, good to hear that it is going better! The OCIOColorSpace Node in then ACES script is only for demonstration and debugging sake. You don’t need it in production. When you set the Input

Dear Eberhard, I can confirm that the Nuke default one is matching my version completely, but without the middle node that you have in the Nuke script.  The RED SDK it seems already sends a half

Hi Gonzalo, maybe you should consider that something in your pipeline is broken. I tried your file out and all worked fine. Attached are two Nuke files (one ACES 1.1, the other Nuke default) with

It happens with any RED file, but if you want one to try, try the first clip (the one with the guy in the motorcycle) from the sample 3d