On Sat, Feb 27, 2010 at 09:04:37PM -0500, Michael Gogins wrote:

> OK, I think I see what you mean. You advise that Csound should not do
> audio output or input in a platform-specific way or driver-specific
> way in orchestra code, those options should be controlled from the
> command line.
> 
> However, as far as I can see, Jack runs on Linux, Windows, and OS X.
> So, Jack opcodes could certainly be portable in that sense.

'Portable' here means that the Csound does not depend
on the type of audio interface, as a long as it has the
required number of channels.

Of course doing things as writing an instrument that 
uses an extern Aeolus would require Jack anyway.

But normal audio I/O should not depend on it, and
your special Jack code can't coexist with the one
that is abstracted.
 
> I see the Jack opcodes as being in the same category as the existing
> VST, LADSPA, or DSSI opcodes.

These are plugin standards, not audio interfaces.
 
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