Wouldn't it be easier to do all this inside 1 instance of Csound? You can do this too in various ways. You can use zak channels, my Mixer opcodes, global variables, and probably other facilities.

My Mixer opcodes permit you to define any number of software busses, then assign ins and outs to busses; it works just like a real studio mixer. The CsoundVST.csd orchestra in csound5/examples shows it in use. There's already a very high quality reverb in there.

Regards,
Mike

-----Original Message-----
From: Ken 
Sent: Nov 4, 2005 1:10 PM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] understanding signals

For instance, run 2 instruments on 2 seperate csound instances, and send 
some signal from each to a reverb running on a 3rd instance.

Michael Gogins wrote:

>It is possible in various ways. What are you trying to do?
>
>Regards,
>Mike
>
>-----Original Message-----
>From: Ken 
>Sent: Nov 4, 2005 12:32 PM
>To: csound-devel@lists.sourceforge.net, csound list 
>Subject: [Csnd] understanding signals
>
>i'm confused.  is it posible, or will it be possible to send and 
>recieve, control and/or audio signal, between multiple running instances 
>of csound?  thanks,
>ken
>  
>

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

My wish is this:
1-I would like to build one .csd file per piece.  Thus I would like to 
insert a number of instruments, midi generators and fx, synthesis with 
insert fx, mixers with auxilary fx. with the gui included for each 
individual component.
2-I think that the gui should be bound, programmed/designed,  for each 
instrument so that I can program a number of preset settings, all midi 
triggered.  Thus a reverb, can have say 128 midi-presets so that it can 
generate, and store all different reverb settings.
3-A master container, the Reaktor equivalent of an ensemble,  would hold 
all the individual instruments, fx, mixer etc.
4- The whole ensemble is under midi control.

Michael Gogins wrote:

>Wouldn't it be easier to do all this inside 1 instance of Csound? You can do this too in various ways. You can use zak channels, my Mixer opcodes, global variables, and probably other facilities.
>
>My Mixer opcodes permit you to define any number of software busses, then assign ins and outs to busses; it works just like a real studio mixer. The CsoundVST.csd orchestra in csound5/examples shows it in use. There's already a very high quality reverb in there.
>
>Regards,
>Mike
>
>-----Original Message-----
>From: Ken 
>Sent: Nov 4, 2005 1:10 PM
>To: csound@lists.bath.ac.uk
>Subject: Re: [Csnd] understanding signals
>
>For instance, run 2 instruments on 2 seperate csound instances, and send 
>some signal from each to a reverb running on a 3rd instance.
>
>Michael Gogins wrote:
>
>  
>
>>It is possible in various ways. What are you trying to do?
>>
>>Regards,
>>Mike
>>
>>-----Original Message-----
>>From: Ken 
>>Sent: Nov 4, 2005 12:32 PM
>>To: csound-devel@lists.sourceforge.net, csound list 
>>Subject: [Csnd] understanding signals
>>
>>i'm confused.  is it posible, or will it be possible to send and 
>>recieve, control and/or audio signal, between multiple running instances 
>>of csound?  thanks,
>>ken
>> 
>>
>>    
>>
>
>  
>

Michael Gogins wrote:

> My Mixer opcodes permit you to define any number of software
 > busses, then assign ins and outs to busses; it works just like
 > a real studio mixer. The CsoundVST.csd orchestra in
 > csound5/examples shows it in use. There's already a very high
 > quality reverb in there.

Note that the same reverb is also implemented by the reverbsc
opcode.