I'm pleased to report progress with the Jack opcodes. I have had to
change the design to permit creating ports first, in the orchestra
header, then using them in instrument definitions. I also have omitted
MIDI input to Csound for now, though I may do it later in the same way
as CsoundVST, feeding MIDI from Jack into the existing MIDI driver.
Using opcodes instead of the backend will enable the use of multiple
MIDI inputs to one instance of Csound (I don't know if the existing
Jack implementation in the backend does this).

However, audio input and output, and MIDI output, are coded and appear
to be working with Aeolus. I need to improve the cleanup code and
remove extraneous log messages, then these opcodes will be ready for
others to test.I have done only very simple tests so far.

The implementation installs a SenseEvents callback, in which the
original Csound processing thread is simply put to sleep. Then the
Jack processing callback simply calls csoundPerformKsmps, so it is
possible to do callback-driven processing in the existing Csound
architecture after all.

Regards,
Miker



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
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