Ember+
Open control and monitoring protocol from Lawo, widely adopted across broadcast for exposing device parameters as a browsable tree that any controller can read and set.
Stewarded by Lawo, with an open specification and reference implementation.
Small messages that either repeat constantly or fire once. Bandwidth is almost never the problem.
What kills it. Latency and loss on the messages that fire once. A repeating level survives a dropped packet; a GO does not.
Why this one, and not what the category suggests. Broadcast device control. It sets parameters rather than gathering statistics.
Ports
Configurable per device.
What goes wrong
Open source implementations
- Lawo/ember-plus — C++, BSL-1.0
Typical use
- Controlling and monitoring broadcast infrastructure from a single panel
- Exposing a device parameter tree to a facility control system
- Third-party integration with audio and video routers
Sources
- Ember+ on GitHub — Lawo primary
Every entry here is maintained by people who run shows.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at Lawo, with an open specification and reference implementation? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.