Redshift cryptomatte invalid manifest

User avatar
JCB91
Fusioneer
Posts: 94
Joined: Thu Mar 10, 2016 1:46 am
Been thanked: 1 time

Redshift cryptomatte invalid manifest

#1

Post by JCB91 » Tue Feb 12, 2019 4:50 am

Hello,
we got cryptomatte .exr frames (sometimes full shots) from redshift Maya that have invalid manifest data.
When looking at the metadata mainfest only has RedshiftGlobalDefaultMaterial and GlobalScatterOneTraceDeepMaterial and it doesnt end with }.
Cryptomatte fuse in Fusion fails using this, but that PROEXR After Effects plugin works fine. It doesnt need manifest data?
Anyone had the same problem with Redshift Maya?

Tags:

User avatar
JCB91
Fusioneer
Posts: 94
Joined: Thu Mar 10, 2016 1:46 am
Been thanked: 1 time

Re: Redshift cryptomatte invalid manifest

#2

Post by JCB91 » Wed Feb 13, 2019 8:34 am

Problem seems to be exr compression. All frames that have invalid manifest data are ZIPS. The ones working are ZIP.
Beauty is always ZIPS for all frames. For the AOVs including cryptomatte in some shots all frames are ZIPS, in some partially ZIP and ZIPS.
Also it doesn't matter which machine rendered the frames.
We tried different exr compressions with Maya and redshift, nothing changed. This is probably a Maya redshift topic.