23 May
2017
23 May
'17
12:48 p.m.
On 2017-05-23 18:22, Hanspeter Portner wrote:
On 23.05.2017 16:50, jack-devel(a)malikc.neomailbox.net
wrote:
Thanks for the reply!
So your view is that packet loss is the cause? I had naïvely assumed it
might be due to latency or congestion, but packet loss would make a lot
of sense. Although -- I hadn't mentioned this explicitly, but my setup
is with both boxes connected on the same local network, in other words
both to the same WiFi router; can there really be such a dramatic amount
of packet loss in that context for the result to be completely garbled
sound? I'm not talking about clicks here and there, but really little
better than static. I wouldn't have expected that; although at the same
time I'm no networking expert...
If so, then I guess what you're saying is that there's simply no way to
leverage NetJack, whether NetJack1 or NetJack2, for transport over
wireless?
Regards,
mc.
...But it only works great over Ethernet. And
I'd very much like it to
work over WLAN, which it doesn't. Over wireless, the sound is completely
garbled. AFAICT, it's a network issue.
NetJACK sends its audio data via UDP [1], e.g. there's no resending of lost
packets like in TCP. If packets are lost (which is *very* likely over wireless),
the packets are really lost and you miss a chunk of audio frames, hence your
garbled sound at the receiver.
That being said, reading the doc and looking
around the web for info
suggests it might very well be the case that NetJack2 simply isn't
suited for WLAN transport. Indeed, some resources indicate that NetJack1
would be more adapted.
Same problem there...
[1]
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…