[PD] midi limitations

Christian Klippel ck at mamalala.de
Fri May 5 18:27:31 CEST 2006


Am Freitag, 5. Mai 2006 17:47 schrieb derek holzer:
> Hi Ash,
> AshK wrote:
> > I'd like to know if there is a way to force ctlin to accept values
> > greater than 127?
> Is your MIDI controller REALLY sending messages with higher precision
> than 0-127? The only way I thought that was possible with the hardware
> MIDI spec was by using the pitchbend controller, which uses two channels
> for double-precision AFAIK. So, you could try to use bendin and send the

nah ... its using a two byte message ... bitch bend is status 0xEc <lsb><msb>, 
where c is the channel number (lower nibble of command byte)

together it forms a 14 bit controller message.

note that 0xf2 is globally a song-position message that also uses two bytes 
(14 bits), but is available only once, since it works on all channels.

so, by using _standard_ midi messages, it is possible to address 17 controller 
messages with 14 bit each on one cable.

> information as a pitchbend message which has higher resolution than a
> continuous controller. Or you could split the data onto different CC
> channels and sum them together. Or you could find someone to modify the
> ctlin object to make it do what you want.
> best,
> d.

or use something else that doesnt use midi at all, to overcome that problem 
and have a higher speed. there are serveral options available. and if you 
really need anything special, im sure i can build it for you ... well, at 
least the electronics for it ... usb is just fun for these things ...



More information about the Pd-list mailing list