Greetings:
Regarding MIDI data filtering, here are some ideas:
Rechannelizing: The ability to redefine and limit channel reception
(i.e., allow only one specific channel through, redirect channel 1 to
channel 10, etc.)
Mapping: Map anything to anything, no matter how apparently
ridiculous it may seem. Velocity to mod, volume to aftertouch, note-on
to controller message, whatever). Only sysex messages are immune. ;)
Blocking: Stop reception of a certain data type, e.g., running
status bytes, program changes, etc.
Set MIDI delay, arpeggiation, range filtering & restriction, etc.
This question has come up before when I was surprised to find how
difficult it was to access *only* the drums from the Fluid soundfont via
Qsynth. Some synths are good about channelization, others aren't, so it
would be nice to have the means to set MIDI channel reception
externally. I keep coming back to the notion of the programmable MIDI
patch bay, or something like the Yamaha MEP4 (a MIDI event processing
unit, much fun).
Best,
dp
Russell Hanaghan wrote:
>On Wed, 2004-05-26 at 10:41, Matthias Nagorni wrote:
>
>
>>On Wed, 26 May 2004, Russell Hanaghan wrote:
>>
>>
>>
>>>I there plans in the future to integrate the midi functions into the gui
>>>
>>>
>>This is a good point. In principle the MIDI bindings should be defined in
>>a separate place, outside of the XML gui description. A dialog similar to
>>the ams control center would be nice. I'll have a look...
>>
>>
>
>Actually, this is exactly what was in my mind. The AMS midi "parameters"
>and setting section is VERY usefull for CC, Prog Change, etc. That would
>be even Awesome..er! :)
>
>
>
>>>and possibly some midi filters too?
>>>
>>>
>>Which midi filters ? For mixer control ? Or general midi filters ?
>>BTW I have written a QMidiRoute utility which is a simple midi filter.
>>
>>
>
>Mostly, my thought was some filtering that might change one CC to
>another or even possibly prog changes to CC?
>
>
>
>>Matthias
>>
>>
>
>
>
>
