<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 25/01/22 23:02, Paul Davis wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFa_cKkikXS3beTODLsOcRhChbC97QuRWBVC=y4Z2GAkK-AfLA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">On Tue, Jan 25, 2022 at 3:37 PM Jeanette C. <<a
href="mailto:julien@mail.upb.de" moz-do-not-send="true">julien@mail.upb.de</a>>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Jan 25 2022, Paul Davis
has written:<br>
...<br>
> There's some confusion here.<br>
><br>
> Pipewire *reimplements* JACK, it does not connect to
JACK.<br>
I am referring to the JACK bridge as described here:<br>
<a
href="https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Config-JACK#jack-bridge"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Config-JACK#jack-bridge</a><br>
Seeing that my soundcard setup is a little complicated, I'd
much rather<br>
start with that, having my normal audio in tact, until I
work out how to<br>
solve that issue.<br>
</blockquote>
<div><br>
</div>
<div>Again, PipeWire *is* JACK and it is also PulseAudio. It <span
class="gmail-Lm gmail-ng">it not</span> a replacement for
PulseAudio, it is a replacement for both of them. Once you
are using PipeWire, everything you've read about JACK
bridging etc. becomes incorrect and irrelevant.</div>
<br>
</div>
</div>
</blockquote>
<p>You can though keep your existing JACK setup and bring pipewire
into it, pipewire then becomes a regular JACK client.<br>
Might be useful if one wants to experiment with pipewire early, or
use pipewire's pulseaudio stuff instead of pulseaudio directly.</p>
<p><br>
</p>
</body>
</html>