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 10:17:55 +0100 [thread overview]
Message-ID: <20150909091755.GC9777@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <499BD4FC-8B37-4181-BA5F-0DAA2F012E25@gmail.com>
On Sun, Sep 06, 2015 at 04:53:29PM -0400, Programmingkid wrote:
> I have been working on making the sound output from the USB sound card actually sound good. When the audio is sent to CoreAudio, the sound is not very good. But when I use the wav file output option, the sound in the wave file sounds perfect. What does this mean?
You didn't describe or post an example of the "not very good" sound via
CoreAudio.
Perhaps QEMU is not filling playback buffers quickly enough, causing
underruns? These are drop-outs in the audio and are caused by missing
the real-time deadlines for filling playback audio buffers.
The wav output wouldn't have that problem since data is appended while
QEMU is running but you only listen to it later. So the timing doesn't
matter and it will sound fine.
Another possibility is that QEMU isn't writing audio samples in the
format that CoreAudio expects, so you hear weird artifacts.
More info is needed...
Stefan
next prev parent reply other threads:[~2015-09-09 9:18 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 [this message]
2015-09-09 14:37 ` Programmingkid
2015-09-09 18:04 ` Stefan Hajnoczi
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=20150909091755.GC9777@stefanha-thinkpad.redhat.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).