CC Binding Bi-directionality - Or How to build the ultimate B3 controller

Cantabile
,
1

I have an odd result happening with a set of bindings that I’ve created to map a Nord Stage 2 “silent” organ patch controllers to GSi VB3 in CP.

The odd result is the updating of the Stage 2 drawbar LED’s from the bi-direction enabled bindings. As I switch from VB3 preset to preset - some of the Nord drawbar LED positions update and some do not - and there no pattern to this. A given drawbar will update sometimes and other times not.

  1. I’m using a designated midi channel, not OMNI as described in another topic.
  2. I am using a “Target Range” of 0 to 0.875 in the binding mapping in order to get the Nord drawbar to match the “throw” of the VB3 virtual drawbar.
  3. Manually (mouse) moving the VB3 drawbar nicely updates the Nord but preset change does not.
  4. The VB3 parameter windows changes with each VB3 preset change as you would expect.

I feel like I’m 97.3 percent of the way there to what would be a lovely setup for Hammond work but can’t see past this point.

Hoping the high level minds can advise.

Best/

J.

Updated

Ahh, well that was easy to sort. It appears this is due to the binding mapping not being a 1:1 relationship. Changing the binding mapping target to the default 0 - 1 allows all Nord LED’s to update (somewhat accurately) with each VB3 program change. It does also mean that the Nord drawbar changes are no longer scaled to the VB3 drawbars either. Have cake, no eat, it appears.

@brad - Is it fair to say as a rule: Anything other than a 1:1 map of controller values will result in bi-directional wonky-ness - specifically data returned to a given controller? This seems to be your statement here - If I’m reading this correctly.

2

Hi @Jack_Harris

If the binding allows you to enable bi-directional mode then it should work, but perhaps the controller isn’t happy with what’s being sent back. eg: if you’ve reduced the range in one direction, Cantabile should remap the range in the reverse direction too and perhaps the controller isn’t happy with the remapped values.

Best bet would be to use the MIDI monitor to see what’s being sent back when mapping is enabled and compare it to what’s being sent when mapping is not used.

Brad

5

Yes, understood. Took me a long bit to locate exactly where to pick up that data for monitoring.

Apologies for the posting mess.

1 Like
6

No problem… let me know if you need me to check anything.

7

A bit of final just to close this out.

The Nord has eight drawbar LED’s to correspond to the eight B3 drawbar detents and it transmits a fixed CC value for each position.

The GSi VB3II plugin divides each detent position into tenths and (probably) attempts to divide 1-127 values into some corresponding ratio. Looking at the midi data it skips sections of the 1-127 range to accommodate this and the Nord moves to it’s closest fixed value LED. This looks like the source of the mismatch to me.

My best solution for this was to leave the binding at default ranges and use the enhance curve to push value discrepancy to the center of the drawbar throw. I’d rather have small audio and graphic jumps in the center of bar values than at the 6,7,8, and zero positions.

J