Rendering with Azure

Offload and speed up rendering jobs using Big Compute on Azure

Key scenarios:

Wide-ranging industries

Rendering is used in numerous industries like media and entertainment for producing visual effects and animated movies; manufacturing for creating advanced engineering concepts and drawings; automotive for creating concept cars; advertising and science for simulating earthquakes, landforms, and ocean trenches; architecture for building, road, and landscape designs; and publishing for recreating historic events, visuals, and illustrations. Azure Batch can help with all of these scenarios and more.

Power when you need it

Rendering can be the most complex aspect of 3D production. A typical rendering workload includes still frames or animation rendered multiple times after changes are made by the artist. With the introduction of 4k technology, and resolution increasing steadily, more compute horsepower is needed for rendering. With Azure Batch, that power is available on demand with the ability to scale when more capacity is needed.

Keep costs down

No matter how cheap the machines are, in-house render farms are expensive to run. They require physical space and air conditioning, consume lots of power, and quickly become outdated. Azure provides many reasons for rendering in the cloud including the ability to quickly ramp up and down tens, hundreds, or even thousands of cores. This also means that you don’t have to worry about unpredictable rendering requirements. You can reduce costs by closely matching resources to jobs as you run them and pay only for what you use.

Streamline user experience

You can build a fully integrated workflow that gives artists access to massive computing power in modeling applications such as Maya, 3Ds Max, and Blender. When in-house capacity is close to full utilization, artists can scale out their workloads to Azure. You can use the Batch SDK to integrate a rich client experience natively into your application and allow artists to manage their rendering workloads including submitting and monitoring rendering jobs and getting outputs back.

Leave the plumbing to us

You no longer have to rely on building a rendering pipeline. Batch takes care of the rendering process. It schedules the jobs, spins up the virtual machines, executes the rendering process with the desired renderer, directs the outputs to the correct destination, and finally shuts down the virtual machines—all under the covers. Now you can focus on the actual production of digital assets rather than building and managing infrastructure.

Licensing that works

Different rendering ISVs and vendors have different licensing requirements. Run your rendering workloads on Azure as a virtual in-house render farm. Bring your own licenses to Azure and the rendering executable connects to the license server when executing the rendering process. This removes the complexity of managing hardware along with licenses and makes sure that you have the right number of cores for the number of licenses you own and vice versa.

Learn more