MIDI settings import/export file format

[willeke1234]

I filed a feature request: Export and import of MIDI settings in editable format #1199.

It is a lot of work to add in and out MIDI events to all buttons and other objects. Hence the request to export and import the MIDI settings in an editable, commonly used format.

I may be considering implementing this (I'm not saying I will) and what constitutes an "editable, commonly used format" is debatable.

So what should the file format be? The simple Numbers spreadsheet app I use can export CSV and TSV. My iPad app would be able to import/export JSON and XML. Multiple formats would be nice but is more work.

It feels like there are way too many MIDI event types. Are they all used? Is a button range event a range or is it two values? Is it ok if a button range event or on/off event is converted to two events?

Which columns/fields must be included? It should be easy to understand. First proposal:
-ODF key
-Name
-Device
-Channel
-Event Type
-Lowest Key
-Highest Key
-Bank
-Key Offset/Number
-Min. Velocity/Value
-Max. Velocity/Value
-Debounce Time
-Function (On/Off/Toggle)
-Receive (Y/N)
-Send (Y/N)

What whoukd be easier to understand and use, more columns or shared columns? One column "Key Offset/Number" or two columns "Key Offset" and "Number"? "Key Offset" is used by Note On/Off messages, "Number" is used by Control Change and Program Change messages.

Should the data follow the MIDI Event dialog or should it be more intuitive? If the upper limit is the minimum velocity, should this value be in the Min or Max column?

Should the Cx Program Change value be split in Bank and Value? How about MSB and LSB?

What do you think?