The UI itself protects you from doing things that don't work anyway but it might be easier if the UI shows you what is possible.
E.g. you can't connect an input to an output (without an application or loopback)
you can't connect multiple inputs to an application.
you can't distribute one output of an application to a sink.
please check my drawing if it's feasible to enhance the UI so this is visible. (And check if I'm actually right)
It should depict what you can connect and on which interfaces you can attach multiple links.
In this example I wanted to inject the mic to an application including some background sound
but also hear this background sound on my headphones... :-D
Current view:
Idea to show connection constraints and 1:n relations of interfaces
... the one application is just blurred because I don't want to make extra ads for this one ;)
The only exception might be an application that has multiple output streams but this is nothing you can "choose" from within pagraphcontrol
The UI itself protects you from doing things that don't work anyway but it might be easier if the UI shows you what is possible. E.g. you can't connect an input to an output (without an application or loopback) you can't connect multiple inputs to an application. you can't distribute one output of an application to a sink.
please check my drawing if it's feasible to enhance the UI so this is visible. (And check if I'm actually right) It should depict what you can connect and on which interfaces you can attach multiple links.
In this example I wanted to inject the mic to an application including some background sound but also hear this background sound on my headphones... :-D
Current view:
Idea to show connection constraints and 1:n relations of interfaces
... the one application is just blurred because I don't want to make extra ads for this one ;)
The only exception might be an application that has multiple output streams but this is nothing you can "choose" from within pagraphcontrol