Hi All,

I'm currently working on using the Csound API from blue and I'm
finding a tricky situation.  I'm running this code in a thread:

while(csound.PerformKsmps() == 0 && keepRunning) {
                counter++;
                if(counter > updateRate) {

RenderTimeManager.getInstance().updateTimePointer((float)
csound.GetScoreTime());
                    counter = 0;
                }
            }
            csound.Stop();
            csound.Cleanup();
            csound.delete();

However, if the CSD that is being run has an instrument that sends an
"e" event like:

event "e", 0, 0, 0.1

in it's code, it seems to immediately kill Csound.  Then the code in
the thread tries to do another PerformKsmps() and will cause an access
violation of some sort, killing the entire process (i.e. will kill
Csound and blue together).

I'm not sure what is a good way around this, nor how the event opcode
processes events.  I asssume the event opcode immediately processes
instead of batching and processing on a ksmps boundary?

Anyone have ideas to get around this or if I have something wrong?

Thanks!
steven

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net