From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "François Revol" <revol@free.fr>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] spice: add audio
Date: Wed, 10 Nov 2010 11:50:23 +0000 [thread overview]
Message-ID: <20101110115023.GM11830@redhat.com> (raw)
In-Reply-To: <4CDA83E0.1070704@redhat.com>
On Wed, Nov 10, 2010 at 12:37:04PM +0100, Gerd Hoffmann wrote:
> On 11/10/10 11:36, Daniel P. Berrange wrote:
> >On Wed, Nov 10, 2010 at 10:48:39AM +0100, Gerd Hoffmann wrote:
> >>The qemu vnc server has support already, and I think Daniel (added to
> >>Cc:) has some experimental patches for the gtk-vnc widget.
> >
> >Yes I do have patches, but I'm yet to get it to work reliably enough for
> >anyone to use for real. eg any time there are large frambuffer updates
> >due to, say, dragging a window around, audio will drop out. Until I can
> >prove that it is even semi-reliable I'm not going to include the code in
> >gtk-vnc, because I don't want to commit to supporting something that may
> >well be fundamentally broken/unusable for live audio playback.
>
> Do you know where the dropouts come from?
Not entirely, it is still rather work in progress to debug it.
Part of the issues is that even QEMU + one of the standard
pulseaudio/alsa/sdl audio backends doesn't seem very reliable
to me, so I've not got a reliable benchmark to compare VNC
audio against. Just testing with mpg123 in the guest, audio
will often simply stop after a few seconds of playback to the
host.
> I think one issue are latencies within qemu. The qemu vnc server is
> busy for a while when doing bulky screen updates and blocks other stuff
> while it runs. I've seen dropouts with vnc + bulky screen updates too.
> The smaller the audio buffers used by the device/guest are the more
> visible this effect is. When enabling the threaded vnc server this
> becomes alot better, did you try that?
It looks like the threaded server is disabled by default, so I've
not been using it thus far. I'll give it a try though.
Is there a particular audio device that is considered to work 'best' ?
I've been using ac97 mostly, but if your new ICH6 device is thought
to be significantly better I'll try that instead.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-11-10 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101109211021.45EC22A34D@zimbra14-e2.priv.proxad.net>
2010-11-09 22:27 ` [Qemu-devel] Re: [PATCH] spice: add audio François Revol
2010-11-09 23:31 ` malc
2010-11-10 9:48 ` Gerd Hoffmann
2010-11-10 10:36 ` Daniel P. Berrange
2010-11-10 11:37 ` Gerd Hoffmann
2010-11-10 11:50 ` Daniel P. Berrange [this message]
2010-11-10 13:21 ` Gerd Hoffmann
2010-11-09 16:29 [Qemu-devel] " Gerd Hoffmann
2010-11-09 16:36 ` [Qemu-devel] " malc
2010-11-09 16:56 ` Gerd Hoffmann
2010-11-09 17:35 ` malc
2010-11-09 20:55 ` malc
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=20101110115023.GM11830@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=revol@free.fr \
/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).