Jesse Chappell
Jesse Chappell
Yep, I know what's going on here. I'm working on an update of the android version (which hasn't been updated in a looong time) to solve that, plus lets file...
Should be fixed now in the latest released version 1.6.1...
Interesting idea!
> Did you have "always use same UDP port" selected, by any chance ? As I believe the UDP port is what makes sonobus distinguish users This is not accurate...
No, it doesn't, it requires C++17 to build. Perhaps I need to make sure CMake doesn't let the configuration succeed without that, but I thought that it would.
I know, the way JUCE presents JACK in the standalone is really not suitable for the best use of JACK. It would take some redesign work to present it more...
> I'm not sure this is the appropriate ticket to request this feature or if I should file a new issue but would a redesign also allow us to define...
The issue here is that only the standalone version runs a local connection server, the plugins do not. So the simple solution for you is just to start a standalone...
AOO which SonoBus is based on uses a single UDP port, mostly to keep NAT traversal simpler. I’d be interested to hear more about your technique’s advantages…
Interesting, SonoBus is purely peer-to-peer, there is no server involved in the audio transmission path, so I don't know if what you are doing will be quite as relevant here....