From: info <info@dressmaker.ca>
Cc: alsa-devel@alsa-project.org
Subject: Re: Discover a microphone device, to later discover if it is receiving input
Date: Fri, 9 Oct 2020 12:11:33 -0400 [thread overview]
Message-ID: <84f644cb-427e-487e-123a-6b1cd15e1d25@dressmaker.ca> (raw)
In-Reply-To: <s5hlfgfs986.wl-tiwai@suse.de>
When Audacity uses ALSA, it somehow knows that something is a front mic.
In the total absence of documentation that I noted in my other email,
how can I replicate this behaviour?
I do not insist on using hints. They were just mentioned somewhere on
the Net. I am agreeable to use any methods in ALSA API to discover the
mic, but w/o documentation, I have no way of knowing what it is, short
of reverse engineering your library. Is this the way you envisioned
adoption of ALSA: everyone is supposed to reverse-engineer?
Regards
Alex
On 2020-10-09 11:35 AM, Takashi Iwai wrote:
> Apart from the lack of the Input direction (maybe a bug in the hint
> code), the fundamental problem is that the driver cannot tell always
> the device type at all for each PCM stream. It's simply because a
> stream may give you any input type depending on the mixer route; it's
> the case of HD-audio. So, the same PCM device may be a mic, or a
> headset mic, or a line-in, or whatever.
>
> Sometimes there are dedicated PCM devices for certain inputs, but most
> of the PCM streams are generic purpose.
>
>
> Takashi
>
prev parent reply other threads:[~2020-10-09 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 16:22 Discover a microphone device, to later discover if it is receiving input info
2020-10-04 21:17 ` Dead link in wiki under Tutorials info
2020-10-16 17:33 ` info
2020-10-09 12:39 ` Discover a microphone device, to later discover if it is receiving input info
2020-10-09 14:07 ` Jaroslav Kysela
2020-10-09 15:35 ` Takashi Iwai
2020-10-09 16:11 ` info [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=84f644cb-427e-487e-123a-6b1cd15e1d25@dressmaker.ca \
--to=info@dressmaker.ca \
--cc=alsa-devel@alsa-project.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 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.