From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2577c9.f3659b0a.ZYYo.mx@tumtum.plumbweb.net> References: <2577c8.0aa552af.tqKm.mx@tumtum.plumbweb.net> <2577c8.fe23c316.C0kk.mx@tumtum.plumbweb.net> <2577c9.12b19530.giyO.mx@tumtum.plumbweb.net> <6CCD7B4C-B298-4F85-91CD-DCD750E946D9@9srv.net> <2577c9.7536e281.66qG.mx@tumtum.plumbweb.net> <7EC7A032-E812-4FC7-9737-3676970BD4BB@9srv.net> <2577c9.f3659b0a.ZYYo.mx@tumtum.plumbweb.net> Date: Thu, 28 Oct 2010 15:07:26 +0200 Message-ID: From: Gorka Guardiola To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] kw audio -- /dev/audio and friends Topicbox-Message-UUID: 701e2acc-ead6-11e9-9d60-3106f5b1d025 On Thu, Oct 28, 2010 at 2:38 PM, Tristan Plumb <9p-st@imu.li> wrote: >>> 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: > I am guessing the io in audio does not mean in/out. I think audioinctl audiooutctl is a little bit more readable. At least do audinctl audoutctl if you are shooting for shortness. -- - curiosity sKilled the cat