Re: MIDI "Controller" Support
Re: MIDI "Controller" Support
- Subject: Re: MIDI "Controller" Support
- From: Glenn Olander <email@hidden>
- Date: Mon, 14 Jul 2003 13:21:00 -0700
I'm not suggesting that one should offer midi learn to
the exclusion of predefined controller-to-parameter mappings. I'm
just pointing out that relying on the hardwiring of cc7 to volume
is not a general solution to the problem Doug described.
By all means, provide default mappings. However, as I believe
Angus is pointing out, you shouldn't be surprised when the
default mappings for any modern synth look nothing like
the midi cc table :-).
- Glenn
Robert Grant wrote:
I think the answer for the 21st century is to provide sensible default
mappings for the common CCs *and* allow the user to reconfigure them
using MIDI learn. My Evolution MK-225C has 8 labeled knows that by
default are mapped to common CCs and it's great to attach it to a synth
and adjust the resonance or release of a synth with out fiddling with
anything. If you have no equivalent mapping then ignore it and allow the
user to map a different CC to that parameter if they want. But if there
is a mapping then it only makes sense to provide that as the default and
let the user override it as they wish. It would be *very* unfriendly to
not provide any default mapping (for those that make sense) and *force*
every user to make those mappings.
IMHO,
Robert.
On Monday, July 14, 2003, at 03:00 PM, Glenn Olander wrote:
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
Doug Wyatt wrote:
On Sunday, Jul 13, 2003, at 00:38 US/Pacific, Urs Heckmann wrote:
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)
Ouch, this is my pet peeve! ;-)
I use my volume pedal extensively. I want it to affect the synth's
output level, not the Logic channel strip, so that if I have an
effect (say a reverb) following the synth, I'm not killing the reverb
as I fade out a sustained sound. But there are and will be other
hosts, and the last time I tried I did manage to make an environment
to route CC7 to a synth. Please, implement it. For Logic users, you
could also connect volume to a different control source (I believe
Expression is sometimes used for this purpose, foot controller might
not be a bad choice either if you don't want to go through making a
UI to make it user-assignable)
Doug
_______________________________________________
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.