[Enhancement] Export and import of MIDI settings in editable format

[willeke1234]

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.

See also:
MIDI setup change #596
how to edit cmb files #622
Custom initial MIDI events #1081
Organ configuration and respective files #565

[willeke1234]

See also:
create a settings file that can be imported into new organs #1951

[oleg68]

@willeke1234 I implemented this capability in my intermediate build. It is available as buttons in the MIDI objects dialog. Could you test it?

[willeke1234]

There are some issues:

• When I try to export then I get
  
  If I choose "Use .ini" then the file is named "Friesach.midi.ini". If I choose "Use Both" then the file is named "Friesach.midi.ini.ini.midi.ini".
• When I try to import then I can't select a .ini file. I changed the name to "Friesach.ini", didn't work.
• The .ini file format is not what I would call an editable format. Technically it is editable, but in practice it is not.

[oleg68]

• When I try to export then I get

Seems it is a mac-specific issue. Do you know anything about forbidding .ini in your OS?

If I choose "Use .ini" then the file is named "Friesach.midi.ini".

It is a correct filename. The right extension is .midi.ini instead of .ini.

If I choose "Use Both" then the file is named "Friesach.midi.ini.ini.midi.ini".

• When I try to import then I can't select a .ini file. I changed the name to "Friesach.ini", didn't work.

Does Friesach.midi.ini work?

• The .ini file format is not what I would call an editable format. Technically it is editable, but in practice it is not.

I think it is acceptable if only non empty MIDI settings are there. The size is not so huge.

[willeke1234]

forbidding .ini in your OS

I don't know why and how I should do this.

The right extension is .midi.ini instead of .ini.
Does Friesach.midi.ini work?

I don't think macOS can handle dots in extensions and sees "Friesach.midi" with extension "ini".

If this file format should be edited by users then it needs a specification and a manual.

[oleg68]

don't think macOS can handle dots in extensions and sees "Friesach.midi" with extension "ini".

Would the ".midi-settings" extension better?

If this file format should be edited by users then it needs a specification and a manual.

I'll look at the possibility to use yaml format instead. The main difficulty is a lot of structured information is encoded in the section name now. It is not user-freandly. I think mapping it to a yaml hierarchy would be better.

[willeke1234]

Would the ".midi-settings" extension better?

It is better to use only alphanumeric characters.

I have decided to stick with GO 3.7 due to bugs and incompatibilities and will not be using this MIDI settings export/import. I have tried to discuss the file format and the MIDI Objects window but it did not work. I don't really care what the format will be, just try to think from the user's perspective.