Farview
Well-known member
It's using an aux send to send the signal to an effect. This way, you can have one instance of a reverb that multiple tracks are sent to. This is the way it was done in the analog world.
Tadpui
Well-known member
That's the way that I always do it. I guess I've just never heard that term before.
But the OP says that he can't do it this way because of the way his tracks are set up. But given the definition of this term, he also says that he's doing it this way...I'm starting to suspect that there are some inefficiencies in his technique. It might be time to go back to the drawing board with some of his routing...
steffeeH
New member
I've spent a lot of time improving my mixer routings. Believe me, if send reverbs would have artistically worked for my sounds - I would have used it. But right now the sends have to work as room gluing only, and that feel more like a mixing technique to me than a reverb effect or artistic reverb, which I suppose is why I didn't include it in the OP.
The differencies between my different reverbs are like night and day. And it has to be this way if needed, otherwise it sounds like a demo since it then doesn't lift up the sounds as much as they could if I were to use the same reverb on a bunch of things.
Parallel reverb processing is simply having a separate channel for your reverb with all the dry sound cut to zero. Then you can add all kinds of further processing to the reverb itself. Though I don't use any extra mixertracks for this, I instead use a routing plugin called Patcher on the original mixertrack for the sound (or submix if there's several layers). The reason why is partly because I save mixertracks, but also because using Patcher for this gives you far more possibilities than if I were to have the reverb on a separate mixertrack.
The differencies between my different reverbs are like night and day. And it has to be this way if needed, otherwise it sounds like a demo since it then doesn't lift up the sounds as much as they could if I were to use the same reverb on a bunch of things.
Parallel reverb processing is simply having a separate channel for your reverb with all the dry sound cut to zero. Then you can add all kinds of further processing to the reverb itself. Though I don't use any extra mixertracks for this, I instead use a routing plugin called Patcher on the original mixertrack for the sound (or submix if there's several layers). The reason why is partly because I save mixertracks, but also because using Patcher for this gives you far more possibilities than if I were to have the reverb on a separate mixertrack.
Bobbsy
Boring Old Git
I've never used FL Studio...does it have the feature most DAWs have whereby once you're happy with a reverb (or any effect) you can render it and "freeze" the track so you CPU no longer has to do everything live in real time.
Steenamaroo
...
+1. Your system shouldn't need workarounds or crutches.
Where's the buffer size at, and what drive are you recording to/streaming from?
Raise the buffer size to 256, if it's lower than that, and move your session to a second drive or external drive (USB2 7200rpm minimum).
If you're using sample libraries in the session, check where those are stored too. System drive isn't always a good idea.
DM60
Well-known member
Really, if you're must mixing, move it up to 1024, should matter that much for mixing.
Bobbsy
Boring Old Git
Yup. In fact, for MIXING just crank it up and don't worry about specific numbers. If you start to get an annoying lag when you hit play, turn it down a notch.
However, don't forget to turn the buffer size down again for tracking. That's where the latency will kill you.
However, don't forget to turn the buffer size down again for tracking. That's where the latency will kill you.