Requires that the file is configured for rendering to Matroska video
files.
Audio is only extracted when there is an audio codec configured. This is
a bit arbitrary, but it's at least a way to tell whether the artist is
considering that there is audio of any relevance in the current blend
file.
This introduces version 2 of that file.
Version 1:
- Only the job doc was saved, with 'missing_files' added inside it.
Version 2:
- '_meta' key was added to indicate version.
- 'job' is saved in a 'job' key, 'misssing_files' still top-level key.
- 'exclusion_filter', 'project_settings', and
'flamenco_manager_settings' keys were added.
These are all needed to use FFmpeg on the worker to render a video from
rendered image sequences.
- fps: float, the scene FPS
- images_or_video: either 'images' or 'video', depending on what's being
output by Blender. We don't support using FFmpeg to join chunked videos
yet.
- output_file_extension: string like '.png' or '.exr', only set when
outputting images (since doing this for video requires a lookup table and
isn't even being used at the moment).
The problem was that there was too much storing done in an on-change
handler, causing things to be overwritten. By splitting up some functionality
and properly marking the "we're now loading" bits of code, its' solved.
Previously it would be saved in the same directory as the blend file, which
may be deeply nested in a directory structure. Now it's saved at the top
of the BAT pack.
This stores project-specific settings, such as filesystem paths, for each
project, and restores those settings when the project is selected again.
Does not touch settings that haven't been set for the newly selected
project.
Blender 2.78c is shipped with a version of the io_blend_utils module that
doesn't have a `pythonpath()` function yet, and that's bundled with an
older version of BAM. To work around this, we ship BAM as wheel, and detect
whether this version is needed to run.
As an added bonus, Blender 2.78c can now also use the file exclude filter
for Flamenco. The `bam_supports_exclude_option()` function is thus no
longer necessary.
Blender would report that the blend file wasn't in the project path, even
though it was. This was caused by resolving symlinks in the project path,
but not in the blendfile path.
A filter like "*.abc;*.mkv;*.mov" can be used to prevent certain files
from being copied to the job storage directory. Requires a Blender that is
bundled with BAM 1.1.7 or newer.
Attract and Flamenco features are (de)activated based on the extensions
enabled on the selected project. As a result, anyone can use the add-on
again, without seeing Attract or Flamenco things they can't use.