From: sirn <sirn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.17
Date: Fri, 04 Dec 2020 14:18:13 +0100 [thread overview]
Message-ID: <20201204131813.bYp_2nSaJ5aJSRm-rSPsTohY_SxGAGx4L1FmQzLKKo8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26822@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
New comment by sirn on void-packages repository
https://github.com/void-linux/void-packages/pull/26822#issuecomment-738779151
Comment:
> I think just `libpipewire` is needed for that though. The spa plugins would go inside `pipewire` instead. Imho it's a bit confusing that some of these plugins are fundamental and others not.
You're right. I think it was this way due to transitional reasons (during 0.2 to 0.3)
> I'm curious about `libspa-control`, do you know what it does? I didn't notice any difference without it. But the name kinda suggests it is important.
I believe it provides mixer control, e.g. negotiating format and buffers size between components. Might not needed for pulseaudio protocol to work, but needed when doing some processing with SPAs (I believe).
> Yes, on the next update we should remove the `-Dpipewire-pulseaudio=true` option (now defaults to false) and make the `libpulseaudio-pipewire` subpkg an empty metapackage.
Yup! Quoting changelog:
> - Many pulse-server improvements. There is now a pipewire-pulse binary that is the prefered solution for PulseAudio compatibility. The replacement libpulse libraries are now deprecated. This also makes audio in Flatpak work.
so we should be safe to deprecate libpulseaudio-pipewire in Void as well (@ahesford what do you think?)
next prev parent reply other threads:[~2020-12-04 13:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 9:48 [PR PATCH] " st3r4g
2020-11-30 12:27 ` st3r4g
2020-11-30 12:28 ` st3r4g
2020-11-30 13:38 ` st3r4g
2020-11-30 13:41 ` st3r4g
2020-11-30 13:53 ` [PR PATCH] [Updated] " st3r4g
2020-11-30 15:09 ` [PR REVIEW] " ahesford
2020-11-30 15:44 ` st3r4g
2020-11-30 15:44 ` st3r4g
2020-11-30 15:46 ` st3r4g
2020-11-30 15:56 ` [PR PATCH] [Updated] " st3r4g
2020-11-30 16:01 ` st3r4g
2020-11-30 16:14 ` Javyre
2020-11-30 16:20 ` Javyre
2020-11-30 16:22 ` [PR REVIEW] " st3r4g
2020-11-30 16:23 ` st3r4g
2020-11-30 16:26 ` st3r4g
2020-11-30 16:26 ` st3r4g
2020-11-30 16:45 ` [PR REVIEW] " ericonr
2020-11-30 16:48 ` Javyre
2020-11-30 17:09 ` [PR REVIEW] " st3r4g
2020-11-30 19:21 ` st3r4g
2020-12-01 18:21 ` [PR REVIEW] " ahesford
2020-12-01 18:52 ` st3r4g
2020-12-01 19:14 ` ericonr
2020-12-01 20:39 ` [PR PATCH] [Merged]: " ahesford
2020-12-01 20:41 ` ahesford
2020-12-01 20:44 ` st3r4g
2020-12-02 20:13 ` gspe
2020-12-03 4:48 ` ahesford
2020-12-04 12:04 ` sirn
2020-12-04 12:37 ` st3r4g
2020-12-04 12:37 ` st3r4g
2020-12-04 12:42 ` st3r4g
2020-12-04 12:45 ` st3r4g
2020-12-04 13:18 ` sirn [this message]
2020-12-04 14:35 ` gspe
2020-12-04 15:11 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201204131813.bYp_2nSaJ5aJSRm-rSPsTohY_SxGAGx4L1FmQzLKKo8@z \
--to=sirn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).