-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
long port names overlap each other in graph #173
Comments
Hello, continuing the discussion from Discord and referencing #174 since I believe it may stem from the same source. If I change
I get a more sensible display, but the connections still don't appear. It looks like some logic is necessary so that port aliases are not used for the Pipewire ports and instead the actual port name should be used for display. So if the port name is "Midi-Bridge:Midi Through:(playback_0) Midi Through Port-0" parse that so you get just "Midi Through Port-0". Not sure why the connections aren't working, but I guess the RNBO runner knows about the ports just by parsing names, right? So maybe something is up with how the parser gets the port info when it's a PipeWire-generated port. |
Ok this is a little bit better. This is with a combination of using Connections are successfully made when dragging between nodes in the interface, but the wires still don't show up. |
here's the patch for rnbo-runner-panel btw:
|
Weird interface name can be fixed with a Wireplumber rule, e.g.
|
I'm running via pipewire.. it creates a node called
Midi-Bridge
here are its aliases
The text was updated successfully, but these errors were encountered: