On Wednesday 24 March 2010, at 22.21.53, "Jeff McClintock"
True. My point was really just that pitch is somehow "hardwired" to the key
number on the receiver end, rather than explicitly specified by some CC or
(Well, there is the SysEx extension you mentioned, but that's not helping much
unless you have the bandwidth to spare, and equipment that supports it - but
that goes for the existing and proposed alternatives as well.)
Precisely. Or, I just solved the problem in the most straightforward way I
could think of. Design and implementation done in a few hours. (Ok; it's a
pretty high level language, but still. Maybe I can score a bonus point for
having designed and implemented the language too? ;-)
I could add SysEx key-based control to the MIDI parser, of course - but I'm
still wondering where I'd get such data from anyway! Perpetuating the
catch-22, that is; sorry about that. :-)
So... How about a library for sending and parsing MIDI with these SysEx
extensions? I'm thinking along the lines of providing a nice API, but using an
existing standard protocol. The idea would be to use ALSA and/or JACK (would
need an extension for SysEx, or does it support that these days?) for
transport layer, to avoid reinventing that too.
Later, when the API has proved to work, and stuff can be wired, one might add
more efficient protocols and transport layers for special cases, such as
between JACK clients, or between plugin hosts and plugins. (LV2 extension?)
Or, one starts with that, just looking at the feature set of MIDI + SysEx, and
add MIDI gateways later, if/when needed. Depends on how widespread support for
these extensions is, I guess.
Just thinking out loud here...
//David Olofson - Developer, Artist, Open Source Advocate
.--- Games, examples, libraries, scripting, sound, music, graphics ---.
| http://olofson.net http://kobodeluxe.com http://audiality.org |
| http://eel.olofson.net http://zeespace.net http://reologica.se |
Linux-audio-dev mailing list