From: Tristan Plumb <9p-st@imu.li>
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 08:38:34 -0400 [thread overview]
Message-ID: <2577c9.f3659b0a.ZYYo.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <AANLkTino1jv05G0-5v=_BP4MrtNYhC9A2u0uoaGPVBc_@mail.gmail.com>
>> multiple inputs or outputs? if so, my first pass would be do something
>> like what #l does: #l0, #l1, &c.
> Wouldn't it be better to use #A0, #A1, ... for the case of multiple
> audio devices instead of multiple in/outs in one device?
that would make sense to me, though if there's a ethernet card that had
multiple interfaces in an analogous way, #l0, #l1 would probably be used.
> 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").
the cs42l51 (the codec used on the openrd) audioctl looks like this:
power in 1 0 1
pgapower in 1 0 1
boost in 0 0 1
micdiff in 0 0 1
micbias in 0 0 3 1
micboost0 in 0 0 1
micboost1 in 0 0 1
gain0 in 0 -6 24 1
gain1 in 0 -6 24 1
atten0 in 0 -96 0 1
atten1 in 0 -96 0 1
vol0 in 0 -103 24 1
vol1 in 0 -103 24 1
mute0 in 0 0 1
mute1 in 0 0 1
power out 1 0 1
hpgain out 3 0 7 1
vol0 out 0 -103 24 1
vol1 out 0 -103 24 1
mute0 out 0 0 1
mute1 out 0 0 1
treble out 0 -21 24 1
bass out 0 -21 24 1
volume0 out 0 -204 12 1
volume1 out 0 -204 12 1
mix0 out 0 0 3
mix1 out 0 0 3
with my current incarnation that becomes:
audictl:
power 0 1 1
pgapower 0 1 1
boost 0 1 0
micdiff 0 1 0
micbias 0 1 0
micboost 0 1 0 0
gain -6 24 0 0
atten -96 0 0 0
vol -103 24 0 0
mute 0 1 0 0
audoctl:
power 0 1 1
hpgain 0 7 3
vol -103 24 0 0
mute 0 1 0 0
treble -21 24 0
bass -21 24 0
volume -204 12 0 0
mix 0 3 0 0
to me, that is ugly, without in1 and out1. ugly enough to talk about
change, maybe not ugly enough to change.
volume is fairly nice: (except with percentages of the range)
power in 1 out 1
pgapower in 1
boost in 0
micdiff in 0
micbias in 0
micboost in 0 0
hpgain out 3
gain in 0 0
atten in 0 0
vol in 0 0 out 0 0
mute in 0 0 out 0 0
treble out 0
bass out 0
volume out 0 0
mix out 0 0
and easially extendable:
vol in 0 0 0 0 0 0 out 0 0 0 0 0 0 out1 0 0 0 0 0 0
but it doesn't give the ranges.
? vol -103 24 in 0 0 out 0 0
which looks liable to break things (out being optional).
tristan
(with apologies for such a long post)
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2010-10-28 12:38 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
2010-10-28 12:38 ` Tristan Plumb [this message]
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=2577c9.f3659b0a.ZYYo.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
--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).