PolderAnimation wrote:Hi Karu,
Thanks for the elaboration.
Concerning the minor issue you mention, I looked at the OCIO config and all seem fine, can you confirm that this is not something that is misinterpreted on your side?
The config.ocio file defines the data role / colorspace as follows: (I removed al non-related lines)
- Code: Select all
ocio_profile_version: 1
search_path: luts
strictparsing: true
luma: [0.2126, 0.7152, 0.0722]
description: An ACES config generated from python
roles:
data: Utility - Raw
displays:
ACES:
- !<View> {name: Raw, colorspace: Utility - Raw}
colorspaces:
- !<ColorSpace>
name: Utility - Raw
family: Utility
equalitygroup: Raw
bitdepth: 32f
description: |
The Raw color space
isdata: true
allocation: uniform
allocationvars: [0, 1]
Are you saying that because the color space has
isdata: true
it should be treated as data by Octane? That's a reasonable thing to expect. Octane currently only partially does that - the actual OCIO transform is a no-op but it still converts to/from the OCIO intermediate color space. Should be fairly easy to fix.