faq on worker not finding blender #104225

Closed
MichaelC wants to merge 12 commits from michael-2/flamenco:faq_wrn_blender_not_found into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

View File

@ -61,6 +61,32 @@ file][workercfg].
[workercfg]: {{< ref "usage/worker-configuration" >}} [workercfg]: {{< ref "usage/worker-configuration" >}}
## My Worker cannot find Blender, what do I do?
When installing and starting the Flamenco Worker you may see a warning in the logs that says
the Worker cannot find Blender.
Example Flamenco Worker <=v3.2 log message...
```
WRN Blender could not be found, Flamenco Manager will have to supply a full path
```
There are two ways to resolve this problem:
1. Blender be installed in [platform dependent paths][blenderpaths] using the Blender installer or

There is no concept of a "well known location" in Flamenco. On Windows it finds Blender via the association of the .blend file extension with an executable. Would you know of a concise way to explain this to people who may not even know what a "file association" is?

The $PATH is correct.

There is no concept of a "well known location" in Flamenco. On Windows it finds Blender via the association of the `.blend` file extension with an executable. Would you know of a concise way to explain this to people who may not even know what a "file association" is? The `$PATH` is correct.

So I used the phrase "well known location" to head off custom locations or using NFS/NAS mount and what I meant was platform-dependent-paths: https://docs.blender.org/manual/en/latest/advanced/blender_directory_layout.html#platform-dependent-paths.

I did think about describing in more detail how Flamenco searches for Blender but as you point out some end users may not know or should necessarily need to know this level of detail.

So I used the phrase "well known location" to head off custom locations or using NFS/NAS mount and what I meant was platform-dependent-paths: https://docs.blender.org/manual/en/latest/advanced/blender_directory_layout.html#platform-dependent-paths. I did think about describing in more detail how Flamenco searches for Blender but as you point out some end users may not know or should necessarily need to know this level of detail.
available in the environment $PATH.
2. Use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS).

This might be a clearer way to phrase this:

Use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS).
This might be a clearer way to phrase this: ```markdown Use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS). ```

I included this phrase in my latest update.

I included this phrase in my latest update.
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" >}}
[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?