I use it frequently. Can't specifically answer the priorities
question, but my own experience is that it has never been an issue,
ie., it runs as well as PD does in general.
Csound can be launched as an independent process and then, using its
osc opcodes, can be communicated to in a similar way to the super
collider client/server model, although personally I have found no
advantage to approaching it this way.
On my own computer I have a custom build of csound compiled against pd
0.40.3. I can't tell you what version the prepackaged csoundapi is
compiled against. I've installed this version with various PDs on
different machines and have never come across an incompatibility, so I
personally wouldn't worry about it.
I don't believe that there is a better way to interact PD->Csound that
the api object. Client/Server over OSC is more trouble than it is
worth.
JP
On Aug 11, 2008, at 11:44 AM, Mike McGonagle wrote:
Hello,
I recently started to use the Csoundapi~ external, and was wondering
if anyone has been using it, and if there are any troubles you have
encountered.I also was wondering (after reading someone's posts) about the
priorities under which these things run. I would imagine that with
it being an external of PD that it runs in the same address space
(maybe?) and that the priorities given to the code would be the same.Is there a better way to us CSound with PD? OSC? Can CSound be run
as a server (alla Supercollider)?Also, is there a more recent version of the external? While I
haven't experienced any troubles, I am wondering what version of
Pure Data that the compiled version that comes with Csound 5.08 was
compiled against.Mike
-- Peace may sound simple—one beautiful word— but it requires
everything we have, every quality, every strength, every dream,
every high ideal. —Yehudi Menuhin (1916–1999), musician _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list