Skip to content

fix(node): audio and video output maps ignore mapping inputs - #38

Open
ibiltari wants to merge 1 commit into
rc_1from
fix/node-output-maps-ignore-inputs
Open

ibiltari wants to merge 1 commit into
rc_1from
fix/node-output-maps-ignore-inputs

Conversation

@ibiltari

Copy link
Copy Markdown
Member

ClickUp: 869fhghhe

Problem

NodeEngine built its <id> → JACK port lookup (audio) and <id> → display output lookup (video) from every list under the node's mappings, inputs included. node_mappings["audio"] is [{"outputs": [...]}, {"inputs": [...]}]. Inputs reuse the outputs' <id> numbering and are read after them, so input 0 overwrote output 0.

An audio cue on output <node>_0 was then resolved to system:capture_1, found no mixer input for it and played SILENT:

No valid mixer inputs found for outputs: ['system:capture_1']
Audio cue … failed to route Audio_Player-… to the mixer - it will be SILENT

This affects any node whose mappings list audio inputs. Seen on dev.stagelab.coop, whose default_mappings.xml lists capture_1/capture_2. Video has the same loop; it only bites when video inputs are listed.

Change

Only the outputs list feeds the two lookups.

Test plan

  • black, isort, flake8
  • dev.stagelab.coop: arm_test's audio cues on output _0 now wire outport 0 → 0_mixer:input_1; no SILENT error
  • engine suite (not run yet: test2 is busy)
  • a real node with audio inputs in its mappings

NodeEngine built the <id> -> JACK port (audio) and <id> -> display output
(video) lookups from every list under the node's mappings, inputs included.
Inputs reuse the outputs' <id> numbering and come after them, so input 0
overwrote output 0: an audio cue on output "<node>_0" was resolved to
system:capture_1, found no mixer input for it and played SILENT ("No valid
mixer inputs found for outputs: ['system:capture_1']"). Any node whose
mappings list audio inputs is affected; seen on dev.stagelab.coop
(default_mappings lists capture_1/2).

Only the "outputs" list feeds the lookups now.
@ibiltari
ibiltari requested a review from backenv as a code owner October 15, 2026 18:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant