11. Notes (Composition Builder v.5.0)
Achieving Maximum Performance
In Composition Builder, there are almost no limitations regarding the number of layers, elements, and animations that can be incorporated in a single composition. Nevertheless, the data acquisition and rendering of graphic templates is always done in realtime.
While developing graphic templates, we recommend testing their performance in just:live or just:play regularly.
If there are too many layers with complex animations/elements, it is a good idea to reduce the complexity and distribute the graphic template playout to multiple Just Out engines. Only this can assure the best On Air performance and a healthy engine buffer status. For information about using multiple Just Out engines and the buffer status, please refer to the just:play/just:live user manuals.
We also recommend using still images (single or part of an image sequence) with the minimum pixel size possible and positioning them later in Composition Builder. Transparent pixels which are part of a still image have to be rendered, which can cost a substantial amount of power. Using fewer pixels can improve the render speed dramatically.
Relative Paths
Support for relative paths for XML, movies, and images has been added as of version 4.0 of Composition Builder. Additionally, there is a new “Make Paths Relative” item in the “File” menu that will automatically find and replace absolute paths with relative paths, assuming the file and the composition are both located on the same volume.
There is also a new “Embed Resources” item available in the “File” menu. This will automatically locate any XML, Video, and image files referenced within the composition, copy them into the composition file, and make the file paths relative to the composition file. This can obviously lead to much larger composition files, but makes copying much easier as only the composition file needs to be copied and not the associated resources.
Legacy Composition Optimization
In the “File” menu, there is a new “Upgrade Components” item. This performs additional optimisations on the underlying compositions saved by Composition Builder and played out in either just:live or just:play.