Dear all,

I would like to hear from anyone who has developed or is developing a
Csound 5 Host API - related project. Anything using any of the languages
supported: C, C++, Java, Python, TclTk, Lua, Lisp.

I want to put a list of names (and contact information, if you don't mind), so
that information can be exchanged about these projects. And I'd also like
to mention your names at the LAC2006 in Karlsruhe.

This was actually prompted by recent discussions, which seem to show that
there's quite a few people out there using the API, which is really great.

thanks

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Victor, 

As you probably know, the MacOS 7-9 graphical interface is now a pure client
of the API.  It used to be very entangled with the internals of Csound
before Cs5, but I have modified it to be a completely separate program that
links to a shared Csound library only via the public API.

I actually have two source trees that function as API clients:  CsoundFront
-- the GUI that I distribute with the release packages; and "Perf5" -- a
testing application that could be considered an (almost) minimal MacOS
client of the API.  (Perf5 requires typing in a commandline but provides
console output, graphs, transport control, and real-time audio like the old
Perf 4.xx series did).

I am also planning a couple of other projects that will make use of the
Csound API.  "RemoteCsound" will be a background server application that
will keep a queue of Csound jobs to render.  Jobs will be added to the queue
by sending an AppleEvent to RemoteCsound either from the same computer or
from any other Macintosh on the same local AppleTalk network using the
MacOS' "Program Linking" feature.  CsoundFront will eventually include a
graphical interface for selecting a remote computer and sending it a job.

I also think that it may finally be possible to provide Csound as a set of
MPW tools for MacOS (a sort of "commandline" environment).  Csound has never
compiled before on MPW because of its use of certain Unix functions, but I
think it may be quite simple to now link a commandline client in MPW to a
pre-existing Csound library.  The goal of all of this would be to allow the
use of "make" and other MPW tools to control the "compilation" of complex
Csound projects.

Finally, if there is any interest, I may put together a Csound SDK (software
development kit) for MacOS including Perf5 as a host app example, plugin
examples, cscore examples, and all of the libraries, headers, and IDE
projects needed to develop these things on MacOS 7-9.

I suppose that visible (audible?) interest from actual users though is key
to motivating me to do any of these things!  (Oh, and certainly, since I
could easily work on Csound full-time, if anyone wants to hire me to program
for Csound .....    ;)

Anthony Kozar
anthonykozar AT sbcglobal DOT net


Victor Lazzarini wrote on 3/16/06 6:01 AM:

> I would like to hear from anyone who has developed or is developing a
> Csound 5 Host API - related project. Anything using any of the languages
> supported: C, C++, Java, Python, TclTk, Lua, Lisp.
> 
> I want to put a list of names (and contact information, if you don't mind), so
> that information can be exchanged about these projects. And I'd also like
> to mention your names at the LAC2006 in Karlsruhe.

There is an upcoming release of dmp.csound~, but the name will have changed
to just csound~.  I've gotten permission from Ma++ Ingalls to change the name.
The new release will include changes so that users of Ingalls' csound~ who 
upgrade won't have to change their Max patches that much.

I'd appreciate you mentioning csound~, but I think I'll limit my contact information
to just email.

Thanks,

Davis Pyon
dmpyon@yahoo.com
www.davixology.com/csound~

Sorry, the correct link is:

http://www.davixology.com/csound~.html

> I would like to hear from anyone who has developed or is developing a
> Csound 5 Host API - related project. Anything using any of the languages
> supported: C, C++, Java, Python, TclTk, Lua, Lisp.
> 
> I want to put a list of names (and contact information, if you don't
> mind), so
> that information can be exchanged about these projects. And I'd also like
> to mention your names at the LAC2006 in Karlsruhe.
> 
> This was actually prompted by recent discussions, which seem to show that
> there's quite a few people out there using the API, which is really great.

I've been using it in C++, as you know. I'm somewhat reticent about
giving out source code early to my project because I am still learning
C++ and good oo multithread design, so I keep overhauling the damn thing
as I go, but I will happily share as long as people know they might not
like the engineering ... ;)

Iain