| I've just started to implement background rendering in my host app, so
that one can start playing the resulting audio file before it's
finished. (this worked fine only with raw float output).
As usual, I do all GUI stuff in the main process, so the csound render
thread should not do any UI but only communicate through global
variables to the main GUI thread. This means that I can't have csound
outputting messages (it crashes GTK).
But now I found the csoundEnableMessageBuffer() in the API which looks
to be the right thing! Only problem is that, according to csound.h, it
uses the host data pointer, which I already need and use for other
stuff. Is this still true?
If so, why is this? As I see it, the whole point with a host data field
is that the API itself should not use it. Now I have to implement my own
message ringbuffer in my host, which is sad since it already seems to
exist in csound...
--
/Jonatan [ http://kymatica.com ]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |