[Csnd] launching multiple csound files orc/sco

Date	2018-04-29 19:18
From	fauveboy
Subject	[Csnd] launching multiple csound files orc/sco
	As my csound instruments are developing there getting noticeably complex to read. To spread things out is it possible to spread the instruments into separate csd files instead of having many instruments, p fields and i statements ect. If this happens however are there ways to launch a number of csd files from the terminal? better yet can these files communicate, for example sending a single from one csd file to another csd file with a mixer and reverb ? Many thanks -- Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-04-29 19:54
From	Victor Lazzarini
Subject	Re: [Csnd] launching multiple csound files orc/sco
	If you have Jack you can do that, just start different csound processes and inter connect them with jack. Beyond that you would need to write your own API host/frontend. ======================== Prof. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy, Maynooth University, Maynooth, Co Kildare, Ireland Tel: 00 353 7086936 Fax: 00 353 1 7086952 > On 29 Apr 2018, at 19:18, fauveboy wrote: > > As my csound instruments are developing there getting noticeably complex to > read. To spread things out is it possible to spread the instruments into > separate csd files instead of having many instruments, p fields and i > statements ect. > > If this happens however are there ways to launch a number of csd files from > the terminal? better yet can these files communicate, for example sending a > single from one csd file to another csd file with a mixer and reverb ? > > Many thanks > > > > -- > Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-04-29 20:03
From	jpff
Subject	Re: [Csnd] launching multiple csound files orc/sco
	Not a real solution but using #include can simplify the code. On Sun, 29 Apr 2018, fauveboy wrote: > As my csound instruments are developing there getting noticeably complex to > read. To spread things out is it possible to spread the instruments into > separate csd files instead of having many instruments, p fields and i > statements ect. > > If this happens however are there ways to launch a number of csd files from > the terminal? better yet can these files communicate, for example sending a > single from one csd file to another csd file with a mixer and reverb ? > > Many thanks > > > > -- > Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2018-04-30 03:45
From	thorin kerr
Subject	Re: [Csnd] launching multiple csound files orc/sco
Attachments	masterex.csd
	For complex orchestras you can go along way with includes, and some kind of patching scheme (using zak, mixer, or chn opcodes). Here's an example of a 'master' csd I was working on for a while. Don't try and run it... you don't have the included files. It's just to illustrate a methodology. If you study it you can probably work out how it's put together: All the instruments, tables and note events are tucked away in individual 'included' files. The 'master' csd is mostly to control a mixer instrument. Admittedly... I never finished this one, but the methodology worked. Thorin On Mon, 30 Apr. 2018, 5:03 am jpff, <jpff@codemist.co.uk> wrote: Not a real solution but using #include can simplify the code. On Sun, 29 Apr 2018, fauveboy wrote: > As my csound instruments are developing there getting noticeably complex to > read. To spread things out is it possible to spread the instruments into > separate csd files instead of having many instruments, p fields and i > statements ect. > > If this happens however are there ways to launch a number of csd files from > the terminal? better yet can these files communicate, for example sending a > single from one csd file to another csd file with a mixer and reverb ? > > Many thanks > > > > -- > Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here