Re: [linux-audio-dev] News about sequencers (not my own though!)

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] News about sequencers (not my own though!)
From: David Olofson (audiality_AT_swipnet.se)
Date: ke tammi  26 2000 - 19:56:13 EST


On Mon, 24 Jan 2000, David Slomin wrote:
> Not to ignore all the good postings on the sequencer thread, but I
> only have time for a quick response before getting back to work. :-)
>
> jfm3 wrote:
> >
> > I agree. The problem is when I want "real time" sequencing with "logic" (not
> > Logic(TM)). If I want to give a command to my sequencer like "in this given
> > MIDI pattern, reduce all CC#11's greater than 72 to 72." my only hope is with a
> > little extension/command language. It's a hard problem and any solution is
> > impressive.
>
> Have you ever thought about using C as your "extension/command
> language"? Sure, it's not interpreted, but we're Linux users,
> right, so everybody has the compiler.

Good point... Also, it's not all that hard hacking something that
*generates* C source code, or translates something with a more syntax
suitable into C...

> Create a set of easy-to-use
> APIs for modifying MIDI (or other) events and use them to write
> separate tiny programs for each song. That way you get the best of
> both worlds... customizability in a language which most people
> already know (sorry Paul), and latency under your own control.

Well, C might not be the ultimate language for this, but it is indeed
one that lots of people know! And those who know C probably prefers
being aware of it's little problems, to learning yet another
language... Also, with a nice API and some templates/examples, the C
newbie shouldn't need to learn all that much before he/she can do the
basic filtering and arithmetics.

> This isn't very far removed from the concept of writing plugins to
> run under MuCoS or such, but the difference is that the API should
> be such that these would be as easy to code as small scripts in an
> interpreted language.

Hmm... Actually, I plan to use macros and/or inline funcs to deal
with the details of the event system, and the basic protocols it
carries.

Moving further along that line, and almost entirely hiding the
plugin API behind an extended macro/inline library, would make it
pretty easy to hack plugins that take events, filter them, modifiy
them and return them. These will run in just about any engine that
supports the MuCoS API...

(Closely related ideas have been discussed regarding modular synths,
where ultra short feedback loops and lost of little plugins would get
too much performance impact from just about any plugin API.)

//David

.- M u C o S -------------------. .- A u d i a l i t y ----------------.
| A Free/Open Multimedia | | Rock Solid, Hard Real Time, |
| Plugin & Integration Standard | | Low Latency Signal Processing |
`------> www.linuxdj.com/mucos -' `--> www.angelfire.com/or/audiality -'
.- D a v i d O l o f s o n ------------------------------------------.
| Audio Hacker, Linux Advocate, Open Source Advocate, Singer/Composer |
`----------------------------------------------> audiality_AT_swipnet.se -'


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:23:27 EST