LuxCore icon indicating copy to clipboard operation
LuxCore copied to clipboard

CryptoMatte AOV support [$30]

Open thiagodesul opened this issue 5 years ago • 11 comments

Hello! Are you planning to add support to CryptoMatte in Lux?

If yes, is it possible to save Cryptomatte files in a separated .EXR file as Redshift usually does. It's better for our comp artists to have beauty and data passes in a different file.

Thank you!


There is a $30 open bounty on this issue. Add to the bounty at Bountysource.

thiagodesul avatar Jan 09 '20 12:01 thiagodesul

There has been talking about CryptoMatte in LuxCore but I'm not sure when it is going to happen, we have a very long TODO list at the moment.

Dade916 avatar Jan 09 '20 14:01 Dade916

There has been talking about CryptoMatte in LuxCore but I'm not sure when it is going to happen, we have a very long TODO list at the moment.

Yes, but allow me to say that you are doing great, a super wonderful job, and we will try to attract more users, and also donors and collaborators :)

I know this is off-topic, you can delete this comment, but I wanted to tell this for your answer :)

juangea avatar Jan 09 '20 15:01 juangea

Agreed!!

thiagodesul avatar Jan 09 '20 15:01 thiagodesul

I posted some bounty on the task a month ago. I don't know how it works but I assumed it would automatically reflect in the thread title. If not it would be nice if it's get added as for the other topics. Maybe it'll pique someone's interest to work on the feature.

https://www.bountysource.com/issues/86691864-cryptomatte-aov-support

AlexeyAdamitsky avatar Jun 05 '20 10:06 AlexeyAdamitsky

It should now.

Dade916 avatar Jun 05 '20 10:06 Dade916

I was looking into this today. I have not much knowledge of rendering yet. Would it be neccessary to do a deep integration into the rendering pipeline or would it be enough to tell LuxCore to just return mattes for a defined set of objects and then create the Cryptomatte from all single renders.

Blender::Cycles has a deep integration of Cryptomatte in its kernel.

RumbleballTheReal avatar Nov 09 '20 17:11 RumbleballTheReal

Cryptomatte are not mattes itself, it's a bunch of metadata that allows the cryptomatte node (or interpreter) to extract whatever matte we need in compositing, without pre-setting anything in the scene, you just enable cryptomatte and you are good to go, then you can extract fine mattes in Blender compositor, or Fusion or Nuke or whatever other software with cryptomatte support :)

juangea avatar Nov 09 '20 18:11 juangea

@juangea its not about reading the data out, its about retriving and writing the data with LuxCore

RumbleballTheReal avatar Nov 10 '20 07:11 RumbleballTheReal

I know 👍 I was answering to this:

would it be enough to tell LuxCore to just return mattes for a defined set of objects and then create the Cryptomatte from all single renders.

But I may have misinterpreted what you meant there :)

juangea avatar Nov 10 '20 08:11 juangea

This may interest you, it' the Eevee implementation for Cryptomatte :)

https://developer.blender.org/D9165

juangea avatar Nov 10 '20 14:11 juangea

Are there any advantages for luxcore renderings, if you can create cyptomattes with Eevee? I think an integration of cryptomatte into luxcore is essential for post production and professional work. Someone who has worked with cryptomattes won't want to work without them. I think the options cycles has are good. You can pick a matte for every single geometry, for every material and for the whole object. Does anyone has a clue how long an integration would roughly take?

mischterlampe avatar Nov 13 '20 16:11 mischterlampe