6. Setup Variants (v2.0)
This chapter explains various setup variants. For detailed instructions on how to deploy just:live/just:play on a machine, refer to the next chapter → Software Installation.
- During the installation the folder Just Live or Just Play is copied into the Applications folder. This folder contains all required applications and links to all documents. You can remove applications which are not needed once the setup has been completed.
- All setup variants work for both – just:live and just:play. For the sake of simplicity only just:play is shown in the figures.
Advantage Of Using A Separate Machine For The User Interface(s)
just:out, just:connect and just:live/just:play can be installed on a single machine, but there are several advantages when using separate machines for the UI and the engine:
- The actual CPU/GPU load is distributed (load balancing).
- The engine cannot be affected by user mistakes.
- Using multiple machines allows for additional fail-over for the playout components. just:connect allows you to configure a slave engine for each layer (video or FX layers). This means another physical machine takes the place of a failing machine.
When using multiple just:live/just:play instances to control the same channel it is possible to work simultaneously on a channel on a first-come first-served basis. Separating the UI from the engine also allows the user working on the machine which runs the just:live/just:play UI to turn off the machine without interrupting the playout.
(Dis)advantage Of Using A Separate just:connect Per Channel
Although it is possible to manage several channels using a single just:connect instance, there are several advantages and disadvantages when using a separate just:connect for each channel:
| Advantages | Disadvantages |
|---|---|
|
|