From: "Eric S. Johansson" <esj@eggo.org>
To: kvm <kvm@vger.kernel.org>
Subject: revisiting speech recognition in a Windows guest on KVM
Date: Mon, 02 Feb 2015 16:51:29 -0500 [thread overview]
Message-ID: <54CFF161.9070401@eggo.org> (raw)
Apologies for taking so long to revisit this topic but well, new
hardware, new software, new microphone and, you know, life…
Summary:
I have unable to forward my USB microphone connection to a Windows guest
and I could use a little bit of assistance pointing me in the right
direction.
Long story:
On my new laptop, speech recognition is working well on the Windows
guest. I don't remember what client I was working with but I'm now using
vmm-view in spice mode. I wasn't able to get the spice connection to
make the USB microphone interface visible in Windows but I was able to
get the built-in host to guest USB binding as supplied by the vmm manger.
It's almost exactly right. What I'm noticing is that the audio stream is
not as clean as it could be. About every 15 to 20 seconds I hear a very
quiet but distinct "thump". The reason this is a bad thing is because
the recognition engine thinks it's the start of an utterance, spins its
wheels for about 10+ seconds trying to decode what it hears. When
NaturallySpeaking is spinning its wheels, it kills off all input because
it is trying to avoid a race condition between other inputs and itself.
I'm not sure where the thump is coming from. I don't hear it on my other
laptop and it's not external noise because it's extremely regular.
I'm wondering if the same problem would occur over the spice USB
forwarding. I could use a bit of assistance figuring out what I'm doing
wrong with spice USB forwarding so I can test out importing audio that way.
Thanks
--- eric
reply other threads:[~2015-02-02 21:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54CFF161.9070401@eggo.org \
--to=esj@eggo.org \
--cc=kvm@vger.kernel.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).