From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] audio standards -- too many to choose from
Date: Fri, 14 Aug 2009 15:05:07 -0700 [thread overview]
Message-ID: <20090814220507.F09795B30@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 15 Aug 2009 05:24:01 +0800." <140e7ec30908141424l425e1da5kaa16d0a521f810fb@mail.gmail.com>
On Sat, 15 Aug 2009 05:24:01 +0800 sqweek <sqweek@gmail.com> wrote:
> On 12/08/2009, Tim Newsham <newsham@lava.net> wrote:
> > Draw the line at what the hardware can be told to decode
> > with a flip of a register? The driver interface can easily
> > accomodate arbitrary encoding names (see inferno's driver
> > for an example).
>
> One thing I haven't seen mentioned (perhaps because I misunderstand)
> is the added state that comes from allowing multiple formats.
> Actually, I think this problem exists with the current interface
> already - say I have a program playing music at 44kHz and then I get
> an email or something that I've set up to cause an aural alert, but
> the program that does that wants to work at 22kHz. This sort of
> interaction sounds bad enough to me, I don't even want to think about
> what it would sound like if the music was in mp3 and the alert changed
> the kernel format to wav.
The mixer would have to be smart.
> I guess this is where mixerfs and the like enter the picture, but
> I've come to think of the kernel as a hardware multiplexer so I'm
> liking the idea of having the kernel support multiple formats.
> Then again, I also respect the argument that the kernel is not a
> hardware multiplexer but a hardware abstractor - doesn't matter what's
> down there the kernel provides the same interface. From this point of
> view the simple approach is compelling, have /dev/audio exclusive
> write to avoid the above sort of interaction and mix in userspace (or
> is there still playback/recording sample rate interaction?). I think
> everyone agrees it doesn't make sense to have an mp3 decoder
> in-kernel...
> -sqweek
A decoder is just a resource (like a mouse, keyboard, disk,
network interface etc.). If h/w provides an mp3 decoder it
would be nice to be able to use it.
One idea is to have a devicename for each format/samplerate.
Some would be backed by h/w, some provided solely by s/w.
Basically you need an ability to interpose some sort of
"stream" module to create a network.
next prev parent reply other threads:[~2009-08-14 22:05 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 1:08 Tim Newsham
2009-08-12 1:14 ` erik quanstrom
2009-08-12 1:31 ` Tim Newsham
2009-08-12 1:45 ` erik quanstrom
2009-08-12 2:07 ` Tim Newsham
2009-08-12 3:14 ` ron minnich
2009-08-12 3:24 ` erik quanstrom
2009-08-12 4:49 ` Charles Forsyth
2009-08-12 4:24 ` Russ Cox
2009-08-12 4:35 ` Charles Forsyth
2009-08-12 15:12 ` Russ Cox
2009-08-12 4:36 ` Roman Shaposhnik
2009-08-12 15:36 ` hiro
2009-08-14 2:45 ` Roman V. Shaposhnik
2009-08-14 13:56 ` hiro
2009-08-12 5:15 ` Tim Newsham
2009-08-12 5:39 ` Roman Shaposhnik
2009-08-12 8:28 ` Tim Newsham
2009-08-12 9:30 ` Steve Simon
2009-08-13 2:16 ` Roman Shaposhnik
2009-08-13 3:17 ` erik quanstrom
2009-08-13 22:48 ` James Tomaschke
2009-08-13 22:52 ` erik quanstrom
2009-08-13 23:19 ` Christopher Nielsen
2009-08-13 23:47 ` James Tomaschke
2009-08-14 0:00 ` erik quanstrom
2009-08-14 1:13 ` James Tomaschke
2009-08-14 1:41 ` Anthony Sorace
2009-08-14 2:30 ` James Tomaschke
2009-08-14 1:42 ` Devon H. O'Dell
2009-08-14 1:51 ` Devon H. O'Dell
2009-08-14 2:22 ` James Tomaschke
2009-08-14 3:16 ` Charles Forsyth
2009-08-14 3:42 ` James Tomaschke
2009-08-14 7:04 ` Charles Forsyth
2009-08-14 20:43 ` James Tomaschke
2009-08-15 9:26 ` Steve Simon
2009-08-14 13:16 ` matt
2009-08-14 4:51 ` Devon H. O'Dell
2009-08-14 5:01 ` Devon H. O'Dell
2009-08-14 5:56 ` James Tomaschke
2009-08-19 9:58 ` matt
2009-08-14 5:18 ` James Tomaschke
2009-08-14 14:39 ` Devon H. O'Dell
2009-08-14 9:16 ` Paul Donnelly
2009-08-14 13:47 ` hiro
2009-08-14 20:03 ` Tim Newsham
2009-08-14 21:24 ` sqweek
2009-08-14 21:54 ` Skip Tavakkolian
2009-08-15 12:23 ` hiro
2009-08-14 22:05 ` Bakul Shah [this message]
2009-08-12 5:43 ` Anthony Sorace
2009-08-12 5:59 ` Roman Shaposhnik
2009-08-12 6:11 ` Roman Shaposhnik
2009-08-12 11:18 ` erik quanstrom
2009-08-13 2:06 ` Roman Shaposhnik
2009-08-12 22:11 ` James Tomaschke
2009-08-13 7:45 ` Skip Tavakkolian
2009-08-12 4:20 ` Roman Shaposhnik
2009-08-12 4:25 ` erik quanstrom
2009-08-12 4:50 ` Roman Shaposhnik
2009-08-12 5:10 ` Tim Newsham
2009-08-12 5:25 ` Roman Shaposhnik
2009-08-12 15:42 ` David Leimbach
2009-08-12 5:15 ` Anthony Sorace
2009-08-13 6:42 ` Skip Tavakkolian
2009-08-13 13:07 ` erik quanstrom
2009-08-13 13:30 ` Skip Tavakkolian
2009-08-13 13:31 ` Devon H. O'Dell
2009-08-13 14:31 ` Anthony Sorace
2009-08-13 14:41 ` Devon H. O'Dell
2009-08-13 17:20 ` hiro
2009-08-12 15:30 ` hiro
2009-08-12 5:54 ` Lawrence E. Bakst
2009-08-12 6:13 ` Roman Shaposhnik
2009-08-12 19:50 ` Tim Newsham
2009-08-12 20:57 ` Bakul Shah
2009-08-13 2:18 ` Roman Shaposhnik
2009-08-13 3:46 ` Tim Newsham
2009-08-13 17:00 ` Devon H. O'Dell
2009-08-13 19:13 ` Christopher Nielsen
2009-08-15 0:44 erik quanstrom
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=20090814220507.F09795B30@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).