For this instalment in our ground-up series about integrating Gaffer into a pipeline, we cover how to change node defaults.
All Gaffer nodes have plugs, whether they are visible in the Graph Editor for easy connection, or in the Node Editor as settings. These plugs have default values defined by the node’s programming. It may be the case however, that these defaults aren’t the most useful values for your use. To help with this, Gaffer allows you to provide your own, “user” defaults.
In this instalment of the Gaffer for Pipeline series of ‘ground up’ posts, we look at adding custom bookmarks to the various Gaffer browsers. We’ll recap the tutorial from the Gaffer docs, introduce dynamic bookmarks and look at Gaffer’s own categories in more detail.
Gaffer 0.55.0.0 introduces the NameSwitch node; like a Switch node, but using names instead of indices for switching between the inputs. This post shows an example of the NameSwitch in use, and describes how you might customise its UI to better suit your pipeline.
Like many other applications that calculate data on-demand, Gaffer has a memory cache that can increase performance in UI sessions if you have RAM to spare.
The default size (1GB) is somewhat conservative as to ensure we don’t use up all the resources of more modest machines when Gaffer is used out-the-box. It is easy to increase the limit though, which can bring performance gains in real-world production scenarios.
It can be hard to know where to start when you first start integrating a new application into a pipeline. This post is the first part in a series that takes a bottom-up approach and brings together a few helpful links for getting started with Gaffer configuration, scripting and development.
In this part, we take a look at how the gaffer application is structured, and what happens at startup.