1 |
On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote: |
2 |
> On 01/10/2022 17:56, Michael wrote: |
3 |
> > Anyway, I ventured into pipewire because I wanted to see if Skype would |
4 |
> > work without pulseaudio and in this system it won't. After I manually |
5 |
> > installed pipewire Skype won't access the microphone. 🙁 |
6 |
> |
7 |
> I've got some vague feeling that pipewire is designed to happily sit |
8 |
> under pulseaudio. The design aim was to replace both Jack and pulseaudio |
9 |
> but it basically just presents a sound device to the layers above, so |
10 |
> just like you can stack block devices for disk access, you can stack |
11 |
> jack, pulseaudio and pipewire for sound. |
12 |
Well, it is actually designed as a drop-in replacement and won't present audio devices in the |
13 |
sense pulseaudio wants to receive it. I guess it would theoretically be possible to use |
14 |
pulseaudio's jack sink to talk to pipewire, but pipewire has the full pulseaudio interface for |
15 |
pulseaudio applications. |
16 |
> |
17 |
> The big difference between a sound stack and a block stack is that a |
18 |
> block stack is asynchronous and latency is (relatively) unimportant. In |
19 |
> a sound stack some applications *demand* synchronicity, and latency is |
20 |
> everything. Jack is extremely latency sensitive, pulseaudio buffers and |
21 |
> doesn't care, and pipewire is intended to satisfy both. |
22 |
> |
23 |
> So the intent was clearly to install pipewire underneath a working |
24 |
> pulseaudio, and just move applications across as and when. |
25 |
This was never an intent, pipewire was intended as an pulseaudio implementation by itself. So |
26 |
it doesn't need (and likely is incompatible running together with) pulseaudio in order to |
27 |
support pulseaudio clients. But it does need to be configured as such. |
28 |
> |
29 |
> Cheers, |
30 |
> Wol |
31 |
|
32 |
Regards, |
33 |
|
34 |
Daniel |