Hey guys,
There's been talk previously about the lackluster state which the Drum Map manager interface has been stuck in for so long.
Others have made suggestions. Here are mine.
BeforeI start, I think the Drum Map Manager could drop the "Drum Map" reference and just be called the Midi Note Map Manager or something. Drum Maps are in fact Midi Note Maps and are not reserved to drums, right?
Ok now let's get down to business. The Manager tools to actually "manage" Maps and Map Templates ("presets", actually) has lots of room for improvement :
1- The saving operations are IMHO not intuitive at all in the current interface, as you need to select a preset first before hitting save; modifying/overwriting an existing Map is even clunkier.
I would like to be able to load and save Note Maps Templates and individual Note Maps from and to file, straight from the Manager. By "to file", I mean being able to browse to a directory of my choosing and save a file just like I can export a Track Tremplate.
2- How about managing Notes and Ports by groups, rather than by individual note? You would create Notes groups and Port groups though the manager GUI. That way one could manage which note goes to which VSTi, matrix style, very easily. I made little diagrams to explain what I mean, see below.
- you need at the minimum 1 Note group with 1 input Note in it, and 1 Port group with 1 Port "slot" in it.
- you can create as many groups of Notes and groups of Ports as you want.
- the GUI would group notes and ports under their respective groups by default; however the user would be abe to sort all entries at once by In Note, Out Note, note Name, etc. on demand when doing a mass edit or creating a map from scratch (for example when copying notes numbers from the midi implementation chart in a user manual).
3- I would like to save Note Map Templates that do not point to any specific output port. See the example below.
Hower, when I DO set specific ports in a Map file that I save, I would like the port "names" to STICK when I load that file into a project. That way if I load a previously saved map on a new project that has 2 instances of the same VSTi plugin, all I have to do is make sure I name the instances correctly in the Synth pane of the Browser and I'll be all set ! No more Sonar messing up the map by re-routing notes to a piano VSTi because it can't find the original drum VSTi the map once pointed to.
Example of a Note Map Template file:
Example of a Note Map file :