JCJR wrote:Along the same lines, your plugin during dev/debug doesn't have to output audio. You could process the dual-mono file as above, with no change to the left channel, but print the envelope output to the right channel rather than audio, and look at the results in an audio editor.
I generally prefer to just make the plugin either ignore the other input channel or simply sum to mono internally. This makes it easier to just feed "anything random" to the plugin, since often times it's quite convenient to debug "live" in a host (with a spectrum analyser and/or scope behind it.. plus Edison if I need to record something to inspect the waveform on sample-to-sample level), feeding it audio from a synth or something, trying to find a "worst case" signal to make problems more obvious etc.
Other tip is to add another parameter that lets you switch the second channel (or even two parameters, one for each channel) between various debug signals... and in general add various debug parameters to change things around internally, since it's much faster to turn around a knob (or slider, whatever) then change source-code constants and recompile.