Quantcast
Channel: xsisupport – Arnold Support Corner
Viewing all 250 articles
Browse latest View live

[HtoA] Denoising light group AVOs with noice

$
0
0

To use the Arnold Denoiser (noice) on light groups, you need to have variance AOVs for the light group AOVs.

There are two ways to associate a variance AOV with a light group AOV.

  • Use the same light path expression (LPE) for both the light group AOV and the variance AOV.

    For example, the “red” and “red_variance” AOVs use the same LPE: C.*<L.'red'>
  • Use the same name for both AOVs, but give the variance AOV a different layer name.

    For example, suppose you give both AOVs the name “RGBA_green”. Then give the variance AOV a different layer name, like “RGB_variance_green”

Use the same light path expression (LPE) for both the light group AOV and the variance AOV.

Give the light group and variance AOVs the same name, but different layer names

Then to denoise the AOVs:

noice -i "light_group_denoise.0001.exr" -o C:\temp\denoised.exr -pr 3 -sr 3 -l red -l RGBA_green
noice 7.1.1.0 [72784a51] - the Arnold denoiser
Using 8 threads.
Loading images...
Loading file "light_group_denoise.0001.exr".
Using feature AOV 'denoise_albedo' with filter 'gaussian_filter'
Using feature AOV 'N' with filter 'gaussian_filter'
Using feature AOV 'Z' with filter 'gaussian_filter'
Working with 1 frame at 1280x720
Will denoise AOV "RGBA", using associated variance
   Output file will be "C:\temp\denoised.exr"
Will denoise AOV "RGBA_green", using associated variance
   Output file will be "C:\temp\denoised.exr"
Will denoise AOV "red", using associated variance
   Output file will be "C:\temp\denoised.exr"
Start denoising (patch radius 3, search radius 3, variance 0.5)
Denoising RGBA
Denoising RGBA_green
Denoising red
Finished denoising
Saving image C:\temp\denoised.exr (1280 x 720 x 12)

Add -irgba to that if you want to skip denoising the beauty. Note that with -irgba. the beauty AOV won’t be copied to the output file. Only the denoised AOVs go the output file.

All the AOV, LPE, and layer information that you set up in HtoA goes into EXR metadata.
noice uses that metadata to find the variance AOVs for each AOV. The association may be through the AOVs having the same name, or the AOVs using the same explicit LPE.


NEW: Getting a trial license for Arnold

$
0
0

To get a trial license, go to the Free Trial page at https://www.autodesk.com/products/arnold/trial-intake

You have to click the Download button. That’s what generates the trial license and adds it to your Autodesk account. But you don’t need that download (it’s the Arnold SDK, not an Arnold plugin), so Cancel that download after it starts.

You can download the Arnold plugin of your choice from arnoldrenderer.com/download.

To use the trial license, install the Arnold plugin and then start the Arnold License Manager and sign in.

Troubleshooting HtoA installs

$
0
0

If you have a problem like this:

  • HtoA does not show up in Houdini
  • the HtoA material nodes are missing
  • or you get node type errors such as
    • Failed to match node type definition
    • Error: bad node type found
    • Unknown operator on load

that is almost always because the environment (PATH and HOUDINI_PATH) is not set up correctly for HtoA and Houdini.

First, how to do you start Houdini? Don’t double-click on a hip file, because the Houdini environment won’t be set up correctly.

Second, what’s your houdini.env look like?
You want something like this (PATH is for Windows only):

# htoa config start
PATH = "$PATH;C:/arnold/htoa/htoa-5.6.0.0_r370661f_houdini-18.0.597/htoa-5.6.0.0_r370661f_houdini-${HOUDINI_VERSION}/scripts/bin"
HOUDINI_PATH = "C:/arnold/htoa/htoa-5.6.0.0_r370661f_houdini-18.0.597/htoa-5.6.0.0_r370661f_houdini-${HOUDINI_VERSION};&"
# htoa config end

Third, check Help > About Houdini > Show Details
You want to see the HtoA location at the start of HOUDINI_PATH

If you have other renderers and plugins, I would remove all other plugins from HOUDINI_PATH, get HtoA working, and then put the other stuff back.

If you need more help, please send support your houdini.env file (or json package if that’s what you’re using) and the Houdini info from Show Details.

The case of the hrender that failed to start AdskLicensingAgent

$
0
0

Or, “things that happen when you use single-user licensing on a render node” 😉

In this case, a Houdini command-line render with Arnold (HtoA) failed because the AdskLicensingAgent failed to start.

---------------------------
AdskLicensingAgent
---------------------------
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, webgl, windows.

