[PD] midi limitations
nicholas.ward at cs.tcd.ie
Fri May 5 21:23:32 CEST 2006
Can your controller be set to send NRPN data? If so check the list
"Re: [PD] 14bit midi. nrpn and ctlin"
this is what i used to get better resolution from a bcf2000 controller.
All the best
On 5 May 2006, at 17:27, Christian Klippel wrote:
> 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
>> for double-precision AFAIK. So, you could try to use bendin and send
> nah ... its using a two byte message ... bitch bend is status 0xEc
> 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
> (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
> 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
>> ctlin object to make it do what you want.
> or use something else that doesnt use midi at all, to overcome that
> and have a higher speed. there are serveral options available. and if
> really need anything special, im sure i can build it for you ... well,
> least the electronics for it ... usb is just fun for these things ...
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
More information about the Pd-list