We’ve all been there, right? “Dang, I could make a whole patch just out of this one thing!” So I invite you to try — and post the result here! The rules are simple:
Make a full voice out of just one module;
You can load multiple instances of the chosen module (extra points if you manage to use just one, though);
It doesn’t have to be a free module either, just be sure to upload a video or audio should you go the premium route;
You can’t load any additional modules other than an audio interface and a recorder;
You are allowed to use notepads and blanks to help document and/or embellish your patch. Basically any visual only module that does not contribute in any way to the sound;
For the sake of this challenge, a VCO playing a constant pitch is not considered a voice. Hey, I’m all in for drones, but that’s cheating!
I’m sure people will ask what I mean by voice. I’m leaving this fairly open, so be your own judge. A clock, a sequencer, something to produce sound, timbre and dynamics control… As long as it sounds good to you and respects the rules above.
This challenge doesn’t have a deadline, so please feel free to submit anytime! I’ll try my best to listen and comment to every entry. Even if you come up with something you find obvious or uninteresting, it’s still a good exercise to try and make it sound good to your ears — and I’m sure others will appreciate listening to your work. Happy patching!
P.S.: I did a quick search to see if a similar challenge had already been done, but couldn’t find any. If you know of one (as I suspect there might be), please let me know!
Is it allowed to use audio input through the audio interface module?
Is it allowed to load samples (wave-files) into the module/modules (if it is possible)?
Is it mandatory that the patch plays by itself? Or is it allowed to ‘play’ the patch using the mouse to change parameters and cable connections while playing?
Preferrably all sounds should come from within Rack, so no samples/external sources — just to keep things interesting, you know Likewise, I think it’s an additional challenge that the modulation comes from the patch itself.
Having said that, I don’t want to discourage people to try something I might not have thought of, so if you already have an idea cooking up then please, by all means, go ahead with it!
What about allowing blanks and/or light strips and/or visual text modules to help denote and document logical sections of a patch? Basically any visual only module that does not contribute in any way to the sound. Something like I did for the AirWindows VCP #75 challenge.
Not only can this help while building a large patch with only one module, I think it is also instructive and more interesting for the consumers of the patch.
I know what module I am going to use, and I am pretty sure I will want to document as I go. If need be I can strip out the visual only modules when I am done. But I think people will enjoy it more with the documentation.
Hmm I believe my reply to Ahornberg extends to this case. I consider keyboard input external modulation, so if you want to be very strict, then no. But you do you!
Got one more to go. Uses Valley’s Interzone for glitchy noises, especially amusing when increasing the LFO rate. Later on, Delay and Reverb is added for emphasis (exceeding challenge requirements).
Note the use of the new input cable stacking feature! Like, half of the time this took to make was spent finding settings where the layers felt reasonably well balanced.
I opted to create 3 different voices using multiple copies of Venom VCO Lab. The patch includes the following functionalities:
V/Oct sequencing
Clock
Envelope generators
VCAs
Pseudo random triggers
LFO CV modulation
Various VCO modalities
0 Hz carrier FM
Audio rate triggered one shot generating sub harmonics
Sine bells
Half way through the video I enable “illegal” reverb, just to see what it could sound like. But it works fine staying within the rules, without the reverb