Sound Reinforcement - Forums for Live Sound Professionals - Your Displayed Name Must Be Your Real Full Name To Post In The Live Sound Forums > Wireless and Communications
Audio over IP - and Intercom over IP - here is a short recording
Neil White:
--- Quote from: Pete Erskine on September 15, 2015, 06:04:03 AM ---The backup audio is a dial in to a conference bridge which functions like a PL group. It feeds each site separately on a BU Director circuit. All sites continuously feed the BU dial up with the director channel. most of the sites in a segment just listen. If they have an issue they just switch tot the BU-DIR. If the site is presenting all sites must switch to hear them.
--- End quote ---
Are you using the Route Audio command and a local port looped back to switch between main and backup into the local Riedel conference?
Are the call to IFB triggered by the VOX on the 4W port of the matrix from the VCOM?
Pete Erskine:
--- Quote from: Neil White on September 15, 2015, 06:30:53 AM ---Are you using the Route Audio command and a local port looped back to switch between main and backup into the local Riedel conference?
Are the call to IFB triggered by the VOX on the 4W port of the matrix from the VCOM?
--- End quote ---
This has taken a lot of experimentation over the last several shows. Josh Flower and I have tried a lot of ways to make this switch. The problem is that you are connecting 2 different paths (VCOM and Telco) to the same conference and feedback is the result.
First we just unplugged the VCOM when we turned on the Telco but that was fraught with timing issues. This year we have created 2 separate conferences and stacked them on the dir keys.
This still didn't fix it. Josh came up with using two 4-wire ports looped through to the 2 conferences. The VCOM path is called to the 1st port on the DIR conference and the telco port is a route audio to the BU dir conference. I'll let you know if it works - all 6 of us are in the air now on the way to load in.
Incoming IFB is in the vox input from the VCOM. Local talk to IFB is regular call. Comms has a lsn to ifb input. all start at standard priority and if ducking is needed the input from VCOM is raised to duck local.
Side note: Often the POTs line is actually over the hotel internet and no actual pots line is available. In that case we're screwed. Because this worries me, I carry a Dapter-Two to create a 4-wire with my cell as ultimate BU.
brian maddox:
This thread gives me some interesting ideas.
One of my clients uses a ClearCom Eclipse Matrix system to interface remote locations with typically a central Master Control Room, be it a fixed facility or one that is built for the job. In fact the job i'm on right now is interfacing 4 remote locations via IP to a central MCR we built for the event in the main hall.
The Eclipse V-series panels provide complete functionality over IP which is super handy. With a public facing IP i can basically plop one down, give it some internet by whatever means is available, and it connects to the matrix as if it were right next to it. It also gives me two additional four wire ports that i can use to interface to local PL gear or to provide IFB or a host of other things.
One thing i Hadn't really thought about doing was using these paths as backup audio paths. i think the bandwidth is a little limited, but it's worth exploring.
ClearCom also has a iOS app solution that connects to the matrix using the same IP card. That also may make for some interesting problem solving ideas.
Thanks for the post Peter. You are always making us think.... :)
Neil White:
--- Quote from: Pete Erskine on September 15, 2015, 09:17:01 AM ---This has taken a lot of experimentation over the last several shows. Josh Flower and I have tried a lot of ways to make this switch. The problem is that you are connecting 2 different paths (VCOM and Telco) to the same conference and feedback is the result.
First we just unplugged the VCOM when we turned on the Telco but that was fraught with timing issues. This year we have created 2 separate conferences and stacked them on the dir keys.
This still didn't fix it. Josh came up with using two 4-wire ports looped through to the 2 conferences. The VCOM path is called to the 1st port on the DIR conference and the telco port is a route audio to the BU dir conference. I'll let you know if it works - all 6 of us are in the air now on the way to load in.
--- End quote ---
So with two separate 4 wire paths in the same conference, the feedback loop is caused by the remote sites mixing the 4W input from the VCOM with the local conference and transmitting it back down the POTS backup to the original matrix, and vice versa? With separate conferences for main or backup, is the feedback loop electronic or is it acoustically feeding back at the remote panels?
Would separating the talk and listens to the remote sites in a similar way to the Dual Complimentary Talk Only conference PDF on your site be enough to break the loop?
Pete Erskine:
--- Quote from: Neil White on September 16, 2015, 05:13:50 AM ---So with two separate 4 wire paths in the same conference, the feedback loop is caused by the remote sites mixing the 4W input from the VCOM with the local conference and transmitting it back down the POTS backup to the original matrix, and vice versa? With separate conferences for main or backup, is the feedback loop electronic or is it acoustically feeding back at the remote panels?
Would separating the talk and listens to the remote sites in a similar way to the Dual Complimentary Talk Only conference PDF on your site be enough to break the loop?
--- End quote ---
Its the combining of the two paths into a single conference that is the problem. A talk only conference leaves out the listen since the 4 wire is a passive port not a beltpack or a C3.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version