Re: Don't ever bother with bridging JACK with ALSA or Pulseaudio.

--===============6109506248796005986==
Content-Type: multipart/alternative; boundary="0000000000002320df059263406c"

--0000000000002320df059263406c
Content-Type: text/plain; charset="UTF-8"

I used SPDIF output and SPDIF input to eliminate dropped samples and xruns
from ALSA loopback.
It was impossible to eliminate dropped samples and xruns rom ALSA loopback.

On Fri, Sep 13, 2019 at 2:16 AM Chris Caudle <[email protected]> wrote:

> On Thu, September 12, 2019 8:05 am, crocket wrote:
> > I've spent months on perfecting the bridge between JACK and ALSA.
>
> I think you have created the most complex monitor controller ever.  This
> is that system that has S/PDIF from the motherboard audio to digital input
> on a USB connected interface that you described earlier?
>
> -----------------------------
> --> 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
>
> -----------------------------
>
> Is this being used for music production, or just listening to audio files?
> PulseAudio can do something similar in a self-contained fashion, at the
> expense of higher latency and the occasional dropped sample.  And of
> course the old fashioned way to do it would be with an analog monitor
> controller or small mixer.  The more modern audio production focused way
> would be to use Dante or similar if you really want network connectivity,
> or the ability to add and remove devices, have large distance separation,
> etc.
>
> My recollection is that the questions you posed were somewhat isolated,
> and mostly how to accomplish various specific tasks with jackd or alsa.
> It may have been better to start with a more general description of what
> you were trying to accomplish and ask about the best way to get to that
> result, because I can't imagine anyone recommending that convoluted signal
> chain just for listening to audio from your desktop and a separate
> computer (RPi in your case) at the same time.  Using an on board audio
> interface just to send audio over S/PDIF to a USB interface to drive
> headphones seems pretty bizarre, I never could make sense of what you were
> trying to accomplish with that rather than just sending audio to the USB
> interface to start with.
>
>
> --
> Chris Caudle
>
>
>
>
> _______________________________________________
> Jack-Devel mailing list
> [email protected]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

--0000000000002320df059263406c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I used SPDIF output and SPDIF input to eliminate dropped s=
amples and xruns from ALSA loopback.<div>It was impossible to eliminate dro=
pped samples and xruns rom ALSA loopback.</div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Sep 13, 2019 at 2:16=
 AM Chris Caudle &lt;<a href=3D"mailto:[email protected]">chris@chrisca=
udle.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">On Thu, September 12, 2019 8:05 am, crocket wrote:<br>
&gt; I&#39;ve spent months on perfecting the bridge between JACK and ALSA.<=
br>
<br>
I think you have created the most complex monitor controller ever.=C2=A0 Th=
is<br>
is that system that has S/PDIF from the motherboard audio to digital input<=
br>
on a USB connected interface that you described earlier?<br>
<br>
-----------------------------<br>
--&gt; is a connection that doesn&#39;t cross the boundary of a computer.<b=
r>
=3D=3D&gt; is a connection that occurs between two computers.<br>
<br>
Anything that doesn&#39;t cross =3D=3D&gt; occurs on my desktop computer. A=
nything<br>
that happens after =3D=3D&gt; occurs on Raspberry Pi 3 B+.<br>
netjack1 runs on my desktop computer. Ethernet cable is the only cable<br>
that connects two machines.<br>
<br>
1. ALSA dmix --&gt; SPDIF out of Realtek ALC887 onboard soundcard --&gt; SP=
DIF<br>
In of X-Fi HD USB --(alsa_in or zita-a2j)--&gt; netjack1 =3D=3D(ethernet<br=
>
cable)=3D=3D&gt; ALSA jack backend --&gt; I2S Amplifier(HiFiBerry Amp2) --&=
gt; Speakers<br>
<br>
2. netjack1 --(alsa_out or zita-j2a)--&gt; headphone jack of X-Fi HD USB on=
<br>
my desktop computer --&gt; headphones<br>
<br>
-----------------------------<br>
<br>
Is this being used for music production, or just listening to audio files?<=
br>
PulseAudio can do something similar in a self-contained fashion, at the<br>
expense of higher latency and the occasional dropped sample.=C2=A0 And of<b=
r>
course the old fashioned way to do it would be with an analog monitor<br>
controller or small mixer.=C2=A0 The more modern audio production focused w=
ay<br>
would be to use Dante or similar if you really want network connectivity,<b=
r>
or the ability to add and remove devices, have large distance separation,<b=
r>
etc.<br>
<br>
My recollection is that the questions you posed were somewhat isolated,<br>
and mostly how to accomplish various specific tasks with jackd or alsa. <br=
>
It may have been better to start with a more general description of what<br=
>
you were trying to accomplish and ask about the best way to get to that<br>
result, because I can&#39;t imagine anyone recommending that convoluted sig=
nal<br>
chain just for listening to audio from your desktop and a separate<br>
computer (RPi in your case) at the same time.=C2=A0 Using an on board audio=
<br>
interface just to send audio over S/PDIF to a USB interface to drive<br>
headphones seems pretty bizarre, I never could make sense of what you were<=
br>
trying to accomplish with that rather than just sending audio to the USB<br=
>
interface to start with.<br>
<br>
<br>
-- <br>
Chris Caudle<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Jack-Devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Jack-De=
[email protected]</a><br>
<a href=3D"http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org=
" rel=3D"noreferrer" target=3D"_blank">http://lists.jackaudio.org/listinfo.=
cgi/jack-devel-jackaudio.org</a><br>
</blockquote></div>

--0000000000002320df059263406c--

--===============6109506248796005986==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Jack-Devel mailing list
[email protected]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

--===============6109506248796005986==--