1 Feb
2021
1 Feb
'21
6:32 p.m.
So, I made some progress over the weekend.... I have been able to get the 2 to connect
with the netmanager, but the source audio on the Windows machine is always sending audio
from the Mic, rather than system audio. I've tried EVERY option in the setup, using
Driver: portaudio, and every interface that is available (some won't even
'connect' and error out), but every time only the mic is picked up and transmitted
across the network.
How do I select the source on the Windows box to be the main system speakers? Am I
configuring the option wrong here? The documentation isn't very easy to follow, and
seems to be outdated and missing a lot of details. Any help here would be appreciated.
Thanks!
Yeah, I've tried snapcast/icecast, and other tools
meant for streaming, but
the latency is even worse. Like I said, there have been others that have done
it with older versions of Jack, but I'm not able to recreate their success with
the latest version. Here's an article from 2015;
https://blogs.gentoo.org/mgorny/2015/01/16/surround-sound-over-
network-with-windows-8/
I did see a note in the list somewhere that one of the most recent versions
didn't work with Windows 10, was that accurate, has it been resolved?
> I'm looking for a straightforward guide
on how to configure Jack as a
> network receiver on multiple Raspberry Pi’s, and Jack as a network
> sender on Windows.... so I can broadcast from Windows to multiple
> Pi's over LAN/Wifi. I'm planning on using this for distributing audio
> to speakers from a live playback and mixing system, so latency is critical.
I haven't tested this myself, but have you
looked at
https://github.com/badaix/snapcast ?
It seems targetted to media playback streaming, so I don't know whether it
will
meet your latency requirements.
_______________________________________________
JackAudio mailing list
JackAudio(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/jackaudio