π Glossary
The terms below appear throughout this wiki. Each one links to the page that covers it in full.
Calendar Defaultβ
The media a screen loops when it goes offline or stops receiving fresh content. Every device has its own, and you can replace it with your own image or video. See Calendar Default.
CMS Editorβ
The Voome web application, at cms.voome.com, where media, projects, schedules, and devices are managed. Unless a page says otherwise, the steps in this wiki are performed there.
Deviceβ
A screen or media player registered in your Voome network. Also called a player. Devices are listed in the Devices view, where each one carries a title, model, serial number, and network position.
Devices viewβ
The full control surface for your fleet, with search, filters, and per-device actions. It is aimed at advanced and IT users. See Devices.
Encodingβ
Converting video or audio into a format a screen or player can actually read, which also reduces file size and improves playback quality. See What is encoding?.
Folder Playlistβ
A layer that plays every item in a media library folder in rotation, instead of a hand-picked list. Adding or removing files from the folder updates what plays, with no edit to the project. See Folder Playlist.
Layerβ
A building block placed inside a project: an image, a clock, a weather widget, an RSS ticker, and so on. Layers are grouped by category in the project editor. See What is a Layer.
Mediaβ
The images and videos stored in your library, the raw material every project is built from. Step 1 of the workflow. See Media.
Monitoring viewβ
The simpler control room, showing each screen as a card with its status, latest snapshot, key timestamps, and any warnings. See Monitoring.
Network positionβ
Where a device sits in your network hierarchy of areas, branches, and zones. It is one of the fields you can search on in the Devices view.
Projectβ
A template filled with your media, text, and layers: the actual thing that appears on screen. Step 3 of the workflow. See Projects.
Publishβ
Sending scheduled content to the devices. A schedule only reaches a screen once it has been published, which is why a device can have content scheduled and still show nothing.
RPC and RTCβ
The two connection types an action can use. An RPC action (publish, get screenshot) is queued, moves from Requested to Executed after about a minute, and needs a refresh to check. An RTC action (fast publish) lands in Executed immediately. See Devices.
Scheduleβ
The sequence of projects assigned to a zone, rotating continuously until you change it. Step 4 of the workflow. See Schedule.
Snapshotβ
A screenshot of what a player is currently showing, sent roughly every 5 minutes and displayed on the device card in the Monitoring view. A snapshot older than 30 minutes raises a warning.
Templateβ
The layout that frames your content, defining the zones on screen where media and layers appear. Chosen from a ready-made catalog rather than built from scratch. Step 2 of the workflow. See Templates.
Third Party Credentials (TPC)β
The credentials that let Voome connect to an external service on your behalf, for example a Microsoft Entra tenant for calendars, rooms, and SharePoint content. See Third Party Credentials.
Zoneβ
A region of the screen defined by a template, and the unit a schedule is assigned to. One screen can carry several zones, each running its own sequence of projects.