Building a CPU friendly General Template in Logic Pro

Hey everyone,

Throwing a template question out there for some of you with more tech savviness than I…

Is it better to load every instrument into its own Kontak player or more ideal to stack instruments inside of Kontakt and use the multi-out feature with individual midi tracks controlling separate articulations?

I’m building a general template in Logic and trying to do one of those big huge inclusive ones. I tried routing several midi tracks through contact as a multi-channel instrument to stack articulations but that seems to be taxing my system more than I thought. I recently found out that Logic automatically turns off anything unused though; so I am thinking having even 6000 tracks of Kontakt loaded with individual articulations shouldn’t matter until I actually using too many of them. Which should be less taxing on the system than loading one Kontakt player with 16 different articulations triggered by individual midi tracks… So is the first approach (zillions of powered off tracks of Kontakt players) the more ideal one for me?

Also, at first glance it’s a LOT to navigate. Even color coded. How many of you folks built one of these mammoths up only to still build individual templates for future pieces of music and end up forsaking the giant, generalized one altogether? Maybe narrowing the scope of instruments on per project basis or getting a “bare bones (strings, percussion) and then customizing on top of that existing, more minimal one might suit me better 🤔 What have you found most successfully helped that tech part of the workflow?

8 comments