How to use StoryLiner in production

StoryLiner was designed by the production, for the production. It can be used from the scale of a simple scene to the one of a feature film, splited in many files.

Project settings

For large-scale productions it is important that each instance of StoryLiner, in every scene of every file, use the same settings, that those settings cannot be modified by mistake by a user and that they all come from the same source so that any change is propataged all over the production easily.

To do so StoryLiner has a notion of “Project”, in other words a set of settings covering the shot naming conventions, output resolution, file formats… All that can be also set by a production tool when a scene is opened for example.

See Project Settings to configure and enable the Project Settings.

Launching Blender in a context of project

When working on a project, it is mandatory to ensure that all the artists work in the same context: they all have to create images that have the same resolution, use the same file formats, same naming conventions…

The harmonization of the artists configuration will be provided by the use of a referenced Project Settings file. But to be sure that the Project Settings configuration is well applied in every Blender file of the project and in each one of the scenes they contain, the artists must use a Blender that is contexualized to the project.

See Project Context to create a shortcut for Blender that will automatically apply the Project Settings to every new file and scene of the project.

When Blender uses a Project Context, the name of your project will be displayed in the main toolbar of Blender.

API

StoryLiner also has its own API. This would allow you to integrate it into your pipeline, or to pilot it from another add-on, by calling functions that will not change even if the architecture of the add-on is modified for whatever reason.