MiniDexed icon indicating copy to clipboard operation
MiniDexed copied to clipboard

[Idea] Use human readable format for storing sysex

Open probonopd opened this issue 3 years ago • 0 comments

Formats like VCED and PCED are made to be machine-readable, not so much human-readable. VMEM and PMEM even more so; they were designed around memory constraints of the early 80s.

So the question is, would it be a good idea to introduce human-readable formats (e.g, "VINI" and "PINI")?

Since the .ini data format is widely used and natively supported in Dexed, I was thinking along these lines:

[Performance]
Performance_Name=
...

[INST 1]
Voice_Number=
Detune=
Note_Limit_Low=
Note_Limit_High=
...

[INST 2]
...

Also see page 29 of the TX-802 Owners Manual.

Table Add-10 in DX7II_MIDI_DataFormat.pdf mentions "PERFORMANCE Parameters (PCED, PMEM format)". Those are not for the TX-802 but possibly are similar? https://www.manualslib.com/manual/779968/Yamaha-Tx81z.html?page=74#manual mentions "Performance Edit Parameters (PCED)".

And while we are at it, we might also want to convert those voice sysex (VCED, VMEM) into something more human-readable like

[Voice]
Voice_Name=
Algorithm_Selector=
Feedback_Level=
Osc._Sync.=
Transpose=

[OP 1]
...

[OP 2]
...

NOTE: We may want shorter names for those (ideally standard names), e.g., "ALS" for "Algorithm_Selector" and "FBL" for Feedback_Level. Also see page 30 of the TX-802 Owners Manual and table Add-8 in DX7II_MIDI_DataFormat.pdf.

What do you people think?

probonopd avatar Feb 23 '22 17:02 probonopd