<div dir="ltr">It seems I should just save headaches and use only ALSA for local audio devices.<div>This means I am going to use a pair of good speakers for my desktop computer and a pair of cheap speakers for Raspberry Pi.</div><div>Raspberry Pi will be responsible for turning on and off speakers via relays.</div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 29, 2019 at 12:46 AM Len Ovens <<a href="mailto:len@ovenwerks.net">len@ovenwerks.net</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 28 Mar 2019, crocket wrote: > On Thu, Mar 28, 2019 at 4:06 PM Len <<a href="mailto:len@ovenwerks.net" target="_blank">len@ovenwerks.net</a>> wrote: > Jack can not use two devices. speakers (via some kind of on board > audio > device I assume) and the usb mic will not be in sync and so clicks > and > pops would be assured. Some kind of sample rate conversion would be > needed. zita-ajbridge or alsa-in would work for that. > > > Can I not just run two jack servers on Raspberry Pi? How would that help you? As soon as you want to use the mic and your speakers with the same application you will have under and over runs between one and the other. The only way around that is to use SRC which can be provided by either zita-ajbridge or alsa-in/out (the second comes with jack, but the first is better and may now be a part of jackd1). Do note that using netjack with the device on the Pi means that the internal audio on your desktop can't be used at the same time for the same reason. The backend for the jack server on your desktop is the jack server on the Pi so any audio device on your desktop would also have to be added via an SRC client such as zita-ajbridge or alsa_in/out. This means you desktop relies on your Pi for a solid sync... if you are usng your desktop audio for anything important that requires solid sync, I would use the local device as backend and use zita-njbridge to join the two jack servers on the two machines. > My Gentoo Linux desktop doesn't have pulseaudio. It only has ALSA at this moment. > I do not want pulseaudio. No problem (no skype either, but you may not need it) Lots of people use a jack to alsa bridge > I want the voices to not lag too much behind the lips. > > I just want Raspberry Pi and my desktop to share my speakers. Raspberry Pi will > serve as a morning alarm, and I need to watch videos on my desktop computer. > I use a USB microphone for foreign language practice and audio calls. That is what pulse (and the up and coming... maybe, Pipewire) is made for, but lots of people do not want to use it, Jack with alsa will get you there too. Latency shouldn't be a problem for that use, even with jack running 1024/2, though 128/2 should still be stable abd much better. > I can technically buy a USB hub that supports per-port power switching to have my > USB microphone turned off most of the time. > But, since Raspberry Pi 3 B+ supports per-port power switching, I wanted to know > whether I could use Raspberry Pi as a network USB hub or a network USB > microphone. Not sure I know what you mean by that... if any of my guesses are right, the answer is I don't know. -- Len Ovens <a href="http://www.ovenwerks.net" rel="noreferrer" target="_blank">www.ovenwerks.net</a> _______________________________________________ Linux-audio-user mailing list <a href="mailto:Linux-audio-user@lists.linuxaudio.org" target="_blank">Linux-audio-user@lists.linuxaudio.org</a> <a href="https://lists.linuxaudio.org/listinfo/linux-audio-user" rel="noreferrer" target="_blank">https://lists.linuxaudio.org/listinfo/linux-audio-user</a> </blockquote></div>