Hey everybody.
ACES still is a big questionmark for me and the more I read about it, the more questions come into my mind. This is how I made my setup, based on @Arvid Schneiders recent Youtube Stream (https://www.youtube.com/watch?v=kReV9sUFe6E ). I hope someone can confirm that I am doing it right.
For testing, I am starting with an old scene, with a few sRGB textures, Maya color swatches, utilities like aiNoise and standard, out of the box settings in Maya.
1. I downloaded the color configurations from https://github.com/imageworks/OpenColorIO-Configs and put the aces_1.0.3/config.ocio file into the OCIO Config Path in Mayas Color Management.
2. A warning message appears "All color spaces used in the scene are not defined in the selected transform collection. If you proceed, affected color spaces will not be applied." and I click on "Proceed"
3. In Mayas Color Management Preferences the rendering space switches automatically to "ACES - ACEScg". The view transform switches to "sRGB (ACES)".
4. Under Input Color Space Rules, is set the Input Color Space to "ACES - ACEScg"
6. I set the View Transform of Arnold Render View to "sRGB (ACES)"
7. All my file texture nodes show a red warning "sRGB" color space not found. No color transformation will be applied.
8. I hit render, the image is darker than rendering with the standard settings but I get a broader range, all sRGB textures are washed out. The objects where I only used color swatches and utility nodes are looking more natural and as they should, highlights look sexy now and not blown out anymore. I have the feeling that the overall quality improved a lot but I know that textures need another color space.
9. Thats the point where I started to experiment with the color space settings in the file texture nodes: I chose "Output -sRGB". Probably wrong, but it was one of the few profiles in the dropdown menu that had sRGB in it and I chose to test. The textures in the rendering look right, I also set bump- and roughness maps to "Output - sRGB" and bump and roughness become way, way more stronger. Overall It looks good, but I know something is wrong with the color space settings.
So here are a bunch of questions I have:
- Is the setup from 1-8 right?
- Arvid says in his stream, that all textures need to be converted from sRGB to ACES. I don't have Nuke at hand and don't know how to convert the textures without it. Can I also convert them in Photoshop?
- Can I somehow use the sRGB textures I already have in Maya and use them as they are by choosing a specific color space in the file texture node without conversion to ACES? Maybe there is an Arnold node I can use to do the conversion in Maya without any third party program?
- I had my bump- and roughness maps set to RAW in the old color space settings of the file node. Do I also need to convert those maps to ACES (in Nuke or Photoshop) or is there an equivalent to RAW when working with ACES in MtoA? Can I just use "raw" from the dropdown menu in the file texture node? Do I need RAW anyway in my old scenes?
- Is there a way of switching all color spaces in all the file texure nodes at once? Without touching the nodes, having everything red and not defined in my old scenes, it would be cool to change everything at once.. like with the attribute spreadsheet editor in Maya for example, without changing everything by hand, one by one.
- After Batch Rendering, what is the right setting in Photoshop? I went through two ACES Proof Setups in Photoshop, where "ACEScg ACES Working Space AMPAS S-2014-004" looked very close to the still image in Arnold Render View. Is that a Proof setup I can work with on still image compositing in Photoshop?
Its a longer post and I am a technical noob when it comes to questions like this color space topic. Now that I know that ACEScg exists and that renders instantly look way more "natural" and better than before, I really want to use this right and hope that someone can give me answers to my questions.
Best Regards,
Kyan
