Source
r/modular•
orb_king

Fun Exercise In Modular Thinking

One thing I've been trying to work on this year is thinking about my modular as a system of primitive components, rather than thinking about features and modules themselves. A good activity for this has been looking at a snazzy module, and thinking about it as the sum of its primitive parts. I've been very interested in the Moog DFAM lately

It seems pretty simple, here are the parts as I can identify them:

  • 2 VCOs (w/ Sync and FM)
  • 1 Filter (HP/LP)
  • 3 EGs (pitch, filter, volume)
  • 2 8 step sequencers (pitch and velocity by default)
  • 1 3-channel mixer (OSC 1 & 2, Noise/Ext)
  • 6 VCAs (mostly attenuating various EGs!)

Using this information, it's pretty easy for me to look at my rack and figure out if I can make a DFAM out of what I have already. This usually results in me trying to squeeze an extra EG or oscillator out of something, which is fun and surprising. Obviously this isn't going to replace a DFAM, but it does provide quick, free ideas and a good way to think about whether buying into a hard-wired solution for a given problem is worth it for you!

Edit: this is in response to a lot of the non-modular thinking that I see here, which looks more like "I would like a drum sound" -> "I should buy a drum module". It's a good illustrator of why buying primitive/simple modules can be more interesting and versatile than buying a kick drum module.

Posted Dec 20, 2021, 7:59 PM UTC · edited

6217
bow_to_lord_spacecat•

There’s a block diagram of the DFAM in the manual that shows signal flow between everything FYI. I’ve patched it up in my rig based off that with good results. It’s a good exersize.

25
the_puritan•

For me, it isn't so much "can I replicate this with my existing stuff?" as much as it's "what functionality would I have left after taking up all of these modules to do what this does by itself?"

20
EndOfTheMoth•

This sounds like a very useful approach.

9
orb_kingOP•

Thank you! Because of this particular example, today I discovered that my Malekko Voltage Block sends a constant voltage out of all 8 outputs when it's not clocked! This makes it very easy to attenuate when used with a VCA! (I was thinking about buying a 16n Faderbank for this and didn't even realize how close this module is to that!)

7
Agawell•

Yeah it’s a good idea to ask yourself before buying any module - do I already have those components? Can I patch xyz module from what I already have? Do I need those modules in the rest of the patch or will I run out of modules to use in the rest of the patch? Etc

6
alexrm1x•

Omri Cohen did a fantastic video on that https://youtu.be/HGixS70ThQM

It even inspired me to create dfam in Maschine: https://youtu.be/1Bt74SE89_g

4
orb_kingOP•

He has a good one on building the Subharmonicon too!

4
Theywhererobots•

These sorts of experiments are great, I’ve learned loads this way. I’ve made a deconstructed marbles by using a random source (white noise into S+H), attenuation/polarizer into logic operations for triggers/gates while using a S+H for pitch cv from clocked LFO’s for looping patterns sent to a quantizer.

I find this exercise extremely valuable. Actually, the more utility modules I bought, my understanding of synthesis grew rapidly. Having a solid function generator really helps the learning process along as well. Mutable instruments Stages helped me understand how to make lots from scratch.

4
Personal-Turnover-31•

I hadn’t thought about it before but Stages is an excellent learning tool for this, in addition to being a module than can emulate almost anything* if you patch it right.

  • anything with 6 or fewer building blocks, not accounting for chaining Stages, and certainly not accounting for ergonomics or clear panel design.
3
stealthgerbil•

Another good exercise which is related is trying to replicate the patches from the patch library website on my modular. They are meant for the semi modular synths but a decent size rack has all of those functions.

3
uglyKIDmoe•

To your point about drum sounds, it’s why I bought a bit box. I prefer synthesizing the sounds myself and recording them into the BB for use later. I already had an MPC, a AudioThingies DoubleDrummer, and a buttload of software samplers and drum machines. So loading sample packs into my modular was not ideal.

But with a simple analog osc + noise source and some relatively basic patching, building your own analog drum kit is pretty easy (and IMO a mandatory study for anyone looking to become a serious synthesist).

3
yeolesquid•

This is the way. I recently sat down and thought about how to replicate a 303. Sequencer > quantizer > slew with gated modulation > VCO > enveloped filter. The fun part is then adding to it or switching it up—add modulation, tweak parameters, swap voices.

I mean this is the whole point of playing with stupid expensive toys right?

2
hrvst_music•

You'll probably find this fun and intriguing then - https://www.patchtcg.com/

2
TimeRaveler•

I did this exact thing - trying to create a dfam from my existing rack, here’s what I ended up with.

2 VCOs + Noise > Mixer > LP/HP Filter > Final VCA

VCO1 > VCO2 FM

Noise > Filter Mod

Env1 > VCA1 Signal In > Final VCA

Env2 > VCA2 Signal In > Filter Mod

Env3 > VCA3 Signal In > VCO1/2 Pitch

Seq1 CV > VCO Pitch

Seq2 CV > Mult > VCA1/2/3 Control

Seq Clock > Mult > Env1/2/3 Trigger

2
AkiraClaw•

This is a nice idea! I wonder if it would be easy to replicate a 0-coast without just having a trove of make noise modules?

2
schtickkicker•

I think the answer depends on a) whether you have a modular rig already or not, and b) whether you're looking for the 'essence' of the 0-coast, or trying to replicate its every capability.

2
orb_kingOP•

There’s one way to find out! Get out the pencil and paper!

1
[deleted]•

[deleted]

1
[deleted]•

[deleted]

0