Nope, deletion of those jobs is impossible for a reason. When the job is in that status, its tasks are being created by Flamenco Server, and nobody else should be touching the job.

I think it's need to have ability to remove jobs in 'under-construction' status, anyway, even if it will be fixed.

Implemented in ff9624d4f37ab035c27d1d5c59c654f88656ad49 (Blender Cloud add-on) and 5f96d2e50b852dcc1bd350dafc72dea67e02983e (Flamenco Server).

Implemented in 7bbbe3c (auto-delete offline workers) and c52c65d (allow auto-deletion in configurable status)

Committed in 4fe11d99f6a00a7fdb0ff2d4a85eacb37051db84

Yes it helps. Looks like i can launch it now.

Please try [Flamenco Manager 2.4-dev6](flamenco.io/download/flamenco-manager-2.4-dev6-linux.tar.gz). If you go to setup mode (./flamenco-manager -verbose -setup) and re-save your configuration, it should automagically remove the variable-name variable for you.

I can confirm the first issue; there is a regression bug in Flamenco Manager 2.3 that causes this duplicate variable.

There are two things wrong:

It now shows 5 KiB of 'head' and 10 KiB of 'tail', except when accessing the URL with WGet/Curl, in which case it downloads the entire log file. See log_server.go.

I was looking into something like this for the create-video task in the blender-render job compiler for the server. I want to be able to set the ffmpeg arguments that are being used to create the resulting video. As I was digging into this, I thought that using a variable override in the manager, similar to the path override for ffmpeg, could allow for at least making the output file an MP4 vs MKV. Is this barking up the wrong tree?

In e47780a63378e6aa664ba69566323a6396b798eb I changed the Manager so that soft-failed tasks are treated similarly to queued tasks. They are now retried by other workers as you'd expect.

'Normal' is fine, I'll look into it.

I'm guessing I can mart this as normal as this is a blender studio issue (?)

Alternatively offer JPEG2000 as only option (supports Alpha).

Implemented as the 2nd option (open blend file, create scene, fill VSE, render) in 3371e5d, b3c620b, and a bunch of commits on the Worker

Feel free to poke me on #flamenco on Blender Chat ;-)

@Sybren A. Stüvel (sybren) : still have to make myself familiar with flamenco [I will have to do this for an upcoming studio job...].
beauty of the rule-based thingie was [iirc], that you could add something easily without having to touch existing code.
So in the case of netrender I added something like "Priority-frames" [frames to be rendered first] without too much hassle. (I think the rules could even be mixed per job, but I would need to have a look again, this was ages ago...)

It's now implemented as a sub-quadratic curve (power of 1.6666) with an artist-given maximum number of samples per task. As an example, 400 total samples with a maximum of 100 per task gives these render tasks (first number is "rendering and merging up to this sample count", and second number is samples in only that task):

@Philipp Oeser (lichtwerk) thanks for thinking along with us :)

Output to JPEG would also be good enough (w.r.t. PNG).

not sure if this is still relevant: netrender had something like this based on rules, see https://developer.blender.org/diffusion/BA/browse/master/netrender/balancing.py

I tried again with double-clicking Flamenco Manager, and here it really doesn't crash. I'm archiving this now, because I can't reproduce the issue and thus can't find the root cause. If you have more information that can help, please comment here.

This is in the master branch now.

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.

I recommend not using any exclamation marks in your path. 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.

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.

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.

In T54099#593120, @Dennis Teusink (Teus) wrote:

@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.

@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.

Implemented in 7680c65daf35712d8a9060c9fe0ccc8fd1716e06 and polished in following commits.

Resolved in e2d9166473184