Jeremy, some great ideas there, but these are more for the "blue sky" thread as they fall under the purview of the hardware and machine programming folks. While my application will make editing your Zendrums' configuration easier, it cannot alter the basic machine code or add non-existent features.
The editor that I'm working on is at its heart a sysex manipulator, much like the Mokugyo app that was available for the 3.x boards. Mokugyo only went as far as exposing the note numbers though, whereas this new editor goes much deeper.
The sysex memory images for the 4.0 boards weigh in at around 8Kb -- much larger than the 3.x. That's roughly 8000 unique memory addresses each of which (for the most part) hold a single setting's value. So there are for instance 30x16 addresses that hold the note numbers, and another set that hold the channel numbers, etc. When you tally up all the "known" addresses there's still a substantial block of memory that is unaccounted for for. There's no telling what gems are hidden in there as it's pretty clear, and David has hinted as much on this forum, that the machine programmer went well beyond the initial feature spec. I suspect that the settings for these extra features lurk within the unmapped areas of the sysex image and are undocumented simply because the simple physical interface of the Zendrum cannot expose them. A PC based editor of course can bridge these limitations.
The first of these "hidden" features that I've discovered is the ability to define exactly which 4 notes are used for the crossfade feature. Not earth-shattering for those people using VSTs exclusively, but for the module folks, that'll be huge. And I hope to uncover other such treasures!
Here is a sneak peek at the interface that's under development. Not shown here are the 'selected trigger edit pane' nor the various view modes. For each trigger (and in each user setup) you'll be able to control the label/information that is shown. Whether it be the canonical names (as shown) or the midi note number, note name, GM map name, GM icon, module specific name or a completely custom identifier.
Annotations will play a big part in the final app. You'll be able to name and annotate pretty much everything. Each user setup can be given a name and descriptive text, groups of triggers can be colored (and moved around for custom rigs). You can even customize the color and wood grain for the body. Once you've got things setup the way you like, you can then print or export the data. You can also transfer the data from one Zendrum to another, share your setups with friends, etc.
I'll share more information as it develops.