This routing is auto generated and is difficult to decipher, especially with several ports being handled this way. ‘IN: VideoSync Virtual Virtual In’ is making my head spin. I’m not able to rename the ports or edit the routing in any way, since BN handles this exclusively. It’s also interesting that BN has a simpler routing for default MIDI port it creates ‘AWOS-Server’ than for the additional virtual port I created. It would help I could either:
exclude the suffix ‘virtual’ for auto-generated names as an option, or
allow renaming of the virtual ports created by BN (preferred), so that I can remove the word ‘virtual’ or replace the name to something that makes more sense to the task.
Hiding the routing would be helpful. As far as the feature request, I realized afterward that I won’t be using the auto-generated ports, so it doesn’t matter how they are displayed.
I was able to create a virtual port named ‘VideoSync’ then route that to another computer just like the automatic port. I like this method because it decouples the VideoSync port from the destination computer. The apps that provide the MIDI sync data don’t care where it comes from. For example, I can change the route to a different computer host without having to change the port settings in several apps that point to that port. BN is working great for that! What would be helpful is the option to hide any or all of the auto-generated ports from MIDI apps that list them… my list is already too long.
