I am using Waves Superrack Performer in a live mixing context. Superrack receives its tempo information via MIDI across the network using Bome Network Pro. I have the “Keep virtual MIDI ports after disconnect” and “Keep virtual MIDI ports for pending devices” options enabled on the Superrack device and the device sending MIDI clock.
Superrack does all of its device discovery on open, so if any devices are added later Superrack will ignore them. If Superrack is opened and then the device that sends the MIDI clock is booted and connected via BNP, Superrack will not respond to any messages on that port even though the messages show up in MIDI monitoring software on the same device as Superrack. If Superrack is opened, or quit and reopened after the sending device is online and connected via BNP, Superrack responds to the MIDI information.
Are there setting I need to enable in BNP so that Superrack sees the assigned virtual port as an active port so that if the sending device is booted after the Superrack device, Superrack sees and responds to the incoming MIDI data?
The settings you have are correct and it should work as long as Bome Network Pro is opened before Superrack. What version of Bome Network Pro are you running? The latest is 1.6.0.
What OS (Windows or Mac) are you using and what version?
Do you have Superrack start automatically when you start your computer? If so, you might need to find out how to add a delay or just manually start it when you computer starts instead.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
BNP is v1.6.0 running on a 2019 Mac Pro on MacOS 14.5
I ran a few more experiments.
Having BNP start and then waiting 30 seconds did not have Superrack detect the MIDI port. Connecting from the other device and sending MIDI was ignored by Superrack.
Rebooting the Mac Pro, connecting and disconnecting BNP from the remote device, opening Superrack, and then reconnecting BNP resulted in Superrack following the MIDI inputs sent from the other device.
2 is not a normal workflow, but the audio infrastructure is often up and running well before the device sending the MIDI to Superrack, making the process of quitting and reopening Superrack mid-soundcheck/rehearsal once the sending device is online unviable. The results of test #2 do indicate that Superrack will see the virtual MIDI port if it is “woken up” before Superrack is launched and that this virtual port is present but not “awake” until it makes its first connection. From there, the port is detectable.
Is there anything you would recommend I do to initiate the “wake up” on that virtual MIDI port in the absence of the remote device?