On Sat, Feb 27, 2010 at 12:27:00PM -0500, Michael Gogins wrote:

> What I am going to do is write a complete suite of Jack opcodes for
> Csound. This will enable use of Aeolus, pianoteq, and so on from
> Csound as if they were plugins. Aeolus does not have a DSSI interface.

My first question is why ?

Csound already allows reading or writing from or to
a Jack port in an instrument. The only problem I see
with the current implementation is that the number
of inputs and outputs must be equal, which would
lead to silly situations if you need e.g. 64 outs 
and just a few inputs. But there are solutions for
that, and it's not a big issue anyway.
 
> The design of the proposed opcodes follows.

>  * asignal jackaudioin Sportname
>  *
>  * Receives an audio signal from the named sending port
>  * (Csound creates a receiving port with an internal name).
>  *
>  * jackaudioout Sportname, asignal
>  *
>  * Sends an audio signal to the named receiving port
>  * (Csound creates a sending port with an internal name).

If by 'named sending port' and 'named receiving port'
you mean ports of other jack clients, this is a *very*
bad idea. If you want to respect the normal way Jack
is used then port creation/destruction and port con-
nection/disconnection must be separate actions. Also
take into account that your 'internal' ports will be
visible externally if you want it or not.

In general, Jack applications should just create their
ports and ensure they have names that mean something
to the user, in other words a name that indicates their
funtion/use within the app that owns them. An app *may*
connect its ports to other apps, but in general should
not care where they are connected. This means you must
allow the creation of ports that are not connected at
all, and let the user take care of the connections. 

>  * Audio from multiple instances of the opcode sending
>  * to the same port is summed before sending.

If you mean the external destination this is not 
necessary, Jack does this anyway. You should just
allow internal summing on your own output ports. 

Ciao,

-- 
FA

O tu, che porte, correndo si ?
E guerra e morte !

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net