Multible programmers on the same show, at the same time

Yes.

:-)

The parts of the help system/user manual you should take a look at are Channel Partitions (Browser>Channels>Settings and Tools>Channel Partitions) and User List (Browser>General Settings>User List).

Please note that playbacks are global - so you'll need to have all your programmers agree on a working method together.

Thanks -

Sarah

The basic layout of this is that you have a network between the consoles that your programmers will use.

One of these consoles is designated the Server, the others are Clients.

Clients could be Windows PCs with a Client dongle, or physical Congo consoles (be they Full-size, Jr, Lightserver or RVI)

Clients are basically 'remote facepanels' that communicate over the network - they also work well over WiFi, but we don't recommend WiFi for timing-critical applications. It's good for focussing or remote displays using a laptop, but don't use WiFi to run the show!

However, more than being 'just' a facepanel or video display, each Client has its own set of tabs, commands/selection and displays, working back into this common Server, so multiple people can all work on different parts of the same showfile. One common task is that there is a 2nd programmer doing the 'cleanup' work in the Preset and Sequence lists while the main programmer gets on with the next scene.

In a fully-networked system without hard-line DMX at the back of any consoles, the Server can be any console as the EDMX/sACN etc just goes out on the network, but if you are using console physical DMX ports they must be the ones on the Server as the DMX ports on the back of the Clients do nothing.

There are a few things to bear in mind:

The Highlight key only works on the Server at present (this is a known bug that's fixed in v6), so you'll probably want to put the moving-light programmer on the Server.

As Sarah mentioned, all the consoles have the same Masters and Main Playback, so you'll need to agree on a methodology that works for your programming team.

When working, the Server is started first, then all the Clients log into it. You're then all working on the same showfile which is actually running on the Server - so if the Server is shut down, all the Clients will immediately exit. The Server can also 'lock out' any or all Clients if they want to.

The basic layout of this is that you have a network between the consoles that your programmers will use.

One of these consoles is designated the Server, the others are Clients.

Clients could be Windows PCs with a Client dongle, or physical Congo consoles (be they Full-size, Jr, Lightserver or RVI)

Clients are basically 'remote facepanels' that communicate over the network - they also work well over WiFi, but we don't recommend WiFi for timing-critical applications. It's good for focussing or remote displays using a laptop, but don't use WiFi to run the show!

However, more than being 'just' a facepanel or video display, each Client has its own set of tabs, commands/selection and displays, working back into this common Server, so multiple people can all work on different parts of the same showfile. One common task is that there is a 2nd programmer doing the 'cleanup' work in the Preset and Sequence lists while the main programmer gets on with the next scene.

In a fully-networked system without hard-line DMX at the back of any consoles, the Server can be any console as the EDMX/sACN etc just goes out on the network, but if you are using console physical DMX ports they must be the ones on the Server as the DMX ports on the back of the Clients do nothing.

There are a few things to bear in mind:

The Highlight key only works on the Server at present (this is a known bug that's fixed in v6), so you'll probably want to put the moving-light programmer on the Server.

As Sarah mentioned, all the consoles have the same Masters and Main Playback, so you'll need to agree on a methodology that works for your programming team.

When working, the Server is started first, then all the Clients log into it. You're then all working on the same showfile which is actually running on the Server - so if the Server is shut down, all the Clients will immediately exit. The Server can also 'lock out' any or all Clients if they want to.