please help. wing and p16

[TBAUDIODIRECTOR]

so i am currently using wing as foh connected to dl32 aes a.then i have x32 rack running p16s monitoring for band connected to dl32 aes b. i need to have a talk back mic in foh talking to the band but i need it to be connected to the back of the wings inputs and not the dl32. how would i go about routing that so that the band can hear me in their p16s

[pvannatto]

With the X32 Rack connected to the DL32 in AES50 B, you cannot get signals through the DL32 from the Wing. The console connected to the B port of the DL32 can only receive the 32 inputs of the DL32. The better way to set up the interconnectivity mapping is to put the X32 Rack in between the Wing and the DL32. That will mean that you will need to do some routing pass-through (on the X32 Rack Routing, AES50 screen) with regards to the Wing and DL32.

[GaryH]

@pvannatto I’m pretty sure you actually can send signals thru the DL32 A from the Wing using its AES50A 33-48 ch’s. The DL32 allows aes50 33-48 to pass straight through it to a connected device. Since the X32 is connected to and running all the P16's in this case anyway, the Wings aes50 33-48 could be used for other things like a talkback ch could it not? Would probably use one User bank for the X32 inputs so as not to burn a full 8 ch's to get the single ch of talkback?

[TBAUDIODIRECTOR]

With the X32 Rack connected to the DL32 in AES50 B, you cannot get signals through the DL32 from the Wing. The console connected to the B port of the DL32 can only receive the 32 inputs of the DL32. The better way to set up the interconnectivity mapping is to put the X32 Rack in between the Wing and the DL32. That will mean that you will need to do some routing pass-through (on the X32 Rack Routing, AES50 screen) with regards to the Wing and DL32.

would it be better if i connected p16s to DL32 and just sent stuff to p16s through wings aes a outs? i really need that talkback from foh to work

[TBAUDIODIRECTOR]

@pvannatto I’m pretty sure you actually can send signals thru the DL32 A from the Wing using its AES50A 33-48 ch’s. The DL32 allows aes50 33-48 to pass straight through it to a connected device. Since the X32 is connected to and running all the P16's in this case anyway, the Wings aes50 33-48 could be used for other things like a talkback ch could it not? Would probably use one User bank for the X32 inputs so as not to burn a full 8 ch's to get the single ch of talkback?

so on the x32 racks routing page what would i have to change so the x32 will receive the local in of the wing?

[GaryH]

@TBAUDIODIRECTOR

“So on the x32 racks routing page what would i have to change so the x32 will receive the local in of the wing?”

It would depend on how many other ch’s need to be used from the Wing itself and elsewhere. If only the one local ch for a talkback mic it would be fairly easy. This assuming that you are connected as you first said. The DL32 in the middle. I would then maybe create a user bank from the X32 routing and probably assign it to x32 local inputs 25-32. Make the first 7 ch’s of that user input bank be aes50a 25-31, the last ch, aes50a 33. If you assign, in Wing routing, the talkback mic to aes50a out ch 33. You should end up with Wing talkback on x32 ch 32. The first 31 ch’s should still be from the DL32. That said you could let the Wing just assign all the P16 ch’s which would be done from the Wing routing aes50a 33-48 and connect your P16m’s to the DL32 ultranet port instead of the X32. You could put the talkback any ch you wanted and avoid X32 routing. Not sure what else the X32 is doing in your scenario.

[TBAUDIODIRECTOR]

@TBAUDIODIRECTOR

“So on the x32 racks routing page what would i have to change so the x32 will receive the local in of the wing?”

It would depend on how many other ch’s need to be used from the Wing itself and elsewhere. If only the one local ch for a talkback mic it would be fairly easy. This assuming that you are connected as you first said. The DL32 in the middle. I would then maybe create a user bank from the X32 routing and probably assign it to x32 local inputs 25-32. Make the first 7 ch’s of that user input bank be aes50a 25-31, the last ch, aes50a 33. If you assign, in Wing routing, the talkback mic to aes50a out ch 33. You should end up with Wing talkback on x32 ch 32. The first 31 ch’s should still be from the DL32. That said you could let the Wing just assign all the P16 ch’s which would be done from the Wing routing aes50a 33-48 and connect your P16m’s to the DL32 ultranet port instead of the X32. You could put the talkback any ch you wanted and avoid X32 routing. Not sure what else the X32 is doing in your scenario.

figured it out! so i ended up using local in for talkback on wing routed it from within wing to aes a out 16 which would be dl32s out 16. grabbed an xlr connected it to out 16 and into aux in 6 from x32 rack. had to do that because our wing is all the way up stairs in tech booth so running a cable directly up there is kind of difficult