Client Questions

1) Once the Master goes away, the Client ceases to be as well. It will show you "Waiting for Master", with a button labelled "Troubleshoot", to allow you to log into another Eos/Ion as client. Alternatively you can exit to the shell and log in as Master to take local control of the rig.

2) Ion can be booted up into "Master" mode, and it will then have control of as much of the rig as your Ion config allows. Any shows that have been saved to the client can be loaded and used - I think it will boot up with the last show it ran as Master.

3) If multiple consoles are in "Master" mode, then they will arbitrate for control using the priorities you've set for ETCNet2 and/or sACN.

• If both consoles have the same priority, then each DMX attribute will merge HTP - which gives odd results for moving lights, and even stranger ones for 16-bit!
• If one console has a greater priority than the other (Smaller numbers in ETCNet2, bigger number in sACN), the console with the lower priority will give up control to the console with greater priority.
• In ETCNet2 this is done on a per-DMX-attribute basis.
• Under sACN it depends on the receivers used.
  

When working with priorities, it's important to know about all the control systems on the network - for example, Unison usually has an ETCNet2 priority of 10, so setting your console to 9 will stamp on Unison for the patched DMX attributes.

4) Security settings are coming, although there is no definitive timeline for them yet.

1) Once the Master goes away, the Client ceases to be as well. It will show you "Waiting for Master", with a button labelled "Troubleshoot", to allow you to log into another Eos/Ion as client. Alternatively you can exit to the shell and log in as Master to take local control of the rig.

2) Ion can be booted up into "Master" mode, and it will then have control of as much of the rig as your Ion config allows. Any shows that have been saved to the client can be loaded and used - I think it will boot up with the last show it ran as Master.

3) If multiple consoles are in "Master" mode, then they will arbitrate for control using the priorities you've set for ETCNet2 and/or sACN.

• If both consoles have the same priority, then each DMX attribute will merge HTP - which gives odd results for moving lights, and even stranger ones for 16-bit!
• If one console has a greater priority than the other (Smaller numbers in ETCNet2, bigger number in sACN), the console with the lower priority will give up control to the console with greater priority.
• In ETCNet2 this is done on a per-DMX-attribute basis.
• Under sACN it depends on the receivers used.
  

When working with priorities, it's important to know about all the control systems on the network - for example, Unison usually has an ETCNet2 priority of 10, so setting your console to 9 will stamp on Unison for the patched DMX attributes.

4) Security settings are coming, although there is no definitive timeline for them yet.

Richard, thanks for the quick response!    

 Follow up question.  So, if I had an Ion backstage meant to be a client that I didn't want anyone unauthorized to mess with it, can I set up ACN priorities so that if anyone boots it into master mode (by mistake or design) it won't control anything in the rig?    Assuming that as a client it's not actually outputting edmx and so as a client prorities are not important?

Yes, you can do (sort of) that.

Priorities are set in the shell:

• At the Primary/Backup.Client etc menu screen, choose "Setup", then "Network".
• You can now set priorities for ACN and ETCNet2/EDMX.
• Remember that 200 is the most important for ACN, while 1 is the most important for ETCNet2.

I say "sort of", because the lowest-priority source does get control if nobody else wants it - so the Ion could have control of anything that's not patched in the Eos, or if the Eos is switched off.

When running as Client the Ion isn't outputting anything - it's simply a clever remote control for the Master console.

Something i read in a while back on an earlier post... If you set the client to  Partition 0 then it will have control over no chs.  I believe you will still be able to execute cues.

Cheers 

Hey Brent.  You are correct.  The playbacks are not partitioned.  So, anyone who has access to playback faders can execute cues, regardless of the channel partition in use on their device.  The main playback on each desk can be assigned a different number.  So, on my desk, the main can be fader 0 while your desk is defined with fader 1 on the main.  This allows both of us to use the main playback with different cue lists.

Thanks!

a