From: malc <av1474@comtv.ru>
To: Alberich de megres <alberich2k5@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Audio latency
Date: Thu, 11 Feb 2010 11:42:03 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1002111137420.3762@linmac> (raw)
In-Reply-To: <12d708831002102303t777e6f83g563311cc0f9cf1a1@mail.gmail.com>
On Thu, 11 Feb 2010, Alberich de megres wrote:
> On Thu, Feb 11, 2010 at 7:53 AM, malc <av1474@comtv.ru> wrote:
> > On Thu, 11 Feb 2010, Alberich de megres wrote:
> >
> >> I'm using the alsa driver.
> >> Even I tried to change some values using the export and some flags
> >> that -audio-help shows, but nothing significant.
> >
> > Please do not top post.
>
> Sorrry!!
>
> >
> >>
> >>
> >> On Thu, Feb 11, 2010 at 1:03 AM, malc <av1474@comtv.ru> wrote:
> >> > On Thu, 11 Feb 2010, Alberich de megres wrote:
> >> >
> >> >> Hi!
> >> >>
> >> >> I'm running qemu on suse, and i got a very high audio latency. For
> >> >> example, using windows latency is about 4s and audio gets distorted
> >> >> with little cuts.
> >
> > How do you measure it?
> With a program called dpc latency, it's for windows.
>
> >
> >> >> On the host side (suse), i changed the audio pci device latency to 99
> >> >> but this only improves a little bit.
> >
> > As in: with setpci?
> Yes. I also tired, on host, to low latency to VGA to 10.
That's completely unrelated latency [1]
> >
> >> >> Other thing i noticed is when lowering video resolution, the audio
> >> >> latency gets better and better.
> >
> > Lowering video resolution of what? Guest, host?
>
> Yes, it was on guest. Even for example if i change the desktop or
> switch to a text terminal when things works better what suggested me
> that could be something with painting the screen. But i'm not shure if
> its just only a side effect of a bad launch command, or something
> else.
>
> >
> >> >> I started played with source code, but i'm just a newbie on qemu.
> >> >> Anyone can point some light to me please?
> >> >>
> >> >> thanks guys!!
> >> >
> >> > -audio-help is your friend, from there you can deduce (at the very least)
> >> > which audio driver your qemu uses.
> >> >
> >
> > It would also help to know which version of QEMU you run and exactly how
> > you invoke it.
>
> You're right..sorry:
>
> qemu-kvm -cpu core2duo -smp 2 -m 1024 -hda /home/nine/imgs/hda1.img
> -vga std -usbdevice tablet
> -name t1 -net nic,macaddr=55:54:00:12:34:56 -net
> tap,ifname=tap1,script=no
> -soundhw ac97
I can't help you with kvm and windows, that said here are the things
to try:
a. Vanilla qemu
b. No smp
And i'm not saying that those will help, just trying to collect more
data points.
P.S. 4 seconds of latency is sortof insane, especially given that
default buffering for ALSA is nowhere near that, not by a
longest shot.
[1] http://www.reric.net/linux/pci_latency.html
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2010-02-11 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 23:40 [Qemu-devel] Audio latency Alberich de megres
2010-02-11 0:03 ` malc
2010-02-11 6:47 ` Alberich de megres
2010-02-11 6:53 ` malc
2010-02-11 7:03 ` Alberich de megres
2010-02-11 8:42 ` malc [this message]
2010-02-11 19:07 ` Alberich de megres
2010-02-11 19:57 ` Alberich de megres
2010-02-11 21:45 ` malc
2010-02-11 22:19 ` Alberich de megres
2010-02-11 22:26 ` 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=alpine.LNX.2.00.1002111137420.3762@linmac \
--to=av1474@comtv.ru \
--cc=alberich2k5@gmail.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).