Encoder problem

trabz

2016-11-12 11:55:53

Hey!

I'm encountering a headache with encoders
I'd like to solve this without changing the way the controller's firmware is mapped.

No matter which encoder I press, it will send the midi message of all 4 encoders:

Midi sent when pressing encoder in, and when pressing it out
Encoder 1 (Ch.01.CC.48) is sending Ch.01.CC.48 value 0, Ch.01.CC.51 value 0, Ch.01.CC.54 value 0, Ch.01.CC.57 value 0
Encoder 2 (Ch.01.CC.51) is sending Ch.01.CC.48 value 0, Ch.01.CC.51 value 0, Ch.01.CC.54 value 0, Ch.01.CC.57 value 0
Encoder 3 (Ch.01.CC.54) is sending Ch.01.CC.48 value 0, Ch.01.CC.51 value 0, Ch.01.CC.54 value 0, Ch.01.CC.57 value 0
Encoder 4 (Ch.01.CC.57) is sending Ch.01.CC.48 value 0, Ch.01.CC.51 value 0, Ch.01.CC.54 value 0, Ch.01.CC.57 value 0

Problem is, I'd like to outgo a preset deactivation when I press any of the encoders 1-2-3, and a preset activation when I press encoder 4.

Is there a way around? I've spend hours on this one I'd need an outside opinion

sjcaldwell

2016-11-12 18:17:21

If each encoder is indeed sending the same message, there will be no way for any midi equipment to distinguish between them.

hgpa

2016-11-13 08:52:11

Is it not possible, to program the encoders new?
It would be nice, if we would know, which typ of encoder you use
(model-name). Most encoders (Behringer, Novation and many others.......)can be reprogrammed
by her own editor-software or directly on the machine.

HG

trabz

2016-11-13 19:57:03

hgpa wrote:Is it not possible, to program the encoders new?
It would be nice, if we would know, which typ of encoder you use
(model-name). Most encoders (Behringer, Novation and many others.......)can be reprogrammed
by her own editor-software or directly on the machine.

HG
I'm using a livid CNTRL:R which has a editor-software.
The thing is I'm also using a max for live device mapped specially for this controller and I don't want to mess it up as it happened to me before.
sjcaldwell wrote:If each encoder is indeed sending the same message, there will be no way for any midi equipment to distinguish between them.
:(

florian

2016-11-15 14:10:26

if each encoder is sending 4 control change messages, it looks to me like a bug, or a strange feature. Does it send MIDI messages when touching/untouching the encoders?
Otherwise, I'd contact the Livid guys.

trabz

2016-11-15 19:03:29

florian wrote:if each encoder is sending 4 control change messages, it looks to me like a bug, or a strange feature. Does it send MIDI messages when touching/untouching the encoders?
Otherwise, I'd contact the Livid guys.
Yeah pretty weird but thoses encoders are mapped to be banks in the firmware. I contacted Livid already...
When turning the encoder it sends only 1 message: the actual CC number and it's velocity. Thats why I finally use it to change my own banks.

Since all the encoders send CC 48/51/54/57 of value 0, I mapped the encoder CC57 to take a value of 126 with a short delay.
And then a rule that activates my banks preset when value=127. (so that I dont have to turn the encoder all the way from 0 to 127, just from 126 to 127 :)
Value <126 disables the presets.
I'm fine with it working like that, of course I'd prefer the encoder press but IDC

Thats messing up a bit the macro knobs but that seems to be fine for now, I'll run some more tests to be sure it's reliable

florian

2016-11-16 10:14:05

Hi trabz, would you mind posting your project file? Would be great for other CNTRL:R owners!