InputPin
Field |
Type |
Repeated |
Description |
input_pin |
Member of
Message |
Description |
Describe an audio source with the output gain mapping for a mixer. |
|
Describe an individual part representing the contribution of one source to a composition. |
|
The MultipleContext message is sent from Norsk in response to a
change to either the Media Node’s inbound set of streams for
certain nodes that are permitted non-disjoint context keys
.
Once received, your code must acknowledge the context change
with a call through a subscription channel |
|
Server event: fires when the engine has handed off to a new active source. The pin in this message is whichever pin is now feeding the output.
|
|
Server event: fires when the engine has held a source pin (pre-warmed + queued + ready). The streams list reflects the pin’s currently visible stream complement; the event re-fires whenever that complement changes so the client can wait for an expected shape (e.g. audio + video both present). The pin remains held until the client calls release_preloaded(pin). |
|
Client request: release a held pin onto the output. Mirrors SSS’s release model — SSQ does not autopilot; every transition is driven by an explicit release_preloaded. Cold start (no active source): the held pin’s queue drains rebased (anchor_pts_us applied) and becomes the active source. Mid-stream (another source is currently emitting): the release is queued and applied at the current source’s next EOF. |
|
Server event: fires when the engine’s currently-active source
fully drained (natural EOF or synthetic via end_current_source).
ended_pin is the pin that just ended; last_seen_pts_us is the
last PTS (microseconds) the engine emitted from it. Clients use
last_seen_pts_us as the |
|
Fires when the active pin’s seen-stream-key set changes — the
active-pin sibling of |
|
The subscription for a single source |
|