Re: MIDI "Controller" Support (was: Rationale for ignoring common
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 12:51:15 -0700
Glenn,
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....
I do agree with Doug, that the most basic controllers, like cc7 for
volume and cc10 for pan really should be implemented.
This is really basic stuff...
Chris Rogers
Core Audio
Apple Computer
Hardwiring cc7 to a synth's volume would help Doug Wyatt :-),
but it wouldn't be much help to many other users, especially
if they use an expression pedal instead of a volume pedal or have
an array of midi cc's on their keyboard that they would like
to use for that purpose.
As I mentioned before, the answer for the 21st century is to
implement midi learn. Enough synths offer it today that you're at
a decided disadvantage if you don't.
It also makes midi implementation charts unnecesary. Okay, so the
filter cutoff on ModelE is CC71. Now what? I don't have a knob
assigned to 71. I don't want to map controllers in the host or my
controller because a moment later I'll be working with a
different synth. If instead you're working with a synth which
has implemented midi learn, just choose filter cutoff from the
GUI, twirl a knob on your controller, and you're ready to go. There's
a good reason why midi implementation charts are virtually extinct.
Let's leave it that way :-).
- Glenn
_______________________________________________
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.