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: Urs Heckmann <email@hidden>
- Date: Sun, 13 Jul 2003 09:38:59 +0200
Bill Stewart:
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 put this list together from a GM spec that is available for perusal
at the MMA (MIDI Manufacturer's Association) web site
(http://www.midi.org/)
In the VST Source Code Archive (www.u-he.com/vstsource/), a site my
Alter Ego maintains ;-) there's a snippet that provides enums and
char*s. Maybe it's helpful for anyone.
www.u-he.com/vstsource/files/midiCtrl.h
this is a mixed mode mail:
Glenn Olander:
I forgot say what I think IS a good/reasonable expectation of synth
developers:
MIDI learn which allows connection of any midi cc to any
controllable parameter of the synth. That implies the synth
should respond to all midi cc's, not just a subset.
It would be nice, of course, if synth developers could rely upon
all hosts to centralize that feature, but that's another can
of worms :-).
Haha, yes, you name it.
I've often been asked why my stuff does not support CC7 (Volume). I
replied "uhm, please, try in Logic" and they knew why. (Because the
host already uses it for channel volume)
Mabe we need a property or any other mechanism to ask the host what it
already does for us? - So we can avoid double-effect hassle?
Cheers,
;) Urs
_______________________________________________
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.