ETC Cobalt 10 - Multiconsole Sessions - Status (8.0); Multiconsole Sessions - Start and Join a Session (8.0)

Cobalt 8.1 - 20181029
230
Patch First!
Start by patching the whole system, with devices and everything. See Patch
. Basically you can
connect several clients directly after patching, to a Server, or Server/Backup system - and each user
can access the whole system in parallel with the other users.
Option: Define Partitions
You can define Partitions that can be activated for different users. The Partitions can be helpful to
avoid one user affecting channels of another user. Make sure you do this BEFORE activating
Partitions or User Logins other than the default ones. See Partitions
.
Option: Define Users
If necessary, define User Logins for different work stations. The User Logins may be of help when
different users try to access the Server - partly because there are personal settings, and partly because
Partitions can be set to default and automatically be activated when a specific User logs in. See User
Login.
Multiconsole Sessions - Status (8.0)
The number of connected consoles/devices are displayed in the lower right corner status indication of
screens.
Multiconsole Sessions - Start and Join a Session (8.0)
To start output from a console a Session has to be joined. There is a default Session in every system
and more can be created in System Settings. The first Console to join an Inactive Session makes it
Active and sets the Software Version. The first Console to load a play file in a Session sets the Play
file.
Starting a Session
The first console to Join an Inactive Session must start this Session.
1. The Software Version is set, and the Session status is now Active.
2. The user is asked which Play to load (Last, Play Archive or New).
Joining a Session
1. Select the Session you wish to Join. If the Software Version is not compatible, your are
warned and cannot join the session.
2. If the Sessionhas a password, your must enter it.
3. Your console then begins the process catching the Session .
• The most recent play file “sequence point” is downloaded from an existing Console.
• Changes are downloaded in the order they occurred and applied to this snapshot.
• The console catching up will adds ongoing changes to the end of the queue, to be processed
when it reaches them.