How do I ensure my digital mixer is on the same local network as the application?
For ChurchMixDSP to successfully dispatch OSC adjustments, both your digital console (WING/X32) and the
host machine running the application must reside on the same Wi-Fi subnet:
- Assign a static IP: On your Behringer X32 or WING console, go to
Setup > Network. Assign a static IP address in your local router's subnet range (for example,
192.168.1.50) and set the subnet mask to 255.255.255.0.
- Ethernet connection: Connect the console's Ethernet remote control port directly to
your network switch or wireless Wi-Fi router.
- Connect host machine: Connect the computer running ChurchMixDSP to the same Wi-Fi
router or ethernet network.
- Verify Connection: Ping the mixer's IP address from your system shell to verify
low-level routing, or click the **Discover Mixer** button inside ChurchMixDSP to run a multicast DNS
query.
How do I choose and configure the audio input device inside ChurchMixDSP?
ChurchMixDSP samples live ambient room audio or queries the mixer directly to compute frequency spectrum averages. To configure your capture hardware:
- Navigate to Audio Input: Open the first step of the configuration flow. Look for the
**AUDIO INPUT METHOD** panel.
- Select Capture Source: The dropdown lists all available physical audio drivers and network streams. Choose
your measurement microphone, attached USB audio interface, built-in system input, or choose **Console Network Metering (OSC RTA)** to query the mixer's built-in RTA over the network.
- Rescan Devices: If you plugged in a USB device after starting the app, click the
**Rescan** icon (refresh indicator) next to the dropdown to re-query the hardware system.
- Offline Testing: Choose **Simulated Test Tone (Mock)** to generate profile-specific
simulated buffers. This is ideal for testing console OSC dispatch offline.
How does the 10-second capture and FFT frequency analysis work?
When you click **Start Analysis**, ChurchMixDSP initiates the capture flow:
- PCM Streaming: Captures low-latency 16-bit mono PCM buffers (44.1kHz)
directly from the hardware input.
- FFT Conversion: Computes a Fast Fourier Transform (FFT) on the raw buffer data,
converting time-domain waves into frequency-domain magnitude arrays.
- Visualizer Grouping: Downsamples the 512 magnitude bins into 64 responsive bands for
the real-time visualizer.
- Baseline Comparison: Averages spectral densities over a 10-second duration and
calculates required adjustments compared to the target profile (e.g. Lead Vocal, Speech).
Which ports and OSC protocols are used to communicate with Behringer mixers?
The application communicates directly over local UDP sockets using native OSC packet format:
- Behringer WING: Operates on UDP port
10024.
- Behringer X32: Operates on UDP port
10023.
- Make sure your computer's firewall allows outgoing UDP traffic on these ports. Adjustments are
dispatched immediately to console paths like
/ch/16/eq/2/g.
How does Console Network Metering (OSC RTA) differ from local audio input?
Unlike local audio input which uses the host microphone, Console Network Metering queries the digital mixer's built-in Real Time Analyzer (RTA) over the network via OSC (using paths like /meters/13 on X32 and /meters/rtc on WING). This eliminates the need for room measurement microphones, allowing ChurchMixDSP to analyze the raw console input channel signals directly and accurately, even in noisy or dead-room environments.
How does the Multi-Channel Auto-Fader Balancer work?
The Multi-Channel Balancer acts as an automatic fader rider. It polls post-fader levels from the console via OSC on a fast 150ms interval, filters out gated/silent signals, and compares active channels against target LUFS-like level baselines (e.g. Lead Vocal: -18dBFS, Speech: -20dBFS). If levels deviate, a smoothed Proportional (P) control loop smoothly rides the mixer's faders (e.g. /ch/{ch}/mix/fader) to maintain a perfectly balanced live mix.
When a channel is in manual mode, the engine keeps level capture and frequency metering active so screensaver visualizers show live activity, while manual fader adjustments are safely broadcast to the console without snapping back.
How do the screensaver visualizers work, and how do I switch between modes?
After 2 minutes of engineer inactivity, ChurchMixDSP automatically activates the full-screen visualizer screensaver. It features two visualization modes:
- Orbit Universe: A solar system simulator where channel boids follow concentric orbital paths mapped logarithmically by center frequencies (20Hz to 20kHz), with speeds scaled by live decibels.
- Classic Bar Spectrum: A neon-glowing 32-channel spectrum analyzer featuring real-time peak-hold indicators that gradually decay.
You can seamlessly toggle between these modes using the glassmorphic segmented controller in the top right. Any mouse movement, fader drag, or tapping the floating HUD cards resets the inactivity timer and returns you to the console.
Does ChurchMixDSP support master fader control and channel mutes?
Yes, ChurchMixDSP has full bidirectional OSC support for master volume control and mute state synchronization:
- Always-Visible Master Fader: A dedicated Main L/R fader is docked on the right side of the screen, visible in both the console grid and the screensaver modes, styled with professional scale ticks and neon cyan colors.
- Channel Mute Toggles: Each channel strip and floating HUD card features an interactive Mute button. It syncs with the physical console via OSC (using
/ch/XX/mix/on for X32, or /ch/XX/mute for WING). Muted channels are visually dimmed to immediately represent silence.
Can I enable auto-balancing for all channels at once?
Yes. Instead of toggling each channel manually, you can click the Auto All button located at the top banner of the Manual Console faders grid. This instantly activates the auto-balancing feedback loop on all eligible channels (respecting Pro tier limitations for channels 5–32).