Re: [announce] - blue 0.92.3
steven <stevenyi-h9wucfWDa/[email protected]>
| Newsgroups | gmane.comp.audio.csound.tekno |
|---|---|
| Message-ID | <[email protected]> |
Hi Iain, I'm not quite sure I understand what you're asking, but maybe this will clarify. When blue goes to run, all it does really is produce a temporary CSD file and runs Csound on it. Csound runs it's own process and functions as it normally would, so if your CSD file has instruments that respond to MIDI, then those will work as you've designed them to. The new realtime features within blue communicate to Csound via a stdin pipe, so that's a separate communications method. So it's possible to create projects in blue that are intended for both midi and blue realtime stuff. Another way to think of it is Csound as a server that when run is able to take in midi or stdin. Midi stuff is not touched by blue and goes directly to csound, while stdin stuff is generated from blue to csound. One thing you might want to try is if your sequencer project is a CSD, importing that into blue from the file menu (Import CSD File). You should get all of your instruments (if they're number and not named instruments) imported into the orchestra manager, and all the other stuff pushed into global orch and score. If you generate that out again as a CSD file, you should get roughly the same thing back. So you could use blue to manage your instruments this way. steven Iain Duncan wrote: >Hey Steven, our sequencer project works by holding the sequencer ( alwasy >on ) in one instrument, and using event calls to start up other instruments. >Do you think it would be possible to run such a thing with blue? Could the >instrument still receive real time midi input for controls? I'm not sure >what this would accomplish, but it seems like it would be worth exploring. > >Iain > > > > _______________________________________________ csoundtekno mailing list [email protected] Subscribe, unsubscribe, change mailing list options: http://plot.bek.no/mailman/listinfo/csoundtekno