GPIO and Control
Ember+ GPIO triggers for visual radio
If your console speaks Ember+, a fader opening or a mic switching on is already a parameter on the network. VRA reads the parameters you choose and uses them to cut cameras or run macros, so the desk drives the picture as well as the sound.
What VRA does with Ember+.
Browse the device's tree
VRA reads the parameter tree of the connected device. Pick a path from the list or type its number, like 1.2.3.
A parameter change runs a command
Use a mapped parameter as the condition of an automation, and a fader opening on the desk can take a camera angle or fire a macro.
Streams and inverted logic
Subscribe to a parameter as an Ember+ stream where the device publishes it that way, and invert an input that reads the wrong way round.
Live state on one page
The GPIO page shows every mapped path with its current value and how long ago it changed. Outputs can be set on, off or pulsed from there.
How to set it up.
Requirements
- An Ember+ device reachable from VRA Core.
- Access to the device's configured network port.
- GPIO in your VRA licence.
In VRA, open Settings, Studio, GPIO and add an Ember+ connection.
Enter the device host and its port; VRA uses 9000 as the default.
Connect, browse the parameter tree and map the paths you need, with their value type.
Change each source on the device and watch it on the GPIO page before using it in an automation condition.
Ember+ questions
Does VRA work with my Ember+ console? +
If the console publishes the state you need as Ember+ parameters, yes. VRA connects on port 9000 by default, browses the tree and uses the parameters you map as automation conditions. Every manufacturer publishes a different tree, so browse your own device first.
Can VRA set an Ember+ parameter? +
By hand, for paths mapped as outputs, from the GPIO page. Automations and macros do not write Ember+ parameters.
Does the Ember+ connection carry audio? +
No. It carries control state. Your audio interface and console keep handling the program audio.
Visual Radio Assist
About Ember+.
Ember+ is the control protocol many broadcast consoles and routers use to publish their settings as a tree of parameters. VRA Core connects to the device and lets you browse that tree, then map the parameters you need with a value type: on or off, a number or text.
A mapped parameter becomes a condition for an automation. When it changes, the automation runs its command, like a camera angle or a macro. Parameters mapped as outputs can be set on, off or pulsed by hand from the GPIO page; automations and macros do not write them. What a device publishes is up to the device, so setup starts with browsing its tree.
What you can do with this connection
Automated camera switching for radio
Switch cameras from microphone activity and prepare PTZ shots off air.
More infoThe products behind it.
More integrations.
Livewire Routing Protocol
Use Livewire GPIO in your visual radio studio. VRA reads GPI states over LWRP to fire camera, graphics and macro actions, and you switch GPO ports by hand.
TCP
Control your visual radio studio over TCP. Send one line of text to VRA Core to put the studio on air, cut a camera or fire a macro, and get a reply.
MQTT
Connect your own systems to a visual radio studio over MQTT. Read microphone, switcher and now-playing state, and write signals, scoped to one studio.
Check your studio setup with us.
Tell us your camera models, video switcher and radio automation. We will check the connections and show you the workflow that fits your station.