From: Gerd Hoffmann <kraxel@redhat.com>
To: "Eric S. Johansson" <esj@eggo.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: just an observation about USB
Date: Mon, 19 Oct 2015 10:02:36 +0200 [thread overview]
Message-ID: <1445241756.13733.6.camel@redhat.com> (raw)
In-Reply-To: <56211C64.5020708@eggo.org>
On Fr, 2015-10-16 at 11:48 -0400, Eric S. Johansson wrote:
>
> On 10/16/2015 07:55 AM, Stefan Hajnoczi wrote:
> > QEMU can emulate PCI soundcards, including the Intel HD Audio codec
> > cards (-device intel-hda or -soundhw hda might do the trick). Low
> > latency and power consumption are usually at odds with each other.
> > That's because real-time audio requires small buffers many times per
> > second, so lots of interrupts and power consumption. Anyway, PCI
> > should be an improvement from USB audio. Stefan
>
> I set it up with ich9. I switched the default audio to my headset. I
> hear the windows startup sound in the headset. Dragon reports that the
> mic is not plugged in. I can see the audio level move in the sound
> settings so I know the host is hearing the audio
>
> what should I look at next?
Try '-device intel-hda -device hda-micro' (instead of -device intel-hda
-device hda-duplex', or '-soundhw hda' which is a shortcut for the
latter).
'hda-duplex' presents a codec with line-in and line-out to the guest.
'hda-micro' presents a codec with microphone and speaker to the guest.
Other than having in and out tagged differently the codecs are
identical. But especially declaring the input being a mic seems to be
needed to make some picky windows software happy.
cheers,
Gerd
prev parent reply other threads:[~2015-10-19 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 19:39 just an observation about USB Eric S. Johansson
2015-10-14 20:04 ` Paolo Bonzini
2015-10-14 20:30 ` Eric S. Johansson
2015-10-16 11:55 ` Stefan Hajnoczi
2015-10-16 15:48 ` Eric S. Johansson
2015-10-19 8:02 ` Gerd Hoffmann [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=1445241756.13733.6.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=esj@eggo.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.