bassinine wrote:outdropt wrote:You could use a multiband compressor to side chain the mid/low end (80-200/300hz) so it only lowers the volume of that range..
In ableton you can use an audio effect rack, create two chains, place a multiband dynamics plugin on each....
Have one solo everything above 200/300hz and the other play everything below that, then place a compressor on the low end and sidechain the kick and snare.
Just thought of this but i haven't tried it out yet.
hmm, that's a pretty efficient way of doing it actually.
personally though, i chop the FUCK out of all my basslines (after i side-chain - love glitching out a pumping side-chained bassline). but could always bounce that out and use your technique on the already glitched copy if it conflicts... i assume that's what you do.
I like to have a default setup in ableton so I don't get conflicts like that... A group is just a bus pretty much.
Ill have 5+ groups that each start with a blank massive instance, and an audio instance that is silent and is listening to the group (so its easy to bounce down, all i have to do is hit record)
Synth
Bass
Sub
Vocals
Atmosphere
In these groups ill do my main eq cuts (roll off synths at 800hz, sub bass LP at 60-80hz, ect), compression, maybe filtering.
Then i have each of those pointing into there own bus with the respective names
synth/vocals
sub/bass
atmosphere
These are then getting sent to a master bus.
Here is where i do my master work (i might have filtering effects going on the sub/bass, Ill put sausage fattner here, And here is where i would put the multiband compression)... So if i bounce down my bass from the bass group.. I can just create another audio instance and play out to the Bass/sub group, avoiding the problem you mentioned.
I try to keep things cohesive so i don't get lost in automation overload.... That is when shits happening and you dont know whats causing... That has happened too many times
