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

[Mike Daniell]

Topic now split for master/slave requirement

[tocsin]

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?

Yes sure! I use it that way.

1. Laptop Master - ShowCueSystem and Light by M-PC controlled via MSC
2. Laptop Slave - ShowCueSystem and Light by M-PC controlled via MSC

Please let it be flexible. No need to cut off control send functionality at the slave by default. Let the user choose.

Thanks
Tocsin

[Mike Daniell]

Thanks, Tocsin. Is your slave SCS effectively controlling a slave lighting controller or similar, meaning that both master and slave SCS instances need to send MPC?

[tocsin]

Thanks, Tocsin. Is your slave SCS effectively controlling a slave lighting controller or similar, meaning that both master and slave SCS instances need to send MPC?

Yes they both need to send MSC independendly. The Slave Laptop is doing the exact same as the master. SCS is doing sound/video and triggers the light via MSC and control send through loopMIDI at M-PC.

If the Master failes, i switch the sound on the audio console, the video with a KVM and the DMX is merged with Slave Laptop and a Lighting desk.

Thanks
Tocsin

[StasUshomirsky]

As we approach our biggest show of the year here at the Starbright Theater, I just wanted to check in regarding the master/slave functionality. Any news Mike? Thank you!

[Mike Daniell]

When is your 'biggest show of the year'?

[StasUshomirsky]

May 24-25

[Mike Daniell]

We've started work on the design for this, but have a terminology issue. There seems to be a certain amount of discomfort around the world regarding using the term 'master/slave' for computer connections. One alternative suggestion is 'primary/secondary', but to me it seems that 'master/slave' best describes the control flow. Any opinions or suggestions?

[jmgordon]

Concern seem to have been floating around for some time. Drupal has suggested Primary/Replica. As Master seems widely accepted as in Master Document, perhaps Master/Replica would be a compromise?

[StasUshomirsky]

My two SCS computers in the booth are actually called:
Primary / Backup

Can we go with that?

[Mike Daniell]

Thanks for the suggestions, Malcolm and Stas. I've decided to use the terms 'Primary' and 'Backup', or more specifically 'SCS Primary' and 'SCS Backup'.

[Buyaicia]

I'm late but I like the proposal of StasUshomirsky. Primary/Backup.