Kontakt in Cubase: one instance per instrument, or as few instances as possible?
I did a bit of googling on this and saw a bit of discussion on this over the years, but couldn't really find any kind of consensus on the question of whether it uses less system resources to run one instance of Kontakt per instrument, or if it's a better idea to run as many instruments as possible in each instance.
Some background: Until just a few days ago, I've been using Cubase 4 (!!!) as my main DAW for the past 15 or so years, and I finally decided to move to a 64-bit host. I had sort of just assumed I would move to Studio One for a few different reasons, but the recent Cubase sale gave me incentive to stick with what I know and like using.
However, I did give Studio One a trial run, and one thing I really liked about it is that its virtual instrument setup works like Cubase's Instrument Rack, except that you can make multiple Instrument Tracks for the same Kontakt instance. Where Cubase would have a main track for automation, an audio track for each output, and a MIDI track for each MIDI channel, in Studio One you can make one track that contains MIDI, audio, and automations for each Kontakt sound/instrument. This is something I had hoped would be in Cubase 12, but it seems that even with Instrument Tracks, it still gets a bit messy with multi-output instruments.
But when searching for information about this, I found a fair amount of people saying that Cubase is more efficient if you just make a new Instrument Track for each sound in Kontakt. So I guess my questions are:
-
Is there any way to do Studio One-style Instrument Tracks in this situation?
-
If not, is running one instance of Kontakt per sound really less of a strain on the system? Having 40-50 Kontakt instances running sounds crazy to me, but I've never actually tried something like that.
Posted Oct 2, 2022, 10:41 AM UTC · edited