I just committed the following new API function:

/**
 * Sets an external callback for Cscore processing.
 * Pass NULL to reset to the internal cscore() function (which does
   nothing).
 * This callback is retained after a csoundReset() call.
 */
PUBLIC void csoundSetCscoreCallback(CSOUND *,
                        void (*cscoreCallback)(CSOUND *));


mummon.c will call the callback instead of the internal cscore() whenever it
is set and the -C flag is used.

There are two problems that I have noticed in using Cscore so far.  First, I
get a seg fault in csfree() or something like that after the score is done
rendering.  (I have not tracked down the exact problem yet).

Secondly, the division between csoundCompile() and csoundPerform() that came
with the API did not take Cscore into account.  The cscore function is
called from musmon, which now normally returns without performing, but
cscore usually causes the processed score to be performed immediately (via
the lplay() function).  So, performance is over when csoundCompile()
returns.

Any suggestions on how to deal with this?

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.net/



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net