Can someone please enlighten me on the new talkback functionality of the Hub4 in connection with the DB48? 
The "documentation" says that there should be a LED indication when "MIC-function" is used. So this leads to two questions: where should the light appear, and what does Mic-function use mean? When the MIC button of one of the connected DP48s is pressed and held, or only when it's pressed?

Although I am a technician, I'm not sure if I read the routing sheet well: Where does the talkback signal go? Only to other connected DP48s (as channel 48 overwriting the channel 16 of P16) or also to the desk?

Thanks in advance

Andy from Austria

Hello,

I've posted previously about having an issue with seeing the channel names broadcasted to the DP48 while using an SD8 with the Behringer X32 Compact. The community has helped with understanding the AES50 A & B streams. However, I still need help from the community to answer this question.

Should the DP48 see the broadcasted channel names when connected to an SD series digital snake or should I be using the S or DL series digital snakes?

What I've experienced is that the DP48 does not see the broadcasted channel name but does get the same channel setup and audio from the AES50 A side the snake box is setup on. When the DP48 is directly connected to a separate AES50 port on the mixer and NOT through the SD snake box, all the channel names are received including real-time name changes.  I've experienced this on the X32 Compact and WING mixers using the SD8 and SD16 stage boxes. 

Tribal help is greatly appreciated.

I have connected my new P16-M via the Ethernet-Cable to one of the four ULTRANTE-Ports on the SD16 Stagebox. The P16-M worked fine (PoE) an I was able to here "something". When I tried to change the routing in the X-32  int P16  (or now utlranet) Side  nothing happen/changed.    I resettet the P16-M , but same Problem.  The I wired it directly to the X-32 (I had to use the wallplug of the P16-M becuase there was no PoE on the UTLRANET-Port of the X-32) everything works well.   Has anybody the same Problem?  Did I something wrong in the routing of the SD-16 ?   

Thanks for any ideas. 

Uli

On my old Behringer P16Ms, I could assign signals from channels post EQ. With the DP48, when I'm assigning the channels using AES50, I am guessing I am tapping the raw signal from source probably after gain but pre effects. I figured I could still tap the 16 channels from Ultranet to get post-eq settings. And it looks like I can tap another 8 via the Aux Out assign (assuming I don't need the physical/digital outs).

Does that mean I'm limited to tapping 24 channels post EQ? Or am I missing some optionality for routing signals post effects.

Thanks!   

Hello,

We have an SD8 connected to an X32 Compact on AES50A port and then the DP48 connected to the AES50B port of the SD8.  On v1.3 the X32 saw that the DP48 was connected and we were able to select the channels for group assignments plus receive audio. We updated to v1.5 to use the broadcast group assignment that we set up using the Library > AES50 setup screen.

SETUP:

• X32 COMPACT CONNECTED TO SD8 ON AES50A
• 1 DP48 CONNECTED TO SD8 AES50B PORT
• SD8 AES50A INPUT = 17-24 OUTPUT = 9-16 (15/16 are L/R)
• AES50 CONFIGURATION - AES B OUTPUT BANKS 
  • LOCAL 1-8; LOCAL 9-16
  • AES50A 17-24; AES50A 25-32
  • AUXIN 1-6/TB
  • P16 1-8

We have the following issues after updating to v1.5 WITH DP48 connected through the SD8.

1. The X32 does not see the DP48 connected to AES50B through the SD8. The X32 only sees the SD8 connected on AES50A

2. We can manually assign channels to groups, however, the DP48 does not see any audio from any channel

3. We cannot change the SETUP > REMOTE option from OFF to ON

When we connect the DP48 directly to the X32's AES50B port all the above issues do not occur.  We went through loading older versions into the DP48 from 1.5, 1.4, to 1.3 and the issue still persists. Each time the DP48 was reset and initialized. At this point our DP48 is bricked when connected to the AES50B port on the SD8. Connecting it directly to the AES50B port on the X32 defeats the purpose of the unit unless we purchase another 100FT CAT6 shielded ethercon cable.

NOTE: Prior to update we were able to receive audio on the DP48 when connected to the SD8. This included inputs on the SD8 as well as the X32 Compact.

Any idea why we are having this issue? Your help is appreciated.