Hi Syrus_BD

I'd agree this sounds like the kind of way to go... I'm guessing that a Python based agent could automate the Poser API to open up each rsync'd scene file and submit it to the render queue?

The only other issue you've got though is how to communicate any alterations in render settings you might want to make on your local composer workstation, up to the cloud based and your automated Poser instance.

I'm guessing there'll be a way, using Poser's python API, to capture the render settings on the local workstation... as this is obviously used in some of the supplied scripts, for advanced rendering etc?

So you maybe want a python script, on the local workstation, to deal with saving your scene to the rsync folder, along with current render settings as a separate xml file (also to be rsync'd).

Then your Poser API automation script on the cloud controller instance would read in those render settings from the xml after it opens up the scene, and apply them to the current Poser session before submitting the job to your cloud based QM render farm.

There may be a more elegant way than this still, of course. But as I don't think render settings are stored in scene files at all (?) then I think a means of passing on these is also necessary...?

;-)