On Fri, Sep 23, 2011 at 10:40:20PM +0200, Renato wrote:
That's part of the problem. It is possible to use sclang in
a way that makes the language/engine separation explicit.
But then not much remains of the language.
> Using Python and OSC I guess you can easilly play SynthDefs (because
Ugens are part of SynthDefs, they are an engine side thing. The others,
Tasks, Routines, Patterns you can do as well in Python, and then at
least you know what's happening. Patterns can be tricky, the easiest
way to do something similar is using Stackless Python.
That assumes you want patterns, most of the time I don't want them
and I'm thinking more in terms of a events on a timeline, or a set
of timelines. That is one thing that sclang does not support very well
- all the attention of its creators/developers is on patterns. You
are more or less forced to think in that way unless you need only
very basic functionality.
BTW, I'm still waiting for a basic description of Tasks, Routines, tne
'.fork' method and whatever else sclang has to offer for concurrent
execution. Are these coroutines, application level threads, system level
threads, or what ? '.fork' suggest it's creating a new process but I'm
pretty sure it doesn't. Etc. Etc.
Linux-audio-user mailing list