Skip to content

Conversation

@sethvincent
Copy link
Contributor

I tried using multiple inputs and outputs with FilterGraph and found that the params for the binding function needed to be updated to use double pointers to fully support the linked lists.

@sethvincent sethvincent requested a review from a team October 29, 2025 05:46
})
})

test('FilterGraph.parse should handle multiple inputs', (t) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
test('FilterGraph.parse should handle multiple inputs', (t) => {
test('FilterGraph should split one input into multiple outputs', (t) => {

According to my understanding. I could be wrong tho 😅

})
})

test('FilterGraph.parse should handle multiple outputs', (t) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

Comment on lines +92 to +100
using inputs = createFilterInOutChain([
[sinkContext0, 'out0'],
[sinkContext1, 'out1']
])
using outputs = initOutputs(bufferContext)

t.execution(() => {
graph.parse('split=2[out0][out1]', inputs, outputs)
})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According what was added in lib/filter-graph.js. It does not look like we have a test that cover that case (having inputs or ouputs with an undefined _handle).

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.

3 participants