MP32 Control 1.3.2

Header rework, a status icon that actually tells you where you stand, and metadata that
survives a restart.

What changed since 1.3.1

The header lost its words. The controller count, the Device button and the status pill
were three ways of saying "who am I talking to". They are now one control with two halves:
the status opens the device panel, the count opens the controllers panel. Both panels are
unchanged. Every remaining label became the icon that already meant the same thing — words
were the first thing to run out of room on a phone.

One status icon, shape and colour. Shape is the role: a plain dot is an ordinary
controller, a dot with arcs is the web host — the machine publishing mp32-control.local
and serving the phones and tablets. Colour is the connection: green live, amber
reachable but in standby or re-establishing after a handover, red nothing there.
Standby is amber rather than green on purpose — the unit answers, but no audio is passing.

A phone lights up beside it while a handheld or another computer is actually on the web
interface, and goes out when none is. It shows only on the web host, and only in the desktop
window: a phone looking at the panel does not need to be told a phone is connected.

Metadata now survives a controller restart. Channel names, colours, groups and shared
notes were held in memory only. Restarting a controller emptied it, and the first browser to
reconnect re-seeded whatever it still held — including values deleted while that browser was
closed. Deletions came back. The field set is now persisted and written atomically, so the
network's current state outlives the process and a stale copy loses instead of winning.

Downloads

macOS (Apple Silicon) — MP32-Control-1.3.2-macOS-arm64.zip

Windows — MP32-Control-1.3.2-windows-build-kit.zip. A build kit, not an executable:
PyInstaller cannot cross-compile, so the .exe is produced on a Windows machine. Unzip and
read START HERE.txt. Two things usually go wrong: Python's "Add to PATH" checkbox, and the
Edge WebView2 runtime, without which the window opens blank.

Read this before installing

The macOS build is ad-hoc signed. On any Mac other than the one that built it, the first
launch is blocked: right-click the app → Open → Open, once. After that it starts normally.

The Windows build kit has never been run. The scripts, installer and guide are written
and internally consistent, but nobody has built this on Windows yet.

The HTTP control API has no authentication. Anyone who can reach port 8765 can change
gain, phantom power, input type and presets. Deliberate for a trusted studio LAN — never
port-forward it, never run it on untrusted Wi-Fi.

48 V phantom power can damage equipment that is not designed for it. Check what is
connected before enabling phantom or any bulk control.

Verified on hardware

Built with the physical device preflight active: the gate connected to an MP32, validated a
32-channel configuration and observed live telemetry before packaging. 162 automated checks
pass, including a new suite covering metadata persistence.

Not verified: two units on one network, any other preamp model, and cross-machine failover
between Mac, Windows and iPad. docs/VERIFICATION.md tracks what is proven and what is not.

MP32 Control 1.3.1

Independent control panel for compatible Antelope MP32 microphone preamplifiers. Runs as a
native macOS or Windows application and serves the same interface to phones and tablets on
the local network.

Downloads

macOS (Apple Silicon) — MP32-Control-1.3.1-macOS-arm64.zip

Windows — MP32-Control-1.3.1-windows-build-kit.zip. This is a build kit, not an
executable: PyInstaller cannot cross-compile, so the .exe has to be produced on a
Windows machine. Unzip it and read START HERE.txt — one script builds the app, another
builds a single installer that also adds the firewall rules. Two things usually go wrong:
Python's "Add to PATH" checkbox, and the Edge WebView2 runtime, without which the window
opens blank.

Read this before installing

The macOS build is ad-hoc signed, so on any Mac other than the one that built it,
first launch is blocked: right-click the app → Open → Open, once. After that it starts
normally. A Developer ID signature would remove this; the build script already supports one
through MP32_CODESIGN_IDENTITY.

The Windows build kit has never been run. The scripts, the installer and the guide are
written and internally consistent, but nobody has built this on Windows yet. If a step
fails, that is worth reporting in an issue.

The HTTP control API has no authentication. Anyone who can reach port 8765 can change
gain, phantom power, input type and presets on your hardware. That is deliberate for a
trusted private studio LAN — never port-forward it, and do not run this on untrusted Wi-Fi.

48 V phantom power can damage equipment that is not designed for it. Check what is
connected before enabling phantom or any bulk control.

Verified on hardware

Both artifacts were produced with the physical device preflight active: the build gate
connected to an MP32, validated a 32-channel configuration and observed live telemetry
before packaging. Gain calibration, standby detection, web-host election and
mp32-control.local publication were confirmed against the unit.

Not verified: two units on one network, any other preamp model, and cross-machine failover
between Mac, Windows and iPad. docs/VERIFICATION.md tracks what is proven and what is not.

Licensing

Original code and artwork are MIT. The bundled application ships the license texts of its
third-party dependencies under legal/third-party — pywebview (BSD-3-Clause), zeroconf
(LGPL-2.1-or-later) and the PyInstaller bootloader (GPL-2.0-or-later with its bootloader
exception). This project is not affiliated with, sponsored by, or endorsed by Antelope Audio.