From what I’ve read, there can be pops heard whenever there’s a problem with loss of sync issues with interconnected equipment.
In a scenario that involves multiple SD16 and a device connected using MADI via the x-madi interface, the question then becomes how to know where the problem is actually arising as the cause.
Is there any sort of diagnostic capability available (or that can be created) that can monitor the ongoing operation of the mixer and help pinpoint the interface that sync or grounding is causing an issue with?
The popping does not happen consistently, which makes it difficult to identify what the cause is.
Any chance the OpenMixerProject could provide a view into what’s going on?
I’d think this ‘diagnostic avenue’ might be quite a useful set of tools for anyone having issues with their mixer, and perhaps detection of sync issues with external equipment could be one of many?
Is it possible something already exists? But can it be used/done while the mixer is also being used in a production?
I don’t have any answers, but I’m hoping someone here might!
The network plugs used for the AES50 connection has to have two metal plates on its side which interact with the AES50/Ethercon connector on the SD16 and X32/M32. These need to have good contact (this is what connects the metal chassis from the SD16 to the mixer). Without that connection different potentials can cause these dropouts or destroy your receiver/transmitter chip - that happend to some users.
Also don’t use regular network plugs, as these can move in the connector. I had these popping noises myself on a band weekend with a regular 30m network cable.
As soon as I changed the plugs to proper shielded(!) Ethercon connectors the cable was rock solid and stable.
Also note, that all the Behringer gear wants to be used with shielded CAT5 cable.
We can not speak for the original implementation of the AES50 in the X32 Family. We use the AES50 implementation from GitHub - YetAnotherElectronicsChannel/AES50: An IP-Core for AES50 protocol · GitHub .
Maybe @chris might know if we can implement some statistics or diagnostic tools in OpenX32 or OpenWING in the future. As far as I know YetAnotherElectronicsChannel (...) · GitHub and @chris had many problems debugging the AES50-connection on a hardware level.
Also all the gear involved should be up to date with its firmware. Some S16 stageboxes do not function on a Behringer WING without the latest firmware update on the S16.
