Midi bindings made from Midi Designer inside Beatmaker 3 or Modstep no longer function after MD is restarted?

Question

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?

Comments

At the risk of asking dumb questions: what's happening in the Connections panel in MD? In the apps you're controlling?

---

Thanks for asking. In both cases, everything is functioning normally in the connections windows on both sides because I am able to send and receive the CC or note from MDP and establish a working remote connection during the current session. When I restart the apps, the connections all show up properly on both sides and are active again, but the previously learned bindings no longer trigger. In Beatmaker3 when I make a midi binding for "Trigger Pad 1" it reads "MIDI Designer Pro 2 Virtual Out: Chan. 4: NOTE 0(C-2)" and functions normally, but after I restart the apps it changes to "<NOT CONNECTED>: Chan 4: NOTE 0 (C-2)" even though "MIDI Designer Pro 2 Virtual Out" is listed and activated in the Input Device column, the same as it was in the previous session in which I made and successfully used the connection. I know the connections are good because I can do the learn/map process again to get them working again...until I close MDP again.

Answer 1

SOLVED!

I solved this for myself. I figured out that you simply can't use the "MIDI Designer Pro 2 Virtual Out" as an input device in Beatmaker3 or Modstep when midi mapping. If you have only MDP2 virtual out turned on in these apps when you make midi map bindings, the bindings will only work during the current session. When you restart the apps, they will no longer function.

The solution is to activate the input device "Beatmaker 3" in Beatmaker3 (MDP2 Virtual Out can also be activated), or in Modstep ONLY activate MIDI Source "Modstep Internal", and of course have them activated in "Hardware and Virtual Destinations" in MDP2.

Answer 2

SOLVED!

I solved this for myself. I figured out that you simply can't use the "MIDI Designer Pro 2 Virtual Out" as an input device in Beatmaker3 or Modstep when midi mapping. If you have only MDP2 virtual out turned on in these apps when you make midi map bindings, the bindings will only work during the current session. When you restart the apps, they will no longer function.

The solution is to activate the input device "Beatmaker 3" in Beatmaker3 (MDP2 Virtual Out can also be activated), or in Modstep ONLY activate MIDI Source "Modstep Internal", and of course have them activated in "Hardware and Virtual Destinations" in MDP2.