FAQ for when worker cannot find Blender executable #104232
@ -66,27 +66,13 @@ file][workercfg].
|
|||||||
When installing and starting the Flamenco Worker you may see a warning in the logs that says
|
When installing and starting the Flamenco Worker you may see a warning in the logs that says
|
||||||
the Worker cannot find Blender.
|
the Worker cannot find Blender.
|
||||||
|
|
||||||
Example Flamenco Worker <=v3.2 log message...
|
|
||||||
|
|
||||||
```
|
```
|
||||||
michael-2 marked this conversation as resolved
|
|||||||
WRN Blender could not be found, Flamenco Manager will have to supply a full path
|
WRN Blender could not be found. Flamenco Manager will have to supply the full path to Blender when Tasks are sent to this Worker. For more help see https://flamenco.blender.org/usage/variables/blender/
|
||||||
```
|
```
|
||||||
|
|
||||||
There are two ways to resolve this problem:
|
If Flamenco cannot locate Blender on the system it is possible to use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS). The Flamenco Worker will still show the same WRN message on startup when you use the two-way `blender` variable. The path specified by the `blender` variable is sent with the render job is enqueued.
|
||||||
Sybren A. Stüvel
commented
Please use the Oxford comma.
I think this can be reworded for more clarity, something like this: This path to Blender is then sent to the Worker for each render task. Note that the Worker will still show the warning at startup, as it cannot find Blender by itself; this is fine, because you now have configured the Manager to provide this path. > Windows, Linux or MacOS
Please use the Oxford comma.
> The Flamenco Worker will still show the same WRN message on startup when you use the two-way `blender` variable. The path specified by the `blender` variable is sent with the render job is enqueued.
I think this can be reworded for more clarity, something like this:
This path to Blender is then sent to the Worker for each render task. Note that the Worker will still show the warning at startup, as it cannot find Blender by itself; this is fine, because you now have configured the Manager to provide this path.
|
|||||||
|
|
||||||
1. Blender be installed in [platform dependent paths][blenderpaths] using the Blender installer or
|
|
||||||
available in the environment $PATH.
|
|
||||||
|
|
||||||
2. Use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS).
|
|
||||||
|
|
||||||
For option (1), Flamenco will attempt to locate Blender by examining the system.
|
|
||||||
|
|
||||||
In option (2) the `blender` path for the Worker is sent when a Render Job Task is enqueued.
|
|
||||||
The Worker will still show a warning on startup and expect the Flamenco Manager to send the Blender
|
|
||||||
path to use.
|
|
||||||
|
|
||||||
[blendervar]: {{< ref "usage/variables/blender" >}}
|
[blendervar]: {{< ref "usage/variables/blender" >}}
|
||||||
michael-2 marked this conversation as resolved
Sybren A. Stüvel
commented
This can be written more positively. It's just a warning, not a "problem". Something like "There are two ways to address this" would be better. This can be written more positively. It's just a warning, not a "problem". Something like "There are two ways to address this" would be better.
|
|||||||
[blenderpath]: https://docs.blender.org/manual/en/latest/advanced/blender_directory_layout.html#platform-dependent-paths
|
|
||||||
|
|
||||||
## Can I change the paths/names of the rendered files?
|
## Can I change the paths/names of the rendered files?
|
||||||
michael-2 marked this conversation as resolved
Outdated
Sybren A. Stüvel
commented
The linked documentation describes multiple paths, for example Furthermore it doesn't resolve this message at all, as Many non-technical users will also not understand "or available in the environment $PATH." The linked documentation describes multiple paths, for example `$HOME/.config/blender/3.6/`. I don't think it's a good idea to suggest that people start installing Blender in their configuration directory. It will certainly mess up as soon as they upgrade Blender and their config (and thus Blender itself) is copied from the old to the new version.
Furthermore it doesn't resolve this message at all, as `$HOME/.config/blender/3.6/` is not a path that the Worker will search for at startup.
Many non-technical users will also not understand "or available in the environment $PATH."
|
|||||||
|
|
||||||
|
I think this line can be removed, and the period in the sentence above can be turned into a colon:
IMO there is no need to specify which version of Flamenco is used. If you do want to be explicit, use something like "Flamenco Worker v3.2 would log:"