From: Chuck Hallenbeck <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: noise-canceling mikes, how to use them
Date: Fri, 7 May 2010 19:52:00 -0400 [thread overview]
Message-ID: <20100507235200.GA24112@rx.localhost> (raw)
In-Reply-To: <20100507232106.GJ2319@sonata.rednote.net>
Hi Janina,
Thanks for the recommendation. I'm dealing with a really
bottom-of-the-barrel gismo from Walmart for $19 at the moment, so I'm
not expecting super quality from it. Kerry called my attention to the
mute switch in the headset cord, and between the muted state and the
unmuted state, the latter is orders of magnitude better than the former
<smile> and will do for my needs just fine right now.
But it's always nice to know in which direction the upgrade path lies.
Chuck
On Fri, May 07, 2010 at 07:21:06PM -0400, Janina Sajka wrote:
> Hi, Chuck:
>
> Not too sure what to tell you. I guess the obvious ...
>
> Are you sure it's your capture of the mic signal? Are you sure the mic
> is actually quality stuff? I guess you'd find out by testing it in some
> other device.
>
> PS: I've been using Sennheiser PC166 headsets for a bit over a year now.
> I was so taken with the quality, I got a second one for my briefcase. I
> strongly recommend it, if you decide your back in the market. Awesome
> audio quality, and you get to run over USB with the included dongle.
> Alsa just comes up recognizing it.
>
> I know that doesn't solve your problem, but I thought I should toss this
> out. I've seen a lot of poor headsets out there.
>
> Janina
>
> Chuck Hallenbeck writes:
> > Hi,
> >
> > I have a simple headset with a mike on a boom, and would like to
> > capture audio from the mike using a mike input on my soundblaster sound
> > card. A normal high-impedance mike works great, but simply switching to
> > the headset mike, a noise-canceling device, the result is pretty
> > dismal: very low amplitude, very poor quality, lots of noise, even with
> > the mike boom lowered to the proper position.
> >
> > Any tips on how to use this type of mike would be greatly appreciated.
> >
> >
> > Thanks,
> > Chuck
> >
> > --
> > The Moon is Waning Crescent (35% of Full)
> > My web site: www.hallenbeck.ftml.net
> > Audio editor weblog: edway.wordpress.com
> > --------
> > Yesterday is a memory, Tomorrow is a vision, Today is a bitch!
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> Janina Sajka, Phone: +1.443.300.2200
> sip:janina@asterisk.rednote.net
>
> Chair, Open Accessibility janina@a11y.org
> Linux Foundation http://a11y.org
>
> Chair, Protocols & Formats
> Web Accessibility Initiative http://www.w3.org/wai/pf
> World Wide Web Consortium (W3C)
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
The Moon is Waning Crescent (33% of Full)
My web site: www.hallenbeck.ftml.net
Audio editor weblog: edway.wordpress.com
--------
Yesterday is a memory, Tomorrow is a vision, Today is a bitch!
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Kitty Litter
` Chuck Hallenbeck
` Kerry Hoath
` Chuck Hallenbeck
` Janina Sajka
` Chuck Hallenbeck [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=20100507235200.GA24112@rx.localhost \
--to=chuckh@ftml.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).