sircuit wrote: ↑
Tue Oct 08, 2019 3:37 am
I say "confusingly" because often time this number of oscs is simply overkill and is somehow "inviting" to think true multilayer (like omnisphere) and leads to frustration.
Also, I'm not at all for "one preset does it all" kind of strategy because you simply can't get inside (any) the synth the processing required for releasable music. So when I use Rapid, I pretty much use 1 layer, and maybe more when programming pads (and I add various layers of movement).
recursive one wrote: ↑
Tue Oct 08, 2019 4:35 am
Well, I've made a lot of various sounds in Rapid but I have to say I still don't understand the purpose of 8 layers. [...] Rapid's effects are good for sound design but getting a finished mix-ready sound still requires external processing.
Maybe it's time to give some food for thought.
When looking at projects created with Serum/Sylenth or other one layer synths I often see behavior like this:
Random EDM Producer wrote:"Let's build a melody! Load up this Serum patch. Oh, somehow it's missing power. Okay, add another instance, just for the attack part. Still not big enough? Add another instance for the bass part!"
In the end there are 3 to 4 synth instances to build just one logical instrument. In the perspective of plugins, yes it's 4 independent elements. But from a songs perspective it's only one
musical element, like a "melody".
The real workflow killer here is when it comes to saving a complicated setup/patch and reuse it. Especially if you switch DAWs. Getting a 4 instance synth patch from Ableton to FL Studio or vice verca? A click nightmare. With one plugin instance you greatly decouple your dependencies. It's easier to manage and switch out thing.
With multiple instances you have to name your synth tracks, group them, probably send them through multiple buses, all with FX. Then join and glue them together to have a coherent sound. With Rapid you move part of this annoying DAW workflow into one instance. This is one of the core concepts of a layer synth.
We build this synth so you can easily polish a sound within one instance. People miss this kind of concept and that's one of the reasons I'm often bewildered by requests like multi-out, since this kind of destroys the whole idea. Really, if someone request a multi-out, it's a sign that they don't embrace the quicker workflow and just want to fiddle around instead of getting their sounds done quick.
Dont just stack things!
In professional EDM production you hardly use one instance with one oscillator to create your main lead. It's always a combination of multiple instances. The thing is, if you continue this idea, you don't even have to think in multiple instance. If you really build your sound from ground up, you can fine tune everything within one instance of Rapid. The 8 layers are not there to use 24 saw oscillators. And they are not there to build complete songs. They are there to combine different dynamic elements. Some good examples are patches like:
Sequence/Flying Data 1
Sequence/Flying Data 2
Which use multiple elements with different motions. You don't get this in a one layer synth. Yes, you can still build it with multiple instances. But it's a logical musical element. You want to play it in one go. Can you imagine how complicated it would be to get this setup from one project to another, or just cloning it? Here it's just one patch.
Anyway. Maybe be a bit more creative. Yes. It's different, but there are also sounds you just haven't thought about. Think about it: If it's easier to manage complexity, you can simultaneously increase complexity and depth in other parts of your production, since you get more time, right? Not wasting time doing multi-out things unnecessarily mixing everything, even if it's not really necessary.