I set out today to experiment with exactly two things: a dynamic trigger patch technique suggested by none other than DivKid, and a new stereo wavefolder that I haven’t used nearly enough. It started off as a simple patch, that turned into a beast.
Dynamic triggers are interesting. Normally a trigger’s amplitude doesn’t matter. Most triggers simply cue other modules to do whatever it is they do. But some drum modules, filters, and LPGs thrive when fed with dynamic triggers because it allows individual hits to be different volumes, which brings an interesting dimension to LPG pings. There’s variety; a variance that adds character and drama.
The patch itself isn’t that difficult. The key is to both attenuate and offset noise, and use that in a VCA CV input. In a thread about Dynamic Triggers on Modwiggler, DivKid writes,
It’s also good to remember (for all of us, I know I need a reminder sometimes) that CV utilities are our friends. Offset and attenuation would get you a long way. So rather than fully random. Take a CV utility and use an offset of say 3V (roughly) and then mix in the noise but attenuated and you’ll have a series of values that are hovering and dancing around the offset. Musically and sort of “humanised” around that offset.
Although it sounded easy enough, I asked, on his Discord server, to elaborate, and he confirmed that the patch is as easy as I imagined it would be:
Trigger > VCA input
Offset/attenuated noise > VCA CV input
If you have a VCA with both level bias/offset and CV attenuators (like the Intellijel Amps, Quad VCA, or many others), simply patch the trigger to the input, set the offset to taste (3V, for example), and set the CV attenuator to taste. If you set it at around 1V, you’ll have triggers between 2-4V. The more attenuated the noise, the closer the triggers will be to the offset level. However you do it, it’s a dynamic treat.
I did this patch times four, using four copies of a Frap Tools Sapel trigger, each patched to the CuteLab Missed Opportunities for probability processing before going to the Intellijel Amps in order to be dynamically controlled by the offset and attenuated noise. Amps made this patch much easier because it has CV inputs that normalize, which means I only needed to use a single patch cable to feed all four channels doing trigger processing.1
These now dynamic triggers pinged four Rabid Elephant Natural Gates, which does register dynamic triggers, where I used four Frap Tools Falistri generators as oscillators before being mixed and sent to the Venus Instruments Veno-Echo.2 There are a lot of patch cables, with plenty of mults and Stackcables throughout. Triggers were flying everywhere in the patch. From Sapel to Missed Opportunities, Amps to Stochastic Function Generator, and Ornament & Crime’s legendary Quantermain quad quantizer algorithm. And that’s just to create notes. Other triggers went to the Nonlinearcircuits Divide & Conquer and Stochaos (to trigger its rather excellent stepped CV outputs), Veno-Echo, and Calsynth Changes, which modulated a lackluster kick and the very very cool Optotronics Stereo Lockhart Wavefolder.
The wavefolder was surely the high point in this patch for me. I really only understand how half of it works, but it’s ultra-fun. It adds harmonics in really interesting ways, fed by sharp envelopes to each side from a Calsynth Changes, triggered by a Calsynth Twiigs quad Bernoulli gate based on the Mutable Instruments Branches. This creates some exceptionally cool stereo movement that I’ll have to explore more of.
I also used the Industrial Music Electronics Malgorithm Mk2 for part, which was cool, but was overshadowed by the wavefolder once it was added.
I actually used all eight VCAs in my Amps chain to dynamically control four triggers and four snappy, stochastic envelopes from the Addac506 Stochastic Function Generator which were patched to the Natural Gates’ Control CV inputs. ↩︎
I meant to mix these down in a slightly stereo orientation, but I simply forgot to turn the pan knobs. 😕 ↩︎
I was short on time yesterday, so put together a reasonably simple patch on the iPad. This Jamuary I’m purposefully trying to use unfamiliar techniques with unfamiliar instruments, and that’s what yesterday was all about in the little time I had. But the patch turned out so beautifully that I wanted to take some time to explore its possibilities in the modular. My first thought was to try and use the Oxi One as a Midi > CV converter so that I might patch the outputs of the Alexandernaut Fugue Machine to something like the Synthesis Technology E370 or some other quad sound source. But despite spending the better part of three hours trying to figure it out,1 I still had achieved no progress and so abandoned the idea and decided to do the next best thing. To patch a more intentional version of Jamuary 2507 into the modular and run it through several effects and see if I couldn’t come up with something new.
The initial patch is the same. Fugue Machine feeds the Klevgrand Speldosa and Decidedly Decent Sampler software instruments in AUM. Yesterday those went to reverb and I called it a day. The patch was beautiful and full of promise. Today went much further. The outputs of both Speldosa and the Cello samples were sent from AUM, via the ES-9 outputs, to the AI Synthesis 018 Stereo Matrix Mixer so that they might be spread around the system to three different effects, shifted and morphed matrix style, and finally sent back to AUM before getting some reverb. Though I’m trying new techniques with new things, that doesn’t mean everything in a single patch, lest I become overwhelmed and frustrated.2 The effects I chose were the Venus Instruments Veno-Echo,3 Pladask Elektrisk Dradd brothers, and the Rossum Electro-Music Panharmonium. Speldosa and the cello samples were sent to the delay, with Speldosa only going to Panharmonium, while the cello only was initially sent to the Dradd(s), before adding the delay to the Dradd(s)’ input, slowly adding more, and allowing those higher pitched notes to be granular-ized and spread through the stereo field. The Dradd(s) really turned out to be the highlight, though the delay isn’t far behind. Panharmonium sounds nice, as it always does, but seemed to get lost when it wasn’t leveled as a prominent voice in the mix at a given moment.
To be fair, I struggle with just about everything with the Oxi One. I really need to revisit it with purpose. ↩︎
I recently suffered that sort of frustration when I put two completely unfamiliar modules in my Xmas 2024 Synth. It was an exercise in frustration when it should have been a relaxing time. ↩︎
I used CoVariant, a now seemingly discontinued midi > cv plugin for the iPad to send out an analog clock from the iPad that is perfectly in sync with the midi clock generated by AUM. I will never delete this plugin as long as it continues to work. It also does midi > CV conversion (but I couldn’t figure it out). ↩︎
I don’t really hate dancers, even if this patch might make you think I do.
I don’t trend towards rhythm driven music set to a time grid very often. And even when I do aim to have a rhythmic patch, it’s almost always doing something to mess with time. Jamuary 2501 is no exception.
The first patch of this wonderful Jamuary 2025 started as a desire to use an old and new piece of gear. I bought the Bizarre Jezabel Quarté a couple of years ago when I ran into several Bizarre Jezabel modules for sale at a retail shop in Germany. Until then, the only way to purchase one was to go through a labyrinthine process (for an American) of ordering directly.1 But when I first bought Quarté I didn’t get along with it well at all. I couldn’t figure out how to control the LPG, and what I got was a mess. The controls were crammed, and I sold it forthright. But a few months back I got another hankering to try the Quarté. The PT2399 delay chips are legendary for their lo-fi character, and the quad nature of it as a LPG and delay is right up my current alley of interest. I went on Reverb and grabbed the first one at a decent price, only this one was the updated Quarté Mk2, with a new wet/mixed switch, and some very clever normalizing across channels. The Mk2 can be used in several output configurations, including stereo or quad mono. But the crunch of the delay is what this module is all about.
Quarté Mk2 is not hard to use, but it is difficult to maneuver. Small, unmarked trim pots in very bad places make wiggling a chore when cables are patched in, particular the “t” and “lpgi” trim knobs. The introduction of a wet/mixed switch (which is a 50/50 mix) is very nice. The vactrol-based LPGs sound good, but are quite aggressive, and with a fairly short tail. It’s not always the right sort of strike, which is why I opted to use a Natural gate to articulate notes in this patch, with the Quarté as a delay only.
Most of this patch is pretty simple. Two outputs from the Joranalogue Generate 3 were mixed together and sent to a Natural Gate. The sequence is derived from the Joranalogue Step 8. Both the Natural Gate and Step 8 are clocked by Pam’s Pro Workout, from separate outputs clocked at different rates. The kick was made by Ringing CUNSA, and the hats were blue noise from Sapel sent through a HPF (also CUNSA). Both were triggered by a x8 click output, via the CuteLab Missed Opportunities at increasing levels of probability.
But why is this music for people who hate dancers? It’s pretty groovy. It’s a good tempo for the nightclub. But there is a wrench. At some points, there was an envelope that ripped through the sequence, disrupting the timing and jolting the groove. It’s sudden and unapologetic. The sequence always got back on the grid quickly, but not always in the same spot it was before things were rudely interrupted. It’s jolting and not conducive at all for dancing. I’m sure I’d get thrown out of the club were I to play something like this.
As a result of acquiring both the Synthesis Technology E370 and the Flame Instruments 4VOX, after also getting the Humble Audio Quad Operator and RYK Modular Algo earlier in the year, I’ve been stringing together a series of chord-based polyphonic patches using various forms of slow modulation to control the volume of each chord tone. From standard LFOs to chaos, and stochastic functions to ocean wave simulations, I’ve tried at least a dozen of this style of patching over the last several months. Some of these have used static chords that don’t really move anywhere. Different notes of a chord come in and out chaotically (in most cases), but the chord itself doesn’t change. Others are based on the harmonic series, where only one pitch change of the master oscillator affects all of the individual harmonics resulting in chord changes. All of those were composed using chaos or random as a pitch source. But, with one exception, it wasn’t until this patch that I used the NOH-Modular Pianist with real intent and composed a chord progression to move the piece along. To set a mood and provide some tension and relief with harmonic motion in addition to volume and timbre changes. And this time I went big with using all eight CV outputs, rather than just four.
The NOH-Modular Pianist is an interesting module. It promises a world of harmonic movement in an environment where using chords isn’t a simple proposition. Polyphony in Eurorack is equipment and labor intensive. Each separate note of a chord requires its own separate oscillator, function generator, and VCA, at minimum. and requires its own discrete signal path. That’s a lot of patching for what is an easy task in a DAW or by using keyboard-based synths. It’s a lot of tuning (and re-tuning); lots of signals to tweak, and lots of modulation to account for. Before the Pianist, ways to get this sort of advanced polyphony was hard to come by. You could use a MIDI > CV converter, which has its own challenges, or else by painstakingly programming a pitch sequencer note by note, which requires a level of music theory knowledge that most don’t possess.1 MIDI > CV converters require careful calibration, and there are few sequencers with more than just four channels. But the Pianist is different.
Rather than programming chords note by note, Pianist uses standard western music shorthand for identifying chords, and the module does the rest. When you program it to play a CM7 chord, for instance, it knows to send out pitch data for C E G and Bb. It’ll even repeat chord notes in a different octave if no color tones are used. You can add two chord extensions beyond the 7th, called Colours in the Pianist, or use chord inversions to designate the third or fifth as the bass note in the chord. If a up to six note chord can be played on a piano, it can be played by the Pianist.
Users can freely enter chords from scratch in Free mode, or, to make the job even easier, set it to Scale mode and choose only from chords within your chosen key. The scale can be set to Major, Minor, or any of the modes2 and Pianist does the rest. So, for example, if a user in Scale mode were choose A Major as the scale, Pianist would present you with only AMaj, Bmin, C#min, DMaj, EMaj, F#min, G#dim, the diatonic chords in A Major, in order to facilitate easier chord progressions for theory novices. As long as your oscillators are tuned, your chords will be in key. Nifty. For those who want to use chords outside of a key, or if your composition isn’t really in a specific key, Free mode allows for creating chords from scratch. Virtually any chord is possible (up to six notes). In both modes, harmonic complexity is simple, with up to two color tones available, and made even simpler in Random Gate mode where each gate received will add random colors automatically, and choose colors that make harmonic sense within that chord. The workflow in creating chord progressions is intuitive. I was quickly making fairly complex progressions with repeats and skipped chords with ease.
Though Pianist is a boon to those of us seeking access to polyphonic 12TET harmonic movement in our Eurorack patches, it does have its weaknesses. Though you can move notes up and down in octaves to create chord depth, it’s done in a haphazard way. Rather than setting each note for the exact voicing you’re looking for, you have to rely on functions Pianist calls Shift and Spread in order to get full, rich chords that don’t clutter a particular part of the audio spectrum, but it’s not exactly clear how that affects the chord as a whole. I can hear changes, but can’t always identify them. Easy variety, however, can be achieved when the Gate mode is set to Spread. No chord will be voiced exactly the same which creates intrigue.
The calibration for the module, at least in Version 1.0, is straight funky. This patch uses eight discrete oscillators. While tuning I sent a C from Pianist to set a baseline. But in order for the oscillators to play the C being sent, they each had to be tuned to G, which I found odd. The newest firmware, 1.2, addresses tuning and scales in a way that version 1.0 does not, which is a great improvement by all accounts, even if I haven’t used it yet to note any changes. Since I’m using Pianist in Free mode in this patch, however, there wasn’t a compelling reason for me to upgrade, though I certainly will now that I’ve finished recording it, even if I have an aversion to the upgrade processes of most digital modules.
The screen has a lot of information, and not a lot of room. However, navigation is still reasonably simple and the information on the screen laid out such that it’s not hard to read. It’s easier to read and use than many far more established modules like the Disting Ex, Kermit Mk3, or uO_C, even if there isn’t a lot of screen real estate. The interface is super easy to navigate using the mini joystick/push button. Version 1.2 is reported to have an even more streamlined navigation and menu system. Though altering global settings like the Scale, Gate or Spread behavior requires some menu diving which is never fun, programming chords decidedly does not. It’s a point and click operation made easy with the joystick, all done on one level. Move the cursor to what you want to change, click, move the joystick to the desired value, and click. Done.
A major issue with version 1.0, which may have been changed, is that it always boots up with the first saved sequence. Unless you save your progression to one of the user slots, you will lose your work if the module power cycles. If you don’t have much in your progression, or it’s a super simple that’s no problem. But if it’s long or has a lot of direction you might be losing a lot. Ask me how I know. 😕
Pianist has its own clock that will change on each beat, along with a clock output to trigger envelopes or some other event as chords change. But it also has a clock input, which will move along the chord sequence with every rising edge like any standard step sequencer. Being that I rarely use a steady clock, I haven’t tried the internal clock, and have instead used clocks created by chaos or some other irregular source. This patch used a fairly complicated sub-patch in order to derive the chord changes. I didn’t want haphazard pitch changes in the midst of notes actively being played, but only when nothing was being heard. Finding an approach for this was time consuming, and although there are probably (certainly?) other methods that would work as well, I settled upon an approach using two comparators, one analog and one digital.
The four waves from Swell Physics first went to the Xaoc Devices Samara II. Samara compares all four inputs, and outputs the Maximum signal (AKA Analog OR). Being that these four waves were controlling the volume of the individual chord tones, it occurred to me that once the Maximum signal went below 0v meant that all four parent signals were below 0v, which meant no volume at all from the chord voice. This is exactly when I want to trigger the next chord in the sequence. I then sent that Maximum signal from Samara II to a digital comparator, the Joranalogue Compare 2, with its compare window set to anything below 0v. So once that Maximum signal went below 0v, it would spit out a gate that would trigger a chord change in Pianist.
The eight chord tones created by the Pianist went to eight different oscillators. The root, third, fifth, and seventh (or fifth if there is no seventh) form the base of the chord and all go to one of the four Flame Instruments 4VOX oscillators, while the color notes and two additional root notes, one that follows chord inversions and one that does not, all go to a self-frequency modulated Frap Tools CUNSA, where each filter is set to self oscillate, and pinged in a Natural Gate.
The Flame 4VOX has been around a long time. My brother, a house sound engineer, producer, and DJ who’s been into Eurorack a long time, lusted for one long before I even knew what Eurorack was. It’s a fully polyphonic, wavetable oscillator beast, split into four sections of up to four oscillators each. Each oscillator can create detuned swarms, chords, or be unison. Each oscillator can be controlled by v/oct CV or midi, and is fully polyphonic with its own output. It really was a very advanced piece of gear for its time. It still is, even if it hasn’t been updated in several years and is showing its age. There are two pots and two CV inputs per oscillator that can control several parameters including scanning the wavetable, detuning, amplification, and more. It has internal VCAs to control volume, but I did not like how they functioned at all, and opted to use external VCAs, which worked to my benefit allowing me to modulate two wavetable parameters rather than the volume and only one parameter. There are also separate FM and reset/sync inputs per oscillator, along with its individual output. Even if CV-able options seem to be limited, virtually every facet of the 4VOX can be addressed via midi, although I haven’t used it with midi at all. It’s a very powerful oscillator bank that can cover lots of ground.
Although I wouldn’t say programming the 4VOX is difficult, it’s not as easy as most more modern interfaces. The screen is bare bones with low resolution and a slim viewing radius. The encoder is a little weird. You have to push it down and turn CCW to move downward in menus, while you simply turn it CW to change parameter values inside the menu. As a unit, it’s impressive. There are lots of options, plenty of stock wavetables to choose from, and it sounds good, but it shows its age. Upgrading firmware is a laborious process with modern computers. Although you can install your own wavetables, the processes to convert them to the right format and get them loaded can be a nightmare, particularly if you’re a Mac user. All of the computer-side software is a decade or more old, and workarounds are sometimes needed. I’m not a “I need to load my own wavetables” kind of guy, and my unit came to me with the latest update, but if I were that guy or my unit hadn’t already had the latest firmware, it would not be an easy task. I’ve had similar problems with older gear before3, and they’re no fun.
The 4VOX forms the base of the chords, brought in and out by the four waves from the Addac508 Swell Physics. The sound is both powerful and delicate, with each quadrant set to four slightly detuned, unison oscillators, each one being slightly modulated by the Nonlinearcircuits Frisson. Although I was pleased with the 4VOX’s performance, the Synthesis Technology E370 is a better overall option. Although the E370 is also based on nearly decade-old technology, it’s still a better user experience. The screen is in color, fully customizable, bigger, and gives more information. The stock wavetables are a gold standard. The software UI is easier to navigate using a more standard encoder. The physical UI is also far better arranged. With the 4VOX, the screen is in the middle of the module, knob locations are not symmetrical, and are more difficult to wiggle once everything is patched up. The E370 has everything laid out very neatly. The screen is on the far left, I/O on the far right, with knobs in the middle, leaving more than enough room to wiggle. It’s really a premium user experience. The only advantages the 4VOX has are its price, size, and complete polyphonic midi capabilities. The 4VOX has always been less expensive than the E370, and that remains true on the secondary market. However, the price differential on the used market is much closer than their respective MSRPs, as the E370 can be purchased for well under 50% of the original retail cost. The price difference on my units, both purchased used within a week of one another, was $100. The size, however, cannot change, and in that regard the 4VOX has the E370 soundly beat. At 29hp the 4VOX is still large (and odd hp 😕), but it’s dwarfed by the massive 54hp E370. It’s the massive size, however, that makes the E370 such a pleasure to wiggle.
Once mixed to mono in the Atomosynth Transmon, the 4VOX chords went through the venerable Industrial Music Electronics Malgorithm MkII, a powerhouse FSU-type module with bit crushing, sample reduction, and various types of waveshaping available to have anything from subtly crunchy through completely mangled audio at the output. Using Malgorithm was an absolute treat. Most of the lo-fi effects I tend towards are of the vintage variety, tape sounds, record pops, etc, vs just slightly old sounding digital artifacting, so it was a different sort of experience. On any other day I likely would have chosen distortion in this role, but the day I started this patch I precipitously chose to go with a different kind of dirt. And it was perfect. I was still able to get some nasty distortion via the “Axis” waveshaper (whatever that does), with the bit crushing and sample reduction playing a slowly increasing role. It’s starts clean, then moves to understated digital artifacting, and finally waves of full blown destruction, ending clean once again. One aspect of Malgorithm I enjoyed was the interaction between input level and the waveshaping. It responds similarly to tube distortion circuits, where the harder you drive the input, the more distortion there will be ranging from just barely there to outright obliteration. Each of these waveshaping circuits has three different levels, red, orange, and green, and all of them have their own character. These waveshapers can even interact with each other for nuking your audio from orbit if that’s what you want. I rode faders on the very awesome Michigan Synth Works XVI to control both the input level as well as the wet/dry mix in order to provide a performative aspect to this patch. Both the bit crushing and Nyquist parameters were modulated by the Addac506 Stochastic Function Generator, with a fairly wide range of both rise and fall times between medium and long. Each of the parameters were set to moderate crunchiness with the knobs, with their modulation moving towards a full-resolution signal. This created an absolutely amazing effect from the sound of dying batteries to the fabric of the universe being unzipped and sewn back together. I would highly recommend Malgorithm to anyone, but you’d have to find one first.
Once through Malgorithm and into the stereo matrix mixer, these now buzzy chords went to the Holocene Electronics Non-Linear Memory Machine, with a very light perfect fifth shimmer in the feedback loop. I initially went with a full octave shimmer, but decided against it as it was too prominent and spiraled too far out of control too quickly. This created a very subtle sheen on the chords that isn’t noticeable much of the time, but is a nice effect nonetheless. Feedback and Spread were both modulated by attenuated versions of the Average output from Swell Physics.4
The color tones of each chord were all sent to the mighty Frap Tools CUNSA, a quad filter extraordinaire, and pinged in a pair of Rabid Elephant Natural Gates. Though I was tempted to use the simple sine waves from each LPF output, I later decided to use the HPF output as a means of each oscillator frequency modulating itself in order to add some harmonics, which worked a treat. In retrospect, I could have simplified the patch significantly had I pinged CUNSA itself instead of running the output to Natural Gate, but I chose the Natural Gate route because Natural Gate.
Using a patch technique I’ve used often, the gates that pinged the Natural Gates were created by running the four waves from Swell Physics into the Nonlinearcircuits Numberwang. But rather than simply choosing four gate outputs, I ran several Stackcables so that each strike input on the Natural Gates were each derived from three Numberwang outputs. This filled in space much better. The notes are still sparse, but they’re triggered at a much better pace using three gates each rather than just one. These notes fill out chords in interesting ways. They’re very short, but combined with delay and reverb, those colors hang around long enough to create intrigue in the overall sound without being intrusive.
These notes were sent to what is becoming one of my favorite delays, the Chase Bliss Audio Reverse Mode C, a re-imagining of one of the modes on the legendary Empress Effects Superdelay. Although it certainly does standard stereo delay stuff, it excels at being a quirky sort of delay, able to output normal delays, reverse delays, and octave up reverse delays, by themselves, or in a mix. Mixing delays creates a beautiful sound space of echoes bouncing all around the stereo field, at different speeds and octaves, which is an incredible aural treat. I haven’t yet learned to properly modulate the Reverse Mode C, but that’s a function of not having a firm grasp on midi. As I figure that out, things ought to get very interesting, with different sorts of delays fading in and out in very creative ways.
The last synthesized voice in this patch is the Good and Evil Dradds as an effects send, sending both the chords and ornamental color notes for some granular action. The Dradd(s) outputs went to separate EF-X2 tape echoes with different settings. Ever since getting a second Dradd, I’ve been infatuated by what I can do with them, and this patch may be the best result yet. Both were set to Tape mode with similar P2, but different P1 knob positions, with the P1 parameter on both being modulated by an attenuated version of the Average output on Swell Physics. The Dradds, in some ways, steal the show. They create all sorts of movement in the stereo field and fill the space between chords and color notes in ways that keep the piece from becoming still. They’re the wake left after a large swell passes by. The bio-luminescence after a crashing wave.
The spoken voice is a set of three samples that were triggered in Koala on the iPad. Triggers emanated from the gate outputs on Swell Physics combined in the new Nonlinearcircuits Gator, sent to the Joranalogue Step 8 and then the Befaco CV Thing and converted to midi notes that were sent to trigger Koala samples on the iPad. It took me a while to figure this one out, though it worked exactly how I envisioned. Gates from Swell Physics were combined in Gator, which triggered Step 8. Each of the first three steps sent its individual gate output to a different CV Thing input. This ensured that the three samples were always triggered in the correct order. The samples themselves were then sent to a new collaborative delay plugin, Moon Echo, by AudioThing and Hainbach.. Moon Echo is a modeled simulation of bouncing sound off the moon, and has a very distinct character. The delay was set to fully wet, and has a delay of about 2.5sec, though that changes depending on the day. The moon is not at a fixed distance from the earth, and the plugin reflects that. By “pinging” the moon upon startup, you will get the current distance to the moon, and a new delay time down to five decimal points (1/100,000 of a second). Fucking cool.
One thing I did differently with this patch paid off high dividends, and will absolutely become a staple in my recordings. I’ve been patching for a few years, but am still an absolute novice at standard studio stuff. Mixing, EQ, compression, and everything else in that sphere evades me. I’ve used some very basic EQ in the past, but really only on the final output, which, as I’ve discovered has several drawbacks. This patch was the first I’ve ever recorded using EQ, the highly regarded Toneboosters TB Equalizer 4, on individual channels as they were being recorded. The chords, ornamentals, and reverb send received EQ that greatly improved the sound quality, even if it could still be better. I did, however, neglect to put EQ on the Dradds, which proved to be a mistake, as there is a very occasional pitch that pierces through in what can’t be far from dog whistle frequencies. It’s not eardrum busting, but I can hear it, and it annoys me. I didn’t catch that behavior when recording, and never EQ’d it out. That said, it was also the first time I’ve recorded a modular patch in separate multi-tracks, including the chords, ornamentals, Dradds, spoken voice, reverb return, and the mixed stereo signal (presented here). I can go back and make changes or additions should that be something I want to do, or send the parts to someone else for mixing and mastering should I ever choose to release it.
Overall I’m very pleased with this patch. It was originally composed in a different key and completely different chord progression, and for a special group of online friends. The chord progression I used in this recording wasn’t composed, as such. At least not by me. I asked ChatGPT for a “sad progression, yet with a sense of hope.”5 I asked for it to be more sad, and it changed key from Amin to Dmin, and ended in a non-diatonic chord (DMaj), which I found a wonderful “choice.” Then, as a means to test the Pianist, I asked for several chord extensions and inversions, and ChatGPT complied, giving us what we have in the recording.
Improvised and recorded in 1 take on iPad in AUM via the Expert Sleepers ES-9.
I studied music performance in college, and have a decent grasp on music theory. The last 30 years, however, have pared that knowledge down to basics. I’m certainly no expert, but I can read chord charts and identify chord notes, even if I have to think for a second. ↩︎
The Humble Audio Quad Operator I purchased did not have the latest firmware update, and the internal VCAs all bled badly. I was unable to install the latest firmware with a modern Mac. I was fortunate to have an older one available to me that I was able to use. ↩︎
There are no fewer than seven modulation points in the patch that are all modulated by an attenuated version of the Average output from Swell Physics. ↩︎
This was literally the first time I’ve ever considered purposefully using AI for anything. ↩︎
I’ve used all kinds of slow modulation sources in my patches. Wave simulators, chaos, and slow, free-running LFOs are all staples in my modular practice, and I’ve used all of them as the engine that drives an entire patch. But one thing I’ve never tried in a lead role in a patch is good, old fashioned random modulation. Sure, I’ve used sample and hold or smooth random generators like the Frap Tools Sapél, Mutable Instruments Marbles, or Make Noise Wogglebug for specific tasks within a patch, but outside of Marbles > Rings-type patches, I’ve never based a patch on staochastic movement before.
Random is, well, random, and it’s hard to be intentional when you can’t really expect what’s going to happen next. In some circumstances, that unpredictability is perfect. In other cases, it just makes a really big mess. There are certainly ways to corral in a random signal to fit within particular parameters to allow for more predictability. That’s the basis of stochastics. Sapél has a range probability knob which directs it to choose output values predominantly from a particular range. Marbles has a switch for voltage ranges. Wogglebug similarly has a mechanism for more or less drastic changes. You can even hone random voltage in on your own with a little offset and attenuation. But it’s still random, and even if completely random might work for certain facets of a patch, using it as the main driver becomes difficult while still remaining musical.1 But I was determined to make it work, and I had just the module to help.
The Addac506 Stochastic Function Generator is a powerhouse modulation source made up of four function generators, and most of the bells a whistles one could want. Need cycling envelopes? Check. Slew limiter? Check. One shot envelopes? Check. Audio rate to very slow? Check. EOR and EOC trigger outputs. Check. Offset and attenuation to get your generated functions in the exact range you need it? Check? Some comparator action for related modulation? Check? And this checklist of features goes on and on. But the killer app of the Stochastic Function Generator is its ability to set a very precise range for both Rise and Fall times. This ability allows for some very compelling modulation that changes every cycle, but, particularly when using very slow modulation, does so organically in a way that seems transparent. It can be set to no random generation (standard envelopes), a very wide range with wildly changing Rise and Fall times, or a very narrow range where changes are subtle, and each of these can be done in three modes, slow, medium, or fast (per generator). The Addac506 is a very powerful module with a compelling feature set that can drive entire patches.
I had set out to make another E370 patch using slow modulation to fade the four wavetable oscillators in and out to create a cloud of a chord that is constantly shifting, yet still always the same. I’d been using slow moving bipolar signals for this purpose on several patches of late, but I wanted to try something a little different this time around. I’ve used chaotic systems, and I’d used both free running and synced LFOs, but I’d had problems using cycling unipolar functions in the past because no voice is ever truly out for very long. It’s a constant chord where each note changes volume, but is almost always audible. Mystery, drama, and tension are minimized; each note like a yo-yo rather than a graceful flow in and out and back in again. But the Addac506 is a little different. Unlike most function generators, with the Stochastic Function Generator you can tailor the outputs to any range you want. Those functions needn’t be unipolar, nor with wide ranging levels, and the ability to offset and attenuate signals allows one to shape your function to suit your destination without issue, and it’s this ability to perfectly condition CV before ever leaving the module that enabled me to use it in this slow fading movement I was looking for.
Setting the stochastic functions on the Addac506 is simple: set minimum and maximum Rise and Fall times, and call it a day. At the instantiation of every cycle both Rise and Fall will receive a random value between those set minimum and maximum times, and that stochastically determined envelope will come out. Flick the cycling switch and every cycle is something different. And the Addac506 gives us that, times four. It should be noted that this behavior can be replicated in any function generator that has both End Of Rise and End Of Cycle gate/trigger outputs, plus CV inputs to control the rise and fall times independently. You’ll need to add in a sample and hold or random voltage generator, plus a module for offset and attenuation to define the range of random. All this times four is a lot of patching, and a lot of modules. The Addac506 does it all seamlessly under the panel.
At first I was a little confused. Although I hadn’t initially set any offset, the output was still silent until the voltage as somewhere between 1-2 volts.2 I had anticipated needing to use negative offset to create some space between the fading out of one wave and when it will become audible again, but instead found myself using positive offset to get the flow I was after. Fortunately the flexibility of the Addac506 allowed for quick and easy adjustments to put each wave in the right zone. I added a fair amount of positive offset to the bass note of the chord so that it was always audible, while still having level changes to keep it moving. The other three oscillators used a very slight positive offset. Combining their need to get to somewhere between one and two volts before becoming audible, with the very slow nature of these ever-evolving functions determined the use of positive offset. Up to 40% of their positive range was already inaudible. Giving the functions a bit of a voltage floor rise was in order, lest far too much silence ensue.
Having already decided on my four oscillators for this chord soup, the quad wavetable oscillators of the Synthesis Technology E370, and having had the level control roughly framed out, it was time to look at modulating the wavetables to create movement within each note. The pitch of each oscillator would remain static, and to accompany the change in level, a change in timbre is natural (especially with a morphing wavetable oscillator). Having already used up the outputs of the Addac506, I looked to a familiar module, and one right next to the Stochastic Function Generator, the Addac508 Swell Physics.
Although Swell Physics is definitionally a chaos-based system, and not a random one, the uneven flow up and down of each output was perfect for the job. The bass note oscillator received modulation only on its Detune CV input, while the other three oscillators received both Wave and Detune modulation, the former from Swell Physics and the latter three free running sine wave LFOs from Batumi II. The triangle wave LFOs from Batumi II were used to pan these same three signals slowly through the stereo field with the ST Modular Sum Mix & Pan, while the bass note was planted firmly in the center. Once mixed down to stereo, the four oscillator cloud went to the AI Synthesis 018 Stereo Matrix Mixer.
Once in the matrix mixer it was time to smooth out some of the rough edges with the Holocene Electronics Non-Linear Memory Machine, a favorite of mine since it went in the rack. As a non-clockable delay I found it a wonderful tool for long, drawn out ambient delays, especially with how it can smear repeats into an almost reverb-like sound. Although I tend to pretty heavily modulate the NLMM, I chose to go with no modulation in this patch, with smearing at about 12 o’clock on the knob, and feedback at around 11 o’clock. The NLMM was mixed with the dry signal in the matrix mixer at about a 50:50 ratio, and perhaps even favoring a bit more delay than dry signal.
This mixed signal was sent to both the output mixer and The Dradds for some broken tape machine treatment. Both sides, left and right, or light and dark as it exists in my case, were set to Tape mode at an octave up, with each side behaving slightly differently. The left side tends to randomly switch between forward and backwards playback at double-speed, while the right side randomly switches both direction and speed, although both sides were lightly modulated and sometimes change temporarily. Although I’ve always been enamored by the Dradd(s), it wasn’t until I really started to learn it have my results been what I was always hoping for. Since I sat down to really understand the Dradd(s), my patching has had an opportunity to be more intentional, with my results more satisfying and effective. Plus, having dual Dradds for a stereo field really maximizes the movement and variation it creates.
A heaping portion of distortion, courtesy of the Bizarre Jezabel Mimosa, was also used towards the end of the patch, which created occasional blips and stutters, and a sense of heavy drama. It was only used on the chord cloud and the Dradds, and even then I chose to keep a fair bit of the original dry signal in the mix. I really like the resulting sound, but something is happening that I don’t quite understand. As distortion was introduced into the mix, I did not lower the dry signal. I would have expected the volume would rise, yet it didn’t. The volume got lower, even once the dry and wet distortion signals were nearing full volume in the matrix mixer. It wasn’t until I started to lower the dry signal (the chord, its delayed signal from the NLMM, and the Dradds) that the overall volume started to become louder. My guess is there is some form of phase cancellation happening, although I don’t really know what phenomenon might explain it. You can hear it starting at about the 10 minute mark, with me starting to lower the dry level at about the 11:22 mark, which corresponded in a total output level rise. Curious, that.
Although I was quite happy with my shifting chord after a whole lot of tinkering with envelopes and CV input attenuators, I knew something was missing. I had blips of granular synthesis to break things up, but it needed more. I was hesitant to use SD Multisample as I’ve done a lot of that, but wanted something in a similar vein. Reaching back to one of my very first patches, an attempt at creating a wind chime-like sound and pattern, I decided to add in a randomly created, toy piano sound (or baby R2-D2 sounds as my oldest relayed ). I really enjoyed making that patch when I did it the first time around. It was the first patching technique I’d ever figured out on my own, and a sense of nostalgia pushed me over the edge, even if only to see if I could remember how to replicate it.
This part of the patch started at the Stochastic Function Generator’s “Average” output. This output was patched to the input of the Joranalogue Compare 2. When the Average out from the Addac506 was inside the comparator window, it spat out a gate to the cycling input on a Frap Tools Falistri. While the function was cycling, the End Of Cycle gate triggered Sapel and Quantermain. Sapel sent a value from the N2 output to both Quantermain, in order to send quantized pitch CV, and the Decay CV input of Falistri that would change the envelope length with each note. The VCO changed pitch, and the cycling envelope opened the VCA, each note with a different pitch and length. The sound went from the first VCA to the output mixer, as well as a second VCA which panned the signal to two separate delays, which were then mixed and sent to the output mixer to be mixed with the dry signal and the rest of the patch.
Although the method I ultimately used in this patch is very different than the first time around, the results are similar. The sounds are much higher in pitch, much faster, and much shorter than my original version, but the theory behind creating the sounds was the same, even if I took a different route to get there.3 I wanted short, uneven bursts, and I got them. It’s quite often these days that I realize there are many routes to the same end. Overall, this part of the patch played a very minor role, but an important one. After several listens, I’d probably integrate this part differently were I to do it again. I’d definitely have it more forward for most of the mix rather than hanging around the background. It seems to get lost sometimes, when it should be more prominent. I would also not mess up a patch connection with my second delay, the Qu-Bit Electronix Nautilus, where I plugged into the Right input, and not the left, which, with the feedback pattern chosen, put virtually all of the delay signal from Nautilus on only the Left side. Some might not even notice, but it bothers the shit out of me.
The last part of this patch is the periodic “bubble burst” with accompanying echoes (courtesy of the Xaoc Devices Sarajewo). I stole this idea straight from one of my favorite patches on the Make Noise channel. It’s a simple sound that is both unobtrusive, and only very periodic. The sound was created by pinging (ringing?) CUNSA, which also had its frequency modulated by the highly attenuated HP output of the same filter (another trick I stole from Make Noise – Thanks, Walker!). It was triggered by using a Stackcable to combine three separate gate outputs from the Stochastic Function Generator. These long functions output only very periodic gates at a random interval, so there’s no overcrowding. It also helped provide a sense of scale and depth of the musical space.
Everything ended with a round trip through the Walrus Audio Slöer, which is quickly becoming my favorite reverb. Although I’ve tended towards one of the pitch shifting algorithms, I ultimately decided on using the Dream algorithm, though the Rain algorithm also sounded nice.
I really enjoyed this patch, even if there are a few things I would definitely change. It was both challenging and highly rewarding. It offers answers to some questions, but also to more questions to explore in a future patch.
Although what is or isn’t “musical” is certainly subject to wide interpretation, I think we can still make useful generalizations, while drawing lines between something most would call musical, with yet other examples most would call sound(s) or noise. ↩︎
I’m not sure, but I suspect that the VCA/mixer I was using to process the audio has a logarithmic response, delaying its response with slow(er) signals. The manual doesn’t illuminate the VCA topography, unfortunately. ↩︎
After looking at a patch diagram of the original patch, the methods used between these two patches was quite different, even if it started similarly. It’s nice to know that there is generally more than one way to accomplish some patching goal. ↩︎
After a fantastic morning of sailing through Glacier Bay, I decided to spend the afternoon and evening patching while I watched the beautiful southeast Alaskan coast float by outside my cabin window, door ajar for the the sound and smell of the sea as inspiration. The first patch started simply enough, the Swell Physics four wave outputs into Quad Operator’s four gain inputs, through some delay and reverb, and out for your pleasure. But this time I decided to add a bit of variation via Batumi’s various wave shapes to modulate the wave shape of each of the operators. This modulation had the unanticipated effect of also modulating the apparent volume of the output as well, which created a very cool phasing effect of the individual waves as both their levels and wave shapes were being modulated at separate rates.
The four Quad Operator outputs are mixed down to stereo, then sent through QPAS which had moderately heavy modulation to the cutoff, both Radiance CV inputs, and with gates to both !!¡¡ inputs. I mixed both the LowPass and Smile Pass outputs at about a 75/25 ratio for some very cool stereo imaging, and sent the signal to Nautilus.
Although I’ve used the Chroma feature of the Qu-Bit Nautilus a lot, I’d never used the wavefolder in the feedback path. I’d never used it because I never said to myself, “Man, what this feedback path needs is wavefolding!” Overdrive, distortion, and bitcrushing sure, but unfortunately wavefolding was ignored. A pretty aqua color in the kelp light show on the panel between the orange overdrive and red distortion. This oversight was a dumb and tragic mistake, alleviated by the conscious choice to use wavefolding in this patch. Wavefolding in the feedback path sounds fantastic! Controlling feedback and the Depth of the Chroma is crucial because wavefolding, like distortion and bitcrushing, can create runaway feedback quickly if the balance between feedback and wavefolder isn’t closely watched. The effect, as modulated by a highly attenuated triangle wave from Batumi, created a mix between a nasally and almost fuzz-like tone where there are some edges of the sound starting to leak and sputter, particularly on lower tones.
As accompaniment I went with the LABS Choir samples in the Disting Ex SD Multisample algorithm, using three of the Swell Physics wave outputs for pitch, and the 1 < 2 and 3 > 4 gate outputs through the CuteLab Missed Opportunities as triggers. What I was watching go by as our ship rolled along the grand Alaskan coastline called for drama. Something that could create tension and with some occasional resolution. Although I might better tune the gates to get just the right amount of action if I were to record this patch again, it’s often too sparse, and with not enough harmonization, I feel like the Choir more or less created the effect I imagined, even if it sometimes veered from dramatic to an uneasy suspense. It’s a feel as much as anything else.
Both the Quad Operator > QPAS > Nautilus and the Disting Ex voices went to the mixer, and on to the Stratosphere Cloud Reverb.
Overall I like the direction of this patch, but it needs work. The waves from Swell Physics are often way too slow (a common occurrence once the simulation has been running for a while), and although the modulation from Batumi created some very cool phasing effects, it all combined into a slow moving soup. A soup with promise, but a soup nonetheless. There’s just no pace. Perhaps that’s a reflection of the glaciers I’d been watching all morning, but by the time I’d hit the Stop Recording button in AUM the patch seemed to have come to a crawl, begging for an ending. With time, this patch can be exquisite, but I need to put in the work to get it there.
The Night Time Patch
Once I’d hit stop recording on the daytime patch, I’d become slightly frustrated that I couldn’t get it where I wanted to take it. Either through lack of food, time, patience, feel, or some combination thereof, the patch ended with a whimper. I wasn’t satisfied. Having done several slow, ambient patches for the last several weeks, I knew I needed a change. I needed something to shake that ass to. Something to temper my disappointment in the daytime patch, and something to quell my desire to create something. But only after a visit to the buffet to both feed my body and cleanse my musical palette.
When I started patching again that evening I wasn’t exactly sure what I was going for. I knew I wanted something rhythmic and fun, but started in a way similar to how I’ve started lots of patches recently: four Batumi outputs going to the four gain inputs on the Quad Operator. But this time was different. Rather than using slow, randomly paced waves, as I would do in an ambient patch, I used clock divided LFOs to create a rhythm. Not only did each individual LFO create individual notes directly by lowering and raising the gain on each operator, but also created a rhythm via FM modulation.
With the Quad Operator, when you’re using the Gain CV inputs, each operator is available at its output when the gain input has positive voltage, just like with any VCA. Likewise, each operator is also only able to act as a modulating oscillator for Frequency Modulation to the other operators via the Quad Operator’s FM Matrix when its gain is positive (or the Gain CV input is not patched), making each Gain CV input have an effect on more than just that operator’s output. Each Gain CV input also controls timbre in other operators’ outputs as well, drastically changing the complexion of the overall sound as these various LFOs fade in and out at different, but related speeds, and with differently shaped waves. Sometimes an operator is being FM’d. Sometimes not. It’s a nice way of being able to use all four of the Quad Operator’s outputs, even if tuning can get complex, rather than sacrificing operators to modulation duties only. It doesn’t make sense to use a FM synth like the Quad Operator in this fashion very often, but it works well in some styles of patching. The four operator outputs are routed to the Mutable Instruments Veils for a stereo mix down before going to the final mixer. From there it’s sent to the Blue Mangoo Stratosphere Cloud Reverb.
If I were to do a patch like this again, I would probably process one or more the Quad Operator outputs individually to add some spice, rather than immediately mixing them to stereo. To treat each of those outputs as individual entities unto themselves, rather than assimilating them into a larger body immediately after their creation, never allowing each to have their own existence. Sending one output or another through a separate effect or process than the others might help create something special that is lost once an individual signal is married to another in a mixer.
The kick drum is about as simple as it gets. A /2 square wave output from Batumi to Plaits, twist the knobs a bit until you find the timbre, decay, and pitch you want, and turn the FM trimmer to taste. One of the wonders of Plaits, and Braids before it, is its versatility. It can be almost anything you want it to be. From a FM oscillator to speech synthesis to kick drums and plucked strings, Plaits can make a whole lot of sounds and be the main voice in any patch. If you have something like the Jasmine And Olive Trees Traffic, or if you’re savvy with CV processing, Plaits can be many things at once. Today, however, Plaits was just a humble kick drum.
I had hoped to use QPAS in a more exciting manner. One of my favorite ways to use QPAS is by pinging it. But because QPAS normally lives isolated in a Make Noise only case, I haven’t really experimented much with pinging it without the using the nice, wide gates of both Tempi and René v2. But my clock in this case, the Sitka Gravity, doesn’t have any of those, and my sequencer, the T12, was already being used. Gravity outputs short triggers, about 15ms, which are great for telling something else it’s time to do its thing, but virtually useless as direct modulation, and the ability to use the gate’s length to help control modulation, such as with an ADSR envelope, is lost. I could ping the input with a trigger easily enough, but instead decided to use a probability gated square wave from Batumi via the CuteLab Missed Opportunities, which wasn’t quite the same as using the 50% duty cycle gates Tempi spits out. Although the developer of the Gravity has said that a gate mode, wherein the duty cycle of the gate will be adjustable, for now it’s all triggers. I could (should) have just used the triggers from Gravity to sync to Batumi and trigger envelopes from that unused Changes sitting there wondering why he was left out of the party, but it just didn’t occur to me until I was too deep in the patch to bother with changing it. With the Batumi square wave, the pronouncement of the modulation and ease of switching up the gate patterns just wasn’t there. You can hear the modulation well enough in isolation, but it’s almost nonexistent in the mix.
Despite my lack of imagination in modulating QPAS with unfamiliar tools, its role in the patch, however, is crucial. Its LP outputs add a marimba-like percussive element (thanks to feedback patching the left HP output to the highly attenuated Freq 1 input) to accompany the kick drum, and contribute a party-like atmosphere in the patch.
There are also two new-to-me elements to this patch that I hadn’t yet tried. The first is to use the Doboz T12 as an arpeggiator. Since the T12 is brand new, there are a lot of new things to try. It’s a deep, highly versatile module. I’ve used it as a sequencer, and as a touch controller (my over-70 mom also had a great time using it as a touch controller). In this patch I’d use it as an arpeggiator with the second new-to-me element: using the Poly Wavetable algorithm on the Disting Ex.
The T12 is turning out to be something akin to the greatest in-case touch controller in Eurorack. Of course I haven’t used many others, and those that I have used never tried to be quite as much as the T12 strives after, but the T12 seems to have some serious chops in terms of immediately challenging Eurorack mainstays like the Make Noise Pressure Points or Doboz’s own TSNM MKII. The T12’s main limitations are its inputs and outputs, and that it requires some level of menu diving . It only has three inputs and outputs. A pitch CV, an AUX CV, and a gate output, with clock and reset inputs, along with one solitary CV input. Something like Pressure Points can put out several voltages from several “channels” simultaneously, which is not something the T12 can do, but the T12 more than makes up for these shortcomings with flexibility, the customizability of each mode, and the ultra-intuitive user interface. The T12 is, by far, the easiest module I’ve used that has a screen based UI. Virtually all of the options for each mode are changed on the surface menu level, without any real diving at all. Doboz did a knockout job with designing the interface to be powerful, expansive, and super easy to navigate.
The T12 in use as an arpeggiator is smooth and ultra-fun. It will arpeggiate as many notes as you can get your fingers on, and the touch plates are very responsive when making changes. There’s generally enough space to maneuver use three or four fingers of one hand to make your note changes, but there are some button combos that require some serious hand dexterity, or the use of two hands. But once you get a feel for how to move your hand in the space, muscle memory starts to take over, and it’s nothing but pure fun. As with most arpeggiators there are several directions or patterns you can choose. This patch started with a forward pattern, and a 20% probability that a gate will be skipped, then, at some point, switched to a random direction, with a 20% probability that a gate will be skipped. There are many options I could have investigated, like the probability and range of pitch variability (by step or overall), or transposition, or using the AUX CV output, but I chose to keep it simple, and, quite frankly, I was having a really good time spending my night doing something simple and performative.
If I’m being honest, this patch was the first time I’ve used the Disting Ex in any algorithm other than the SD Multisample. The Disting Ex too is a deep, highly versatile module, to put it lightly, but I traded away a 1010 Music Bitbox Micro for a Disting Ex because of its capability as a multisample player, specifically that it can play eight simultaneous voices of polyphonic multisamples via pitch CV and gate inputs. No other module can do that in quite the same way. But I’d already used SD Multisample in my first patch on the trip, the Daytime Patch before this one, as well as my test patch before leaving. Every patch I’d made with this case included SD Multisample, and I wanted to try something new with this synth.
Because the patch was lively, I wanted to use a lively sound source for my arpeggios. Quad Operator was already in full use, and Plaits was thumping along as a kick drum, so I knew I needed to find another algorithm in the Disting Ex. If QPAS could self oscillate (without help), and if it could follow v/oct pitch CV, I probably would have used it as the arpeggiator voice either by pinging it (which QPAS does fantastically, as this patch shows), or as a sine wave oscillator through a VCA using the envelopes created by the T12. But QPAS doesn’t self oscillate or follow v/oct pitch CV, so the Disting Ex was the way. I could have chosen a completely unpatched CalSynth Changes, a very excellent MI Stages 1:1 clone, loaded with the latest quimem firmware in Ouroboros (Harmonic Oscillator) mode, but by the time I decided I wasn’t going to use Changes as a modulation source I was already set on using the Poly Wavetable algorithm in the Disting Ex.
Fortunately, Poly Wavetable is very similar to SD Multisample in how it functions. Poly Wavetable can take 3 CV sources and 3 gates and play up to 8 simultaneous voices polyphonically. That said, the weakness of the Disting UI and very small display becomes glaringly magnified when you need to make parameter changes, especially with nearly-50 eyes. You get a slew of options, several dozen, and a very tiny screen with which to navigate and make changes. I would have greatly preferred to control envelopes and such with a dedicated envelope generator outside of the Disting in a VCA or LPG, but I elected to use the internal envelope because I didn’t have any more VCAs to use, much less two of them. The 8 VCA channels (plus VCAs within modules like QPAS and Quad Operator) I brought with me were already in use doing other things, so fumbling through the menu system was the only way. Don’t get me wrong: the Disting Ex is incredibly powerful, and each algorithm is highly customizable. It sounds fantastic, and it can do dozens of operations from polyphonic multisample player to a pitch to CV generator, matrix mixer, or lots of other tasks. The Disting line, but particularly the Ex, is truly is the ultimate Swiss Army knife of Eurorack. Such a broad tool, that is also quite deep, is bound to be awkward sometimes. Since they’re built to do everything, it’s impossible to also have a UI that will match a good workflow for all of the algorithm functionality (perhaps, some might argue, for any of them). That said, the UI manages to be fairly simple to navigate. If you can see it. Most of the options are controlled on the surface level of the menu. You turn one encoder to change options, a second to change a parameter within that option, and click a third to save it.
Having listened back to the recording several times, I definitely wish that I had a pair of LPGs available to me in the case. That attack and intoxicating decay from a LPG would have been just the thing. The arpeggios in the Night Time patch are enunciated, but only just adequately. I never really got to shaping the internal ADSR envelope beyond shortening the release a bit, and the UI is actively hostile to changing while trying to perform. The UI really hindered me there, (I was trying to booty shake, not squint my eyes at a tiny screen trying to optimize my envelope), and that unused Changes was still staring at me with that sad face one gets when everyone except you were invited to the party. I know there are 3rd party screens for the Disting that alleviate the problem, this one came with one when I traded for it, but of the ~2200hp in my synth, my only 1u row is in the Make Noise 4 Zone Bus Case, which is occupied by a CV Bus Mk2, so it’s out of the question unless I decide to get two Distings.
This patch was a lot of fun to build and perform. I hope to patch in this same vein on my full synth soon enough.
One last tool that I used on this trip that I hadn’t really written much about, and that I bought specifically for this trip, is the Bolanle PH400 4-Channel Headphone Amp. Since the plan was to use this synth with my brother, I wanted a means to have independent volume control. I loathe having to share volume control of headphones, and so decided on a small headphone amplifier. Although the PH400 is certainly not something I’d call studio worthy, I can say that it’s a good piece of kit, and it met all of my requirements. It had to be powered by USB C, small and portable, and it had to have individual control, and it had to sound good or better. I wanted something with both sized headphone outputs for each channel to avoid adapters, and the PH400 has that. Each channel also has its own mute button. As an added bonus, the LED light show is cool. This thing works great.
