Network Rendering

Bigger, better, faster, more. If that's your mantra, you probably have a number of computers on your own network. Surely if one computer is good, more must be better. With network rendering, that's never been more true.

Network rendering allows you to designate a specific computer to render the entire output file, (nondistributed rendering) or you can distribute a single rendering job among several computers.

Both distributed and nondistributed rendering jobs can be queued to be performed as computing resources become available so you can render multiple projects or render the same project in multiple formats.

Rendering using a computer other than your main editing computer allows you to continue working without waiting for the render job to complete.

Is network rendering for you?

Maybe. There are many variables involved with network rendering: your computer speed, network speed and project complexity all have an impact on network rendering performance.

If you have fast computers on a fast network, you may see improved rendering performance. If you have slow computers on a slow network, you may see no benefit.

What do you want to do?

Set up your computers for network rendering

Set up file mappings

Run multiple instances of the service on a computer

Use nondistributed network rendering

Use distributed network rendering

Monitor rendering progress

Set render service options