![]() Like a lot of us I can suffer from analysis paralysis. But generally speaking I can add Console 1 and dial it in pretty quickly for any track. Vocals and bass always have other stuff before and after Console 1. It is the primary or even the only plugin on most tracks. I use it on every track, bus and output track. I decided when I got C1 that I'd commit fully to it until such a time that it let me down in some way. It's also been easier on my system resources than the approach I was using in the past. The reason Console 1 has worked well for me is mostly on the workflow side. It's also worth noting that a LOT of mixers don't agree with this philosophy at all and use whatever plugins they think make each track sound best, and it works well for them, so there is no "right way." Softube is one of the more expensive ones. Some are free/cheap and some are expensive. So instead of having a 1073 on the snare and an SSL on the overheads and a Trident on the kick, you have one emulation for all tracks.Īs others have pointed out, there are other console emulations out there that should do the same thing as long as you apply them across your entire project. The idea is that the tracks should fight each other less and "mesh" more than if you use the typical approach of treating each source with whatever pre/eq/comp combination make each track sound best in isolation. I mentioned it here because it seems like a lot of the presumed mojo with MixBus is based on the idea that every channel, bus and output track use the same "console strip" with the same emulation of EQ, compression, gain staging etc. It's commonly available on Reverb around $400. It is a package consisting of console emulation plugins and a hardware controller. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |