How to output Arnold AOV with filter ("closest", "Gaussain", "heatmap", etc..)

[Rachid Hadj abderrahmane]

hi
I'm really new to gaffer, I'm using Gaffer_0.60.7.0 py3.0 with Arnold-6.2.1.1 on Windows 10.
How to use Arnold filter like "closest" for P,Z,N and ID, or other filters like "heatmap", "gaussian", etc.. when outputting AOVS
any simple test scene will be appreciated
Thanks

[Daniel Dresser]

Sorry for the slow reply, we're all on holiday and the office is offline, and I don't have an Arnold install handy on my home machine.

But if I recall correctly, you just need to go to the "Outputs" node where you're setting up your  AOVs, click the triangle to expand the AOV parameters,  click the + to add a parameter, and add a string parameter named "filter", and set that to "closest" or whatever you want ( we automatically append "_filter" before looking for an Arnold node named appropriately ).

-Daniel Dresser

[Rachid Hadj abderrahmane]

Thank you for your help and good holiday!
I've edited the "outputs.py" in C:\Gaffer\startup\gui  to match other DCC, and all work fine,


but when I add the filter " closest" for zDepth (Z ), I get an error :
ERROR : Arnold : 00:02:31  1.4GB node "_filter" is not installed
WARNING : IECoreArnold::Renderer::output : Unable to create filter of type "_filter"
The Z aov is outputting correctly.

Outputting another AOV:  AA_inv_density, I get a warning 

WARNING : Arnold : 00:00:00  1.5GB [aov] all output filters not optimized for progressive -- expect worse performance and memory consumption

but the AA_inv_density  is rendered correctly.

if I put the word "_filter" rather then "filter" no error in the console for most AOV, except for  AA_inv_density witch work with "filter" .
So why I'm getting this error and warning?
Thanks

[Daniel Dresser]

Hmm, the "Unable to create filter of type _filter" message does sound broken - you would get that if you added the filter parameter to an aov but left it empty - Gaffer would be looking for a filter named "empty string", which doesn't exist.

The "all output filters not optimized for progressive" warning you're getting comes from Arnold, some of the filters you're wanting to use aren't specifically optimized for interactive rendering - if you're getting that warning, then everything is probably working.

--
You received this message because you are subscribed to a topic in the Google Groups "gaffer-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gaffer-dev/P0q-zbgvXK8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gaffer-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gaffer-dev/458c7419-0cd1-4c9a-a181-a325041f321dn%40googlegroups.com.

[Rachid Hadj abderrahmane]

Hi
So most of the filter are not optimized for progressive rendering!
but for "Unable to create filter of type _filter"  the filter is not empty as you can see in the image bellow

So  what do you mean by "if you added the filter parameter to an aov but left it empty" ?
Thanks again for your help, much appreciated.

[Daniel Dresser]

Just to check - the closest filter isn't actually working, is it?  The error message doesn't say which AOV has the problem, so maybe there's a bad filter on the beauty?  The other thing that occurs to me is that if there was a typo where you added a space at the end like "closest ", that might mess things up.  Just trying to think of possibilities now, because that looks like it should be working.

To view this discussion on the web visit https://groups.google.com/d/msgid/gaffer-dev/7d13f9a9-7d46-499c-95b7-c8daf3242c90n%40googlegroups.com.

[Rachid Hadj abderrahmane]

You are right, there was an invisible space at the end of the word "closest".
all work as expected mow, thank you so much