On 1/7/21 5:52 PM, Neal Gompa wrote:
> On Thu, Jan 7, 2021 at 5:51 PM Mukundan Ragavan <nonamedotc@gmail.com> wrote:
>>
>>>
>>
>> There is a problem in doing this. If we move to pulseaudio-daemon, we
>> lose our current volume mixer - pavucontrol (which, I am sure requires
>> pulseaudio and is not generic). Other DEs, as far as I know (i.e. GNOME,
>> MATE, and Cinnamon), have their own mixers. pulseaudio-plugin relies on
>> an external mixer.
>>
>> I would prefer not to move to without a suitable replacement for
>> pavucontrol - if we can avoid it. Does pipewire provide a suitable
>> replacement for pavucontrol?
>>
>> Does this make sense?
>>
>
> pavucontrol works fine with PipeWire. The libpulse library interacts
> with the PipeWire-PulseAudio daemon just fine, and everything
> basically works.
>
>
>
In that case, I can definitely change it.
I remember seeing something like this -
Problem: problem with installed package
pulseaudio-module-x11-14.0-2.fc33.x86_64
- package pulseaudio-module-x11-14.0-2.fc33.x86_64 requires
libpulsecore-14.0.so()(64bit), but none of the providers can be installed
- package pulseaudio-module-x11-14.0-2.fc33.x86_64 requires
pulseaudio(x86-64) = 14.0-2.fc33, but none of the providers can be installed
- package pulseaudio-module-x11-13.99.2-1.fc33.x86_64 requires
libprotocol-native.so()(64bit), but none of the providers can be installed
This is from my test VM but let me check again.
--
GPG Key: E5C8BC67
No comments:
Post a Comment