We are currently using firmware v1.4 on our 4x DP48s. Can someone point me to a full revision history from v1.4 to the latest v2.0. I can only find revision history for v2.0. Is there a full user manual to go with this firmware? All I can find is the quickstart guide and that is for v1.3 of firmware.

Has anyone update to this firmware version and can vouch for it's stability/reliability?

I have a HoW installed M32R connected to a DL16 stagebox thru AES50-A.  How do I configure AES50-B on the DL16 to send to the daisy-chained DP48s used as IEMs on stage? Currently, the DP48s are connected directrly to the M32R on AES50-B on a CAT5 mess along the floor edge. If I could run the DP48s off the AES50-B from the DL16, I would be able to avoid running cable thru the ventilation system, crawl spaces, walls, and drop ceiling to get to the DL16 in the rack at FOH. Will the Hub4 do this or is there a more economical solution?

Hi,

I noticed i can only assign an aes channel once to a group. When assingning the same channel to a second group it dissapears from the first group.
This is logical but.

When i want to use the DP48 for  two musicians it could actually be helpfull to assign  the channels to 2  different groups.
Because then user 1 can use group 1 for (example) drums and adjust the individual channels to his own flavour. User 2 can use group 2 for drums and adjust the individual channels for his own flavour.

Is there a possibility to change this in future firmware?

Willem

Noticed this recently that when I switch off a DP48 with other units daisy chained to it, the downstream unit will produce a very loud pop sound in the headphones output even though the Volume knob has been fully lowered.

I noticed it because I could hear the pop from the headphones connected to another unit that was almost 2 meters away when I switched off 1 unit for firmware upgrade and testing.

Once again the volume level has been fully lowered on that downstream unit yet the pop sound came through so loudly and this happened consistently.

What will it do to a musician with in-ears when another musician upstream switches the unit off, by accident or for whatever other reason?!

Please fix this soon.

I'm wondering if anyone has used, or could comment, on using CAT5e or CAT6 unshielded cable for a DP48 daisy chain system.

I've already read the 'recommended shielded' information and don't need posts re-iterating the same.

This post is to solicit real world installations where end users may have used unshielded CAT cable and I'm interested in the results and learnings of doing that.

I have an existing CAT network from the M32 mixer to the rack and from the rack to stage boxes that is all unshielded CAT6.  I'm stongly leaning toward migrating to the DP48 personal monitor system.

I'm trying to figure out if I really need to replace all the CAT6 unshielded cable with shielded. Does unshielded really affect the performance of the system?

Hope you guys are well. I am having the weirdest issue with 1 of our DP48s. We are connecting them via HUB4.  For the most part, the system is work well.  We have 1-DP48 that is making a wierd digital noise.  It's only comes from 1 routed channel & that channel is not making that noise on the other 3 DP48 units.  Very strange.  Anyone else experience any weirdness like this?

I have a DP48 for my IEM and the other guys in the band are using P16's. I also have the S16 in aes50-a. So for that reason my DP48 is connected to aes50-b.

if I record a sound check the guys using the P16's can then adjust their personal mix without having to do any re-routing at the X32(rack). However, it seems that this can not be done for the DP48. As far as I am aware I would have to re-route to playback the soundcheck so I can adjust my IEM mix???? or am I mistaken, is there a way I can play back without having to re-route (and then having to re-route again to be able to use IEM for the actual live performance?

please email me as I will probably never find this discussion again. (The most confusing forum ever designed).

[email protected]

thanks.

There is currently no way to assign a name to the saved preset slots(FW v1.9), from a management point of view this is a problem as musicians may not remember which slot they saved their preset to and slots will get used up pretty quickly and things get messy when musicians end up overwriting another's preset slot.

Please do add in a feature to name the preset slots for easy identification, and to edit the name as well.