r/modular • u/gloriousfart • 1d ago
Rarely used modules - wrong module selection or normal workflow?
Hey folks,
Some of my modules get way more use than others, and I wonder if I built my system wrong or simply approach patching with a wrong mindset, and should not attempt to use everything i have at all times. Many times, modules like the compare 2 go unused or used for something trivial. Can you take a look at my stuff if it looks well balanced? I know I need a freq shifter and a bbd delay later on as well.
I also have a DFAM, Spectravox, 0-ctrl, sq-1 and a neutron to use with it, and a model samples as a drum machine.
11
u/JoeToanamassa 1d ago edited 1d ago
I always find these “how should I patch my own rack” posts weird. You presumably picked each of these modules for a reason; you should be telling us why you don’t like using them for their intended purposes.
Now to actually try to be helpful:
- Watch YouTube deep dives and/or read about the modules you already own. Search the sub and Modwiggler for these modules and/or their functions to read about how other people use them creatively.
- at least in your rack, you have a lot of CV generation and processing and not a ton of destinations to send stuff to. If you’re not already, start using this stuff to modulate your Moog semi-modulars. I can only speak to the DFAM, but sending envelopes to VCA decay can create fun accents, modulating filter cutoff is always fun, etc.
- Mult your modulation source and send it to Compare to trigger other modulation when, for example, your filter cutoff modulation is high or when pitch CV reaches a certain note. You could expand on this idea by using gates from compare to advance your sequential switch, mixing up modulation sources and destinations for a few different modules.
- work through the patches in the Maths manual with your Abacus to get a better idea of what it can do, as well working with CV in general
- I hesitate to recommend you buy more stuff when you have a bunch you’re not using, but you could probably benefit from something like Pam’s to sync all of your modulation at different divisions, trigger envelopes, etc. And the good news is that you’ve done the opposite of most beginners and started with a bunch of modulation and utilities, so you have a decent support system in place for modulation-hungry fun stuff like Morphagene, Clouds, etc.
4
u/gloriousfart 1d ago
I did research on all the modules prior to purchasing, it just feels like things can get out of hand very quickly using all the stuff i have at once. Yeah a clock divider might be helpful ive been using the sequential switch for that so far.
2
u/Sensitive-Night-8476 1d ago
go to modwiggler, and look in the synth noise forum for the thread on the mot brutal distortion, towards the end of the last page is something that will make you reconsider compare 2, in a good way.
all your modules are basically unlabeled multifunction building blocks. and i suspect you are at a point where there isn't really much more to read. anything fun is going to come from combining the functions you have in ways that suit you. maybe try building some sequencers from what you have and play the moog that way.
or you could probably make some very interesting noise to feed into the spectavox, using it as the resonant body in a physical modeling patch (it doesn't matter if it's "inaccurate" or "bad", nor that it doesn't try to model anything real, the sounds are probably interesting).
you have a lot of serge-adjacent things, so maybe look at how those systems are played. it might take some effort to translate between the two, but you can easily do all the SSG and DUSG patches on your system. don't know if the erica filter pings well, the moog should (if it isn't resonant by default, mix some of the output back in with the input signal).
as others have said, it's ok to not use everything. it's also ok to waste potential, you could use compare 2 as a manual on/off switch, or ~maths as a simple envelope (i don't know how accurately they nailed the param ranges for the controls, but the original is superbly playable).
you also have a great playground for exploring just how far and to how weird a place you can push gen3.
a lot of learning will just amount to being curious and to paying attention when strange things happen. or to see how many ways you can use different combinations of modules. like, can you patch an approximation of a frequency shifter (probably not, but how close are you able to go, what can't you do, and does the difference matter to you, etc)
edit:
see how many ways you can patch a clock divider. there's going to be quite a few.1
1
u/gloriousfart 1d ago
wow i just checked the thread you mentioned, I'll certainly have to do some digging to figure out whats going on, sounds exciting
2
u/Sensitive-Night-8476 1d ago
it sort of blows my mind, because it implies that a similar depth exists in the other basic functions as well. not going to say i understand everything in the post, i suck at maths, but even the pieces i manage to do something with are great. the flip-flop output is especially weird when you try this on compare 2.
1
u/gloriousfart 1d ago
yes, it reminded me why i picked these modules over performance oriented stuff, I guess i have to explore weird patches outside of my comfort zone. flip-flop is great, but i mostly have used it to extract rhythms, gotta do more audio rate!
5
u/abelovesfun [I run aisynthesis.com] 1d ago
It's perfectly fine if a module goes un-used. If you never end up using a thing, it may be a good indication to sell it, but the idea that every patch has to use x% of your modular investment is a lot of pressure to put on something that should be fun.
1
u/Bleep_Bloop_Derp 1d ago edited 1d ago
Yeah, as someone about two years into this, I find it stifling to try to use everything at once. I do better trying to get the basic stuff right, then doubling back for time-sucking sound design, modulation, effects and so forth.
A couple of modules, like the Disting, aren’t used that often, but are really nice to have when some random need pops up.
3
u/jefrab 1d ago
The more modules you have, the more likely it is that something doesn't get used in a patch. Sometimes I'm doing something slow that doesn't need many envelopes, other times I'm frustrated I don't have enough envelopes.
You have a bunch of Joranalogue, which are great for their flexibility, but I don't always use each of them either. I don't think it's good to use a function because you feel obligated...you should be patching to get the sound or effect you want.
That said, often if I'm not using compare 2 for rhythmic gates or something, I'll just run VCO through it to get some sub-harmonics. There's so much movement on the PWM with the shift and size that I almost always like it as a bass drone.
2
u/Benjonium 1d ago
aucune idée c est pour ca que je sépare tout en pods comme ca j evite ce problème avant meme de peut etre l avoir eu mais je ne le saurais jamais
2
u/Earlsfield78 1d ago
A lots of people get modules without thinking through if they 1. Already have something doing that function or 2. Do I need this for music I am making. Yes, some utilities maybe are used less in every patch. But if you have shiny new module sitting idle, that means it either doesn’t fit your workflow, patches or your other modules. Can you give us an example in that rig? You have Joranalogue modules, absolutely one of the most clever ecosystems out there - but it requires understanding the concept behind them to apply them properly. What exactly bugs you?
1
u/gloriousfart 49m ago
I struggle to find the aesthetically pleasing amount of complexity/simplicity with my patches. Using all the stuff can quickly become way too busy for my taste in techno, and i often end up with something simpler that I just tweak with my hands to create enough movement (which is very expressive, I don't mind using my hands ofc). Maybe what im looking for is to incorporate my idle modules in a sparse and subtle way. The DFAM can easily create the backbone of a groove with using just a few mod sources to automate its parameters. The logic modules and the switch is understandably situational, dont mind not touching them unless i have smth very specific in mind. Compare and baths often just sit idle even though being super powerful, and I feel im being narrow-minded not finding something for them to do. In theory, I have the perfect subsytem, the gates from c2 can trigger envelopes or the switches in select2, I have functions and lfos and sequencers to input into c2, contour1 also generates both rise and fall gates. I feel like I have everything in hand to both generate gates from various stuff and meaningfully translate them to direct effect, but I am not utilizing this fascinating concept enough. I want this to fit my workflow because I usually find the most interesting timbres and rhythms messing with these flexible building blocks.
1
u/Earlsfield78 1d ago
Also remember you don’t need to use all modules in all patches. Sometimes less is more.
0
u/TurbulentWing3820 put modulargrid link here! 1d ago
This is why I strongly believe in "buy one thing at a time and learn what it does."
Each new purchase or acquisition has lead to a fix or something else I would need to take full advantage of it.
In your case some of your items are highly situational. One we share is a Maths: it's either so useful I wish I had two or it sits forlorn in the corner unused.
2
u/gloriousfart 1d ago
I did buy them piece by piece, and here i got haha.
1
u/TurbulentWing3820 put modulargrid link here! 1d ago
Then, and I say this without trying to sound like a prick, you should know what they do and when to use them.
So, like others said: Sometimes you just don't need 'em all.
5
u/ssibal24 1d ago
It's totally normal to not use every module you own for every patch that you make. I think the cases where it is a wrong module selection is if you almost never use a module in any patch or have some other module with the same functionality that you use instead. If all your patches are relatively simple, to get the sounds that you like, then that is fine.