[In 11.7.1] setting up a backup laptop --> master/slave

[enigmatheatre]

I to would love to see a master/slave setup available for SCS. I think it is the only thing that I can not do with ease.

Greig.

[StasUshomirsky]

I would also like to add my vote for a Master/Slave setup.

I do want to emphasize that Mike has done a fantastic job developing a very stable application and he deserves major credit for making SCS very reliable for live shows. Knock on wood!
However, computers in general and Windows in particular are what they are... so crashes do happen. Therefore, I always run a primary and a backup computer. Switching between Primary and Backup computers is accomplished simply by cross-fading two DCA's on my audio console. (I prefer DCA's to mute groups, because I can transition to the backup system with a smooth fade and that makes the transition much less noticeable to the audience.)

Currently, I am keeping the primary and backup computers in sync completely manually. Our musicals are very heavily cued, and sometimes I just don't have enough hands to hit "Go" on the backup system! If I have to jump to a cue out of order, I try to jump on both computers -- again, hard to do... and sometimes when something goes wrong in the show, there is just not enough time! Manually keeping track of the backup computer is tough in a fast-paced show. So, indeed it would be incredibly helpful if one SCS instance could be configured as "Master" and another one as "Slave" and the two systems would stay in sync.

I did explore a variety of third-party utilities that mirror keystrokes or mouse movements across two computers. I am very wary of relying on such utilities in a live show environment... Any third-party utility is just adding another potential point of failure.

I don't think tracking mouse movements is important. The basic functionality needed during a live show is mirroring the "Go/Pause/Stop" commands, and mirroring which cue is loaded as "next". So, if the operator jumps to a different cue on the Master system, the Slave system would ideally jump to the same cue. This would cover 95% of use cases and provide a robust backup in case the Master computer has an issue. It is important that all cues are mirrored, regardless of how the cue is triggered: manually triggered, auto-follow, hot key, external midi control, etc... Basically, if the Master system starts playing a cue (regardless of how that cue was triggered), then the Slave system should start playing the same cue. If the Master system fades out a cue or stops a cue -- then the Slave system should do the same, regardless of how the fade out of stop was triggered.

Less commonly needed commands (and of much lower priority) would be things like mirroring manual level changes and manual fast-forwarding/rewinding actions during cue playback.

Thank you,
Stas

[StasUshomirsky]

Just wanted to check if there were any news regarding the "Backup system"? Thank you!

[Mike Daniell]

Not yet, although it is on the list of enhancements planned. I'm currently working on a number of changes for 11.4.0, particularly simplifying the 'device map' handling to make it much easier to transfer a production to another computer.

[Buyaicia]

"simplifying the 'device map' handling to make it much easier to transfer a production to another computer"

It will be a very helpful feature!!!!

[StasUshomirsky]

The basic functionality needed during a live show is mirroring the "Go/Pause/Stop" commands, and mirroring which cue is loaded as "next". So, if the operator jumps to a different cue on the Master system, the Slave system would ideally jump to the same cue. This would cover 95% of use cases and provide a robust backup in case the Master computer has an issue. It is important that all cues are mirrored, regardless of how the cue is triggered: manually triggered, auto-follow, hot key, external midi control, etc... Basically, if the Master system starts playing a cue (regardless of how that cue was triggered), then the Slave system should start playing the same cue. If the Master system fades out a cue or stops a cue -- then the Slave system should do the same, regardless of how the fade out of stop was triggered.

Less commonly needed commands (and of much lower priority) would be things like mirroring manual level changes and manual fast-forwarding/rewinding actions during cue playback.

Just wanted to ask if there are any news regarding the above?
Having a Backup SCS that tracks along with the Primary SCS would be extremely useful!

Thank you!

[Mike Daniell]

I'll see if I can get this done soon as there's quite a demand for this feature. With functionality already in place it's fairly easy to have a slave stay in sync with a master, at least with regard to major functions such as go, stop, etc. But it's a bit more complicated than that. It will be necessary to have one computer designated the master so this will send commands to the slave. But if the master goes down then the slave will initially be operated independently. If the 'master' computer is then rebooted and SCS reloaded, then the roles will be reversed, so the original 'slave' must now become a 'master' and send commands to it's 'slave', including whatever commands are necessary to bring the slave into sync with the master.

