Add a setting to disable aliasing/multisampling on AOVs
It's not quite possible to use AOVs to generate cheap, easy-to-control masks/mattes. The problem is that the buffers are aliased or multisampled or something, meaning that there are soft edges that aren't valid values (or worse, valid values for a different part of the matte).
I'm aware that the recommendation is probably to use cryptomatte, but my target output is a
.png
file, which would require me to convert the saved
.exr
- and in any case, this is an automation scenario, and I have yet to discover a way to recover the hash value to do so (or even retrieve the manifest data).
2 Comments
Can't you just extract your desired matte from the cryptomatte in the compositor and then output it as a PNG? You can even export multiple passes as PNGs using the file output node.
No, because I haven't found a way to get the cryptomatte id out with python (the entire setup is automated, so I can't click on the UI, which would be a problem anyways). Additionally , cryptomatte is somewhat a poor choice due to it also being aliased and motion blurred , aside from the sampling already done during rendering.