Frequently Asked Questions
This is a list of frequently asked questions, with their answers. It’s by no means an exhaustive list.
Yes, absolutely. To support multiple platforms, first configure your Manager for its own platform (so if you run that on Linux, use Linux paths). Then you can use Two-way Variables to translate those paths to the other platforms.
First check the Manager output on the terminal, to see if it shows any messages about “auto-discovery” or “UPnP/SSDP”. Most of the time it’s actually Spotify getting in the way, so make sure to close that before you start the Manager.
If that doesn’t help, you’ll have to tell the Worker where it can find the
Manager. This can be done on the commandline, by running it like
flamenco-worker -manager http://192.168.0.1:8080/ (adjust the address to your
situation) or more permanently by editing the worker configuration
Where Flamenco places the rendered files is determined by the job type. You can create your own custom job type to change this. With that, you can even add your own custom job settings like a sequence identifier and use that to determine the location of rendered files.
This is possible with Flamenco, but it takes a bit of work. It’s not managed by Flamenco’s default job types. You can create your own custom job type for this, though. With that, you have control over the arguments that get used before and/or after the filename on the CLI.
If you have this working, please share your job compiler script with us!
Flamenco assumes that once a file has been written by one worker, it is immediately available to any other worker, like what you’d get with a NAS. Similarly, it assumes that when a job has been submitted, it can be worked on immediately.
Such assumptions no longer hold true when using an asynchronous service like SyncThing, Dropbox, etc.
Note that this is not just about the initally submitted files. Also the rendering of a preview video from individual images assumes that those images are immediately accessible after they’ve been rendered.
It might be possible to create a complex custom job type for this, but that’s all untested. The hardest part is to know when all necessary files have arrived on a specific worker, without waiting for all syncing to be completed (as someone may have just submitted another job).
This means that you have to click on the little “Refresh” icon next to the job type:
It means that the program (probably Blender) exited with an error status. Take a look at the task log, which you can access by going to the task in Flamenco’s web interface.
OpenCue is aimed at a different audience than Flamenco. OpenCue is a large and complex project, and relies on a lot of components (source), whereas Flamenco is made for simplicity and use in small studios or at home, running on your own hardware.