How are you!

I live in Suwon, South Korea, and am an office worker who is interested in sound equipment.

I had an idea for a wireless method during acoustic monitoring for a long time, so I sent it to AVIX & CUOSHOP the official Korean importer of Midas & Behringer, to propose and discuss it.

The wireless WIFI monitoring app development book and STAGE WAVE & other monitoring APP Guide materials are attached as additional materials through AVIX.
In the future if necessary, we will make it into a translated material and provide it.

Currently, I am in charge of circuit parts in JIG and equipment assembly and manufacturing at Samsung VD and a primary supplier (Na & Na).

In general, in relation to monitoring, it is a form of using one's own smartphone as a monitoring device from a wired method using

Behringer P16-M to a wireless network method using WIFI Router. Innovative products are being launched to support you.

We have analyzed STAGE WAVE App, which is currently the most emerging, and we would like to suggest a way to develop more advanced than

STAGE WAVE App by identifying the improvements in the network of that APP.

Advantages of STAGE WAVE: App compatibility / stability / Low latency possible (latency changes depending on the setting)

Cons: Requires high-performance Router and mid-range performance smart phone
Amount of high-power WIFI data / Monthly flat rate

Advantages of the New Behringer App (temporary name): Intermediate performance Router / Entry-level Smart Phone support available

Basic output WIFI data amount / Calculation of reasonable monthly fixed amount for users

Development and sales of PC-only and WIFI Router combined (small-scale) models

There are additional materials reviewed and analyzed to make this proposal, and ideas related to Line Up that will be upgraded in the future from

this proposal model are also being prepared.

Please review the contents first, and if you need interest or discussion about my proposal, please message & call.

thank you.

[email protected]

082-10-2780-1587

H.K.Oh (Hong Kyun Oh)

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?

Hello,

I have 6 DP48s and have 2 Hub4s being shipped as we speak.

My question, will I need 6 ethernet cables from the 2 Hub4s to each of the DP48s to power them (PoE) OR can you use 1 ethernet cable from the hub4 to the first one and then daisy chain them and get power to them without having to use the ac adapters?

Hi,

My only DP48 is directly connected to AES50B of my M32. No daisy chain, no HUB4.

In the M32 inputs routing, i selected AES50B 1-8 for the channels 1-8.

On M32 channels 1-4 and 7-8 there is no signal, on channels 5-6 I get the signal from the DP48 microphones.

When I switch on the DP48, after 2 seconds, there is a loud pop on channels 5-8, nothing on channel 1-4.

DP48 firmware is 2.2.

Question : Is the upstreaming only allowed in conjonction with HUB4, meaning that upstreaming without it is not supported and leads to the weird results i explained ?

Thank you for your support.

BR

Hello everyone

I am currently working on a WING based systems with DP48s and a HUB4. I'm trying to do the following:

WING-A <-> DP48-1 IN/DP48-1 through <-> HUB4 Master/HUB4 through <-> DL32-1 A/DL32-1 B <-> DL32-2 A

I have the follwoing questions regarding this setup:

1. As I understand it this should pass inputs 1 - 16 from DL32-2 to WING-A on AES50-A 33-48. However this is not the case. What does work is the HUB4 sending the talkback from the DP48s to WING-A on channel 48 (but only when taking DP48-1 out of the chain, as the 8 channels that unit inserts at the start of the AES50 stream replace 40-48 and therefore also the talkback). This is the only signal I am able to receive on the WING on AES50-A 33-48.

No routing options on the HUB4 are engaged. The outputs of AES50-A are routed to all DL32s as expected (1-16 duplicated on the XLR outputs of both stageboxes.)

When bypassing the HUB4 and daysichaining only the stageboxes on AES50-A everything works as expected; inputs 1-16 from DL32-2 are combined with inputs 1-32 from DL32-1 on the AES50 stream.

Am I doing something wrong or is this currently not supported?

2. Of course I also have DP48s connected to the hub:

WING-A <-> DP48-1 IN/DP48-1 through <-> HUB4 MASTER/HUB4 Port 1 <-> DP48-2 IN/DP48-2 through <-> DP48-3 IN

In this configuration DP48-1 can only remote control DP48-2 but not DP48-3. When daisychaining DP48s without the HUB4 in between, remote control works for all devices.

Am I doing something wrong or is this currently not supported?

3. I don't really need it in this scenario, but just out of curiosity: When daisychaining two DL32s is it possible to get OUT 1-16 on DL32-1 and OUT 17-32 on DL32-2 on their respective XLR outputs?

Obvioulsy this would all be fixed by running a second CAT cable on AES50-B, but I would very much like to avoid this if possible...

Thanks for your help!

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.

**Glad to report that the above issue has been resolved in DP48 FW v2.2!

Hi there! My name is Thanos and I'm a sound enginieer-designer and I'm using the midas DP48 personal monitor for three months now and I'm satisfied. The problem is that the musicians need the mute function sometimes because I'm changing the inputs from the midas DL32 stagebox or I'm changing the instruments. Everytime I warn them to turn off the master volume because the mute function does not exist. Is there something better than this??? Is it available a firmware update with the mute function???

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