Jonathan Mack

I don't think so, as that checkbox effectively makes it into a single task

jlait
If you want to cap VRAM consumption you can use Edit::Copernicus Settings::Video Ram. By default we will use all of your VRAM before we start evicting stuff to RAM. For compositing you may get away with a low value for this - the high value is to avoid things like Pyro from swapping.

We don't convert to RGBA in memory - it may look like that because the nodes all operate on RGBA, but they are doing just-in-time widening; so the memory use of a Mono channel is just one mono value. However, we DO operate on 32bit float by default, so that is 4x the memory of a 8-bit image.

An important optimization we don't do yet is to throw away the results that are no longer needed. Currently every COP node keeps its output, which adds up quickly at 4k. This means you can walk the network without recooking; but that is cold comfort when you've run out of memory.

How is memory managed on platforms with unified memory? With no main memory to evict to, is that setting used at all? Is there any unnecessary copying of layer data when moving from cpu to gpu compute? I'm finding even with 128GB of unified memory, it can be pretty constraining, I can't imagine what it's like with only 16GB of VRAM.

ronald_a

olivierth
Sorry, I was a bit busy.

I wanted to create a simpler scene to upload and I noticed that I get a very similar result for both Houdini/Karma and Maya/Arnold when I set both View Transform to RAW. This shows me that the colormanagement must be the problem.

Here are my default setting when I open a new Houdini 20.0.671:
sRGB - Display
Un-tone-mapped

Is this right?

View needs to be set to ACES 1.0 - SDR Video. This should be the same in Maya/Arnold as well.

that's not true at all, only use the ACES tonemap if you want the tonemapped look. Using that tonemap will only exacerbate the issue since it totally crushes the shadow values in the image.

For the original issue, to determine if it's a colorspace issue or a renderer difference, open both renders in the same viewer--that should reveal any difference if both renders are treated the same.