When using Redshift and rendering multipart EXRs, the instances for cryptomatte AOVs are getting falsely marked as multipart EXR even though they are being forced to be separate files by Redshift.
Since we cannot query the AOVs multipart individually, we'll need a hardcoded rule.
Ideally I guess AOVs should be separate instances in the publishing process but that is too big of a scope atm.
Testing notes:
Configure Redshift render in Maya for multipart EXR and add Cryptomatte AOVs.
Publish and validate that only the main render instance has "multipartExr": true in the metadata json.
Changelog Description
When using Redshift and rendering multipart EXRs, the instances for cryptomatte AOVs are getting falsely marked as multipart EXR even though they are being forced to be separate files by Redshift.
Since we cannot query the AOVs multipart individually, we'll need a hardcoded rule.
Ideally I guess AOVs should be separate instances in the publishing process but that is too big of a scope atm.
Testing notes:
"multipartExr": true
in the metadata json.