From: Florian Faber <faber@faberman.de>
To: alsa-devel@alsa-project.org
Subject: Re: channel names
Date: Fri, 08 Feb 2013 08:07:47 +0100 [thread overview]
Message-ID: <5114A443.5090004@faberman.de> (raw)
In-Reply-To: <s5hbobv8fga.wl%tiwai@suse.de>
On 02/08/13 07:52, Takashi Iwai wrote:
> At Thu, 07 Feb 2013 22:23:15 +0100,
> Adrian Knoth wrote:
>>
>> Hi!
>>
>> Am I missing something or doesn't ALSA support channel names?
>>
>> When dealing with multichannel interfaces, it's pretty inconvenient to
>> remember whether channel 193 is on MADI 3, AES-EBU or phones.
>>
>> We can address this on the jackd level, however, since OSX allows audio
>> drivers to name their channels, I wonder how to do the same with ALSA?
>
> It's possible to give some information via the new channel map API,
> but things like AES-EBU or phone aren't defined there. We'd need new
> value definitions for such.
There might be interfaces that change the type of connection depending
on the current configuration (clock setting, pluggable hardware modules
etc.).
In the hdsp(m) and marian drivers I added ports.in and ports.out in
/proc which contain a list with the current physical port names. It is a
quick hack, but it works fine together with a patch for jack that
imports this list.
Flo
--
Machines can do the work, so people have time to think.
public key B3B9226C
next prev parent reply other threads:[~2013-02-08 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:23 channel names Adrian Knoth
2013-02-08 6:52 ` Takashi Iwai
2013-02-08 7:07 ` Florian Faber [this message]
2013-02-08 13:39 ` Adrian Knoth
2013-02-08 14:00 ` Clemens Ladisch
2013-02-08 14:05 ` Takashi Iwai
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=5114A443.5090004@faberman.de \
--to=faber@faberman.de \
--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.