Table of Contents Show
Render recording, but where to put it?
Once you have linked the desired render presets to the various recordings according to this principle, the question naturally arises as to how the various storage paths should be handled. A render preset can easily be used by several recordings. C4D 17 has an answer to this with the new token system. Storage paths can now also contain placeholders and variables. One of these variables is called $take and represents the name of the currently rendered recording. Such placeholders can be anywhere in the save path and therefore also stand for the name of a folder, which is then automatically generated when the rendering is saved. Similar tokens make it possible to include the name of the render preset used, a multi-pass or the camera in the save path.
This of course helps enormously in being able to find the results directly sorted on the disc. In addition, an identical storage path can in principle be used for each render preset, as this can be automatically varied by the tokens contained so that no file overwrites can occur. As it may be necessary to render individual recordings again from time to time despite all the care taken, various commands are available to start the rendering of the recording. For example, all recordings in the project can be automatically calculated locally or via Team Render, or you can select individual recordings before rendering by ticking a box and then send only these separately for rendering. Similar options can also be found in the Render Manager if not only several projects, but also several projects with several recordings included there are to be rendered automatically.
