Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
render [2015/06/01 22:33] slackermedia |
render [2021/06/03 19:48] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | [[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}qtractor|]] | ||
- | [[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}rosegarden|]] | ||
Line 15: | Line 13: | ||
- | ==== CGRU ==== | + | ==== Afanasy (Cg Toolkit) ==== |
Afanasy is part of the [[http://cgru.info|CGRU Cg Toolkit]], and it includes software to drive the render farm, to manage the render queue, scripts to produce dailies, and more. | Afanasy is part of the [[http://cgru.info|CGRU Cg Toolkit]], and it includes software to drive the render farm, to manage the render queue, scripts to produce dailies, and more. | ||
- | Set up is fairly simple; install the server on a "master" machine, install the clients on subordinate machines, and finally install the Blender plugin so that jobs can be submitted. | + | Set up is fairly simple; install the server on a "master" machine, and install and activate the Blender plugin (so that jobs can be submitted) on the client machines. |
+ | One installed, jobs are submitted through the ''Render'' panel in Blender. | ||
+ | |||
+ | {{ afanasy_properties.png }} | ||
+ | |||
+ | Currently there are no SlackBuild packages for Afanasy, so you will have to build and install from the project website. | ||
==== No Farm ==== | ==== No Farm ==== | ||
Line 36: | Line 39: | ||
With these options activated, you can point each Blender instance on each computer to the same network filesystem, (you can use **fish** or **samba** in KDE) and open the scene you need to render. Each computer will render frames until there are no frames left to render. | With these options activated, you can point each Blender instance on each computer to the same network filesystem, (you can use **fish** or **samba** in KDE) and open the scene you need to render. Each computer will render frames until there are no frames left to render. | ||
- | blender /network/drive/foo.blend -o /network/drive/out -t 0 -a | + | You can run Blender in the background: |
+ | |||
+ | <code> | ||
+ | $ blender /path/to/networked/file.blend \ | ||
+ | --render-output //relative/path/to/output/dir \ | ||
+ | --background --render-anim -E CYCLES \ | ||
+ | --threads 8 | ||
+ | </code> | ||
+ | |||
+ | Which means: | ||
+ | |||
+ | *blender: invokes blender. | ||
+ | */path/to/networked/file.blend: the path to the file that you want to render; store it on a networked file system so that other computers on your network can reach it. | ||
+ | *--render-output: this is the path to the directory where you want you output files stored. Note the special syntax of preceding the path with //two// slashes (''<nowiki>//</nowiki>''), which in blender-terms means "path relative to the .blend file being rendered". | ||
+ | *--background: run in the background rather than launching the GUI interface. | ||
+ | *--render-anim: render the animation in the .blend file (you could also render the scene). | ||
+ | *--E: which render engine to use (use ''-E help'' to see a list of available engines) | ||
+ | *--threads: how many threads to use while rendering (''0'' tells blender to decide on its own). | ||
+ | |||
+ | Blender is very strict about syntax. The options themselves must come //after// the file paths, and you cannot combine flags (so the traditional combining of options ''-b -a'' into ''-ba'' cannot occur), nor can you omit spaces between flags and arguments (no ''-ECYCLES'' when you mean ''-E CYCLES''). | ||
+ | |||
+ | For further details on options that you can use in the shell, run | ||
+ | |||
+ | <code> | ||
+ | blender --help | ||
+ | </code> | ||
- | Be sure to have -f # or -a last since rendering will run and evaluate the other args later. | ||
+ | <WRAP centeralign> | ||
+ | <wrap fa>[[qtractor|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[rosegarden|Q]]</wrap> | ||
+ | </WRAP> | ||
- | [[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}rosegarden|]][[{arrowp.png|border:0;background:none;width:0;float:right;}qtractor|]] |