• 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
CoreMIDIServer throttling respawn?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CoreMIDIServer throttling respawn?


  • Subject: CoreMIDIServer throttling respawn?
  • From: scott brewer <email@hidden>
  • Date: Mon, 5 Jan 2009 17:35:20 +1100

I'm experiencing an issue with coreMIDI and was hoping someone has some insight into what's going on. I'm running on 2.4Ghz CoreDuo, 10.5.6 and xCode 3.1.2.

The issue can be reproduced with the sample code SampleTools project:
Developer/Examples/CoreAudio/MIDI/SampleTools/SampleTools.xcodeproj

I get the following system console message:

Sender[PID]: com.apple.launchd[73]
Message: (com.apple.CoreMIDIServer) Throttling respawn: Will start in 2 seconds


This message is triggered by sending a large number of midi commands (ie. hitting lots of piano keys repeatedly and at the same time -- like really mashing _lots_ of commands in there) while the app is starting. But the real showstopper is that after this happens i'm not able to receive midi callbacks until the App is restarted.

So, to reproduce with the above code example: Build&Go within xCode followed by consistent mashing of keys will result in aforementioned message in the console. Everything seems to work fine as long as you don't touch too many keys during the booting of CoreMIDIServer.

Does anyone know anything about this, or should I file a bug report and wait?


Thanks, Scott. audiomulch.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
  • Prev by Date: Re: AudioQueueStart result code: -308
  • Next by Date: Using AudioQueueOfflineRender...
  • Previous by thread: Re: AudioQueueStart result code: -308
  • Next by thread: Using AudioQueueOfflineRender...
  • Index(es):
    • Date
    • Thread