Little bit o' Replicant...

We’re just finishing up the major coding on Replicant, and now moving in to the usability phase, where we tune all the parameters to useful ranges and such. During the course of development, I make a project that I use throughout to check the audio. Every time Adam sends me a new build, I plop it in my VST folder and proceed to give it a workout. This is also the time where we start to think about presets and such. Once a plugin is more or less working, I start to use it in my projects, so I’ll know _how_ to use it when I write the presets.

In any case, I thought you guys would get a kick out of hearing the testing track I have going this time around. Here is a 8-measure loop of the output of Nuendo. Replicant is, in this instance, on the snare that appears on the 2 of every measure. In the first four bars, it is operating forward, and in the second four bars, it is in reverse mode. (There will be two separate reverse functions, with randomization, in case you were curious. More about that later.)

In any event, I should mention that there is no automation whatsoever in this track, other than the reverse switch. There is _so_ much randomization in this plug, with dedicated controls for each random feature, that it can really run the gamut, from a simple looper to complete haywire aleatoric craziness. Whether you’ll find that useful in your music is up to you. But at any rate, that’s a (tiny) taste of some random delay action.

EDIT: Okay, per request, here are two examples of the Amen break getting chopped by Replicant. I know that using this break is long past irony, and getting in to extreme redundancy, but the benefit is, of course, that everyone knows the break well, so you thus have a good idea of what’s happening.

Example 2. In this example, “IGNORE” is on, so Replicant finishes whatever it starts before it will receive a new trigger. I’ve set it to be about 75% likely to trigger on beats 1, 5, 9, and 13. I’ve also set the LPF sweep to its most extreme (no resonance, though.)

Example 3. In this one, I’ve set Seq Mode to “RETRIG” and the “RANDOM BEATS” slider to about 40%, so any given beat is about 40% likely to trigger the loop engine, and any time a retrigger is received, the loop engine starts anew. I’ve turned the filter sweep and “DECAY” features off.