Page up/Bank up Buttons as Subcontrols?

Question

I am using MD with Midiflow to control patch changes as a keyboard player in a show. The Keyboard book has about 300 changes and I figured out how to use MD to send program changes to my synth and scene changes for the various routings to Midiflow using a picker that is controlled by a foot switch.  I can easily change patches while playing and the next patch on the page highlights as I step through them. Very cool, I am psyched!

With ~300 patch changes, I used 3 banks with about 4 pages per bank. At the end of each page the picker will call up the first patch on the next page. I tried using a page up button as a sub control in the first patch on the next page to automatically change pages when the first patch on that page is triggered, but it doesn’t work. The foot switch continues to step through the patches, but the page with the button that super controls the page up button acts strangely in that any button on that page causes the page to jump forward when tapped manually.

How do I configure a page/bank up button as a subcontrol? Is this even possible or do page/bank buttons have to be tapped manually? Thank you. 

Answer 1

So we seem to be fighting two behaviors here.  First is that it is the OFF action on the page jump that causes the action.  Second is that when you change a supercontrol, it seems the man behind the green curtain checks all subcontrol values, seeing that button is supposed to be off, sends the off value, and we get the undesired page jumps.

So we just need to hook up some controls that hold the page jump button on, except when you want it off - i.e, cause the page jump.

Build and test your page jump buttons.  Do not assign as subcontrol yet.

For each page jump button, build a relay button, type toggle, supercontrol, options as super - inverted.  Do NOT assign as a supercontrol of the page jump button yet.  Make it a subcontrol of the setlist picker.

On the setlist picker, go to the preset where you want the page jump.  Turn the relay toggle on, and store the preset.  (The off value should automatically fill all the other presets.)

Now assign the page jump button as a subcontrol of the relay button.

Comments

Thank you. Works like a charm now.

---

Actually I did a slightly different procedure in that I made each relay (in the on position) a subcontrol of the first preset on the page that I want to jump to, instead of a subcontrol of the set picker. Then I would make the page jump button a subcontrol of the relay as you described.

I noticed that these two buttons would not work if they were on the same page that I wanted to jump to so I placed them on the page I would jump from. Maybe when the buttons were on the same page as the preset MD already thought it was on that page when the preset was called up in sequence (from the previous page). I don’t know but anyway it works fine now. All the page jump buttons reside on the page I want to jump from.

Answer 2

So we seem to be fighting two behaviors here.  First is that it is the OFF action on the page jump that causes the action.  Second is that when you change a supercontrol, it seems the man behind the green curtain checks all subcontrol values, seeing that button is supposed to be off, sends the off value, and we get the undesired page jumps.

So we just need to hook up some controls that hold the page jump button on, except when you want it off - i.e, cause the page jump.

Build and test your page jump buttons.  Do not assign as subcontrol yet.

For each page jump button, build a relay button, type toggle, supercontrol, options as super - inverted.  Do NOT assign as a supercontrol of the page jump button yet.  Make it a subcontrol of the setlist picker.

On the setlist picker, go to the preset where you want the page jump.  Turn the relay toggle on, and store the preset.  (The off value should automatically fill all the other presets.)

Now assign the page jump button as a subcontrol of the relay button.