• 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: Documentation starting points question.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation starting points question.


  • Subject: Re: Documentation starting points question.
  • From: Thomas Hudson <email@hidden>
  • Date: Wed, 11 Sep 2002 08:16:00 -0500

I would suggest Midi Programmers Handbook, by Steve De Furia and Joe Scacciaferro.
The code examples are in Pascal, but the section on the MIDI protocol is very good.

A good one page summary is available at http://www.srm.com/qtma/davidsmidispec.html

Since CoreMIDI Services deals with all the parsing issues (running status, clock messages, etc)
it is pretty straightforward.

TH

On Tuesday, September 10, 2002, at 06:46 PM, Robert Abernathy wrote:

Hi everybody,

I'm starting to write a midi app for OS X. This is the first midi application I've ever written. It is also the first app I've written for OS X (for that matter its the first app I've written for the Mac in 15 years).

I'm looking for pointers to documentation on midi messages and their construction for use in packets and packet lists. I can't find anything in the CoreAudio docs that talk about this. Is there any documentation for OMS (or the like) that would be relevant here?

Thanks for any help,
Rob
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Jaguar and AudioOutputUnit
      • From: email@hidden
References: 
 >Documentation starting points question. (From: Robert Abernathy <email@hidden>)

  • Prev by Date: Re: [coreaudio] Jaguar broke our audio input engine
  • Next by Date: Jaguar and AudioOutputUnit
  • Previous by thread: Re: Documentation starting points question.
  • Next by thread: Jaguar and AudioOutputUnit
  • Index(es):
    • Date
    • Thread