Just wanted to say the binding modifiers are terrific. Any chance of having a
#1 AND #2 = fire binding - function one day?
J
1 Like
I think you can do that by checking both boxes, one after the other. Then they will appear in the condition dialog box separated by a comma.
Thanks Dave - yes, I experimented with that but it looks like the binding sees multiple set modifiers as an OR kind of status. In my testing, either #1 or #2 -when active - were capable of firing the dependent binding when both were selected in Source. (I could be wrong - it’s happened once or twice.)
J
Sorry Jack, my bad. AND means AND,lol. 
To do AND type boolean you need to use an expression. What exactly are you trying to set up?
Ha, yes - hence the caps.
Right, I could have used the expression option but that disables controller bi-direction which was sort of important in this case.
I’ve created a bunch of bindings to map the nine Nord drawbars (Stage 2) to the VB3ii plugin in sets of nine for each - Upper / Lower (manual) and A/B presets in the B3 paradigm. It works pretty well except I can’t create enough variable states to accommodate all permutations of Upper/Lower A/B in the bindings area - it’s a bit hard to explain in text but having a Boolean AND function of some sort would solve some of that.
Having the bi-direction working lets every VB3 program load state reflect correctly on the Nord organ section - drawbar position, leslie, vib, percussion etc etc. and switching to Upper/Lower A/B then allows for traditional live B3 button pressing etc without squinting at my Lilliput 10 inch.
Since I’m on this path - there is one other item that I’ll flag @brad for.
It seems that the bi-direction data for a binding that DOES NOT have a modifier match is still sent. It would be great if it didn’t do that. If a binding doesn’t have an active modifier match - it should ideally be dead for it’s given Source. There’s probably other factors there that I’m not aware of.
Jack
BTW @dave_dore , you’ve always been a tremendous resource in this group. I’ve watched your responses for many years - Thanks for all you do.
1 Like
That’s a bug - it’s supposed to be AND, but it’s functioning as OR. I’ll fix this for the next build.
1 Like
So, if it works with 2 or more Modifiers as an AND then for an OR setup I would need separate bindings to do it?
Correct
1 Like
Build 4225 is up, now with correct AND behaviour.
Any thoughts on my comments re:CC bi-direction activity if binding is NOT fired ?
Thanks for your always blazing fast turn-arounds - amazing piece of software.
J
Hi @Jack_Harris
To be honest I’m not really sure how this should work and normally I wouldn’t suggest using modifiers on bi-directional bindings because it would mean the reverse binding would only trigger if the modifiers happened to be active when the target value changed.
I’m not sure that’s actually a useful behaviour is it?
Brad
-
Yes, I would expect the reverse binding to only trigger if the modifier is active. But it appears that reverse bindings trigger regardless of the active modifier. (unless I’ve botched something in my example below.)
-
I think it is a useful behavior - here’s my example
I have two modifier dependent bindings set up plus two more in the group “A/B preset Low…” These simply set #1 OR #2 based on a controller switch. Currently only #2 is active as shown. The last binding dialog box is open and shows mod #2 so I expect only this binding to fire when I move CC 9 / Ch 1.
Here - I have toggled VB3 presets twice - FROM the previous preset which has a value of 0 for the left drawbar indicated and 127 for the right - TO (this snapshot) - the preset “Bright comping” which has a value of 76 for the left and 127 for the right.
My midi monitor is inserted at the CP master outputs and you can see that even though only modifier #2 is active, both dependent bindings are firing.
The result is that my controller displays the inaccurate data of 127 - when it should have displayed 76 to reflect the new preset changed data.
If I disable both bindings - no midi data is displayed as expected - just as a control test.
Both bindings have suppression on - so there should be no subsequent trigger.
Interesting that one set of midi is not timestamped - that may be normal for reasons unknown to me.
Jack
@brad …dead horse???
No, just haven’t had a chance to look into it…