Mark You are quite right. I originally tested it with .easypar CC 1 19 0 16383 absolute/14 and only got one message, but now when I test it again I get the two. I must have left something out in my first try. Thanks for putting me straight. All the best Royce --- In bc2000@yahoogroups.com, "Mark" <markwinvdb@...> wrote: > > --- In bc2000@yahoogroups.com, "Royce" <rpcfender@> wrote: > > I'm afraid this is not quite true. > > If you set a range of 0 to $3FFF, minmax of 14 bit Midi values, and the > > CC was something like 7 volume as there is a Fine volume defined in in > > the Midi spec 39 so you would get 2 Midi messages > > > > $B0 07 00 > > $B0 39 00 > > $B0 07 00 > > $B0 39 01 > > $B0 07 00 > > $B0 39 02 etc > > > > but if you use CC 19 there is no defined course or fine complement CC so > > you get > > > > $B0 19 00 > > $B0 19 01 > > $B0 19 02 > > .. > > $B0 19 126 > > $B0 19 127 > > $B0 19 00 > > .. > > $B0 19 127 > > $B0 19 01 > > $B0 19 02 > > .. etc > > > > It just loops around > > I'm afraid this is not quite true. > For any controller m in the MSB range [0, 31], the BCR outputs both the MSB CC message AND the corresponding LSB CC message (with m+32). > (See "BC MIDI Implementation.pdf", section 16.3.) > > So for CC 19 you don't need ".tx" definitions: > you can simply use a "standard" definition with ".easypar", e.g. > > $rev R1 > $encoder 6 > .easypar CC 1 19 0 16383 absolute/14 > .showvalue on > .mode 1dot > .resolution 1000 > .default 0 > $end > > Or am I missing something? > > Mark. >
Message
Re: Slim Phatty 14-bit MIDI CC messages
2011-02-01 by Royce
Attachments
- No local attachments were found for this message.