• 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
MIDIClientDispose and MIDIServer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MIDIClientDispose and MIDIServer


  • Subject: MIDIClientDispose and MIDIServer
  • From: Pete Gontier <email@hidden>
  • Date: Fri, 03 Dec 2004 18:04:55 -0800

Since MIDIClientCreate implicitly launches MIDIServer if necessary, I
assumed that the last client to be disposed via MIDIClientDispose would
implicitly quit MIDIServer. This seems not to be the case. MIDIServer only
quits when my app quits.

This is problematic, since, when deployed, my app won't ever quit. (It's a
startup item.) It's bad enough my app will be hanging around all the time,
and I don't want to be responsible for keeping MIDIServer also hanging
around all the time. Unfortunately, it no longer seems there is a way to
avoid this short of writing a separate app which I can quit whenever I want
to enable MIDIServer to quit. But that's going to be work for which I do not
have time.

Ideas?

  --

    Pete Gontier
    http://www.m-audio.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

  • Follow-Ups:
    • Re: MIDIClientDispose and MIDIServer
      • From: Doug Wyatt <email@hidden>
  • Prev by Date: Re: coreaudio in cocoa/objC/objC++/c++
  • Next by Date: Re: coreaudio in cocoa/objC/objC++/c++
  • Previous by thread: Re: [OT]Non-padded odd-length chunks in AIFFs
  • Next by thread: Re: MIDIClientDispose and MIDIServer
  • Index(es):
    • Date
    • Thread