Stupid Auxiliary remote panels
- Login to post comments
So for a particular show we changed some of aux assignments to different outputs. Aux 10 use to go to a particular physical ouput but we changed it aux 17 to group our loop backs together. Everything was working fine until someone went to Aux 10 on an aux remote panel and attempted to route something in. To our amazement it changed Aux 17. Why I was amaxed is because Aux 17 was my primary loop back for a studio camera with an edging keyed over it for our 3way boxes. This source was punched to line and zoomed up to full frame and to my surpirse Camera one was replaced by EVS Echo. I quickly punched the camera up direct and it took several minutes for me to work out what happened.
It seems like the remotes work by finding out what cross points each of the auxilaries are when booted up and if a different aux is assigned to that crosspoint the remotes don't update unless they are power cycled.
My solution was going into the menu and disabling the remotes to only a select few auxilaries that they absolutely needed. However our TD (you would call them an EIC) complained that they couldn't route all of the outputs if they needed to.
- Login to post comments
Turns out the issue was my lack of understanding how the Aux Bus Control Panels work. Turns out that they are connected via S-Bus so the menu that disables them from routing the Aux Bux doesn't do anything for them. I learnt that you need to Export the Src and Destinations if you change them in registry, they don't auto update. So I have built a menu macro that takes care of it when I run the main show setup Shotbox.
To fix my Aux problem I have assigned the additional ME outputs directly to the phyical outputs so they don't get changed.