Ultimate Playout

DonateDownload 1.1.6

The installation in detail

What happens when you run the setup, in order. Part 1 covers the same ground for the person installing it once; this page is for whoever has to do it on twelve machines or explain it afterwards.

In order

  1. Asks for the language. The language of Windows is preselected; on a reinstall, the one chosen last time. The setup continues in it, and the program takes it over on its next start — see languages.
  2. Checks the machine. Is tar.exe missing — part of Windows since Windows 10 version 1803? Then it stops, with an explanation. Is an application built on the engine running — OBS Studio, or Ultimate Playout itself? It stops too: the two would write over each other’s configuration.
  3. Shows the terms of use. They have to be accepted before the setup goes on.
  4. Offers a desktop shortcut.
  5. Asks for the licence key, and with it, which modules belong to this account. Skipped when the key is already known — from the command line or built into the installer.
  6. Asks which modules to install, and which to switch on straight away.
  7. Shows a summary: the folder, the engine and the modules.
  8. Downloads the engine and installs it with the program. The engine (about 180 MB) and the modules from your account are fetched, the engine is unpacked, and its own updates are switched off — the program does not update itself; see the pinned engine. Already there in the right version? The download is skipped, and a second run takes seconds.
  9. Copies the program files, creates the launcher and the shortcuts, and grants write access to the configuration folder.
  10. Writes the chosen modules to the Modules folder, with which of them are switched on.
  11. Reports the installation to the website — only when a key was entered. That is what unlocks the pages reserved for installed customers. If it fails, the installation is still fine — you get a message and the setup does not fall over.

Unattended

For several machines:

UltimatePlayout_Setup.exe /VERYSILENT /KEY=UP-XXXX-XXXX-XXXX

In silent mode the module page is not shown and its defaults apply: everything installed, everything switched on.

If the download archive is already on the machine or on a share:

UltimatePlayout_Setup.exe /VERYSILENT /OBSZIP="D:deployobs.zip"

That skips the download, which on twelve machines is the difference between an afternoon and a coffee. It must be the official zip of the engine version shown on the summary page; another version is refused. A zip with its original name next to the setup is found without /OBSZIP.

The language goes with /LANG=: english, dutch, norwegian, german or

spanish. The program starts in it. Without /LANG=, a silent installation

over an existing one leaves the program’s language as it was.

What ends up where

C:Program FilesUltimate Playout
  UltimatePlayout.exe        <- the launcher
  Modules                   <- the chosen modules
  engineconfig             <- settings, scenes and logs (writable)

engineconfig is writable by everyone who logs in on the machine, so a

control-room PC with changing volunteers shares one setup. Where personal settings are expected, that is the thing to know about — see where the files live.

Uninstalling

Removes the program folder completely, including engineconfig and the modules — the uninstaller warns first. Rundowns and bundles in

DocumentsUltimate Playout stay.

Updating an existing installation

Running a newer setup over an existing installation replaces the program but leaves engineconfig alone: settings, scenes and designs survive.