qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] wav output sounds good - what does this mean?
Date: Wed, 9 Sep 2015 19:04:27 +0100	[thread overview]
Message-ID: <CAJSP0QW8aDCYnyjGNSChU2Td5ptg9CRwL7sNunJenV5WXucOYw@mail.gmail.com> (raw)
In-Reply-To: <F8CBF339-136E-491E-A479-85194DCCC864@gmail.com>

On Wed, Sep 9, 2015 at 3:37 PM, Programmingkid
<programmingkidx@gmail.com> wrote:
> On second thought, I will send you audio samples of both live playback and wav output in a second email.

Thanks.  In my reply I mentioned that there is definitely a timing
problem because the song was at a slower tempo in the live audio
capture.  That is either caused by buffer timing issues or by a bad
sample rate conversion algorithm (I haven't checked how QEMU does it).

There's a third possibility if you're using the ALSA sound system on
the host.  Make sure no other applications are accessing the ALSA
device.  This includes PulseAudio.

I've heard weird issues like this when multiple applications use a
sound device and change settings (e.g. sample rate) at the same time.
You can use pavucontrol to disable PulseAudio on the sound device, if
necessary.

Stefan

      reply	other threads:[~2015-09-09 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 20:53 [Qemu-devel] wav output sounds good - what does this mean? Programmingkid
2015-09-09  9:17 ` Stefan Hajnoczi
2015-09-09 14:37   ` Programmingkid
2015-09-09 18:04     ` Stefan Hajnoczi [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=CAJSP0QW8aDCYnyjGNSChU2Td5ptg9CRwL7sNunJenV5WXucOYw@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=programmingkidx@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).