I'm having a problem with Midi Designer 2 no longer triggering the bindings I set with it inside Beatmaker 3, and the same with Modstep, after Midi Designer is closed and restarted.
For example in Beatmaker 3, in the "Focus Actions Editor", I click on "Trigger Pad 1" (putting it into learn mode), then press the button in Midi Designer that I want to trigger Pad 1 with. The "Midi Binding" in Beatmaker 3 now reads "MIDI Designer Pro 2 Virtual Out: Chan. 4: NOTE 0(C-2)" and the button in Midi Designer is now triggering Pad 1 in Beatmaker and playing it's sound as it should. The problem is if Midi Designer is closed and reopened, the "Midi Binding" in Beatmaker for "Trigger Pad 1" now reads "<NOT CONNECTED>: Chan 4: NOTE 0 (C-2)" and no longer triggers Pad 1. No amount of restarting both apps or saving/loading Focus Actions templates changes the "<NOT CONNECTED>" message in the Midi Binding list. I have to redo the binding process to once again trigger Beatmaker Pad 1 from Midi Designer.
In Modstep I can use the midi learn button to make bindings for interface objects (mute button, track volume slider, etc.) from Midi Designer but they work only until I restart Midi Designer, then no longer function even though still listed in Modstep. I have to relearn them to regain CC remote functionality.
I do not have this problem with Beatmaker 3 and Modstep when I make the bindings from Genome Midi (sequencer app). Also, I do not have this kind of problem triggering interface elements in other apps (AUM, Genome Midi, Turnado, Beatmaker2) from MD even after restarting MD.
Is anybody successfully using MD to remote control Beatmaker 3 or Modstep?