Re: Midi sysex request in new thread
Re: Midi sysex request in new thread
- Subject: Re: Midi sysex request in new thread
- From: Herbie Robinson <email@hidden>
- Date: Thu, 16 Dec 2004 16:09:09 -0500
At 1:42 PM +0100 12/15/04, Peter Karlsson wrote:
I have a little problem.
When I click a button, the code under that button starts a new thread. In
that thread I send a midi sysex request message to one of my synthesizers.
In my MyReadProc I increase a counter every time I receive a sysex midi
byte. This counter is checked for in a while loop in my new thread. And
when the counter have reached the size of the sysex message the while loop
is finished and the thread exits. That's the idea but...
It does not work so good. I get [MIDISportLike] sending full buffer
messages so it seems that my way of doing this consumes a lot of cpu power.
Can someone please help me to solve this?
Maybe there is a much better way? I must find a way to stop my code
executing until the sysex message is finished. That's the whole problem.
I'm open for suggestinss
Best regards Peter
It's kind of hard to know how to answer this without knowing what
else the while loop is doing. It sounds like you should just
terminate the second thread immediately without bothering with the
while loop, but there must be something you aren't telling us...
--
-*****************************************
** http://www.curbside-recording.com/ **
******************************************
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden