• Date
    DgrossIA52
  • Date
  • Replies 6 replies
  • Subscribers 186 subscribers
  • Views 8986 views
  • Users 0 members are here

Multi Ion users

Hey Guys,

I'm a relatively new ION user in NYC. I have extensive networking experience and I'm also a expression damily programer and a MA programer.  I'm doing a install for a pair of TV shows sharing one stage space with multiple sets and two Ion desks already working together on the network.  Right now we have our booth console set up as the primary console and the floor unit working as the client.  They have different ID numbers so that they can share dimmers and save files but different command lines, pages, and cue stacks.  we currently have 7 98 touring racks sensor+2's and 2 60A out sensor 2+ racks.  Data is being run NET3 to a common dimmer room and all racks are daisy chained into a 4 port ETC gateway. 

My question is, is there any way we can have two programers one on each desk working on the same network and writing cues and subs without interfering with the other? we've thought about writing in blind only using subs for each set as a work around.  If both consoles were setup as primary but with only one as the DHCP server could the work independently? Also would Partitioning work to solve this problem if we set up partitions for each of the 20 or so set spaces ? 

Thanks for the ideas

Cheers

Derek Gross

IA 52

 

  • not having the slightest idea about tv and studio, i think this is a text book case for partitions...

  • in reply to ueliriegg

    we played around with partitions are there more in depth settings for it than just what channels can be selected? It seemed that we could separate the channels out but we still couldn't record new cues without recording the channels of the other desk. 

    Derek

  • in reply to DgrossIA52

    Derek,

    In the theater world, we partition the channels between the two consoles, and then set up each console with its own cue list.  For example:

    User 1, Cuelist 1, Partition 21 (channels 1>300)

    User 2, Cuelist 2, Partition 22 (channels 301>600)

    This will keep playback, recording, and channel selection all totally separate.  You can map the main "Go" button on each console to the correct cue list in the Fader Configuration page.

     

    I hope that helps,

    ~Paul

  • in reply to DgrossIA52

    We have 2 Ions in 2 rooms sharing the same Sensor+ racks. Both Ions are configured as primary console and are patched to control only the dimmers allocated to them. To discourage a programmer from grabbing control of a dimmer they should not be controlling, the Sensor rack has been configured so dimmers for the main room accept input only from DMX-A and ACN. Dimmers for the secondary space accept input only on DMX-B and EDMX. It is still possible to reconfigure either Ion to grab the other room's dimmers but it has to be done deliberately.

    As an added wrinkle in the Sensor programming. The dimmers allocated to the main room are numbered 1-154 on DMX-A and ACN. The dimmers for the secondary space number 1-42 on DMX-B and EDMX.

  • DgrossIA52 said:

    My question is, is there any way we can have two programers one on each desk working on the same network and writing cues and subs without interfering with the other? 

    [

    Curious as to the reason behind 2 consoles.  Backup ?, separate gaffers ?.  

    A couple of useful replies here as to methods to partition channel, cue lists and playback control, and/or isolating the dimmers and keeping the consoles separate, noting that you don't setup 20 different partitions, just one per desk.  One question that I can't answer is how partitioning acts on fader wings with subs configured, if you use any. 

    The issue with channel partitions is that desk 1 will be channels 1 - 350 or so and desk 2 must be channels 351 thru XX.  The channels for desk 2 will be background visible only on desk 1 (with channel tombstones greyed out), but the only control would be thru the Park section (if memory serves), thus no action on cuing, ditto for desk 1.  In any case, each operator, and more importantly, the gaffer(s) need to remember that they can only call up channels for each system by the defined channels for that room/set partition.

    The advantage to NOT combining is that you can have your channels starting as 1 on each desk, which might make the thought process of calling up systems (rooms) easier.  Hard to recommend more without knowing the reasons behind the 2 desks.  

    The advantages to partitioning is the desks act as backups to each other, as the show file is saved on each desk.  You can also Master/Slave so one can take over in the event of a failure.

    The advantage of separate systems is it's easy to setup, (you would need a 2nd Cat5 run as well as 2nd Gateway, or just just run straight DMX and daisy all).  Not sure if you have a rack(s) that split,  That may make the system you have the only answer unless you have spare dimmers and can assign racks 1-4 to one console, rack 5 thru 7 to the 2nd.  

    Steve B.

     

     

     

     

     

     

     

  • You could very easily set up both desks as primary, and have individual show files, and both could control all of the dimmers on an HTP basis (most likely without having to change any settings since both consoles are networked to a NET3 gateway). If you want to limit what each desk can control, you can set the range of outputs available to each Ion in the shell, or establish per address priorities in the NET3 gateway.

    The downside to this setup is if Ion B needs the information stored on Ion A. If you truly need two independent systems using the same dimmers, you're probably ready to go.
Related

www.etcconnect.com