Is it possible to program an encoder to use it like a button?

3 posts / 0 new
Last post
roji11
roji11's picture
Is it possible to program an encoder to use it like a button?

Hi, I'm using a BCR2000, the Mountain Utilities for the commands and Midi2LR to transform those into Lightroom commands. The BCR2000 has 32 possible presets, on each preset you can define 4x8 (four buttons to choose the layout for 8 Encoders)+3x8 (three rows of 8 encoders)= 56 Encoders and 4x8 (multi use)+2x8 (single use)+8 (single use)= 56 Buttons. That's quite something and of course I always can define a new preset. Nearly endless possibilities and it all works really great

But nevertheless on some presets I need more buttons than encoders and would like to define some of the single-use encoders to work as a button (toggle on / toggle off) for the reason, that I don't have to change presets.

In combination with the Midi2LR software I only can use CC options. Encoders are defined as Channel # (preset #) Controller ##  Value 1 = 0 Value 2 = 127 Mode = Absolute.  So the encoder has 127 steps to go. Buttons are defined as 1 CC Nr Value 1 = 127 Value 2 = 0 Mode = Toggle Off and so working toggle on/off. This all works just fine.

To get a button, I tried different things and set  an encoder  to  CC ## Value 1 = 127 Value 2 = 0, then Value 1 = 0 Value 2 =1, then Value 1 = 0 and Value 2 = 0 and  changed the Mode with all options: Absolute - Relative - ...  But nothing worked. The still astonishing fact  was that my encoders still did run from Value 0 up to 127, no matter what I defined for Value 2. What's wrong?   

And the more general question "Can a encoder be programmed to work like a button?"

 

Mark van den Berg
Mark van den Berg's picture

The still astonishing fact  was that my encoders still did run from Value 0 up to 127, no matter what I defined for Value 2. What's wrong?

Are you sending your encoder definitions to the BCR correctly?
You should be aware of several differences between the behavior of the temporary preset ("preset 0") and the memory presets (1-32).
See the BC Manager manual: section 7 (Tutorials), and questions 8, 40, 41 and 42 in section 33 (FAQ).
In particular, it is important to realize that after uploading a memory preset to the BCR, BC Manager restores the temporary preset to its original state, as discussed in question 42 in section 33.

"Can a encoder be programmed to work like a button?"

In general, the BCR's buttons and encoders overlap in functionality only partially.
But in the context of MIDI2LR the answer is basically yes.

For use with MIDI2LR, the encoder's Mode parameter should always be set to Absolute.

For Lightroom parameters having a multi-value range (like Develop -> Basic -> Contrast), an encoder's Value 1 and Value 2 should normally be set to 0 and 127 respectively. Usually 0 then corresponds with the Lr parameter's minimum and 127 with the maximum. However, I've noticed that for at least one particular parameter this doesn't quite work: Develop -> Basic -> Temp parameter has a wider range (2000-50000) than what is covered by 0-127 (3000-9000).

For the on-off Lr parameters (switches) that I've tried (e.g. Develop -> Lens Corrections -> Remove Chromatic Aberration), MIDI values 0-50 cause the switch to go ON, and above that (51-127) the odd values lead to OFF and the even values to ON. So your BCR button or encoder definition must comply with this. (For instance, an encoder with Value 1 = 51 and Value 2 = 52 works correctly with Remove Chromatic Aberration.)

Note that you can customize the resolution of an encoder via BC Manager's "General" tab. This may be particularly relevant for these small "button-purpose" ranges like 51-52: you may want to choose a resolution lower than the standard 96 (e.g. 16 or 32), so that the encoder doesn't flip quite as quickly from off to on.

Hope this helps,
   Mark.

roji11
roji11's picture

Hello Mark, thanks for your help. Now I understand preset 0 better. The encoders can be programmend like suggested. 
The tip, to set slowest in General to 16 was helpful too. So even the complicated "zoom in/out some" works somehow. 
I play around some more, than I'm back with another question. (-;

Thanks Günter