Macros, meters, and more for Behringer WING. An independent community project for Apple Silicon Macs, with a classic desktop interface.
Turn audio levels and console state into conditional, timed action sequences. Watch Sources as well as channels, use their meters as triggers or IF conditions, and combine console actions with MIDI/OSC messages and operator HUDs. Incoming MIDI/OSC bindings and LTC/MTC cues provide additional ways to launch sequences. Keep mixing with your console or preferred control app.
Installation guide · Release notes and checksums · Operator guide · Feedback · Español
Apple Silicon / M-series Macs only. The application is self-signed and not notarised by Apple; the installation guide explains first-launch approval.
Community beta. Many hardware and inter-application workflows still need real-world testing. Read the disclaimer and help with community testing.
Unofficial software. Use at your own risk. This is not a Behringer or Music Tribe product and is not affiliated with, approved, certified, supported or endorsed by either company. It comes without warranties. You are responsible for testing your setup, keeping backups and maintaining a manual recovery plan. Read the full disclaimer before using it, especially at a show.
- Download the Mac DMG from this repository's Releases. Check it against
SHA256SUMS.txtfrom the same release. - Open the DMG and drag WING CONTROLLER.app to Applications.
- Eject the DMG, then open the copy in Applications. If macOS blocks it, follow the first-launch instructions.
No developer tools are needed. GitHub's Source code downloads contain the project's source, rather than an installable app.
| Capability | What it lets you do |
|---|---|
| Programmable macros | Combine WHEN / IF / THEN: up to 16 conditions with AND or OR and 32 ordered action steps, including waits, fades, toggles, HUDs and MIDI/OSC sends. Apply supported actions to several channel IDs or ranges. |
| Metering beyond channels | Build mixed views of channels, buses, mains, matrices, Sources and outputs. Source families include local inputs, AES50, StageConnect, USB and Card/Dante, according to the console and fitted hardware. |
| Source levels as automation inputs | Use Source meters as WHEN triggers or IF conditions, including meters that neither window displays. A macro subscribes to its own meter targets independently of the visible bank. |
| A customisable Meter Bridge | Choose mixed named banks, aliases, ordering, size and zoom; use LED bars, analogue-style needles or history graphs, with peak hold and clip indication. The workstation and separate bridge can show different banks, including on a second display. |
| Parameter-aware fades | Start at a chosen value or read the console's current value; move to an absolute value or by a relative amount, with linear or smooth curves and the supported parameter's units and limits. |
| Inter-application automation | Learn incoming MIDI/OSC bindings, add binding conditions, and mix console operations with outgoing MIDI/OSC in one sequence. MIDI conditions can watch another MIDI message; OSC conditions filter an argument of the incoming message. |
| Timecode and cue tools | Follow LTC or MTC, analyse LTC WAV files, edit cue lists and frame offsets, open a separate clock and forward the followed position as MTC. Cue history records execution outcomes. Physical LTC and external-receiver timing still need independent testing. |
| Trigger response and operator feedback | Tune audio-trigger response and cooldown, choose Drop / Queue one / Restart on retrigger, add custom HUDs and notices, check syntax and targets, inspect action outcomes, and cancel pending work with PANIC STOP. |
Condition scope: the macro's IF list is evaluated on meter and console-state triggers. MIDI/OSC bindings use their own conditions; bindings, timecode cues and manual firing run the action sequence without evaluating that IF list. IF is a flat AND or OR list. Rearm and dwell tune rising transients. MIDI/OSC sends report sending, not confirmation by the receiving application; PANIC STOP cancels pending work and cannot undo actions already applied.
A macro combines a WHEN, optional IF conditions, and an ordered THEN sequence. The example below has a meter trigger, two console-state conditions, a HUD message, a relative smooth fade, a wait, a multi-channel action and a second HUD message.
| Part | What you can configure |
|---|---|
| WHEN | Meter thresholds or typed console-state comparisons. MIDI/OSC bindings and timecode cues provide additional firing routes. |
| IF | Up to 16 gates, joined with AND or OR, using supported meter values (including Sources) or console state. These are checked when the meter or console-state trigger arrives. |
| THEN | Up to 32 ordered steps: Set, Toggle, Wait, Wait then Set, Fade, Smooth Fade, HUD, Send MIDI or Send OSC. Available modes depend on the target. |
| Fade | Start at a chosen value or the console's current value; aim at a value or a relative change, with the parameter's units and range. |
| Retrigger | Drop another trigger, queue one follow-up run, or restart the sequence. |
See the trigger tuning, IF gates and action editor
Meter triggers provide response presets and custom tuning. Rearm and dwell apply to rising transients; other paths use their crossing and cooldown rules.
The gates form one AND or OR list, rather than nested branches. They are checked when the meter or console-state trigger arrives, rather than continuously supervising later actions.
The selected fade reads the current playback fader, then reduces it by 12 dB over 1,500 ms. A separate wait and later actions follow sequentially. Channel roles and values are illustrative; this is an inactive interface example, not a tested show preset.
Choose supported channels and groups from a visual grid. Bank buttons and selection tools help build target lists and meter views. This is a channel selector; audio routing is a separate function.
The trigger grid selects one channel; typed trigger lists/ranges are also supported. Action targets and meter lists can select several, where supported. The meter picker can add to the view or replace it. Meter and bank guide.
Open meters in a separate window, mix channel, Source and output meters in named banks, add aliases and arrange their order. Choose a layout, size and visual style. Each window can show a different bank; keep the bridge alongside the workstation or on another display. Macro meter subscriptions continue independently of the bank you are viewing.
Meter availability depends on the connected console and source. The analogue VU option is a visual style, rather than a claim of calibrated VU ballistics. Meter Bridge guide.
An optional courtesy notice shows which macro fired, its action summary and the time. A HUD message is a separate action you can add to a macro: a centred card, corner notice or full-screen message, with optional sound.
These messages report app activity; they do not prove a console accepted a command or replace a safety system. Macro notices · HUD actions.
All images above use the real interface with example configurations, rendered offline. No console is connected, no macro is executed and no meter signal is simulated. Media sources and regeneration.
Choose Light (Classic Slate) or Dark (FOH Low Glare) in Properties → General. The controls and configuration stay the same.
Use incoming MIDI notes/controller messages or OSC to trigger macros between applications, with Learn and optional binding conditions. A MIDI binding can check a tracked MIDI value with an expiry time; an OSC binding can compare an argument of the message that arrived. Include outgoing MIDI/OSC messages in the same action sequence as console operations and HUD messages. Inter-app configuration guide.
LTC (audio timecode), MTC (MIDI timecode) and cue tools are included in the beta: inspect LTC WAV files, follow timecode inputs and associate cue positions with macros. Timecode guide. Hardware and third-party workflows need community testing; see the testing priorities.
The source is here so people can study it, fix things and contribute. You do not need to write code to help: report a bug, suggest a change, share a test result or describe what worked and what did not.
Report a bug · Suggest an improvement · Report a test · Share an experience
Community testing and how reports are handled. English and Spanish reports are welcome. A GitHub account is needed to submit a report.
- Roadmap and to-do: storage and recovery, physical LTC/MTC tests, hardware coverage, accessibility and maintenance.
- Report a bug or suggest a change: include the version, steps and expected result; remove private show/console details.
- Contributing: how to choose a task, verify a change and submit a pull request.
- Tests and CI: what runs, where the tests live and what they do not establish. Latest runs.
- Audit · Architecture · Validation: evidence, structure and checks.
- Security reporting: report vulnerabilities privately.
| Item | Current status |
|---|---|
| Mac | Apple Silicon / arm64 (M-series) |
| Checked environment | macOS 26.6.2 on arm64; a wider runtime range remains unverified |
| Intel / Windows / Linux | No supported desktop installer |
| WING consoles | WING-family protocols; model, firmware and feature availability vary |
| Mobile | Original Expo source retained; mobile work is parked |
| Release | v0.3.0 community beta |
Read known limitations before relying on a feature. The package validation records checks of the installer separately from hardware/show acceptance.
© 2026 MÁRMOLES SUPPLY CO. and contributors.
Free to use, study, modify and share under the WING CONTROLLER Source-Available Licence 1.0. Professional use, including paid shows, is allowed. Selling copies or derivatives is prohibited. Redistributions must include corresponding source under the same licence.
Because of the sale restriction, these are source-available terms, rather than an OSI open-source licence or GPL. They do not become permissive later. Third-party components keep their own licences. Trademarks identify compatibility and grant no affiliation or endorsement.
Set up the source, run checks and find your way around the repository
Use an Apple Silicon Mac with Xcode Command Line Tools, Node.js 26.8.2 with
npm, Rust/Cargo 1.98.1 and Poppler (pdftotext). Chrome is needed for the
complete verification gate. These are the measured development/CI versions;
compatibility with earlier versions has not been established.
git clone https://github.com/marmoles-supply/wing-controller.git
cd wing-controller
npm ci
node scripts/setup-protocol-reference.mjs
./scripts/verify-all.sh --quick
cargo run --locked -p wing-controller-desktopProtocol setup downloads and verifies Maillot's pinned manual locally, then extracts an ignored reference file. The complete manual is not redistributed. See reference acquisition/checksums.
cargo run compiles and launches a development app, not a release installer.
Node generates the UI vault during Cargo compilation. No maintainer signing key,
activation key, customer data or generated Android directory is needed to verify
this source checkout.
See the dated verification record for measured results, environment, dependency-cache use and what was not established. The 0.3.0 package validation records installer, signature, architecture and checksum checks separately.
./scripts/verify-all.sh --quick # Everyday checks; omits named browser suites
./scripts/verify-all.sh # Complete source gate, including browser suitesQuick mode also runs the design screenshot check when Chrome is available. Run only one gate/browser suite at a time. Scripts manage their Chrome instances; do not drive the shared test browser concurrently. Pixel baselines depend on the rendering environment: review differences rather than accepting them blindly.
Ordinary checks are console-free. Hardware tests need explicit LIVE_WING_*
opt-ins; inspect them before enabling anything against a console. A source gate
does not certify a live show, packaged app or installed system. Historical
provenance is retained; 15 archival notes lack surviving build evidence and are
explicitly labelled unverified.
| Path | Purpose |
|---|---|
desktop/src-tauri/ |
Tauri app and native integrations |
desktop/ui/ |
Workstation, meters, timecode, cue editor and guide |
crates/ |
Protocol, runtime, transport and probe crates |
design/ |
Tokens, components, reviewed renders and conformance tools |
scripts/ |
Verification, reference setup, generation and release tools |
docs/guide/ |
Operator guide sources |
src/, native/, plugins/ |
Parked mobile source/integrations |
This repository starts a new public history. Private backups, operator exports,
machine diagnostics, credentials and downloaded manuals are excluded.
SOURCE_MANIFEST.json records the source revision and exported hashes.












