From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pulseaudio - pipewire
Date: Wed, 03 Aug 2022 17:34:01 +0100 [thread overview]
Message-ID: <12036933.O9o76ZdvQC@lenovo.localdomain> (raw)
In-Reply-To: <CAK2H+ecO-+FX7NVaXDVCgF8fF15V3AS6+MN4a85wh-kr_-bxqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Wednesday, 3 August 2022 17:22:13 BST Mark Knecht wrote:
> On Wed, Aug 3, 2022 at 9:15 AM hitachi303 <gentoo-user@konstantinhansen.de>
>
> wrote:
> > Hi,
> >
> > so there is a eselect news "2022-07-29-pipewire-sound-server" telling
> > that changes have been made.
> >
> > I care about having sound but don't care to much about how it is
> > working. Any suggestions which path will lead me to the goal of having
> > the least trouble in future?
> > Like is pulseaudio going to disappear so I will have do switch anyway?
> > Is pipewire that new that it'll be buggy for the years to come?
> >
> > Regards
>
> Many other distros are using it without major problems.
>
> Ubuntu still ships PulseAudio for its long term version which is what I use
> but I've
> not heard of any problems with the leading edge version.
I've been using pipewire with default settings and USE="-pulseaudio" in
make.conf. It works fine for my basic needs.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-08-03 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:17 [gentoo-user] pulseaudio - pipewire hitachi303
2022-08-03 16:19 ` Matt Connell
2022-08-03 16:22 ` Mark Knecht
2022-08-03 16:34 ` Michael [this message]
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=12036933.O9o76ZdvQC@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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