Midi sysex request in new thread

• Subject: Midi sysex request in new thread
• From: "Peter Karlsson" <email@hidden>
• Date: Wed, 15 Dec 2004 13:42:02 +0100
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Dear list!

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

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: Midi sysex request in new thread
    • From: Pete Gontier <email@hidden>
  • Re: Midi sysex request in new thread
    • From: Herbie Robinson <email@hidden>
  • Re: Midi sysex request in new thread
    • From: Doug Wyatt <email@hidden>

• Prev by Date: Re: Objective Audio Quality Measurement
• Next by Date: Re: Midi sysex request in new thread
• Previous by thread: Using program changes instead of key switches with QLSO and Logic
• Next by thread: Re: Midi sysex request in new thread
• Index(es):
  • Date
  • Thread