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

 

Parents
  • 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.

     

     

     

     

     

     

     

Reply
  • 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.

     

     

     

     

     

     

     

Children
No Data
Related