Increase number of Presets?

Question

I've been singing the praises of MD to a potential user, but I've come up against the limitation of the 20 Presets in MD. For someone looking to create sufficient Presets as 'scenes' for a live show 20 isn't going to go much beyond a couple of songs.

I realise that there is limited space in MD's menu system, so 20 is a not unreasonable limitation there, but when creating a Preset recall button in a Layout, maybe a larger number could be accessed? I realise that this would require a way of storing those Presets, but maybe a creative way could be found to add this function?

Comments

Right now, the easiest way to expand this would be to give you proper saving and loading of presets. In fact that functionality is already there, but you only can mail them and then open them from another app. You would still be limited to 20, but it would be a very safe way to iterate and group your presets

---

I groaned about this a couple weeks ago and @jkhiser corrected me and it sent me digging. When talking about presets in MD we really need to recognize GLOBAL verses USER presets. This request to increase the number of preset memory locations is about GLOBAL presets. USER presets are unlimited; have a look at Dan's video on the different types of presets and then the praise singing will snowball even more :-D

---

I have to admit I don't understand, but I'll do my homework to see what this is all about.

---

Thank you. Group Presets. Yes, I get it. This is great!

I have a horrible feeling that I know the answer to my next question... Do I take it that the automatic naming dialogue only works when the control is limited to 12 positions? If so that's a painful limitation. I guess I can go name the ticks behind the scenes, but that automatic naming is so useful.

If my fears are correct... can I please add a suggestion for this restriction to be lifted? Maybe just an auto-naming on/off option?

---

This software, like any, is an empirical (quasi-living) entity. It's easy enough to test this question -- or most questions -- with a "HelloWorld." I like to start with a blank layout, but you can do it even on an existing layout. Make a control with 1000 named ticks and two subcontrols and a store button. Make that supercontrol a Presets knob. And try it out.

I'm quite sure the limit to user presets is something much higher like several thousand.

Good luck, please report back and always use a HelloWorld!

---

What auto naming function am I missing?

---

Looks like I have it under control now. My 1-12 Preset control would ask me to enter a name when the 'Store' button was pressed, but my 1-200 Preset control wouldn't (hence me asking if this is expected behaviour). But...

I loaded in a different Layout, then re-loaded my test Layout and now I *am* getting the naming dialogue from my 1-200 Preset control's Store button. I swear it wasn't working before the re-load!

My fears are alleviated and I'm happy! Thank you all. I've learned something new and VERY useful today.

---

good news! Thanks to @jkhiser for correcting me and getting me to research the user (Group) presets functionalities...so now I need to confirm that...it's "Group" presets? I'll dig in and look

---

I have been doing a slow refresh on the manual, maybe I will look at freshening up the presets section next.

---

I consider myself a fairly seasoned user these days, but I'm still learning new things that would have been useful had I known it earlier. It leads me to wonder what else I haven't discovered, or simply haven't considered relevant to me...

---

interesting comment - MD has come a long way, with many incremental steps in capability, until today when it is essentially a compete visual environment for MIDI control and display. And what we don't pick up with the visual building blocks (controls and control relationships), we can complete with StreamByter.  Sort of implies we need to update the way we advertise and introduce new users to MD.

---

It can be intimidating to newcomers. As it is I often struggle to find guiding information. My current impasse with sys-ex strings is a prime example - I'm stumped!