Hi guys! I’m struggling with two problems with my Bome Box. First, I noticed that while using one of my midi controllers through a Bome Box (IRig Pads) – I’m getting multiple “note ons” and “note offs” at the same time…it arrives doubled to my mac. I mean if I press a pad – I get two “note ons” and “two note offs” at the same time…I have some glitches in my software because of that. Please check a Midi Monitor screenshot. What may cause this? Other plugged in midi controllers work fine.
The second issue…after update to latest firmware I started to get those messages after I disconnect Wi-Fi connection. It’s pretty annoying and happens many times in the row. But the worst thing – if I forget to Quit “Bome Network” app – it can get my Macbook out of “Sleep mode” even with a closed lid. It happened several times already while my mac was in my backpack and it was very hot after that with deployed to zero battery.
Marked as spam
Hey guys! I little update – I entered into Web Config and saw red sign saying this: Errors: ERROR: MIDI OUT ”ANTONs-MBP” does not exist. It is set to ’pending’ so that it is used automatically when you plug it in. ERROR: MIDI OUT ”ANTONs-MacBook-Pro” does not exist. It is set to ’pending’ so that it is used automatically when you plug it in. ERROR: MIDI IN ”ANTONs-MacBook-Pro” does not exist. It is set to ’pending’ so that it is used automatically when you plug it in. ERROR: MIDI IN ”iRig PADS” unexpectedly closed. It is set to ’pending’ and it will be opened automatically when it becomes available again.
Are you running an MT Pro project in on your BomeBox or are you just using BomeBox routing? Usually multiple note-on note-off messages happens is you both have a MIDI through path (route) and a translator in the project file that sends notes. So I would recommend you close any projects you have running on your BomeBox. Clear all MIDI routes and then define the route you want for that device. If that fixes it, then go ahead and restart the project. Once the project is started try again and of the problem returns, then the MT Pro project is likely the culprit and we should look at your project file.
For further troubleshooting, if you could provide me with information on what you have connected to BomeBox and how it is configured on your network, I can be of additional assistance. Having screen shots of the following would help as well:
Are you running BomeBox both WiFi and ethernet? Are they on separate networks?
Are you running multiple BomeBoxes or just one? Multiple PCs (how many and how connected).
Another think to check on is to delete any MIDI network connections and then re-establish. It is usually good practice to try to always initiate the connection from the same node each time. For instance always initiate it by the Mac or always initiate by the BomeBox. Sometimes if you try to do both you get one pending connection and one connected and some error messages on the pending one even though the connected one is working correctly.
Another thing to consider is that if you change your device name on your BomeBox or Mac/PC, you connection name will usually change. So for me if I renamed “BomeBox” to “BomeBoxSteve”, the name “BomeBox” no longer exists on the network but the network doesn’t know that and sets it to pending assuming that at some point in the future it will show up again. To fix this you just delete the old connection name on you network MIDI screen.
Please let me know if any of this helps and if you have any further questions. If this doesn’t help, let me know and maybe we figure out a more efficient way to get this resolved.
Marked as spam
Hello Steve! Thank you very much for the detailed answer, I managed to deal with multiply midi messages and now it’s fine.
The only thing that still annoying as hell is those error messages that pops on the screen from time to time, see attachment. It usually happens when I’m away from my BomeBox (like 20 kilometers) or if I activate VPN on my Macbook. Is there’s a chance to solve it somehow? It’s wasn’t like this before update.
VPN also usually introduces some latency.
In either case, I will pass your concern up the chain to see if Florian has any other suggestions. Maybe there is a way to suppress the messages.
Personally I wouldn’t recommend running BomeBox ( or any other MIDI network solution ) more than a few hundred meters without expecting some latency issues.
Hi Anton, indeed, BomeNet is not meant to be used in WAN’s, only in local networks. It will mark a device as missing when it doesn’t respond in a matter of a few hundred milliseconds. The MIDI connection should be unaffected though.
Please log in to post a topic
(this is your bome account, not the old forum account):.