I'm trying to share speakers with my desktop computer and Raspberry Pi 3 B+. Both machines should be able to play audio simultaneously.
--> is a connection that doesn't cross the boundary of a computer.
==> is a connection that occurs between two computers.
Anything that doesn't cross ==> occurs on my desktop computer. Anything that happens after ==> occurs on Raspberry Pi 3 B+.
netjack1 runs on my desktop computer. Ethernet cable is the only cable that connects two machines.
1. ALSA dmix --> SPDIF out of Realtek ALC887 onboard soundcard --> SPDIF In of X-Fi HD USB --(alsa_in or zita-a2j)--> netjack1 ==(ethernet cable)==> ALSA jack backend --> I2S Amplifier(HiFiBerry Amp2) --> Speakers
2. netjack1 --(alsa_out or zita-j2a)--> headphone jack of X-Fi HD USB on my desktop computer --> headphones
netjack1 can route audio to either headphones or HiFiBerry Amp2. I can control routing via a keyboard shortcut.
netjack1 can accept audio from alsa_in, zita-a2j, or just regular JACK clients like mpv.
Here are questions.
1. If SPDIF out of Realtek ALC887 onboard soundcard stops emitting clock signals, would the following audio route cause pops and clicks in alsa_out or zita-j2a?
mpv --> netjack1 --(alsa_out or zita-j2a)--> headhpone jack of X-Fi HD USB --> headphones
I suspect that if SPDIF out doesn't emit clock signals and the clock source for X-Fi HD is SPDIF, alsa_out can misbehave. If SPDIF out may not emit clock signals in the absence of audio signals, everything should be routed via SPDIF out.
2. If SPDIF out stops emitting clock signals in the absence of audio signals and starts emitting them again in the presence of audio signals, can alsa_in or alsa_out be confused and inject pops and clicks into audio?