OSC Manual Gaps: Missing Input/Output Distinction and Undocumented Commands#455

“OSC Manual Gaps: Missing Input/Output Distinction, Undocumented Commands, and No Known State-Sync Command”

Here’s the updated body text with that point folded in:

The manual (v2.0.6) documents the OSC command set, but it has some gaps:

It doesn’t distinguish input from output. Some listed addresses aren’t commands an OSC client can send — they’re only status/feedback messages the console sends out when something changes on its own. For example, /lampy/pbf/1/name appears to be the console reporting the current name of playback fader 1, not something the client is meant to set via that address.

Non-obvious commands aren’t described. Some addresses (e.g. /lampy/sync) are listed with only a path and a data type (0/1), with no explanation of what they actually do.(Maybe there is a typo in the address, it seems like on the console is /lmpy/sync)

No documented way to request a full state dump. It’s unclear whether there’s a command to request all current information from the console (fader values, names, modes, etc.) upon first connecting — or whether a client is only expected to build up state passively from whatever feedback messages happen to arrive afterward.

Thank you for the feedback.

Sync is doing a full state dump, and the command is indeed /lampy/sync not /lmpy/sync.

We are working on updating the documentation to match v2.2.x