The page that decides what the rest of the program has. Every module you have installed is listed here with a switch.
What you see
Per module: its name, and whether it is on.
A module that is on brings its buttons, windows and designs into the interface. A module that is off removes them completely — not greyed out, gone.
That is the rule the whole program is built on, and this page is where you exercise it. Nothing here offers you a feature you do not have.
Switching one on or off
Set the switch. Some modules are ready immediately; others need a restart before their parts appear, and the program says so.
Switching one off does not delete anything. The module stays installed and its settings stay where they are; switch it on again and everything is as it was.
What it does affect is your rundowns. A list containing cues that a module provides — songs, name plates, presentation slides — loses the parts that module drew. The cues stay in the list; what they put on screen does not exist while the module is off.
When a module cannot start
Modules run in their own process, next to the program rather than inside it. If that process cannot start, you get a message that says which of the causes it is:
| Message | Usually means |
|---|---|
| Windows refused to start it | Antivirus, or a blocked file after copying |
| It is missing | An incomplete installation |
| It started but did not report in | The process is being held up — antivirus scanning it |
| It did not come up in time | A very slow machine or a very slow disk |
| The installation is half finished | Program and modules are from different versions — reinstall |
None of these stops the base program: the cue list, the outputs and everything in this documentation keep working. You lose what those modules provided.
Where the modules live
C:Program FilesUltimate PlayoutModules, together with a small file that
records which of them should be on. Which modules belong to your installation is decided at install time — see your licence key.
Updating them
Settings → Info → Check for module updates… reports which modules can be updated and installs them on request. The modules stop for a moment while that happens, so do it before a service rather than during one.