@benjaminfox Thanks for your approach for building this great resource!

As i have integrated an old iPad for audio routing in my pcless synth setup your CSV's seems to be a great addition for my tiny webgui.
So i have added a few devices that did not exist in your database.

I noticed 2 things that can be improved in standardisation within your database:

Formatting specific CC values/ranges with special meaning

My effort to parse and render the csv files is not that bad. But there are a lot of different data formats in the notes column which can't be parsed with javascript in a relieable way. Further the notes column may hold real notes instead of CC values/ranges

I think it would make sense to put those values in a separate column which requires a special format (unified delimiters) to be able to parse the data in a relieable way.

Some examples of variations:

0:Sine 1:Tri 2:Saw 3:Square 4:S&H 5:S&G
0-31: -24LPF; 32-63: -12LPF; 64-95: -12BPF; 96-127: -12HPF
0 to 31: off; 32 to 63: ring; 64 to 95: sync; 96 to 127: ring sync
0-41 Retrig / 42-83 Free / 84-127 Single
0-63 for off; 64-127 for on
0-42 for low; 43-84 for high; 87-127 for last. Default is last.
0: 16', 32: 8'; 64: 4'; 96: 2'
<63=OFF; >64=ON
0=24db; 127=12db
.. and a lot more variations...

As you can see there are so much different delimiters (; , / for : =) in the existing CSV files.
What do you think about moving those values to a separate column (for now i don't have a good idea for a name) with unified formatting instructions?
Or do you think this is an overhead without that much benefit?

Tons of variations in categories/sections

In my additions i have tried to find some orientation in existing csv files for the column sections.
So basically i used General, Oscillators, Filter, Envelopes, Mix, FX.

Digging deeper in the rest of the database there are a lot of variations and depths as well:
For example: OSC 1 Amp LFO 1 Delay FX VCA Envelope,...
Maybe it make sense to add an optional column subsection to all csv files to increase the data quality and extend the possibilities for rendering the data!?

Or do you think this would be an overhead without benefit as well?

Anyway. Even without those 2 improvements your resource is great!
thanks again

EDIT
with unified delimiters in notes column something like this is possible
my personal music setup helper GUI

based on this data it would also be possible to create buttons or faders in any GUI and send the MIDI data directly to a specific channel