---------------------------
OK  
---------------------------

After AdskLicensingAgent crashed, the render would continue, but license authorization would fail:

00:00:00   148MB         | authorizing with license manager: user ...
00:00:31   153MB WARNING | rendering with watermarks because of failed authorization:
00:00:31   153MB         |  [clm.v2] timeout before callback was called

Using Process Monitor, I saw (as expected) that the problem was that the AdskLicensingAgent was loading Qt platform plugins from Houdini:

The solution? Set QT_QPA_PLATFORM_PLUGIN_PATH to point to the AdskLicensingAgent\platforms folder.

set QT_QPA_PLATFORM_PLUGIN_PATH=C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\Current\AdskLicensingAgent\platforms

The case of the Sign In that didn’t sign in…

$
0
0

In this case, a macOS user was able to sign in using the Arnold License Manager in Cinema 4D R23, but not with the Arnold License Manager in Cinema 4D R25. Instead of opening accounts.autodesk.com in a browser window, all that happened was the “Signing in…” progress message:

The solution?
Install the latest Autodesk Identity Manager

The reason that Sign In worked in R23 was because that was with an older version of C4DtoA and Arnold. And that older Arnold did not use the Autodesk Identity Manager, it used Autodesk AdSSO (which Autodesk replaced with the Identity Manager).

Unfortunately, signing in with an older Arnold doesn’t help with a newer Arnold. You still need to sign in with the newer Arnold. But it works in the reverse direction: sign in with the latest Arnold, and that will work for the previous versions too!

Looking for the Arnold API Reference?

$
0
0

[HTOA] How to…use append mode in Solaris

$
0
0

Append mode (aka check-pointing) allows you to restart an interrupted render, and render just the remaining tiles. Those tiles are “appended” to the tiles that were rendered before.

If you’re using the Arnold Render Settings LOP,  the Append check box is under File Output > Driver Options. You have to enable Arnold product type for any of the driver options to work.

If you’re using the regular Render Settings LOP, you can turn on Append mode in the Render Product LOP. Don’t forget to change the Product Type to arnold.

[HtoA] Example package file

$
0
0

Here’s the package file I’m currently using.

{
    "load_package_once": true,
    "env":
    [
        {"HTOA_PACKAGE": "HTOA"},
        {
            "HTOA_INSTALL_PATH" :
            [

                {"houdini_version == '20.0.506'": "D:/programs/htoa/htoa-6.2.5.0_re21740b_houdini-20.0.506/htoa-6.2.5.0_re21740b_houdini-20.0.506"},
                {"houdini_version == '20.0.547'": "D:\programs\htoa\htoa-6.2.5.1_r539f2c5_houdini-20.0.547\htoa-6.2.5.1_r539f2c5_houdini-20.0.547"}
            ]
        },
        {"HTOA_STARTUP_LOG": 3},
        {"HTOA_MAKETX_WORKERS": 30},
        {"HOUDINI_PATH": [
                {
                    "value": "$HTOA_INSTALL_PATH",
                    "method": "prepend"
                }
            ]
        },
        {"HOUDINI_TEXT_CONSOLE": [
                {
                    "value": "1",
                    "method": "append"
                }
            ]
        },
        {"HDARNOLD_DEBUG_SCENE": [
		                {
		                    "value": "C:/temp/hdarnold_debug.ass",
		                    "method": "append"
		                }
		            ]
        },
        {"HOUDINI_SPLASH_MESSAGE": "Loading HtoA: $HTOA_PACKAGE"},
        {"PATH": [
                {
                    "value": "$HTOA_INSTALL_PATH/scripts/bin",
                    "method": "prepend"
                }
            ]
        }
    ]
}


Getting an Arnold log from the Houdini Log Viewer

$
0
0

First, set the Arnold log verbosity to Info (typically, Info is more than enough).

Then open the Log Viewer.

Render something. Then in the Log Viewer, switch to text-only view.

Select All (Ctrl+A) and Copy (Ctrl+C) and paste into a text file.

Importing render vars and products into Arnold Render Settings

$
0
0

Here’s a setup that renders cryptomatte to one Render Product, and the lighting AOVs to another Render Product.

This uses the new input port on the Arnold Render Settings LOP.

This results in the following scene graph:

which renders two EXRs

00:00:09  3152MB         | [driver_exr] writing file `C:/Users/blairs/Support/houdini/beauty.0001.exr'
00:00:09  3152MB         | [driver_exr] writing file `C:/Users/blairs/Support/houdini/crypto.exr'

Viewing all 250 articles
Browse latest View live