From: yy <yiyu.jgl@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] kw audio -- /dev/audio and friends
Date: Thu, 28 Oct 2010 09:53:13 +0200 [thread overview]
Message-ID: <AANLkTino1jv05G0-5v=_BP4MrtNYhC9A2u0uoaGPVBc_@mail.gmail.com> (raw)
In-Reply-To: <7EC7A032-E812-4FC7-9737-3676970BD4BB@9srv.net>
2010/10/28 Anthony Sorace <a@9srv.net>:
>> the other problem with both volume and audioctl will come with multiple
>> streams. in1 and out1 might work, but it starts to look ugly. usbaudio
>> appears to ignore multiple inputs or outputs.
>
> i'm not entirely sure what you mean by "streams" in this context. multiple inputs or outputs? if so, my first pass would be do something like what #l does: #l0, #l1, &c. Alternately, let any (theoretical future) driver for such a thing implement /mnt/fancydriver/0/audio &c, and bind as needed.
>
Wouldn't it be better to use #A0, #A1, ... for the case of multiple
audio devices instead of multiple in/outs in one device? I don't see
why control^(1 2 3 4 5 6) or in1, out1 are so ugly (specially
considering that this is just a potential "problem").
--
- yiyus || JGL . 4l77.com
next prev parent reply other threads:[~2010-10-28 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 14:06 Tristan Plumb
2010-10-26 14:31 ` Russ Cox
2010-10-26 14:49 ` erik quanstrom
2010-10-27 12:30 ` Tristan Plumb
2010-10-27 12:50 ` Lucio De Re
2010-10-27 13:29 ` erik quanstrom
2010-10-27 14:15 ` Tristan Plumb
2010-10-27 18:58 ` Anthony Sorace
2010-10-27 20:07 ` Skip Tavakkolian
2010-10-27 21:05 ` David Leimbach
2010-10-28 0:11 ` Tristan Plumb
2010-10-28 3:01 ` Anthony Sorace
2010-10-28 7:53 ` yy [this message]
2010-10-28 12:38 ` Tristan Plumb
2010-10-28 13:07 ` Gorka Guardiola
2010-10-28 13:26 ` Tristan Plumb
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='AANLkTino1jv05G0-5v=_BP4MrtNYhC9A2u0uoaGPVBc_@mail.gmail.com' \
--to=yiyu.jgl@gmail.com \
--cc=9fans@9fans.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).