While a safe option, in some situations this is not the most optimized solution. If you choose 4 Seeds and 4 Gardeners, RenderGarden will split your comp into four segments and render them concurrently. If you are rendering on one workstation, the simplest way to proceed is to plant the same number of Seeds as Gardeners.

The number of Seeds will vary depending on numerous factors.

if you have a 16-core computer, never go above 15 Gardeners). To be safe, always leave at least one physical core available (i.e. If you are using a computer as a render node and want to maximize cores you can try adding more Gardeners, but you never want to launch more Gardeners than physical cores. This should give you a solid boost in rendering performance while leaving headroom to continue to work in the background. We recommend starting with half the number of Gardeners as physical cores. In addition, it is very important to look at the number of physical CPU cores in your computer when deciding how many Gardeners to use. Modern computers use a technique called Hyper-threading which adds a virtual core (vCore) to each physical core, so a 12-Core MacPro will be seen by the OS as a 24-Core Mac. The number of Gardeners open per machine should be dictated by the physical CPU cores in your computer. RenderGarden splits the comp up into multiple segments (Seeds) which can concurrently run in multiple Gardeners to maximize your CPUs. Is there a formula to decide the best ratio of CPU cores to Seeds and Gardeners?Įach Gardener is a background After Effects “aerendercore” process. The following GPU plug-ins have been reported as problematic and are officially not supported (i.e. And on a single workstation, they can be used with one Gardener which still gives you add functionality over AE including background rendering and post-render actions. Note that these GPU-heavy projects can still see a RenderGarden benefit when used in a multi-machine render farm setup, assuming each render node has a single Gardener and compatible GPU. These projects can render with a single Gardener, but this prevents RenderGarden speed-ups on a single computer. Plug-ins that heavily rely on the GPU can not run multiple instances (Gardeners) at the same time due to the GPU over-saturating. Plug-ins that heavily rely on the GPU can not run multiple instances (Gardeners) at the same time concurrently. RenderGarden helps speed up CPU intensive operations by running multiple instances of aerender concurrently. Plug-in Support Does RenderGarden work with GPU plug-ins? Though we have had some users report success, we recommend you try it at your own risk and let us know what you find. We do not officially support cloud drives with RenderGarden. Does RenderGarden support cloud drives like Dropbox or Google Cloud? We’d love Adobe to add more command-line tools for other applications, so please reach out to Adobe with this feature request if you are interested in seeing RenderGarden support other tools. RenderGarden requires a command-line tool that is only offered in Adobe After Effects (aerender). Does RenderGarden work with other Adobe applications like Premiere or Media Encoder? No.

The current workaround is to save your Teams project as a stand-alone After Effects project then renders from there. Does RenderGarden support After Effects Teams projects?

Adobe premiere audio overload error