Thank you for this great software!
Works perfectly in LAN.
Now I’m thinking: can Bome Network Pro be used over long-distance internet as well?
I do have a static IP address and I am proficient in NAT port forwarding. Also, I don’t really care about latency as I would use it only for transport messages (play, stop, rewind).
Hi, yes it should work. It won’t do self discovery but as long as your router knows where to get to the remote device, you would manually add it. There is an area of the bottom of the Bome Network tool “Connect to IP address”.
After using Bome Network over the internet for more than a year now, I’ve noticed that the reliability varies wildly depending on the quality of internet connection.
In some cases it is flawless, in some others it skips a beat here and there, and yet, in some cases I have a feeling like every 3rd/4th message is missing.
Interestingly, other tools connected at the same time work much better or even without a hitch (WebRTC, Sonobus, Parsec…).
Hence my question: what protocol is Bome Network using? UDP? Is there a setting or a hack that could switch it to TCP maybe? Are there any plans to make it internet-resilient?
So it was Bome Network software version mismatch after all.
The server was running v1.6.0 while the client was running v1.4.1.
As soon as we updated the client to the latest version everything started working correctly.
Two things threw us off here:
the fact that the version-mismatched-connection did kind of work, just not 100% correctly
the fact that we had several clients connecting to the server simultaneously so we couldn’t see a clear picture. Once we had only the offending client connected and started comparing each and every parameter carefully, did we notice version mismatch.