|
|
Post by pt3r on Mar 2, 2024 13:56:03 GMT
Have we all figured out how to make music on the AE modular that goes beyond ambient drones, or is this your only purpose for owning a modular? How do you translate musical ideas to the ‘limited’ world of modular? How to you rhythm? How do you build your melodies on a modular (sequencer)? What are your go to modules?
Is there uberhaupt any interest in discussing these topics?
|
|
|
|
Post by maydonpoliris on Mar 2, 2024 20:48:49 GMT
Have we all figured out how to make music on the AE modular that goes beyond ambient drones, or is this your only purpose for owning a modular?
Haven't yet worked out which direction I really want to go with the modular but I do know it hasn't yet been in the direction of drones. it mostly turns into some sort of techno.
How do you translate musical ideas to the ‘limited’ world of modular?
sometimes it's just one sound either on the modular or outside of it that can trigger an idea and then I build a rhythm or melody around that. For my last upload I used the original 'it doesn't mean a thing' music video to try to copy parts of it into the Ae.
For example
To make a violin sound - played around a lot with this part and ended up using the 2 auto to generate a little flowing melody into an Osc and then added some tremelo via the Multifx.
Add Swing - via the 2env end out triggering another 2 env both with the decay on about half.
Down stepping beat - Turned the Seq 8 into a Seq 4 by using the reset input. Adjusted the 4 knobs to make a CV that stepped down from mid to low
Played around with using a piano swing via the Solina and Le Module
Googled how to make a brass sound using a synth/modular to add trumpets and patched around this for a while.
I failed at adding the piano and trumpets the way I wanted to and didn't suit so the patch went into a different direction but this gives an example of how a patch idea evolves and translates for me.
How to you rhythm?
mostly use a combination of the MMdiv, Heartbeat and Slew/Edge. adding uProb is good too.
How do you build your melodies on a modular (sequencer)?
Seq8 is my go to for a melody, sometimes use 2 Auto. The O&C Sequens firmware is great for building melodies.
Seq8 random is good to change the melody up.
Using the 3vSwitch to go between the different Seq8's or combining the different Seq8 into the MM33 then attenuating each of them is a good way to build on them.
What are your go to modules?
2env and Seq 8 are my absolutes as everything can come from those.
SV is my go to filter.
Wavetables is probably my go to source
Is there uberhaupt any interest in discussing these topics?
absolutely, would be interested to hear others ideas as it sparks further ideas
|
|
ketap
New Member
Posts: 8
|
Post by ketap on Mar 3, 2024 5:49:51 GMT
I have a great interest, but I have little to contribute since I have a very empirical approach to modular systems. But that's the point for me: up until modular, there has always been a keyboard or some other mediator between me and the music that had to be learned with difficulty. With modular systems, the approach is more like a drum, sound without a level of abstraction. For me, modular systems are not limited, but probably the first time that I can make the music I like without the dogma of virtuosity. Kind of punk. In this sense, my go to module is TheGreatDivide by Kurt and Algodrone because I don't understand anything but it sounds beautiful!
|
|
pol
Wiki Editors
Posts: 1,278
|
Post by pol on Mar 3, 2024 8:32:33 GMT
My approach on patching very much depends on why I switched the AE on that day; quite often it's just to have a fiddle and see what happens.... I am trying to use it more like I use the rest of my studio, i.e I have a type/ style of sound in mind and can I get it relatively quickly on the AE? This has got more successful by sticking to simpler sounds rather than patching every module that might help in... I love using the AE for weird fx/pads/percussion - it is excellent for the latter which I usually end up sampling but do prefer to trigger the AE from my MPC as much as I can. The main reason to sample is so I can do another patch  . I had to ban myself from using the Solina module as it was on everything for a while, I often start with the Baestle drum if I want weird percussion and nearly always use several lfos to subtly vary parameters not in time with the music. I've done quite a few of the patch challenges, partly to help me understand my AE better. I sometimes set my own in say, use a VCO and the Wavetable to make a different lead sound which often starts off a new song idea 😁. |
|
|
|
Post by pt3r on Mar 3, 2024 10:34:38 GMT
For the historians amongst us you can clearly see/hear an evolutuion in the patches I made over the past three years. Wow just writing it down made me realize it’s been more than 3 years now since I got my first starter rack 2 at the end of 2020 (best christmas persent ever to myself). Anyway my first tracks were very much drone oriented since that is the easiest thing to patch up on a modular, understand the whole cv thing and listen to the statisfying soounds you can squeze out of the spaghetti of patchcables. And then over the years I started to get more melodies worked in as I started to find a workflow for the seq8 which first looked very limited but it is so patchable that I got me another one and figured a way to connect them together into a frankenstein 16 step sequencer. then I build my first module using the diy kit which result in my first AEclidian module based of a arduino module squeezed in there. Thing still works like a charm after 2 years and it is my goto pulse divider. The drones never grow old for me, instead they just grew darker and more alive with the arrival of the algodrone and the cirrus modules. My approach to drones and sc(r)apes is very loose, I let the modular take it wherever it goes in a very organic way like a monster living behind the faceplates. The arrival of the namke ‘s wonkystuff drum modules was another major evolution in my patching since all of a sudden I could produce convincing drums without the need to sacrifice all my vca’s and envelopes to create proper kicks. The sd110 is just the best snare sound for my goal. First I did a lot of sequencing of the drums with the AEuropi module but that is now my main masterclock module which I use to drive a triq164 as the brain of my sequencing. It gives me the proper level of granularity and it allows me to produce beats that are offkilter yet premeditated. I’m still trying my hand at making proper melodies on the AE modular but I guess funbun has taken the crown in that respect. The melodies Damon manages to squeeze out of his AE modular system are just mindboggling. So perhaps he can give use a look behind the curtain own how he does that. |
|
|
|
Post by chillja on Mar 6, 2024 1:59:33 GMT
My focus is now on making one flexible (semi-permanent) patch. Some things might be changed around later, and especially during construction, but goal is to have some set structures in place. So it would feel like one coherent (learnable) system/instrument. Before i felt that the patching would naturally stop (“patching fatigue”?). Then i finish by just connecting enough to make a recording. So having a plan is what works best for me. Happy i don’t lack ideas, i just want them incorporated into a greater whole. As for style of music, thats not totally clear yet. But possibilities for rhythm and melodies are for sure part of my goal.
I have it broken it down to four main objectives (of course they all blend at some points). - Mixing, - Modulation, - Sound generation and - Sequencing.
So far…
Mixing:
Working with 2x Mixconsoles due to previous quad-mixing ideas. Second mixer is routed to one of the first ones return ch. Both mixers sends’s are mixed for now (in two “B” mixers, also mixing them in mults is tried/an option). This makes both mixers send’s send to the same destination. Then i want to at least split one of the send’s further, to two or more fx. And have manual control over these “secondary send’s”. It’s based on previous studio experiments. I call it «send tree». If two stereo effects, their outputs would be mixed into two utility mixers again to keep them stereo and return as one. The return, preferably also to a mixconcole channel, to allow for fx-feedback and to “send effects to other effects” possible alternate back to the first effect again. And fun stuff like this. To save on mixconsole channels for other instruments i have multiple sound sources going into two sub mixers with gain knobs, each feeding a shared filter, before mixconsole, now. For mixing i’m also thinking about sidechain-ducking, in a crude form.
Modulation: Both generated and manually played, and routing of these. The manually played modulation consist of Nanosynth Ribbon controller, joystick, and sc500 (turntable device). The sc500 is setup (for now) to play two steady tones, both as “beat” and “sample” track. This allows for envelope followed “beat” tone with fader cuts, and PLL pitch tracking “sample” tone, separately, so they don’t interfere during following/tracking. Other than that, Switchmatrix and possible additional 3vcswitches, diy attenuators and latching switches to route the modulation.
Sound generation: Not so far on this one yet. I want to try making a kick out of nanosynth. I made a funky snare-like sound today with Wavetables output patched back into freq mod. I don’t need more sound generators, and i would like them to be able to change into different roles.
Sequencing: Not determined/explored enough. A Beatstep pro (via Nanobridge) would likely be the main one. Not so much to sequence only from it directly, but use it for clocking and starting/stopping ae sequencers, selector, dividers, etc. I’m inspired by Venetian Snares modular sequencing setup and techniques, among others. I like the idea to input these clocking-patterns unquantized, so some day i might try to program Bela to be a midi looper for the beatstep (it always locks to the beat). For melody/harmony i also don’t like the idea of inputting every note. Here i would like to borrow some ideas from Steevio, the way he combines simple sequences into more complex ones. Also i might take a look at the original ornament&crime firmware for this task.
So this are the main ideas. I’m looking for my input/playing to matter, but also to be suprised, so it becomes not only «playing an instrument», but playing «togheter with». It’s hard to imagine some of these previous points never to be re-patched at some points. Especially the sequencing and modulation part. I just realize i need some structured goals to work towards.
Edit: also using a roll of some velcro-like material, cut to size, to gather patch wires and see the modules and patchpoints better.
|
|
|
|
Post by solipsistnation on Mar 6, 2024 19:50:47 GMT
I mostly don't do ambient drones. 8) I've built up a collection of sequencers and things that generate semirandom notes like the RBSS. I clock them differently and have different stuff happening on each. Usually I have a SEQ8 doing some kind of backing (chords or a slow bassline) and 1 or 2 SEQ16s doing leads that I can switch between or layer. I'll run them all through the same quantizer so they stay more or less in tune with one another. Then I modulate whatever else is going on (filters, parameters on the oscillators, whatever) with LFOs or envelopes or whatever's handy, or do something where I've got a SEQ16 doing the CV and some other thing (Euclid Grid, Topograf) doing the VCA envelope trigger to make it rhythmically interesting. It's not super complex. I tear down and repatch every time to keep things from getting TOO similar (although I have patching habits for sure, and I sometimes forget to change the melody on the sequencers between patches). I find that if I go in with an idea like "I want to do a thing that sounds like this" I usually fail, but sometimes in interesting ways. It works better to find a thing that seems interesting and build on top of that. I tend to build "performable" patches-- I set it up so I can turn parts on or off or turn a couple of knobs to do stuff (Topograf drum fills, Euclid Grid step changes), jam on it until I have a feel for how it fits together and what layers work together and what doesn't (and usually I decide to not use some piece here-- like, a part that seemed interesting on its own but doesn't work with the rest of it), hit record, and perform the piece. I usually do a couple of takes and keep the best. I don't always post or upload the recordings. Rhythm is clocked from MIDI, using Heartbeat or just the basic MASTER midi in and divided down. Heartbeat is nice for the multiple outputs that you can set to different clock divisions. For drums, I use a mix of Topograf and TRIQ164 and whatever drum modules (mostly Wonkystuff) are installed, or VCO or filter blips of various sorts. What are your go to modules?
I have some habits I'm trying to get over, like this:
* RBSS (clocked at 16th notes) -> quantizer -> RAINS CV in
* Euclid Grid (clocked at 16 notes) -> RAINS pluck input, then RAINS outputs -> some delay -> reverb
* slow LFO -> one of the RAINS modulation inputs (structure or damping)
* SEQ8 (clocked at one step per 4 or 8 quarter notes)-> quantizer -> Le Module CV
* an envelope (triggered by something-- euclid grid? quantizer note change trigger?) -> Le Module modulation inputs
* Le Module -> phaser -> reverb
That's instantly very very pretty and I can spend a lot of time grooving on that. I should pull Rains and le module and hide them for a while.
|
|
. 
