Flamenco is Blender Institute's render management software. It has been used in productions such as the Caminandes series, Cosmos Laundromat and Agent 327 - Barbershop. Check out live site and docs on flamenco.io.
Fri, Jan 11
This is in the master branch now.
Thu, Jan 10
Implemented & deployed to production.
Also only use mapped network drives (so S:/ instead of rackstation/software), as means something else to Blender. That, and of course T60131 should be fixed.
Wed, Jan 9
I recommend not using any exclamation marks in your path, and only using mapped network drives (so S:/ instead of //rackstation/software). That, and of course T60131 should be fixed.
Tue, Jan 8
Please make sure that you have the latest Blender Cloud add-on 1.11.0 (just released) as it contains Windows and Blender 2.8 fixes. If you still see issues, please provide us with a proper bug report.
Mon, Jan 7
I wasn't thinking about encoding those as actual Tasks, but more as an extra payload in the same way we now also handle task cancellation requests. It would be just a list of job+task IDs to upload to the server. I'll have to think about it more to come up with a nice design that both works rapidly enough (when there are no workers asking for tasks, the Manager only infrequently polls that endpoint) and also doesn't load the server too much.
So this would be a parallel queue of "tasks" that are accessible from the "dpsgraph/dispatch" endpoint.
The main difference is that they would be performed directly by the manager?
Could this system be also used for uploading render previews to the server, or should that be part of the job definition?
We can have the Manager upload it to the Server on demand, for example by piggy-backing the 'depsgraph' endpoint the Manager uses to pull any changed tasks from the Server.
Fri, Jan 4
@Sybren A. Stüvel (sybren) I previously haven't had a chance to test this script properly. For now we are working with Backburner as our main render farm tool. We would like to use Flamenco though. But it is not very compatible with our Windows network. Everytime we try to work with Flamenco we run into strange issues.
Thu, Jan 3
Thu, Dec 20
Tue, Dec 18
Mon, Dec 17
Dec 14 2018
Implemented in 7680c65daf35712d8a9060c9fe0ccc8fd1716e06 and polished in following commits.
Dec 7 2018
Resolved in e2d9166473184
Dec 5 2018
Nov 29 2018
I tried last night with a render. I started Flamenco Manager using cmd.exe and with the - verbose command.
The manager didn't crash and worked perfectly all night long.
Nov 28 2018
I've tried running Flamenco Manager on Windows 10 for close to 7 hours, and it keeps running just fine. It has one Worker connected to it, so it does get frequent polls for more tasks.
Can you start Flamenco Manager from a cmd.exe terminal? That way it stays open and you can read any error message. Start it with flamenco-manager.exe -verbose to get more verbose logging. If it turns out that that still doesn't give enough information we can use flamenco-manager.exe -debug to enable debug logging, but this will produce a rather copious amount of log messages.