Save/load named ticks data to/from a file

Question

Probably a bit pie in the sky for you guys right now but.....

I would love it if I could load/save named tick data to/from files. The very best way would be if the file were plain text so you could walk over it with a text editor or possibly play with it in a spreadsheet.

This would allow different recipes for the preset list to be loaded in for different occasions.  

In my case I'm thinking synth patches and set lists...

Answer 1

It's brilliant and essential and Rainer Keizer was smart enough to suggest it back in the day.

https://mididesigner.com/wiki/doku.php/manual:chapter-more-advanced-part-2#named_ticksedit_text

Now you can enter text via copy and paste, which is probably the easiest thing on iOS, anyway.

Comments

Thank you for answering.

This is a good function because it seems like it would allow me to easily rearrange the list of which incoming midi patch number selects which preset. This is the answer to another question on my list but not this one :)

What I want to do is save/load/edit the list of subcontrol values associated with each preset.

---

One of the features that's on the list is export and import of global presets. So this is basically export and import of presets for groups?

---

If you mean being able to save and load the list of all of the control values in the system then yes, being able to load/save the list of parameters associated with the preset. If there is more than one preset in the layout then the parameter list should be saved for each preset in the layout.

I also encourage you as strongly as possible to make the exported list be a text file, I think you already agree with that.

After thinking about it more I'd like to add that the best situation would be for the load/save operations to NOT require you to go into design mode. It should work with the layout locked so you can reuse the same layout and just pull in different parameter sets.

---

Thanks. We hadn't really thought of this before. We've considered preset packs, and that'll be in the App soon, but... hmmm, so these aren't really named ticks, but rather a way to share Presets for Groups, right?

---

What I would like is for the preset values for each subcontrol associated with the group preset to be dumped and loaded.

For example, in my application I use a group preset to select patches on a synthsizer. Presently I'm controlling 2 synths so there are two presets with it's own set of subcontrols.

The parameter list sent to the synth when a new preset is selected varies between the 2 keyboards. In one case the subcontrols are patch, bank, volume, and fine tuning (sysex).

What I would like are all of parameter values for each preset. In other words using the example above I want the patch, bank, volume, and tune values for each preset.

---

Thanks for explaining that. It's slightly complicated on the implementation side, because we have no smart way of knowing which sub control is which. When I send you a layout, or a page, each of the controls has a unique ID, and MIDI Designer uses that to determine which values go with what control. In this case, I'd be sending you values for a layout that I don't know the unique values for. Anyway… Just thinking aloud. Will consider this feature, and how to implement it. For the present moment, it's on the list! Thank you.

---

I think you are saying that the graphics object have an integer identifier and they could be different between layouts. That could be annoying alright.

As I understand it all the values are stored in the db using the OID (object id) of the control they are associated with rather than under the supercontrol.

What about putting them in the order of the subcontrols?  That way the OID wouldn't even be involved. For example, write the preset number, name, etc. and walk down the subcontrol list. I don't think it would be too agregious to require the subcontrols to be in a certain order if you wanted to load into a different layout with the same controls.

One sticky point left in my solution is how to identify with preset group to load into or save without using the OID.  You could look for the label.... hmmm.... you might actually need to add some kind of settable string ID you can use to find objects in your db.

---

Good conversation! TBH I hadn't thought about order of subcontrols.

I imagine that preset groups would be loaded and saved like layouts... so that's NOT a performance-time thing. No?

---

No, it's not a performance thing.

The preset groups would be loaded and saved like a layout.  Other than that the points I think are important is for it to be an ascii file and that you be able load and save it without going into design mode.

---

I'm using multiple preset groups so I've wondered whether the save should get them all in one try or if each preset group should be a separate save.

I'm leaning in the direction of one save for all preset groups in the layout. That makes the question of having an OID independent identifer like a string that you can set for each preset group more important because you need to tag which preset group the data belongs to.

Answer 2

It's brilliant and essential and Rainer Keizer was smart enough to suggest it back in the day.

https://mididesigner.com/wiki/doku.php/manual:chapter-more-advanced-part-2#named_ticksedit_text

Now you can enter text via copy and paste, which is probably the easiest thing on iOS, anyway.