Support

Report a bug or send feedback

Submit anonymously — no account needed, nothing tracked. Add an email only if you'd like a reply. Saying which console and which firmware helps more than anything else here, because the four families differ in what they expose.

Prefer email? Send to amposc@jtap.com.au — useful if you want to attach a packet capture or a screenshot.

Before you report a connection problem

Four things account for most of them, and all four are quick to check.

1. The MIDI channel has to match. Set on the console under Utility → General → MIDI. If it doesn't match, ampOSC connects and no data flows correctly — which looks like a broken app rather than a mismatched setting.
2. The console and the Mac must reach each other. TCP 51325 to the console, UDP 51319 and 51320 for discovery. A managed switch or a VLAN between them will pass one and not the other, so discovery failing while a typed address works is normal and tells you where to look.
3. Your OSC client needs a route back. The server publishes on UDP 8765; a firewall on the Mac blocking inbound UDP stops clients reaching it.
4. On SQ and SQ+, check the fader law. The console switches between Linear and Audio taper and no message reports which is set, so ampOSC has to be told. Told wrong, every level is out by as much as 20 dB while everything else behaves.

The protocol

ampOSC speaks BroadwayOSC — address format, message intent, the namespace, value types and engineering-unit ranges, published in full. Download PDF · Download Markdown.

What ampOSC does, and which console exposes what.

Privacy

ampOSC holds no account and sends nothing off your network. The privacy policy says so in full, and it is short.