Joshua Hodge

I'm using ctlin to parse midi from my Pioneer DJM s-9 mixer. The midi channel and controller messages work fine, but as I move a fader up and down the messages are going from 0-127 again and again.

I can see why it's been done this way (tighter control) and I'm assuming there must be another midi message that specifies overall where I am on the fader, however I need to map this. Is there something else I need to do to parse this midi correctly? Thanks for any help.

I'm using ctlin to parse midi from my Pioneer DJM s-9 mixer.  The midi channel and controller messages work fine, but as I move a fader up and down the messages are going from 0-127 again and again.  

I can see why it's been done this way (tighter control) and I'm assuming there must be another midi message that specifies overall where I am on the fader, however I need to map this.  Is there something else I need to do to parse this midi correctly?  Thanks for any help.

I'm using ctlin to parse midi from my Pioneer DJM s-9 mixer.  The midi channel and controller messages work fine, but as I move a fader up a

ctlin-not-parsing-midi-values-correctly

Ok I can see what's happening just trying to fix it now. There's a least significant bit (lsb) which controls fine control and a most significant bit (msb) that uses the overall or coarse pitch control. When using this kind of control the midi message resolution is 14-bit rather than the normal 10-bit.

Trying to figure out how to only find the msb and use this to map. Currently trying xbendin and the hi-res mode of midiformat but not quite working right

Ok I can see what's happening just trying to fix it now.  There's a least significant bit (lsb) which controls fine control and a most significant bit (msb) that uses the overall or coarse pitch control.  When using this kind of control the midi message resolution is 14-bit rather than the normal 10-bit.  

Trying to figure out how to only find the msb and use this to map.  Currently trying xbendin and the hi-res mode of midiformat but not quite working right

Found an answer, and here's a reference for anyone that has a problem like this in the future. It appears Pioneer put their MSB and LSB on separate controller numbers, so you won't be able to use xbendin.

I've referred to the Pioneer list of midi messages (download from http://faq.pioneerdj.com/product.php?c=129&lang=en&p=DJM-S9&t=faq) to find the appropriate msb channels for each parameter, so from there I've used different ctlin messages to specify the MSB channel so I'm getting the appropriate values. Hope this helps!

Found an answer, and here's a reference for anyone that has a problem like this in the future.  It appears Pioneer put their MSB and LSB on separate controller numbers, so you won't be able to use xbendin. 

I've referred to the Pioneer list of midi messages (download from http://faq.pioneerdj.com/product.php?c=129&lang=en&p=DJM-S9&t=faq) to find the appropriate msb channels for each parameter, so from there I've used different ctlin messages to specify the MSB channel so I'm getting the appropriate values.  Hope this helps!

a similar question arose here recently; and if you want to retain the 14-bit resolution, you could use bitshifting:

https://cycling74.com/forums/manually-converting-14-bit-pb-to-msb-lsb

https://en.wikipedia.org/wiki/Arithmetic_shift

and here it is, with an excellent explanation by JFCharles:

https://cycling74.com/forums/dj-controller-midi-issues

Thanks Brendan! Funny how these two similar questions popped at the same time...

i never understood why it doesnt go 126/0, 127/0, 0/1, 1/1, ... would make life easier.

ctlin not parsing midi values correctly?