Expand description
Inbound typed event notifications from a RØDECaster console.
DeviceEvent represents notifications emitted by the device in response
to hardware changes or user actions:
- Physical or virtual fader movements.
- Mute and cue/solo button toggles.
- Rotary encoder adjustments and color updates.
- Input source assignment changes.
- Audio processing adjustments (EQ, dynamics, HPF, pan).
- Sub-mix changes and routing matrix links.
§Handling Events
When using crate::ProtocolSession, events are yielded by
crate::ProtocolSession::ingest:
use rodecaster_protocol::{DeviceEvent, Fader};
fn handle_event(event: DeviceEvent) {
match event {
DeviceEvent::FaderLevelChanged { fader, level } => {
println!("{fader:?} level is now {level}");
}
DeviceEvent::FaderMuteChanged { fader, muted } => {
println!("{fader:?} muted: {muted}");
}
_ => {}
}
}Re-exports§
pub use crate::trigger::TriggerPhase;
Enums§
- Device
Event - A typed event emitted by a connected RØDECaster console.
- MixLink
Direction - Direction of a mix-cell link request echo.
Functions§
- decode_
event - Decode one wire payload (the change-frame, not including transport frame)
into a typed event. Returns
Noneif the payload isn’t a recognized JUCE change-frame at all. - decode_
event_ from_ frame - Decode an already-parsed
ChangeFramethrough the discoveredLayoutinto a typedDeviceEvent. - extract_
initial_ state - Walk a parsed fullSync tree and extract the initial device state as a list of
DeviceEvents.
Type Aliases§
- MixLink
Request Origin - Origin of a mix-cell link request observation (alias for
TriggerPhase).