Drop-down Menus

Question

I really hope you plan to add drop down menu support as my current template could really do with it.

As an example, 2 whole pages are taken up with what could be achieved with just 2 lines with drop down menus.

Hooked on your product by the way.  It's like the LittleBigPlanet of Midi editors :)

Comments

Thanks for your suggestion and for the kind words. Would "hidden controls" do the same thing? Not sure what you're proposing drop-down menus for, but I take ALL suggestions very seriously.

---

Say a modulation page has 2 main sources, each with a choice of 6 control sources and 12 destinations and then 4 destinations with depth control for each for example.  Now image that there are four layers to the sound!

  On one page with Drop down menus with multiple options and values I could have 2 Control source drop downs, 4 destination drop downs and 4 depth knobs, four times.

As it is, I have to use 2 pages, have a big ish text lookup table and knobs for you to cross check and select.  Easy to misread and really messy.

It's going to be even worse when it comes to effect chains!  

  Drop downs would also help people making patch selectors as they can add the preset names to the list and just jump to the right bank and patch name really easily.  The 200 or so waveforms I have in my synth would also benefit from having the name to select from instead of 1,2,3,4,5 etc.

Although from a different page, there are some really obvious places where drop downs could save space here :)

http://s9.postimage.org/mwhfma3hr/drop.jpg

---

I'm almost sure I can cover all of this stuff with "faceless" (or "headless") controls, or they would at least get you most of the way there. I'll be reading your comment over a few times (and looking at the example) to see if my first instinct is right. The idea is that you would "reveal" the page and then be able to see all the controls as rows of text, and be able to also see controls that have no "face." Does this make sense?

Thanks for the dialogue and persistence so far.

---

It is not so much control as selection.  

Like:-   Select Waveform (choice of 30 wave names)
                                           or
            Select Rompler Patch (choice of 200 patch names)


As far as implementation, you have 'number of clicks', so all you need is to have a 'name each click' option with a list box.   


So much of your editor and it's elegance comes from these type of controls so you can imagine a user having the same perspective :)




Anyway.  Back to my last example.

This is from my JD990 manual and shows a nice, simple and elegant original LCD menu giving a powerful selection process would potentially lead to a complex setup with Midi Designer (Pro, of course :) )  Remember, this is one of four layers, each having the same options.

http://s1.postimage.org/fxhfdgmhr/example.jpg

- Source 1 and Source 2 each have 6 options (Modulation, Aftertouch, Expression Pedal, Breath Controller, Pitch Bender and Foot Controller)

- The 12 Destinations are shown in the picture

- Each of the four destinations has a Depth value covering 0-50 (easy in MD)

Need this repeated 4 times on one half screen
                                                 --------------------

Merry Christmas BTW!

---

Okay, I'll be studying this example to see if I can figure out exactly how it fits in. Thanks for taking the time to respond so thoroughly!

---

Hi, curious if you've given any more consideration towards implementing this? I don't mind dealing with the lack of such a feature, as I'm chugging along fine without. All of the reasons above are exactly why I came here to post this suggestion myself. It would save space and some headache with labeling steps in fader values for waveform selectors; mod matrixes, switches etc within already cramped layouts, if we were able to condense a lot of buttons into one menu. If we could then also assign a string/value per menu item within this fantasy (ideally scrollable/scalable) drop down, well, that would also be cool.

---

at the risk of opening a can of worms: has this problem been solved with Named Ticks? Or some part of it?