alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Adding a "capture" device naming scheme
Date: Wed, 12 Jan 2011 11:12:42 +0000	[thread overview]
Message-ID: <igk2ba$mfs$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1101121013330.28150@eeebox2.perex-int.cz>

'Twas brillig, and Jaroslav Kysela at 12/01/11 09:17 did gyre and gimble:
> On Wed, 12 Jan 2011, Colin Guthrie wrote:
> 
>> 'Twas brillig, and Takashi Iwai at 12/01/11 06:53 did gyre and gimble:
>>> I read Colin meant front:CARD=x is incorrect while hw:CARD is a lowlevel
>>> access that one doesn't always want.
>>
>> For capture. Yes that's what I was meaning.
>>
>>> I'm fine with creating a new name, but wondering which name is best.
>>> Basically what you want here is the default use-case but without
>>> dsnoop like the current "default".  (If dsnoop were acceptable,
>>> "default" should have been used in most places.)
>>> "capture" may be also too ambiguous for defining that, I'm afraid.
>>
>> Yeah, "default" wont work here due to it being redirected to PulseAudio
>> (as opposed to dsnoop) in this use case, so we need to avoid that name :s
>>
>> IMO "capture" is quite clear (or at least as clear as "front" is for
>> playback!), but here are a few other suggestions:
>>
>> "record"
>> "input"
>> "read"
>>
>>
>> Personally, "input" and "capture" are my two favourites.
> 
> The question is, if we should identify more the source of the captured 
> data. The default device does the basic job.
> 
> analogin
> iec958in
> 
> Eventually:
> 
> linein
> micin
> iec958in


Well in the case of digital in I think "iec958" (or spdif) is used
directly (but could be wrong).

In 98% of cases, using front for recording works fine, but it is
technically wrong as Raymond pointed out several times on other threads.
Is it "technically wrong" to use iec958 for input? If so the then same
change we'll need to add for analog recoding would also cope quite fine
with digital recording, so adding a iec958in wouldn't really be a
problem in my book.

As for line vs mic etc, is this not usually handled by different
[sub]devices and/or switch elements? Would it really be possible to wrap
up such permutations in a config name without a lot of extra work?
(please forgive my ignorance here)


If we can't decide, we'll just have to tweak PA to use hw: directly for
input but it would seem like a cleaner design to have a proper name for it.

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

  reply	other threads:[~2011-01-12 11:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 18:40 Adding a "capture" device naming scheme Colin Guthrie
2011-01-12  1:08 ` Raymond Yau
2011-01-12  6:53   ` Takashi Iwai
2011-01-12  8:38     ` Raymond Yau
2011-01-12  9:04       ` Colin Guthrie
2011-01-12  9:10     ` Colin Guthrie
2011-01-12  9:17       ` Jaroslav Kysela
2011-01-12 11:12         ` Colin Guthrie [this message]
2011-01-12 17:00           ` Takashi Iwai
2011-01-12  8:53 ` Raymond Yau
2011-01-12  9:04   ` Colin Guthrie

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='igk2ba$mfs$1@dough.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --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 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).