Use SonoBus to expose DAW tracks to AUM

espiegel123

Did a little testing. With WiFi turned off, using address127.0.0.1 works, and there did not seem to be a performance benefit over using it for a private group consisting of just my iPad with WiFi on. Latency is about 25 ms for both setups for me. This was sending 6 channels of 24-bit audio from AUM to NS2

rs2000

@sonosaurus said:

@rs2000 said:
@espiegel123 SonoBus uses version 2 of AoO, the Audio over OSC library. I've just checked the repo and found this:

• aoo_sink buffer helps to deal with network jitter, packet reordering and packet loss at the cost of latency. The size can be adjusted dynamically.
• aoo_sink can ask the source(s) to resend dropped packets, the settings are free adjustable.

It would be good to know if SonoBus can use these features, I haven't found anything in the settings.

Yes, it uses these features, but it can really only take advantage of them if you use a large enough jitter buffer so there is actually time for resending.

That's excellent news, thank you!! 👍🏼😊
Using a larger buffer isn't a problem because the audio track recorded at the destination has to be moved back in time anyway.

[Deleted User]

@sonosaurus said:

@arktek said:
OK. Got it to work. First test - I have the iPad and the MacBook connected via an Ethernet cable. I created a manual IP address for both of them so they are on the same subnet and so that I don't have to think about what address they are on. I opened the standalone application of Sonobus on the Mac and left it alone. I then opened Bitwig on the Mac and AUM on the iPad. Inserted a Sonobus instance on an audio channel in Bitwig and one in an AUM channel with an instance of Gauss as the sound source. Set my Ethernet addresses manually on both the Mac and the iPad so that they are in the same subnet. Pointed each inserted instance at the Mac Ethernet IP address with port 10999 (in this instance 192.168.9.2:10999) in the server field and hit connect on both of them. Audio received in Bitwig. Seems to be pretty clean on PCM 24 bit. Latency is around 15 to 16 each way. The jitter buffer is 13ms. So as a basic first test it works. I'll now go ahead and test multiple channels and sending from the Mac to the iPad which should just work I would think. Starting to get a little bit excited. 🙃
I discovered that I don't need to actually do anything with the standalone app except open it to have it work as the server. I was prepared to build the SOO server from the Github source but it looks like I might not have to.
The bonus part for the Ethernet connection is that I can run Ableton Link to sync things. Not sure what this will do to the audio connection, but that's part of the fun isn't it?

By the way you don't need to use the local connection server in your standalone version, no audio goes through it, it has no bearing on latency at all. You can use the default aoo.sonobus.net server with no ill effects if you are connected to the internet, which just means a bit less typing and IP address finding. The only advantage to using your own is no need to actually be on the internet.

I understand that. The problem for me in this scenario is that I am currently using my phone as a personal hotspot. When I connect my iPad and MacBook to this I then have issues with my Ethernet connection and the Sonobus app doesn't want to behave. I know with a bit more messing around I could probably get it to work OK, but it's not as smooth as keeping my network connection through one interface. It seems to be a much smoother process if I just use the local server in this instance.