GenMce + GenMceXT were built using SynthEdit.

If you have not tried it and are into making your own vst effects or instruments, you really, should.

I will add synthedit midi modules, built by Bill and Kip here, soon.

page under construction

Here are some screen shots from the synthedit source file. Descriptions of each will be below each screen shot.

.

main screen design screen (in synthedit)

• Each box above is a container.
• Inside each container are modules or other containers.
• In SynthEdit, you draw lines between containers and modules.
• The signals, be it audio, midi, int, bool, or choice go thru those lines. Much like an old analog (modular) synth like the ARP2600.

jog wheel (detail)

In the above example, for the jog wheel;

• InCh, CC selection, arm select boxes are all containters (meaning inside, them are more modules that are connected, or more containers)
• Jog_wheel is a module written in C++ (by Bill and I) for the synthedit api.
• You can write your own modules, the sdk is available at the synthedit site.
• If you look, you can see midi input going to the Jog_wheel module and midi out going out to output.
• The other connections are to select parameters of the Jo g_wheel module.
• Arm select - is really- Response Control, I just reused the container from another section of GenMce.

mute_switching system

These schematics can get very complicated (this one is not very but, let your imagination run...). The use of containers is very important for sanity when designing.

• This schematic, inside a container, is used to make the led's light up when the particular selection is made. No midi output is shown for this.
• Most of this schematic is comparing bools - a logic switching system to select which mode the multifunction mutes are in.
• There is a list output that will select which midi note to output.

solo detail sub container of mute_switching system

This schematic is a detail view of the solo, sub container from the previous example (above)

• The midi comes in and depending on which type of input is selected, the midi will be routed to the correct translator, sub container.
• The midi is converted to a bool to compare if it meets the criteria for true or false. If true it passes on.

note trigger input (detail) from solo container above

If the input type is set to note, then the midi data passes into this sub container where the work is done for translation.

• Again, the midi (for this sub container) is converted to a bool, if all criteria are true a true bool will pass out of the container.
• That bool will pass back up to the solo container, which will assign the note value to pass out.

As you can see, this is really about drawing lines, not about writing code.

You can make your own synths or fx (vsts), I have made a couple. I will post them here, for anyone interested.