In order for Studio A to talk to Studio B:
Route Studio A's microphone into Talkback Return 2 in Studio B. (If Studio A is on a different engine, Studio A's talkback microphone must be on the network so it will appear as a source on Studio B's engine.
Turn on the talkback return in Studio B when the appropriate button is pressed. For Lone SHARCS dated November 2002 to June 2003, this is accomplished by turning on bus zero on Talkback Return 2. For Lone SHARCS after June 2003 or for SHARC Attack cards, this is accomplished by turning on Bus 3 on Monitor In. When the talkback return is engaged, the monitors will mute and the source routed to the talkback return is sent to the speakers. When the button is released, the bus is turned off and the monitors return to normal.
Audio Too High / Audio Too Low Alarm
Keeping track of your Profanity Delay's Status
Building Intercoms with The Audio Engine
Using a Beta Brite Message Board with the Logitek Audio Engine
Mix Minus, It’s Not Just for Codecs Anymore
Router 101 (Acrobat PDF file)
By default, the talkback is NOT routed to the headphones. In order to insert the talkback into the headphones, bus 3 must be turned "on" on Headphones In. (This may be enabled at engine startup by using the Command Library, contact support for help. This can also be enabled at Supervisor startup using an init trigger; an example follows.)
By default, the talkback is NOT routed to the guest headphones output (Phones PF Out). In order to insert the talkback into the headphones, bus 2 must be turned "on" on Guest Headphones In. (This may be enabled at engine startup by using the Command Library, contact support for help. This can also be enabled at Supervisor startup using an init trigger; an example follows.)
To enable headphone insertion at supervisor startup add commands (the lines that follow the trigger line) like the ones in this example to your existing init trigger, reflecting your engine and port numbers. If your trigger table does not have an init trigger, create a new trigger by using the entire example.
trigger init
cmd ae1 d[Port1 Headphones In] bus 2 on
cmd ae1 d[Port2 Headphones In] bus 2 on
cmd ae2 d[Port1 Headphones In] bus 2 on
The sources and destinations in s[source] and d[destination] brackets may be found in your system by typing <alt> <D> in Command Builder. You must have already typed on that line the desired engine number for Command Builder to pull up the correct list. If the list is empty, go to System Page in Command Builder and click the Browse button next to the Network File line to find your .nco (Network Control File). For more information on this process, see the Command Builder 2002 manual.
In all triggers, text after the tilde (~) is comments that Command Builder will ignore.
In the studio that is originating the intercom, we will turn bus 5 on the monitors on and off to dim the monitors in that studio. This will let the person talking to the other room know that he/she has activated the intercom.
Example trigger 1: Port 1 surface 1 talks to Port 1 Surface 2 (ON)
[11/02 - 6/03 Lone SHARC version]
trigger ae1 surface1 bridgebutton1 on
cmd ae1 surface2 bridgelamp1 on ~ turn on the lamp on surf 2
cmd ae1 route s[Studio A Mic 1] to d[Port2 Talkback Rtn 2]
cmd ae1 d[Port2 Talkback Rtn 2] bus0 on ~ Talkback In ON
cmd ae1 d[Port1 Monitor In] bus5 on ~ dims monitors in originating studio
[6/03 - current Lone SHARC and all SHARC Attack version]
trigger ae1 surface1 bridgebutton1 on
cmd ae1 surface2 bridgelamp1 on ~ turn on the lamp on surf 2
cmd ae1 route s[Studio A Mic 1] to d[Port2 Talkback Rtn 2]
cmd ae1 d[Port1 Monitor In] bus3 on ~ Talkback In ON
cmd ae1 d[Port1 Monitor In] bus5 on ~ dims monitors in originating studio
Example trigger 2: Port 1 surface 1 talks to Port 1 Surface 2 (OFF)
[11/02 - 6/03 Lone SHARC version]
trigger ae1 surface1 bridgebutton1 off
cmd ae1 surface2 bridgelamp1 off ~ turn off the lamp on surf 2
cmd ae1 d[Port2 Talkback Rtn 2] bus0 off ~ Talkback In OFF
cmd ae1 d[Port1 Monitor In] bus5 off ~ undims monitors in originating studio
[6/03 - current Lone SHARC and all SHARC Attack version]
trigger ae1 surface1 bridgebutton1 off
cmd ae1 surface2 bridgelamp1 off ~ turn off the lamp on surf 2
cmd ae1 d[Port1 Monitor In] bus3 off ~ Talkback In OFF
cmd ae1 d[Port1 Monitor In] bus5 off ~ undims monitors in originating studio
If you have any questions on how to adapt these examples to your station or if you'd like us to look over your trigger table, contact support or ask questions on our Tech forum.
_________________
John Davis
Logitek Electronic Systems, Inc.
Post your suggestions to the Logitek Tech Forum!