search

sonosaurus / sonobus

Source code for SonoBus, a real-time network audio streaming collaboration tool.
https://sonobus.net
GNU General Public License v3.0
1.55k stars 114 forks source link

Bug / unhandled: the other party is muted ? #121

Open AtmanActive opened 2 years ago

AtmanActive commented 2 years ago

I've been using Sonobus for months now to DAW-audio-collaborate with a friend half way across the globe, and it all worked flawlessly. But, the other day, just like that, it stopped working with the message "the other party is muted" shown on both ends. I suspect some ISP or home router got moody all of a sudden and I will keep investigating, but right now I'm wondering:

Is this a known issue? Is there something that would help me diagnose the problem?

Thanks.

essej commented 2 years ago

Has that persisted with that specific individual when you’ve tried to connect with them again at other times?

mixticninja commented 2 years ago

He, thanks for this great application. I was trying to use the sonobus vst2 as a filter in OBS and connect it to another windows PC running Sonobus standalone on my local network : the standalone app was always displaying "the other party is muted" with no sound transferred, it was working perfectly when i used the 2 apps in standalone. Perhaps same kind of problem ?

AtmanActive commented 2 years ago

So we restarted the modem/router at my friend's house and Sonobus started working properly again.

However, we did notice some weird behavior:

Windows exe (A) to windows exe (B) - B can send to A as expected, but when A tries to send compressed audio to B, B gets "other party is muted". When A tries to send PCM to B, then it all looks fine but there is no audio whatsoever. Buffers are rolling, packets are being counted - no audio.

Windows VST3 (B) to windows exe (A) - everything working just fine in both directions be it opus or PCM.

I wish I had some kind of signal generator built into Sonobus...

musician1 commented 1 year ago

I'm having similar kind of issues and I created a ticket here. Your post made me think that it may be related to router port forwarding (which I did not do) or a firewall..? But then it's wired that it works sometimes...

strk commented 1 year ago

I've had similar problems today while using 3 sonobus instances on 3 devices within the same LAN. Each of them was configured to use a specific UDP port always static and a different port each. Sometimes disconnecting and re-connecting helps. I'm not clear whether the aoo server receives ALL IP addresses or which one (as for LAN only routing I think I saw the local IP used, but not sure how that was possible)

essej commented 1 year ago

The local IPs are also sent to the server (and propagated to the clients), and they generally win the "race" for connection when the clients are all on the same LAN... this is how it works so that intra-LAN clients can use the best routing. However, this can also mean that when you have multiple IP addresses on your LAN (eg, both ethernet and wifi) active at the same time, weird routing issues can occur. Always best to make sure there is only one active IP for your machine on your local LAN (eg, turn off wifi).