• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
CoreMIDI problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CoreMIDI problem


  • Subject: CoreMIDI problem
  • From: Stéphane Letz <email@hidden>
  • Date: Mon, 22 May 2006 16:54:27 +0200

Hi,

We have an application that use the "MIDISendSysex" function and the send callback completion mechanism to send big sysex. We may have cases when the application quits while a sysex has not been completely sent. Although we desallocate CoreMidi ressources using "MIDIPortDispose" and "MIDIClientDispose", it seems that the completion callback is still called afterward.

What is the recommended way of dealing with this case? Should our "Stop" function wait until all completion callback have been called? (And if yes how?)
or is there a way to dispose Midi ressources and be sure that the completion routine will not be called anymore?


Thanks

Stephane Letz
_______________________________________________
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


  • Follow-Ups:
    • Re: CoreMIDI problem
      • From: Doug Wyatt <email@hidden>
  • Prev by Date: Re: AudioDeviceStop and ioProc
  • Next by Date: Re: Audio playing too quickly
  • Previous by thread: Re: hardware output latency
  • Next by thread: Re: CoreMIDI problem
  • Index(es):
    • Date
    • Thread