I usually make the part (if I'm programming the drums), pick the kit, even tho' I always end up changing snare and/or kick and pick those from other kits, then assign to the tracks and print them (usually I run some outboard insert already when printing) My go to is SSL Ch, actually I usually mix with the whole faux console so SSL Ch on every channel, Api eqs on every channel and pretty much only CL1B, FET and 2500 as plugin compressors, with some "outsider" here and there like mPressor or EMI.īricasti and Lexicon impulses for reverb via TL Space I never touched the internal plugins, I always use outboard or external plugins (external to Superior of course). How much processing do you guys use when you use Superior 2.0 on your tracks? Do you use the internal plugins? External plugins? Or are you using them dry? If you are using external plugins, which ones? Sometimes it seems like the program is just TOO deep with too many variables to handle at once.Superior is great, Allaire, Avatar and Barresi here (altho' I didn't hear the latest libraries and I heard they're pretty cool).ĭo you PRINT your tracks? Because you don't want to mix with the sounds coming out from the plugin. I've been trying hard to put together a template complete with plugins on the drum tracks so I don't have to redo it every time I start a new song. I can never seem to get my drum tracks just right and it makes me wonder if I'm just overthinking this. Bass, Snare, Overheads, etc., which leads me to use external processing on them, typically the Waves SLL channel strip. I always bus the outputs to different tracks in Logic, i.e. I've been using Superior 2.0 for about a year now.
0 kommentar(er)
