Copied binding loses mapping if target changed

Cantabile
1
  1. Duplicate a binding
  2. Change the target
  3. The mapping values are reset

This is a bit of a PITA when the user requires duplicate plugins with bindings which might only need a subtle tweak.

1 Like
2

I really cant believe how this fundamental bug has not been addressed. No replies. Nothing. Easy enough to copy and paste the bindings from a particular plugin but as soon as the target is changed the values are reset to their default.

3

Is step 1 of the OP relevant to reproducing this bug? My experience is that any change to the source or target of any binding (irrespective of whether it was created through duplication) risks resetting the mapping pane to default values.

My suggestion for @brad: While the binding editor window remains open, all mapping values (rightmost pane) should be remembered, even if a change to the source/target settings causes them to temporarily disappear from view. Any change to source/target that causes a mapping parameter to reappear should restore its remembered value too. (It’s probably safe to forget any unused temporary values once the binding editor window closes.)

While we’re discussing the binding editor window, I’d also like to recommend that it should not make live changes to bindings while the user adjusts the fields. It should have an Apply button, and changes should be committed only when the user presses Apply or OK. For example, right now when I make a binding that sends 110 to cc 127, the binding window sends the following series of midi messages to my controller as I type the numbers “127” and “110”:

cc 1 ← 0
cc 12 ← 0
cc 127 ← 0
cc 127 ← 1
cc 127 ← 11
cc 127 ← 110

This sort of thing messes up my controllers frequently. I’m guessing it’s not an intended feature.

Thanks for considering,
–Kevin

2 Likes
4

This is a tricky area because it’s not just the type of source/target/mapping that affects whether values need to be reset - it’s also the value ranges (eg: cc vs fine cc) that would key on that map of previously set values. Let me think about this.

Interesting I don’t think anyone has asked for this before. Would that also mean:

  • Clicking on another binding without pressing apply would discard?
  • Closing dialog would discard?
  • Should there be a save prompt?

Curious if anyone else would be interested in this approach.

5

I think any solution that recovers the original values for the same field and same range-limits would work for most users. For example, if I have a coarse-cc value x, and then I switch the target to fine-cc and back to coarse-cc, I want x to be in the value field again. What appears in the fine-cc value field is less important (could be x, a rescaled/clipped x, or a default value).

No, I think it should commit changes and focus on the new binding, similar to how the route-editor window already works. Clicking on a new binding means the user wants to save and go to the next binding.

I think there should be a Cancel button. Clicking OK saves and closes, clicking Cancel discards and closes, clicking Apply saves but does not close. There could also be a Reset button (like the route editor window). With explicit OK & Cancel buttons, there’d be no real need for a separate close widget. (But if people really wanted one, I don’t think I would care what it does, since using it would be optional.)

I vote no. With OK & Cancel, there’s no need for any save prompts, which would just slow users down.

1 Like