MIDI2CV A small SynthEdit module
Download

MIDI2CV Ranking & Summary

MIDI2CV Tags

MIDI Module SynthEdit Module SynthEdit Screenshot SynthEdit MIDI filter SynthEdit synth SynthEdit effect MIDI level SynthEdit Prefab SynthEdit modules SynthEdit SDK

MIDI2CV Description

ThMIDI2CV filter was developed to be a SynthEdit module.I found a problem with the Midi to CV in SE v1.015, namely that in mono mode the velocity is not instant, instead, it's smoothed/filtered. This prevented me to use the velocity as a trigger, since it's always too late because of the heavy smoothing. Jeff says this is to prevent clicks in mono mode, however I think it would be better not to include this filtering since it can be added later externally any time.I tried solving this problem by using poly mode and setting polyphony to 1, but then Retrigger doesn't work. So I had to make a MIDI to CV module to be able to use the velocity for triggering properly. Differences from SE v1.015 Midi to CV:The velocity is not smoothed/filtered in any way! It's always instant. Poly mode is not supported (this is not possible in the SDK2), so it's only usable for monophonic synths. You can add more sc:MIDI2CV modules in a container. Note priority is always 'Last' (the SE default). When note A is held, and you press and release note B, SE Midi to CV changes pitch/vel back to note A and retriggers Gate. sc:MIDI2CV changes pitch/vel back to note A too, but doesn't retrigger Gate. Portamento is not supported. You can simulate that by placing some kind of filter after the Pitch plug (you can use some of my filter modules). It doesn't retrigger the Pitch/Vel plugs when their values aren't changed - this might result in a very slight CPU-save in oscillators in certain cases. It seems to use about 50% less CPU, however, this is notable only with very fast sequences or fast arpeggio patterns. The Retrigger option makes Gate 0 V for 1 sample, whereas SE Midi to CV makes Gate 0 V for 3 samples. In practice, this does not matter.

MIDI2CV Related Software