Subject: Re: [linux-audio-dev] A Python loop sequencer, was re: using csound as a sampling engine
From: David Slomin (dgslomin_AT_CS.Princeton.EDU)
Date: ti syys 07 1999 - 17:55:08 EDT
On Mon, 6 Sep 1999, Paul Winkler wrote:
> I was thinking about building a vaguely 303-ish sequencer that, while
> not pretending to be a general-purpose sequencer, does a LOT more than a
> 303-clone. Sort of like a graphical tracker with unlimited parameters.
> I was thinking of writing it in python with a Tkinter interface. And
> most relevant to your post, I was thinking of ignoring midi entirely and
> using Csound as the synthesis engine, via stdin or a pipe.
Intriguing. It brings to mind something I was thinking of playing with
once my sequencer got to a useable state:
We all know that Csound can take input over MIDI in realtime. We also
know that when it does so, it loses all the power of its arbitrary-number-
and-meaning-of-parameters-per-event design. Would it be possible to write
a patch to Csound so that it _would_ accept full score-file-style events
wrapped as MIDI sysex events in realtime?
If you could do that, you could drive Csound (at full power) from a MIDI
sequencer or something like JMax. At the same time you would get free
[MIDI-based] syncronization with other softsynths and even hardware MIDI
devices. This would be truly wonderful to me.
Div.
P.S. Anybody want to propose a sysex message format for a Csound event?
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:11 EST