9 Jun
2013
9 Jun
'13
8:11 p.m.
On Sun, 2013-06-09 at 11:55 +0200, Tim Goetze wrote:
[David Robillard]
Yeah, dumb (i.e. non-standard) use of CC would have to be preserved,
especially to/from hardware.
Within Jackville, it's easy enough to specify: events must be bundled
iff they are actually intended to be a high-res controller. Otherwise
they, by definition, are not part of one.
Like Tim R. said though, there's probably no magic way to deal with this
for driver input, which is unfortunate[1]
(For output it's a non-issue since they'd be delivered as discrete
events regardless)
-dr
[1] Oh look, another Jack metadata use case...
I really think that, in Jack (and LV2), it should
just be mandated that
these (and all other multi-) events be shipped as one, for the same
reason that running status is forbidden: it's annoying and entirely
pointless.
Some MIDI devices do not employ 14-bit CCs or the NRPN mechanism.
Access' Virus for example maps all CCs as single 7-bit values, and a
forced 14-bit mode will break communication.