Midas DL32

Clock/link status comes before patch troubleshooting.

1. Read sync at both ends; compare supported rate, clock plan and documented port/cable. Do not assume both ends should follow each other.
2. In rehearsal, compare one known-good approved cable/path. Verify stable sync then audio; if still failing, record states/versions for service without opening hardware.

If both ends lack a stable link, changing buses does not resolve that status. Once sync holds but an output is missing, follow the return map; record which condition changed before attributing it to hardware failure.

The rack outlet has a specific receive mapping. For the documented port-A setup, trace console transmit channels 1–16 to DL32 outputs XLR1–16; check bus assignment and mute. If output returns, verify the exact outlet at protected level. Otherwise preserve the complete map for support; do not copy another show’s routing. On M32, distinguish the console’s local XLR outputs from the AES50 transmission feeding the rack. Record the bus, transmitted AES50 position, and stage connector; their numbers need not match. If the local output changes but DL32 does not, review that transmission without changing the clock of a stable link. We can prepare a return map and a check with the technician before proposing more hardware. Send the console, port used, and affected destination, even with a provisional patch.

The analog preamp can be shared.

1. Identify who controls HA and phantom before changing gain; check both destinations using that preamp.
2. Agree gain ownership and any supported downstream trim; verify both mixes. Unclear control/topology requires the system technician, not competing gain adjustments.

Before testing, identify which consoles or destinations receive each source and who may change the preamp or phantom power. Compare the same voice or instrument in both mixes and record what changes; do not have two operators adjust the preamp simultaneously to compensate. We can assess shared I/O with an agreed procedure or separate inputs and suitable distribution if the show requires different independence. For the proposal, describe front-of-house, monitor, and recording tasks and the consoles available. Any split, accessory, and control method must be specified for the actual system and rehearsed; it is not assumed included with a DL32 rental.

Sharing inputs does not automatically distribute outputs. In the documented arrangement, DL32 XLR1–16 receive AES50-A1–16. Combining FOH and monitor returns requires signals from both positions to reach that send; connecting a console to each rack port does not establish that both can feed its outputs. Record each destination: originating console, mix bus, inter-console send if present, AES50 position toward the DL32 and final XLR. With a stable link, check that path and mutes at a protected level; if a signal exists at one console but does not reach the rack send, changing the bus number does not complete the route. Do not copy a fixed eight-and-eight allocation without checking models, firmware and patch.

The analog preamp remains shared: agree who controls gain and phantom power and who originates each return. During rehearsal, check a source at both positions, the agreed gain changes and every PA and monitor feed. Retain that configuration during the show. GLMedia can assess a compatible system with a documented digital split, local outputs with separate cabling, or an analog split and separate preamps where greater independence is needed. The alternative is designed for the actual system and is not assumed to be included with DL32 rental. For rental/purchase and preparation/operation pricing, send known consoles and versions, mono/stereo mixes, PA and recording destinations and positions, even with a provisional rider. We identify equipment, links, patch, responsibilities and outstanding checks, subject to compatibility and availability.

No: that USB connection is for firmware, not multitrack audio. For recording, assess a console interface or a compatible documented recording path; connecting the stagebox does not complete that chain. Define whether you need the final mix or separate tracks. Before the event, record and play back a sample, checking sources and the effect of mutes/faders. We can compare console recording, an additional interface, or a simpler solution for what you need to retain.

If considering ADAT, confirm actual ADAT inputs, supported channel count, and clocking on the receiving interface. Two optical outputs do not guarantee every interface can capture all microphones. The guide places ADAT on AES50 returns 17–24 and 25–32: verify which program the console sends to those positions; they are not inherently a direct copy of all 32 local inputs. Receiving audio through an interface also does not establish remote DL32 headamp control. We can compare recording through the installed console interface, a documented ADAT feed, or a stereo mix when sufficient. Send console, card, interface, and required tracks to quote connections, patching, file checks, and operation subject to compatibility.

DL32 is a stagebox: it brings inputs and outputs to the stage but does not replace the mixer handling channels, mixes, and returns. A rider that physically fits the rack may still exceed the selected console’s resources or available links. List microphones separately from monitor mixes and PA feeds. We can assess DL32 with a compatible console, existing equipment, or a smaller solution. Include links, power, and an operator as agreed; rehearsal should identify every source and return rather than assume compatibility from a similar-looking port.

Prepare three lists: inputs by location, monitor mixes per musician, and feeds to the PA, camera, or recording. Note equipment supplied by the band or venue and who prepares the showfile and operates each position. This distinguishes missing connections from missing mixes or staffing, without proposing another console by default. We can compare integrating DL32 with existing resources, a complete prepared package, or a smaller solution for a simple stage. An approximate rider, positions, and check schedule are enough to start the proposal; we will identify consoles, cards, links, accessories, and pending checks before confirming rental or purchase.

Do not confirm it from the connector. DL32 operates at 44.1/48 kHz: verify sample rate, audio transport, and remote gain and phantom control separately. Passing audio does not prove the artist can adjust the preamps. Send the console model, card, and known firmware. We can assess retaining a compatible system, a rack appropriate for the visiting console, or an analog split designed for both positions. Compatibility and availability are confirmed in the proposal; rehearsal must also check control and outputs, not just synchronization.

They do not use the same protocol: P16 uses ULTRANET and DP48 uses AES50. Identify the exact personal mixer before selecting a port, distribution, and documented power arrangement. Similar connectors do not establish compatibility. Prepare which sources each musician receives and check that each label matches the actual audio; do not copy another console’s map. We can compare operator-prepared mixes, compatible personal monitoring, or a combination for each performer. Send models, performer count, and mix requirements even with a provisional rider; links, accessories, and testing are defined for the complete package.

Do not count them as four extra mixes. The DL32 guide assigns AES/EBU to AES50 channels 13/14 and 15/16, which also feed those analog outputs. Document the program occupying those positions and every destination receiving it before reassigning them. Confirm the exact processor’s digital input, format, and synchronization, then verify delivery at a controlled level. We can compare analog connection, a compatible digital feed, or a system with more routes when independent programs are needed. Send the processor model and destinations; the package is quoted subject to compatibility and availability.

The ULTRANET port can feed compatible personal-monitoring equipment, such as the P16 system; that listening stage is required. It is not a headphone output for connecting in-ears directly.

We can compare compatible personal mixers with monitor mixes prepared at the console. Define who will adjust each mix and which sources are needed, then identify units, distribution, power, and a suitable output. Rehearse voices and instruments for each musician at a protected level, and retain the operating routing before changing shared assignments.

Not directly. The DL32 carries audio over AES50; using an RJ45 connector does not make it a Dante device. An ordinary Ethernet switch cannot replace a compatible AES50 link. Before setup, confirm the console, protocol, clocking and cable route with the venue technician.

We can assess a dedicated AES50 link, a compatible interface to Dante or a stagebox suited to the venue console. Midas documents DL32 with M32C and optional cards; the card is not installed in the DL32. To quote, we need exact models, input and return channel counts and time for testing. The proposal includes checking routing and synchronization before the show; availability and compatibility require confirmation for each system.

Transporting audio between systems does not establish remote preamp control. Agree on who manages gain and phantom power and which mixes must remain unchanged before choosing the adaptation.

No. Check each socket/received position against channel source/bank. For a missing block, compare its assignment with a working block before changing clocking or replacing the stagebox.