ampOSC manual
Help and troubleshooting
Help at the bottom of the panel opens a short reference you can keep open while you work, and can save the two bundled documents to disk.
The Help window
A list of example messages with their type tags, and the one line most worth remembering: values are dB, not 0–1, and pan is −100 to +100. Almost every first-time problem is a client sending a normalised float.
The examples are selectable, so they can be copied straight into a client.
The bundled documents
Two buttons save documents out of the app.
- Quick Start… — getting a first message through, with a dependency-free Python sender you can run as-is.
- OSC Reference… — the full address list. The same material as the OSC reference here, in a file you can take to a desk with no internet.
The copies inside the app travel with the app, which is the point — a production network is often not on the internet. This site is the version that gets corrected first.
The first four checks
In order. Most problems stop at the first or second.
- Is the Inventory count non-zero? If it is zero, nothing else matters — the console is not really connected. Go to connecting a console.
- Is the Clients count non-zero? If it is zero, nothing has reached the server. Check the port, then the firewall, then the address your client is aimed at.
- Open the log. It will tell you which side is silent.
- Switch the log to Raw. If messages are arriving but doing nothing, the type tag is usually why.
Common symptoms
| Symptom | Usually |
|---|---|
| Green dot, Inventory zero | Wrong console family, or the MIDI channel base does not match the desk |
| Faders move the wrong channels | MIDI channel base out by one |
| Faders land at the wrong level | The desk is on Audio taper. ampOSC speaks Linear — change it on the desk |
| Everything works except values coming back | Subscription mode with nothing subscribed |
| A mute does nothing but the log says it arrived |
A number was sent where a boolean belongs. Mute takes ,T /
,F, and from
AppleScript that means the word
true, never 1 |
| Levels are all at the extremes | The client is sending 0–1 rather than dB |
| Nothing found on the network at all | Local Network permission was declined on first launch |
Reporting a problem
Use the form on the support page. What helps most:
- The console family and firmware version.
- The Inventory, Clients and Subscriptions counts.
- An exported log with Date and Time on, covering the moment it went wrong.
- Whether Enable Subscriptions was on or off.