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: Brian Willoughby <email@hidden>
- Date: Mon, 14 Jul 2003 13:20:15 -0700
[ > As we've already discussed, the support for Program and Bank Select
[ > messages are not required if the synth is a preset based synth -
[ > essentially a mono-timbral synth in most cases, thus the host services
[ > will generally provide a way to map a Patch/Bank to a preset
[ > selection... I've left off Polyphonic Aftertouch, as no-one has seemed
[ > that interested in supporting this...
[
[ He. That's not fair! - I want Polyphonic Aftertouch. My Keyboard
[ does it and - like built in the Access Virus - I think it's a nice
[ way to circumvent the limitations of only 128 Control Changes.
[ (For synths with more than say 100 parameters to be controlled
[ via a hardware fader box, such as the Virus)
[
[ Really. What annoys me most with Midi CCs is that there are not
[ enough.
I second the above. Polyphonic Aftertouch is very important. I admit that it
should not be on the "required" list for every synth, but I do not want the
feature to atrophy. I'd hate to see it actively discouraged in Mac OS X
CoreMIDI by being left off the longer lists of controllers.
Brian Willoughby
Sound Consulting
_______________________________________________
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.