Re: Csound, PureData, and pipes.

> Well, another way to go would be to use PD to send out midi to drive a
> midi driven csound score, pd is better at algorithmic composition than
> csound, but csound has a far better sonic pallete, I think you can also
> turn off pd's audio and run midi only, but I'm not certain, but if you're
> running midi only on pd, it would be taking very few system resources,
> unless pd automatically locks down a huge chunk on its own.

That's kind of what I was thinking, except I don't want to be using midi 
to communicate with csound. I want an easy way to lash together a gui 
that communicates with csound via csound score events. Csound score 
events via pipes mean I can send messages with arbitrary numbers of 
pfields of 32 bit floats instead of silly 7 bit midi messages. So I 
thought PD would be using midi in ( in case I wanted some sliders to be 
controllable from a midi external controller ) and doing the gui, but no 
audio, while csound would receive score events from the pipe and do all 
the audio.

I think in the meantime I will work on making a mini embedded csound 5 
controller app using the api though, 'cause that will be even faster 
than pipes, far more flexible, and cross platform. The downside of 
course is that the gui will not be as easy to make and it won't be 
possible to change it in real time.

Iain
_______________________________________________
csoundtekno mailing list
[email protected]

Subscribe, unsubscribe, change mailing list options:
http://plot.bek.no/mailman/listinfo/csoundtekno