• 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: MIDI "Controller" Support (was: Rationale for ignoring common
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDI "Controller" Support (was: Rationale for ignoring common


  • Subject: Re: MIDI "Controller" Support (was: Rationale for ignoring common
  • From: Chris Rogers <email@hidden>
  • Date: Mon, 14 Jul 2003 15:47:53 -0700

Hey, I realize the world doesn't always match our perfect ideal.
But, look, we're trying to create a standard here which avoids the kind
of hacks, ill-specified behavior, and work-arounds to support specific hosts that have plagued other plug-in formats in the past. Sometimes the hosts or AudioUnits
haven't yet caught up to our ideal, but we're still looking to the future
and trying to encourage host developers and AudioUnit developers to
agree on a standard way of doing things (with much help from people
on this mailing list). The last thing we need is to
have all kinds of special case code floating around to work-around this
or that limitation or bug of some specific host or AudioUnit. I thought
we all understood that.

Chris Rogers
Core Audio
Apple Computer





<facetious>
:-) hmmm, where is this planet where, because all hosts implement
that mapping, synth developers do not need to? It must be the
same planet where AU is the only platform which synth developers must
support, and where Logic supports multiple outs for AU's.
</facetious>

I'm sorry, I couldn't resist :-), but sometimes on this list
it feels like Apple is on that planet and the rest of us are
not.

- Glenn

Chris Rogers wrote:
I completely agree with you that MIDI learn is much more powerful
than MIDI implementation charts. However, I'm not sure it's necessary
for each MusicDevice to have to implement it. The hosting application
can effectively implement this soft-mapping feature without any
extra work on the part of the soft-synth developer....
_______________________________________________
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.

References: 
 >Re: MIDI "Controller" Support (was: Rationale for ignoring common (From: Glenn Olander <email@hidden>)

  • Prev by Date: Re: Audio Units and sending Midi
  • Next by Date: MIDIGraph and runtime error
  • Previous by thread: Re: MIDI "Controller" Support (was: Rationale for ignoring common
  • Next by thread: Re: Re: MIDI "Controller" Support (was: Rationale for ignoring common
  • Index(es):
    • Date
    • Thread