Neal Gompa wrote:
> What are you talking about? I seem to be able to select devices and
> such. The only thing I don't seem to be able to do is do "advanced
> audio settings" which is grayed out and says it requires the
> PulseAudio gsettings module.
It turns out that the relevant settings have al
On Tue, Feb 23, 2021 at 3:13 PM Neal Gompa wrote:
> On Tue, Feb 23, 2021 at 8:16 AM Kevin Kofler via devel
> wrote:
> >
> > Lóránt Perger wrote:
> > > I suppose I should have looked a bit more into this before opening this
> > > thread, but oh well, no use crying over spilled milk. I looked into
On Tue, Feb 23, 2021 at 8:16 AM Kevin Kofler via devel
wrote:
>
> Lóránt Perger wrote:
> > I suppose I should have looked a bit more into this before opening this
> > thread, but oh well, no use crying over spilled milk. I looked into how PW
> > replicates PA's module loading... and turns out it d
Lóránt Perger wrote:
> I suppose I should have looked a bit more into this before opening this
> thread, but oh well, no use crying over spilled milk. I looked into how PW
> replicates PA's module loading... and turns out it doesn't (
> https://github.com/PipeWire/pipewire/blob/master/src/modules/m
> Well, if the modules can work with PipeWire's PulseAudio replacement, then
> they ought to be in a subpackage of pulseaudio, yes. (But are they
> binary-compatible or do they actually need to be rebuilt against
> pipewire-pulseaudio?)
>
> Kevin Kofler
I suppose I should have looked a
Lóránt Perger wrote:
> I would like to ask about the developers' stance towards supporting
> PulseAudio plugins when using `pipewire-pulseaudio`. On some other
> mainstream distributions this can easily be achieved as the modules are
> packaged with the PA pipewire replacement package, however, in
