General information¶
Notice
If you have any questions, suggestions, or comments about this documentation, please send them via email to documentation.stream@qvest.com.
All texts, files and images in this documentation are protected by copyright. The content may not be copied for distribution, used for commercial purposes, or modified by third parties. The right to make changes and additions or to delete content is reserved only for Qvest Stream GmbH.
© 2024 Qvest Stream GmbH | All rights reserved | https://www.qvest.com
About this document¶
This user manual is intended for both new and advanced users of the Fusion software. It explains the underlying bricking concept, describes how Fusion Designer and Editor work, as well as common workflows when using Fusion.
About Fusion¶
Fusion is a so-called "bricking" software that serves as middleware between a newsroom computer system (NRCS) and a studio automation system (e.g. Viz Mosart). Bricks make complex technical workflows intuitively available to editors. They are executed by the studio automation system and should already be available during the planning stage for stories and shows. Fusion provides users with the Fusion Designer and Fusion Editor modules to manage bricks.
As a bricking solution, Fusion makes it easier for users to design stories in a technically correct way. Stories are no longer seen as a collection of control elements, but as a composition of video and audio content. Users know which visual and audio devices are available to them and what their capabilities are, but they do not need to know how to control or operate the devices.
This approach is instrumental in specifying information about the flow of a story in the NRCS and Fusion. As a result, users get a system that makes it easy to describe what and where something should be seen and heard during a show.
System architecture¶
Fusion is a vendor-independent middleware designed according to the principles of a service-oriented architecture. The system can be deployed across diverse platforms using appropriate technologies depending on the use case. This includes:
- On-prem/bare-metal (physical server)
- Virtualized (virtual machine)
- Cloud (hosted at a public or private cloud provider as a Kubernetes environment)
Fusion consists of the following main components:
- Fusion API (backend component for providing the main functions of Fusion)
- Fusion Database (backend component for storing the data managed by Fusion)
- Fusion Designer user interface (enables superusers to manage bricks)
- Fusion Editor user interface (enables editors to edit bricks directly from an NRCS)
Figure: Fusion system architecture
This user manual describes the Fusion Designer and Fusion Editor modules, which can be used to create and manage bricks and assign them to stories in the used NRCS.