Arnold ROP: Cryptomatte AOVs

[BigRoy]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Arnold is known for rendering the Cryptomatte separately, even when merged AOVs are configured - so extra testing is needed to confirm Arnold ROP works with Cryptomattes currently with how layers are merged or not.

With the #72 it's unclear whether there are issues with the Cryptomatte AOV and whether everything functions as intended when rendering to a single file or not.

So, this would be follow-up on #72 and in particular to resolve the points mentioned in this comment.

How would you imagine the implementation of the feature?

• Confirm merged AOVs (no separate files configured) works as intended when rendering output files with Cryptomattes. There should be no errors and if the cryptomatte ends up being separate (because Arnold forcing that) the publishing should pick up the files to become an extra product.
• And fix any issues if there are any

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

So the core of this issue is to first test the functionality more - and confirm the different edge cases of how the Cryptoatte AOVs get rendered from Arnold.

[BigRoy]

The Cryptomatte AOVs with Arnold ROP in Houdini do not force/default to writing to a separate file - it behaves like other AOVs using the "Separate File" checkbox. So the collecting logic should work as intended.

Tested with HtoA 6.3.2.1 in Houdini 20.0.724