To clearly define the functional scope, the following section summarizes the main features provided by q.air.
The following graphic shows the basic workflow for using q.air:
Figure: Basic workflow
From a top-level perspective, q.air consists of the following functional areas:
- Schedule (Traffic/Planning)
- Playout (Automation)
- Ad triggering
The ingest functionality provided by q.air is focused on the file-based upload of video content. To upload files, the included q.air Asset Uploader application can be used. To be used properly by q.air, uploaded video files are automatically processed, which includes the creation of a thumbnail image, a low-res (proxy) video file and media information (technical metadata).
q.air includes a traffic component for strategic/operative as well as rough/daily planning. It enables using uploaded files to create shows, adding shows to playlists as well as adding graphics and other secondary events. A playlist can be added to a rundown in the q.air Automation to define the content the playout should actually play.
q.air uses the Singular.Live graphics platform for overlay graphics, that provides tools for composing, controlling and output of professional graphics. Each output generated by Singular.Live can be received by the q.air Automation and can be used as additional layer on top of the main video output.
The q.air Automation component is used to control one or more players running on playout instances, that are seamlessly playing video files from a playlist. In addition to file-based content, live segments (provided to the automation as web streams) can also be used as input source for the playout. The automation can be controlled either manually by the operator or scheduled/time-triggered via the planning component. The player output can be distributed to web, OTT and IPTV targets.