It shouldn't be difficult to write a C frontend that
connects various instances of CSOUND using Istvan's
software bus interface; you can send in/out audio,
control or string data.

The only thing to bear in mind is that each instance
will be competing for audio I/O resources. In certain
systems, ie. OSX, this will only be possible if each
instance is using a different soundcard. On Windows, with
the MME interface, you can do it, as everything is sent
to a software mixer, which then talks to the card. But not
with ASIO. On Linux, this is also possible with Jack; with
ALSA, at least on my systems, you will only be able to
connect to separate soundcards (for instance if I have
jackd on, I can't use any programs that try to access the
soundcard directly; I haven't extensively tested this,
though).

What you can do is distribute/collect the data from all the
different instances and implement the IO yourself; that is
what
csoundapi~ does. Then Csound does not use its own IO
modules.

Victor

Victor
>
> >> 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
>
> You could use a host app using the csound 5 api to do this
> , in theory at  least. You can have each csound instance
> running with its own CSOUND  pointer and have audio come
> in and out of the api host passing to each  instance I'm
> not sure if anyone has actually tested that yet? However,
> it won't be all that simple as far as programming goes, so
> I would think  hard about whether that is actually
> necessary, and whether it confers  any real advantages. It
> preserves namespaces between instances but makes  it very
> difficult to pass control data back and forth between the
> different parts compared to just using one instance.
>
> Iain
> --
> Send bugs reports to this list.
> To unsubscribe, send email to
> csound-unsubscribe@lists.bath.ac.uk

Why is this true on OS X??  CoreAudio certainly supports any number of
programs sending audio output simultaneously.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.com/

Victor Lazzarini wrote on 11/4/05 2:41 PM:

> The only thing to bear in mind is that each instance
> will be competing for audio I/O resources. In certain
> systems, ie. OSX, this will only be possible if each
> instance is using a different soundcard. 

Victor Lazzarini wrote:

> It shouldn't be difficult to write a C frontend that
> connects various instances of CSOUND using Istvan's
> software bus interface; you can send in/out audio,
> control or string data.
> 
> The only thing to bear in mind is that each instance
> will be competing for audio I/O resources. In certain
> systems, ie. OSX, this will only be possible if each
> instance is using a different soundcard. On Windows, with
> the MME interface, you can do it, as everything is sent
> to a software mixer, which then talks to the card. But not
> with ASIO. On Linux, this is also possible with Jack; with
> ALSA, at least on my systems, you will only be able to
> connect to separate soundcards (for instance if I have
> jackd on, I can't use any programs that try to access the
> soundcard directly; I haven't extensively tested this,
> though).
> 
> What you can do is distribute/collect the data from all the
> different instances and implement the IO yourself; that is
> what
> csoundapi~ does. Then Csound does not use its own IO
> modules.

Or you can use audio I/O in only one of the instances that
collects data from the others through the bus interface.
However, it is currently not possible to use FLTK opcodes
in more than one instance at the same time.