All of lore.kernel.org
 help / color / mirror / Atom feed
From: dE <de.techno@gmail.com>
To: Alsa-devel@alsa-project.org
Subject: Re: Selecting correct input device port.
Date: Thu, 30 Oct 2014 10:07:48 +0530	[thread overview]
Message-ID: <5451C09C.80606@gmail.com> (raw)
In-Reply-To: <s5h38a7e39x.wl-tiwai@suse.de>

On 10/29/14 13:06, Takashi Iwai wrote:
> At Tue, 28 Oct 2014 09:57:18 +0530,
> dE wrote:
>>
>> As I learn't in this mailng list, a device can typically handle only one
>> stream at a time unless it supports hardware mixing which's exposed via
>> subdevices in ALSA
>>
>> What does subdevice mean for input device?
>
> When a device can do multiplexing, the driver can give multiple
> substreams (= subdevices).
>
>> Do they mark physical ports
>> for input? If not how do I record from a specific input port?
>
> You can pass the subdevice number explicity.  It's -1 as default,
> which means to select the next free one.
>
>> Is it
>> automatically selected by the card?
>>
>> And what's 'input source' in ALSA mixer?
>
> It's usually a MUX to select the input source, e.g. line in or mic.
>
>
> Takashi
>

Input source for single subdevice right? I've 3 sub device, does it have 
to do anything with the fact that I've 3 input source in alsamixer? Do 
the 3 input source mark 3 different subdevices?

By muxing you mean muxing via software the multiple individual (and 
simultaneous) audio input streams as supported by the cards?

  reply	other threads:[~2014-10-30  4:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  4:27 Selecting correct input device port dE
2014-10-29  3:10 ` dE
2014-10-29  7:36 ` Takashi Iwai
2014-10-30  4:37   ` dE [this message]
2014-10-30  5:42     ` Raymond Yau
2014-10-30  9:31       ` dE
2014-10-30  5:08 ` Raymond Yau

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=5451C09C.80606@gmail.com \
    --to=de.techno@gmail.com \
    --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.