Subject: Re: [linux-audio-dev] News about sequencers (not my own though!)
From: David Slomin (dgslomin_AT_alumni.princeton.edu)
Date: pe tammi 21 2000 - 11:16:35 EST
Paul Winkler wrote:
>
> Very interesting idea. Though from what you've written, I'm not sure
> what I'd gain by keeping pysco in the equation at that point, since
> I'm not sure what pysco can do that PEGS can't. (In fact following
> this thread has occasionally made me wonder just how much of my time
> I'm wasting. :) )
Ah, but you already have something usable, whereas I have some
foundation code and a lot of design ideas. One in the hand worth
two in the bush and all that!
> PEGS, in turn, would then
> > be able to sequence algorithmically generated phrases, with each
> > such phrase mapping to one PEGS event. Here, as with audio clip
> > sequencing, the mixdown for output would be rather critical.
>
> Interesting...
> How do you see this working? Would each PEGS event somehow request
> pysco to generate this algorithmic phrase? How would communication
> be done? Pipes?
I don't understand the full workings of Pysco yet, so maybe I'm
off track, but here's what I was thinking: For an algorithmic
composition system, I would envision a set of functions that
generate phrases according to a few parameters such as starting
time and current chord. The functions would then be invoked
with different combinations of arguments to produce an output
file (or realtime stream). The function definition stage would
be handled by Pysco as it always is, but the invocation stage
would be controlled by PEGS events.
If you wanted a simple, non-realtime way of communicating between
the two programs, assume that Pysco works like Csound where the
function definitions are placed in an orchestra file and the
invocations are placed in a score file. PEGS would generate the
score file and exec Pyscore when a "play" button was pressed.
It's fairly easy to get fancier with pipes, sockets, or shared
memory if you want a faster response when pressing play.
The whole issue of nested events is trickier, since in this simple
version PEGS knows about Pysco events but not the other way around.
Just musing... there's a lot of potential here
Div.
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:23:26 EST