[2Gunz]

Hiya!

I just found this product and so far in testing its awesome and easy to use.

The one thing that Im very interested in is a redundant "hot" backup. We do a bunch of events where the Video machine taking a dive is simply NOT an option.

A simple go go go backup would be a great start. Even if a crashed machine wasnt able to rejoin the show, presumably crashes are very rare to begin with.

And I have a question.... is it possible to delay audio to fix lip sync issues?

Anyway, great work keep it up!

[StasUshomirsky]

I'll see if I can get this done soon as there's quite a demand for this feature. With functionality already in place it's fairly easy to have a slave stay in sync with a master, at least with regard to major functions such as go, stop, etc. But it's a bit more complicated than that. It will be necessary to have one computer designated the master so this will send commands to the slave. But if the master goes down then the slave will initially be operated independently. If the 'master' computer is then rebooted and SCS reloaded, then the roles will be reversed, so the original 'slave' must now become a 'master' and send commands to it's 'slave', including whatever commands are necessary to bring the slave into sync with the master.

These are excellent points Mike!

I would further add the following: The Master should be outputting all it's Network and Midi commands; while the Slave should NOT be outputting any Network and Midi commands. If the Master fails, and the Slave takes over, then the Slave should start outputting its Network and Midi commands.

Here is the setup at our theater:

• SCS Primary Computer
• SCS Backup Computer
• LightFactory Primary computer
• LightFactory Backup computer (warm spare -- DMX cable needs to be manually replugged)
• X32 Mixer
• (2) NEC Video Projectors [PJLink Control Protocol]

All of the above devices are networked together.

I use Control Send cues (network) to trigger light cues in LightFactory. If we were to have an SCS Master and SCS Slave, then only SCS Master should be talking to LightFactory. SCS Slave should NOT be talking to LightFactory and triggering each light cue twice. But if SCS Master crashes, then SCS Slave needs to begin sending Control Send cues to LightFactory! This somehow needs to be accomplished without restarting LightFactory. In other words, Network Connection to LightFactory needs to be active from both SCS Master and SCS Slave, BUT Slave network packets are "muted". If the Slave takes over, then network packets are "un-muted".

I also use Control Send cues (network) to control the the X32 Mixer. Same exact logic applies as with LightFactory: SCS Master is controlling X32, SCS Slave's network packets are "muted". If the Slave takes over, then network packets are "un-muted" and X32 is now getting it's commands from SCS Slave.

Is this doable?

[StasUshomirsky]

Hello Mike,

Just wanted to follow-up regarding the above discussion.

Having a Backup SCS that tracks along with the Primary SCS could really save some shows!

Thank you!

[StasUshomirsky]

Any news? Thank you in advance!

[Mike Daniell]

It's now 'on the drawing board'. I'm considering three scenarios for an SCS instance: 'stand-alone', 'master' and 'slave'. Communication between 'master' and 'slave' will be by a network connection. There could theoretically be multiple slaves.

[StasUshomirsky]

That's great to hear, thank you Mike!

Please consider several of my posts above, regarding the desired behavior of the Master/Slave setup.

Thank you!

[Buyaicia]

It will be very useful if the cue file used as master and cue file used as slave are identical.
I think it could be set in options and all triggers played on master computer should be sent to the slave(s) computer(s).

It will be easy to use in projects with audio files only, but could be difficult to have an slave computer with a second set of devices connected (dmx, midi, video...).

Regards,
Lluís

[Mike Daniell]

Please consider several of my posts above, regarding the desired behavior of the Master/Slave setup.

Noted, especially the comments that a 'slave' should not send network, MIDI, etc. IE, only 'stand-alone' or a 'master' mode should actually send anything from a control send cue or a lighting cue. Can anyone think of a scenario where a 'slave' should be able to send output from a control send or lighting cue?