MIDI DESIGNER
The only MIDI controller for iPad, iPhone, and Mac


Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Check out our Facebook Group.

Of course, if you want to send us an email, feel free.

Open problem reports

Summary of user requests
Jump To Page Button Throws Bank Error For One Big Page Destination - MIDI Designer Q&A
0 votes
in Defect (Is this broken?) by ctreitzell (460 points)

1 Answer

0 votes

I use a separate control for each 1/2 page with supercontrol


To make jump to page work properly with one big page, I put a separate jump to page control on each 1/2 of the page.  Then I use a super control to activate both at the same time.  You can see this in the Master Class layout.
by jkhiser (22.5k points)
thanks jkhiser,
I still can't figure it out from your post here. I DL'd your Master Class docs and hope to see a working example in there. There are clearly settings within the controls I have gotten set correctly yet.
The entire master class layout is one big page, with jump buttons for navigation.  If you open it in design mode, you will see each displayed link is NOT a jump button, but a super control that links to two hidden jump buttons, one on each 1/2 of the page.  For each jump, you need one supercontrol and a separate jump button for each side of the layout.
...oh...cross post :-)

Yeah, what I want to do is similar to your Overview page:
buttons that open One Big Page targets :-D

Is Change Banks Together required?.... I see that is how you've made this layout...I seem to want to Design on Banks 1+2, 3+4, 5+6, 7+8...like the MDP2 manual says not to do...gotta use Change Banks Together 1+5, 2+6, 3+7, 4+8....which also requires use of only 4 banks on Left page....which hurts my planned amount of control pages

I'll look more deeply into how you have made this....

Thanks so much!
For one big page to work properly, bank 1 needs the same number of pages as bank 5, etc.  Otherwise you don't have one big page....

If you want more flexibility, turn off one big page, then just manage bringing up the proper pages with the double jump links.  You could pair one left page with multiple different right pages, etc.
hey, thanks...looks like I was overthinking it.
I kept trying to modify my original controls which wasn't working
So I made new controls from scratch and it is working great with One Big Page disabled...only problem there is that the tabs don't function properly with One Big Page and Change Banks Together turned off...Hence why I'd like to turn the tabs off altogether

thanks so much for the help!
OK, so turning One Big Page off does work; BUT the doubled subcontrols will have to be on every opposite Page for every Bank. In the event a different bank is loaded. It was working fine for me when I don't change Banks

for example:
Page 1- Bank 1 is left half; Page1 - Bank 2 is right half with your workaround works fine.
Change Right side Bank to any bank other than 2 and that Right side subcontrol isn't present; there is no Jump To Page function so nothing changes. The only way to get back to functionality is Banks and Tabs. It's a recipe for an overwhelming amount of hidden subcontrols on every single page :-| The reason for that is users will jump to control pages from the algorithm diagram and back and forth...I might be stuck with One Big Page for 6 algorithms...meaning 7 different remote layouts to accommodate the 43 algorithms...hmmmm
Yep.  Either you live with the constraints of one big page, or try to manage everything yourself.

Or, just don't worry about it.  Many of my layouts have some pages that need both sides, while most don't.  The index page has separate links to both 1/2s.  The user can bring the right half up on the left side, etc.  I add a visual cue that the pages are loaded correctly - a unique color line that meets only in the middle when correct.  If you have the left 1/2 of the Jup 8 and right 1/2 of Juno 106, the colors will not match.  If the sides are reversed, the lines don't meet.

And for a good laugh, look at the upcoming video on the new features in 2.5.  I mean to bring up two 1/2s of the old version, then compare to the new.  I bring up 1/2 old, 1/2 new, and don't realize until I try to go to the new.  (Having an old version and new version in the same layout is a unique situation.)

Sometimes you cannot fix everything in code.
...