Yes definitely. The aes50 protocol carries 48 channels in EACH direction - and it just stacks them in order of what the daisy chains is. So it's 1-16, 17-32 (From the two S16's), then 33-40 and 41-48 from the two DP48's
Thanks for the question! Yes the daisy chained dp48 can have its completely own mix and assigned mix groups! The cable carries all 48 channels being sent from the console (Wing or x/m32), and going through one DP48 does not change these 48 channels at ALL. Note that the RETURN channels to the console also is limited to 48 channels, and each DP48 will send 8 channels back to the console. (Mix A L/R, Mix B L/R, Aux input L/R, and onboard Mics L / R) Regarding power - if you want to power them via the network cable then you'll need to buy the Midas HUB4 and run a network cable to EACH DP48 individually. For us we didnt need the Hub4 (we use the S16 outputs) and so powering them each with the power adapter was the best option here. Let me know if you have other questions!
Not able to attach a drawing in comments :/. But I'll try to explain. The aes50 link is 48 channels in EACH direction (total 96). The dp48 receives 48 channels that are sent from the console (whether through stageboxes like these S16's or direct - no difference). Each dp48 then sends 8 channels BACK to the console - so in this case the inputs at the console are 1-16 (S16#1), 2-32 (S16#2), 33-40 (DP48#1), 41-48 (DP48#2). Since the S16's cannot take a "returning" signal (e.g. from the dp48 direct) and send that out of the analog outputs, in order to get the MixA and MixB signals from the DP48 to the S16 we must, at the console, send those returning MixA and B DP48 signals BACK out to the S16. In this case If we are using S16#1 outputs 1-8 for the IEM's we will route the returning MixA L/R and MixB L/R signals (At the console) as AES50 OUTPUTS. Effectively telling the AES inputs to go right back out as outputs - which the S16 will then output at it's analog XLR outs. I'll try to record another video to answer and diagram this!
The DP48 mix comes into the Wing at FOH via the AES cable. Each DP48 has 8 channels returned - so in my case I have 2x S16 (32 channels) and then 33/34 are MixA from the first DP48, and 35/36 are MixB from that same DP48. I then simply route those AES INPUT signals (AESA 33 and 34) back down the SAME AESA but via OUTPUTS to - for example AESA OUT 5/6, which I then grab those signals from the first S16 Outputs 5/6 to the IEM Tx. And if youre following then YES you are indeed sending the MixA "back" to the DP48, but I can afford to give up the first 8 of the 48 channels going to the DP48 for this use. And yes you would never select these inputs for use on the DP48 at all lol
Hi there! No I do not. For this setup we just powered them on their own, and daisy chained them off the S16's. We used the routing to send the mixes back to the S16 outputs to feed the rack IEM Tx
Can you access all channels from both s16s when you run aes from the Stagebox to the dp48?
Yes definitely. The aes50 protocol carries 48 channels in EACH direction - and it just stacks them in order of what the daisy chains is. So it's 1-16, 17-32 (From the two S16's), then 33-40 and 41-48 from the two DP48's
Can daisy chained DP48 have totally different mix for monitoring?
Does the cable used for daisy chain contains power?
Thanks for the question! Yes the daisy chained dp48 can have its completely own mix and assigned mix groups! The cable carries all 48 channels being sent from the console (Wing or x/m32), and going through one DP48 does not change these 48 channels at ALL. Note that the RETURN channels to the console also is limited to 48 channels, and each DP48 will send 8 channels back to the console. (Mix A L/R, Mix B L/R, Aux input L/R, and onboard Mics L / R)
Regarding power - if you want to power them via the network cable then you'll need to buy the Midas HUB4 and run a network cable to EACH DP48 individually. For us we didnt need the Hub4 (we use the S16 outputs) and so powering them each with the power adapter was the best option here. Let me know if you have other questions!
I did not understand how The signal comes Back and The outputs Used for in-ear. Can you explain further? Maybe a drawing?
Not able to attach a drawing in comments :/. But I'll try to explain. The aes50 link is 48 channels in EACH direction (total 96). The dp48 receives 48 channels that are sent from the console (whether through stageboxes like these S16's or direct - no difference). Each dp48 then sends 8 channels BACK to the console - so in this case the inputs at the console are 1-16 (S16#1), 2-32 (S16#2), 33-40 (DP48#1), 41-48 (DP48#2). Since the S16's cannot take a "returning" signal (e.g. from the dp48 direct) and send that out of the analog outputs, in order to get the MixA and MixB signals from the DP48 to the S16 we must, at the console, send those returning MixA and B DP48 signals BACK out to the S16. In this case If we are using S16#1 outputs 1-8 for the IEM's we will route the returning MixA L/R and MixB L/R signals (At the console) as AES50 OUTPUTS. Effectively telling the AES inputs to go right back out as outputs - which the S16 will then output at it's analog XLR outs. I'll try to record another video to answer and diagram this!
How do you route the dp48 mix back the stagebox
The DP48 mix comes into the Wing at FOH via the AES cable. Each DP48 has 8 channels returned - so in my case I have 2x S16 (32 channels) and then 33/34 are MixA from the first DP48, and 35/36 are MixB from that same DP48. I then simply route those AES INPUT signals (AESA 33 and 34) back down the SAME AESA but via OUTPUTS to - for example AESA OUT 5/6, which I then grab those signals from the first S16 Outputs 5/6 to the IEM Tx. And if youre following then YES you are indeed sending the MixA "back" to the DP48, but I can afford to give up the first 8 of the 48 channels going to the DP48 for this use. And yes you would never select these inputs for use on the DP48 at all lol
Hi. Do you also have the Hub4?
Hi there! No I do not. For this setup we just powered them on their own, and daisy chained them off the S16's. We used the routing to send the mixes back to the S16 outputs to feed the rack IEM Tx
@@huktek thanks for your reply. Thats my plan as well. They make it seem like you need the hub4 to route back down the aes line. Thanks again.