114
Replies
Hi,
This is very exciting for me, because I work with a lot of brand colors and Aces is always a struggle. But I can not get this to work properly. I tested a scene from Cinema 4d 2023.1 with the latest Redshift 3.5.09.
Then I imported the .EXR file into the Beta After Effects. These are the project setting I use, sort of mirroring the Color Management in Cinema 4d.
As you can see the result below. The colors are more saturated.
I also tried the Ocio Config from the Cinema 4d folder
With the same result. So I thought it has something to do with the color profile in the .exr file.
So I'm guessing, or Cinema 4d / After Effects is not showing the correct working or I am doing something wrong. I hope it's the last one 🙂
Thanks,
Willem
You folks deserve a million kisses for this one! It's finally coming and I've never been a excited as now for an Adobe software update. This will mean so much for the industry.
Here's my initial feedback:
Upon some quick tests I already ran into an issue with exporting with ODT applied. What would be the way to bake in SDR Rec.709/sRGB into ProRes? Both the gamma is off and values above 1.0 are clipping.
(output was set to sRGB display, interpret footage + viewer set to Raw)
Left exr through sRGB ODT, right ProRes with baked ODT
Another thing that immediately stood out to me was that we aren't allowed to use the OCIO Color Space Transform without setting global management to it. What if we wan't to manually manage a project in some cases? I think it could be nice to still read from the project settings which config to use but have Adobe managed enabled instead. Or/and give the option to browse to a config on the plugin itself. May sound weird after all the craving for OCIO but for some setups it can be nice to only have some tools to convert between certain spaces via a config and not use the display/aces output side of things.
And what about OCIO through environment variables? Can imagine many studios wanting to manage configs through that on their systems.
Design:
Now that we have a pretty full page on the Color tab the other 4 tab's settings look quite lonely....
Maybe group them up a bit? They could all fit within one tab now the window is this big by default.
Workflow:
Will be be able to define color spaces in the color picker so we can choose say Display sRGB colors instead of values that become the workingspace's color values. I think globally via color picking role makes sense but could be nice to have a setting for it in the colorpicking window so it can convert from there too?
Like that for example.
But again, great progress has been made already! Also really happy with other improvements lately with v23.0 release and now in current beta ARRIRAW on the GPU finally with proper processing for Anamorphic :D. Recently finished a project with that were it would have been incredibly helpful to have already but we managed in the end.
Look forward to more features and improvements. OCIO Premiere next?...
Hi Shebbe,
Regarding OCIO 2.x Display Transformed exports
We already have a switch `Show all` check box in Output Module Settings dialog to list all the color spaces from OCIO configuration file. Currently we do not list Display view color spaces.
We are proposing to extend this switch to list color spaces from Display list as well. I hope this will fix the problem of export with baked RRT + ODT.
Modified list will look something like: display color spaces appended at the end after a divider.
Please let us know your thoughts on this.
Thanks,
Hi @Chetan Nanda ,
Finally had some time to evaluate. This works for now but I don't believe this is the way to move forward as it suffers from design issues in conjunction with how OCIO works. The same could actually be said for the composition viewer.
Problem 1:
The entries are all the way at the bottom of the list whilst you could consider them more important than all the other color spaces except for the interchange color space ACES 2065-1.
Problem 2:
The ACES 1.3 OCIOv2 configuration lists a set of Un-tone-mapped and Raw spaces for each display device trippling the amount of entries in the list. In all cases the Raw option means the same as it displays the working space without ODT/RRT.
In total there are 9 target displays but 39 entries in the list. If a single display gets added in the future it would have a minimum of 3 more entries.
Suggested solution:
Separate the View Transform from the Display Device. This way we can simply pick the target device like sRGB or Rec.2100PQ and in a second dropdown we have the choice for the View Transform like HDR Video 1000 nits. This option automatically switches depending on the chosen Display Device.
This works the same as the OCIODisplay tool (which AE is also still missing as a plug in!). You can see how this works in Nuke's implementation for example.
Composition viewer:
I would place the two menus next to eachother. You could make it dynamically switch between labeled and menu only depending on the size/available space of the viewer window.
Output Module:
Option 1:
Instead of a Show All checkbox make it a mode switch. Perhaps 'Display Output' or 'Bake View' is a suited name. Upon checking this we would get the same two dropdown menus instead of the main OCIO colorspaces list.
Option 2:
Add a second field for this setting with an enable option greying out the above settings.
Hope this is useful to you!
HeyJoanna,
- both Beta OCIO configs are broken - can't get proper colors displayed in viewer no matter whch sRGB transform I use in the viewer - no problems with built in 1.0.3 config and custom 1.2 config
The configs aren't really broken, it's just the way OCIOv2 works. If we want to be able to export display views the color spaces need to be added into the config as it's own full defined color space. If you run your own config you can add this as it's own entry but all OCIOv2 configs will work like this unless ACES decides to change their configurations.
Adobe could also decide to alter the config but since they're still beta it's not really relevant at the moment.
The older OCIOv1 config is LUT with the RRT already in the transforms. Now they live separate.
What Adobe should also do is add an OCIO Display effect similar to the fnord plugin and Nuke so you can have it on an adjustment layer.
- is there a way to still use display color profile? Right now it seems the best we can get is display the viewer in sRGB, but I have a calibrated WsRGB monitor, so sRGB values come out too saturated. With the default CM in AE, after everything was configured we could check in the View menu "Use display color management" which added one last operation in the chain of pushing the sRGB viewer colors through the system monitor color profile - with the new OCIO color management that option in the View menu is grayed out
This is not how OCIO color management is intended to work. Your display should be calibrated to a specific display standard and software that run OCIO should do a clean feed to that display. If your monitor is much wider than sRGB it's very likely you have an sRGB profile setting in it's menus. Calibrate on that or create a separate calibrated profile for sRGB if it can be hardware calibrated.
- the old CM could read embedded color profiles in source footage, not all, but jpgs came in as sRGB, rec709 footage was recognized as rec709 etc. The new OCIO CM just gives up and applies the scene color profile to everything, could we get the same behaviour as the old one? If it thinks it's an sRGB source, apply a proper OCIO import profile.
OCIO works differently. Defaults/roles for certain filetypes can be defined by the user and implementer can also expose seettings to change them. Adobe should implement this imo.
(example from Nuke)
On top of that you can also configure filename aliases. In 3D this is common to do. Think 'MyTexture_albedo.jpg' would be recognized as "Albedo" and get sRGB - Texture assigned if it was written to do that.
PS. I specificaly wrote import profile not input profile because the proper sRGB profile in this place would actually be the Output - Output sRGB profile from the OCIO
What I said above also explains why you wouldn't want sRGB files by default to be Output - sRGB per se.
But still, most studios adjust the configs to suit their workflows and needs.
Nothing is stopping you from changing your configuration to best fit your work.
Very easy to create an extra entry to the list instead of custom too. Just add it to Adobe After Effects (Beta)\Support Files\OpenColorIO-Configs\ or use the environment variables method.
AdChoices