1 |
On Monday, 3 October 2022 22:48:09 BST Håkon Alstadheim wrote: |
2 |
> Den 02.10.2022 11:47, skrev Michael: |
3 |
> > On Saturday, 1 October 2022 19:32:11 BST Daniel Sonck wrote: |
4 |
> >> On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote: |
5 |
> >>> On 01/10/2022 17:56, Michael wrote: |
6 |
> >>>> Anyway, I ventured into pipewire because I wanted to see if Skype would |
7 |
> >>>> work without pulseaudio and in this system it won't. After I manually |
8 |
> >>>> installed pipewire Skype won't access the microphone. 🙁 |
9 |
> >>> |
10 |
> >>> I've got some vague feeling that pipewire is designed to happily sit |
11 |
> >>> under pulseaudio. The design aim was to replace both Jack and pulseaudio |
12 |
> >>> but it basically just presents a sound device to the layers above, so |
13 |
> >>> just like you can stack block devices for disk access, you can stack |
14 |
> >>> jack, pulseaudio and pipewire for sound. |
15 |
> >> |
16 |
> >> Well, it is actually designed as a drop-in replacement and won't present |
17 |
> >> audio devices in the sense pulseaudio wants to receive it. I guess it |
18 |
> >> would |
19 |
> >> theoretically be possible to use pulseaudio's jack sink to talk to |
20 |
> >> pipewire, but pipewire has the full pulseaudio interface for pulseaudio |
21 |
> >> applications. |
22 |
> > |
23 |
> > At the moment only some applications support PipeWire's native API, but |
24 |
> > most support PulseAudio's API. When you come across an application like |
25 |
> > Skype which expects PulseAudio, the solution is to enable |
26 |
> > USE="sound-server pipewire-alsa" for PipeWire and in addition to PipeWire |
27 |
> > also install media- libs/libpulse. No other PulseAudio packages are |
28 |
> > needed. |
29 |
> |
30 |
> To get that, I seem to need media-sound/pulseaudio (meta package) with |
31 |
> USE="-daemon" |
32 |
|
33 |
This USE flag setting would be required if you use pulseaudio (I don't have it |
34 |
installed) and need to avoid it fighting with pipewire over control |
35 |
of audio devices. |
36 |
|
37 |
At the present moment, because the migration to pipewire is work-in-progress, |
38 |
there are a number of options available to cover all use cases, depending on |
39 |
your system configuration and init system: |
40 |
|
41 |
https://www.gentoo.org/support/news-items/2022-07-29-pipewire-sound-server.html |