Subject: Re: [linux-audio-dev] a new application underway
From: thudson_AT_cygnus.com
Date: pe loka 08 1999 - 09:05:17 EDT
Paul Barton-Davis wrote:
> the beauty of the ALSA sequencer is that it offers an extremely
> generic event router with a timing limit that is not subject to the
> same limits. Alas, this is a theoretical possibility right now, since
> even the kernel doesn't check the timer queue more than HZ times a
> second. However, add the UTIME patch, and the kernel can do flexibly
> scheduled stuff with microsecond resolution.
>
> once you've got the MIDI file, the existence of MIDI playback tools
> *and* the ALSA sequencer allow anything to become automated *without*
> any special code: you just add the relevant sequencer port to the list
> of MIDI ports you select(2) on, and it all works like magic.
>
I agree. The ALSA sequencer architecture is one killer feature that
would make any user have to seriously consider linux over other OSes.
One feature I think would make the ALSA sequencer even more useful would
be to add a "fake" raw midi interface. That is, an interface that behaved
like the raw midi interface to the client application, but showed up
in the list of ALSA sequencer clients that could be routed to other
applications. It would deliver raw midi events from other clients
at the right time. As far as the app is concerned it would see them
as coming in from an external port in real time. This would allow
legacy apps to participate in the routing architecture and perhaps
benefit from the enhanced timing *without modification*.
I know this was discussed at one time, was a decision ever made to
include this? Or could it be done with a separate alsa kernel client?
Thomas
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:13 EST