qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <mlevitsk@redhat.com>
To: "Zoltán Kővágó" <dirty.ice.hu@gmail.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] audio: paaudio: fix client name
Date: Mon, 26 Aug 2019 23:58:14 +0300	[thread overview]
Message-ID: <7d92f795d80ae7a2bc2db9f7af6ae7e20ff5d3b1.camel@redhat.com> (raw)
In-Reply-To: <8ca01890-b337-6590-c415-48563ca938d1@gmail.com>

On Mon, 2019-08-26 at 21:28 +0200, Zoltán Kővágó wrote:
> On 2019-08-26 10:21, Maxim Levitsky wrote:
> > On Mon, 2019-08-26 at 02:29 +0200, Kővágó, Zoltán wrote:
> > > pa_context_new expects a client name, not a server socket path.
> > > 
> > > Signed-off-by: Kővágó, Zoltán <DirtY.iCE.hu@gmail.com>
> > > ---
> > >  audio/paaudio.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/audio/paaudio.c b/audio/paaudio.c
> > > index bfef9acaad..777b8e4718 100644
> > > --- a/audio/paaudio.c
> > > +++ b/audio/paaudio.c
> > > @@ -866,7 +866,7 @@ static void *qpa_conn_init(const char *server)
> > >      }
> > >  
> > >      c->context = pa_context_new(pa_threaded_mainloop_get_api(c->mainloop),
> > > -                                server);
> > > +                                "qemu");
> > >      if (!c->context) {
> > >          goto fail;
> > >      }
> > 
> > Also tested, and this works.
> > 
> > May I suggest though to make this configurable as well, for the sake of
> > usability since gnome sound settings show only the client name, and it
> > is per each sound card.
> > Although on the other thing the client name is qemu.
> 
> There is a small problem with that.  Currently we only open one
> connection to pa, even with multiple -audiodevs (they will just create
> different streams), which means we can only use a single client name per
> qemu process.  Because of that, I wouldn't turn this into an audiodev
> property.  Some other kind of global setting could work, but I'm not
> sure whether it's worth it or not.
> 
> Regards,
> Zoltan

All right.
We could use the VM name for that though, so that at least multiple VMs
would show up as different client.


Best regards,
	Maxim Levitsky





  reply	other threads:[~2019-08-26 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  0:29 [Qemu-devel] [PATCH 0/3] Audio: misc fixes for "Audio 20190821 patches" Kővágó, Zoltán
2019-08-26  0:29 ` [Qemu-devel] [PATCH 1/3] audio: omitting audiodev= parameter is only deprecated Kővágó, Zoltán
2019-08-26  8:31   ` Maxim Levitsky
2019-08-26  0:29 ` [Qemu-devel] [PATCH 2/3] audio: paaudio: fix client name Kővágó, Zoltán
2019-08-26  8:21   ` Maxim Levitsky
2019-08-26 19:28     ` Zoltán Kővágó
2019-08-26 20:58       ` Maxim Levitsky [this message]
2019-08-26  0:29 ` [Qemu-devel] [PATCH 3/3] audio: paaudio: ability to specify stream name Kővágó, Zoltán
2019-08-26  8:14   ` Maxim Levitsky

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=7d92f795d80ae7a2bc2db9f7af6ae7e20ff5d3b1.camel@redhat.com \
    --to=mlevitsk@redhat.com \
    --cc=dirty.ice.hu@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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).