From: Michael Gerdau <mgd@technosis.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-user] Cheap USB audio card with phantom
Date: Sun, 28 Jan 2007 18:03:08 +0100 [thread overview]
Message-ID: <200701281803.24483.mgd@technosis.de> (raw)
In-Reply-To: <1169974525.4788.13.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1501 bytes --]
> > Why do you need XLR connectors and a preamp for Internet Podcast?
>
> I need a professionnal voice microphone, like in a normal radio.
> Therefore, I need XLR entries.
<disclaimer>
I'm not trying to be picky, just precise.
</disclaimer>
Whether or not a mic is "a professionnal voice microphone" has nothing
to do with it having XLR plugs or something else as such (you can
have them with "normal" stereo plugs as well from a "quality of
signal" POV). Many such microphones allow you to choose the plug,
or at least that is the result of scanning my own mics.
However I do agree that most higher quality mics I have come across
are equipped with XLR plugs by default (though they can be refitted)
which makes XLR kind of the canonical choice in studio environments.
[recording sip phone and for DV video]
> I need to record voices with good quality.
From this I deduce you don't require long cables with your mic which
implies you don't need balanced cables (at all cost).
Nothing wrong with using XLR, but from what you write not a "must have"
type of requirement.
> More generaly, are there established standards in audio?
> What are theses acronyms: ASIO, ASIO2, GSIF2, WDM, CoreAudio, CoreMIDI,
> kernel streaming, etc...
Have you tried google and/or wikipedia ?
Best,
Michael
--
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: mgd@technosis.de
GPG-keys available on request or at public keyserver
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2007-01-28 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1169882126.3763.5.camel@localhost>
2007-01-27 21:15 ` [Alsa-user] Cheap USB audio card with phantom Jean-Michel Pouré
2007-01-27 22:30 ` Bill Unruh
2007-01-28 0:42 ` John Rigg
2007-01-29 13:46 ` Matthias Koenig
[not found] ` <1170078899.13908.1.camel@localhost>
2007-01-29 14:37 ` Matthias Koenig
2007-01-28 8:55 ` Jean-Michel Pouré
2007-01-28 16:30 ` [Alsa-user] " Pieter Palmers
2007-01-28 17:03 ` Michael Gerdau [this message]
2007-01-28 17:50 ` Jean-Michel Pouré
2007-01-28 19:36 ` John Rigg
2007-01-28 1:22 ` Robert Emil Berge
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=200701281803.24483.mgd@technosis.de \
--to=mgd@technosis.de \
--cc=alsa-devel@lists.sourceforge.net \
/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).