Chaos Corona for 3ds Max > [Max] Feature Requests

Choosing specific elements for CXR

(1/3) > >>

RecentSpacesSam:
There was some discussion in this thread https://forum.corona-renderer.com/index.php?topic=35535.15 that for Cryptomatte it would be beneficial to only output that element into a .cxr file, whilst saving the other elements out in another format in an effort to prevent the file from being larger than necessary.

We're investigating using Cryptomatte more in our workflow (even more so now material masks are supported) and huge CXR files could potentially be a big stumbling block.
I appreciate this may be too late for 12 but in future versions is there a chance this might get looked at again in the future?

RecentSpacesSam:
Reading my post back I felt the need to clarify a few things.

My main reason for wanting this is to be easily able to use Cryptomatte in Fusion.
This already works but the downside is that you have to use a monster sized CXR file for it to work as currently the cryptomatte metadata doesn't get written into normal EXR's (not sure if this is the same across other renderers).

Generally one multi-layer EXR's is slower to load than several individual layers which slows down an artist's ability to work and increases comp render times.

Two possible solutions:
1. Implement functionality similar to 3DS Max's default exr setup, where individual passes can be added/removed and their bit-depth changed per element
2. Write cryptomatte metadata/manifest information to the Cryptomatte render element so that all passes rendered to separate files.

Ink Visual:
+1

As I already posted in the Cryptomatte Playground thread linked above, I would love to see improvements to the way CXR is saved, and fully support RecentSpacesSam proposed solutions.

piotrus3333:

--- Quote from: RecentSpacesSam on 2024-06-26, 11:35:01 ---Reading my post back I felt the need to clarify a few things.

My main reason for wanting this is to be easily able to use Cryptomatte in Fusion.
This already works but the downside is that you have to use a monster sized CXR file for it to work as currently the cryptomatte metadata doesn't get written into normal EXR's (not sure if this is the same across other renderers).

Generally one multi-layer EXR's is slower to load than several individual layers which slows down an artist's ability to work and increases comp render times.

Two possible solutions:
1. Implement functionality similar to 3DS Max's default exr setup, where individual passes can be added/removed and their bit-depth changed per element
2. Write cryptomatte metadata/manifest information to the Cryptomatte render element so that all passes rendered to separate files.

--- End quote ---

in general what you need for fast exr read is multipart exr (requires exr 2 support). software reads only one part (so one render element) and not the whole file.
assuming you are using cryptomatte plugin from Reactor - this one does not support multipart exrs - so you end up with two exrs per frame (multipart and non-multipart for cryptomattes)

you can basically edit the cxr file (LifeSaver plug for Fusion or Photoshop + Natron I guess), use better compression for colour data (dwab should be ok for LightMix), keep crypto at 32bit.
will save you a lot of disk space.

RecentSpacesSam:
Once again thanks for the detailed reply Marcin!

I had a look at LifeSaver and its counterpart pioSaver, unfortunately Lifesaver won't work for Cryptomatte as it only saves out to multi-part EXR's and neither option saves in the cryptomatte metadata.

Unless I've missed a step, for now we may still be stuck with creating two renders (beauty elements vs. masking/utility elements) but being able to re-order the render into multi-part will no doubt be a huge help, especially with the smaller sizes DWAB brings

Navigation

[0] Message Index

[#] Next page