From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Dorinda Bassey <dbassey@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-devel@nongnu.org, kraxel@redhat.com, armbru@redhat.com,
pbonzini@redhat.com, wtaymans@redhat.com,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Subject: Re: [PATCH] audio/pwaudio.c: Add Pipewire audio backend for QEMU
Date: Wed, 15 Feb 2023 15:08:54 +0100 [thread overview]
Message-ID: <5159868.WgR6L5i3FV@silver> (raw)
In-Reply-To: <CAJ+F1CL0_OAj5-jsyCVY5aF=qoSoPx2Mu=q8Z7mpp3mesRi6=Q@mail.gmail.com>
On Wednesday, February 15, 2023 2:18:50 PM CET Marc-André Lureau wrote:
> Hi
>
> On Wed, Feb 15, 2023 at 12:51 PM Dorinda Bassey <dbassey@redhat.com> wrote:
> >
> > This commit adds a new audiodev backend to allow QEMU to use Pipewire as
both an audio sink and source. This backend is available on most systems.
> >
>
> Hmm, I would rather have less audio (and ui) backends in QEMU. (for
> audio, if I could introduce and keep only one, that would be
> GStreamer: to remove the others..)
>
> What is the main advantage compared to using the ALSA backend? (I
> assume pipewire depends on ALSA anyway on Linux)
I think it does make sense to add Pipewire. Apparently it gains popularity.
The main advantage of Pipewire is its interoperability: It allows you to
connect apps with each other that only support a specific audio system. Say
one app that only supports JACK, another app that only supports PulseAudio,
another that only supports ALSA and so on. So it tries to provide a universal
plug on a system for all.
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2023-02-15 14:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 8:51 [PATCH] audio/pwaudio.c: Add Pipewire audio backend for QEMU Dorinda Bassey
2023-02-15 11:26 ` Daniel P. Berrangé
2023-02-15 13:14 ` Dorinda Bassey
2023-02-16 10:33 ` Michael Tokarev
2023-02-16 10:47 ` Daniel P. Berrangé
2023-02-15 13:18 ` Marc-André Lureau
2023-02-15 14:08 ` Christian Schoenebeck [this message]
2023-02-15 14:11 ` Marc-André Lureau
2023-02-15 15:08 ` Daniel P. Berrangé
2023-02-15 15:09 ` Dorinda Bassey
2023-02-16 11:43 ` Gerd Hoffmann
2023-02-15 15:11 ` Gerd Hoffmann
2023-02-15 15:46 ` Dorinda Bassey
2023-02-15 15:59 ` Daniel P. Berrangé
2023-02-16 11:53 ` Christian Schoenebeck
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 9:23 Dorinda Bassey
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=5159868.WgR6L5i3FV@silver \
--to=qemu_oss@crudebyte.com \
--cc=armbru@redhat.com \
--cc=dbassey@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wtaymans@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.