[Bf-committers] remote controll blender renderer renderfarm / queue

Robert Grah smilingmolecule at web.de
Wed Mar 18 11:08:43 CET 2015

I did it like you suggested. Started everything from the Python script. I also use the argument passing to Python.What format do you pass the arguments. Since they come in as a list I decided to bundle them with equal sign. "framestart=1"
and split them in Python. 
The last thing I am not sure about is if it is a good idea to call the blender command for each single frame or pack jobs into severall frames.
Since the background option seems to start blender really fast it might give more flexibility to restart blender every frame.

Thanks for the example!

---- Ein Fr, 13 Mrz 2015 12:49:08 +0100 Campbell Barton <ideasman42 at gmail.com> hat geschrieben ---- 

On Fri, Mar 13, 2015 at 9:19 AM, Robert Grah <smilingmolecule at web.de> wrote: 
> Hey Campbell, 
> thanks for your answer. 
> It worked out quite well so far. Only two things are strange. 
> The Python script gets started after the rendering and my commandline render result path gets ignored. 
> Any ideas how i can change this? 
> Seems that I maybee should start Blender in the background and let the python script do the other actions. 
Arguments are executed in the order given, so you could do, 
blender --background my.blend --python my.py --render-anim -- custom args 
But typically you wont want to render if the Python script has some 
exception mid-way, 
so you can call the render operator from the script: 
Heres an example rendering from a script & command line (uses blender 
as a batch image processor): 
Bf-committers mailing list 
Bf-committers at blender.org 

More information about the Bf-committers mailing list