Closed x37v closed 2 months ago
no need to expose rnbomidiout1
as an alias though, it is just used internally
might wanna mouse over ports to get aliases or non aliased names depending on what the default is?
beyond aliases - what's actually the idea of having the instance ins & outs listed in as part of the jack ports? Currently that's the thing throwing things off wrt creating "system" nodes and makes it hard to potentially cater for other node types if their prefixes aren't "hardcoded".
Currently requesting /rnbo/jack/info/ports
gives you a list of what seems like all ports? The UI currently filters them by checking for a system:
or system_midi:
prefix in order to distinguish it from what's assigned to things in /rnbo/inst/...
.
Is that actually the most reliable / failsafe way to do it or is there a better way?
Is that actually the most reliable / failsafe way to do it or is there a better way?
The idea is that there you have all the i/o that jack sees, including those that the runner provides.
Maybe it would be simpler to add a node in /rnbo/jack/
that allows you to make any connection so that we can connect system pass thru, connect non rnbo nodes, etc?
I think for a user, if you're doing OSC.. there is utility in having the instanced based connection:
"foo:bar" -> /rnbo/inst/0/jack/connections/audio/sources/out1
but maybe the runner panel would benefit from a more generic "hook whatever sink to whatever source"
That's not necessarily what I meant - I'd just like to get a list of ports that are non-instance (read system or whatever) associated rather than doing the error-prone prefix filtering which seems to be different depending on the platform.
so #50 addresses the more generic system nodes creation.
Back to the core of the issue - not really problematic to store a map of port ids and aliases. The questions is just how we'd like to display this to the user. A popup in a patching env seems potentially noisy / crowded? We could also display a fixed positioned "helper" at the bottom (small info toolbar) that shows a port alias on hover.
the helper at the bottom could work.. though, we might get away with simply using the first alias for display, except for rnbomidiout1
for instance, system i/o might have better names in the aliases