• 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
Re: CoreMIDI behavior?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreMIDI behavior?


  • Subject: Re: CoreMIDI behavior?
  • From: Doug Wyatt <email@hidden>
  • Date: Mon, 7 Jan 2002 11:33:24 -0800

On Monday, January 7, 2002, at 05:37 , Kurt Revis wrote:
I suppose I should have said "is similar" rather than "maps quite closely". Anyway, reading about MIDI over USB helped me understand what I was empirically seeing in the packets, especially why the packets were so small (in the case of sysex). Of course now I know that it doesn't matter so much, but it was an interesting diversion.

Yes, CoreMIDI is endeavoring to deliver the incoming data to your app as quickly as possible, so if there's a full-bandwidth sysex stream coming in, and you're getting only 3 bytes of sysex at a time, you're getting woken up rougly once per millisecond to receive the incoming data. If you're getting more at a time, then either the interface or the Mac is CPU loaded to the point where things are getting buffered up.

Doug

--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden http://www.sonosphere.com

"Music and Living----"
"The same thing," said Pooh.
-- Benjamin Hoff, The Tao of Pooh


References: 
 >Re: CoreMIDI behavior? (From: Kurt Revis <email@hidden>)

  • Prev by Date: Re: CoreMIDI behavior?
  • Next by Date: digital audio tutorial
  • Previous by thread: Re: CoreMIDI behavior?
  • Next by thread: Re: CoreMIDI behavior?
  • Index(es):
    • Date
    • Thread