Hi, I’m working since many years with Cantabile 2.
Here I use setlists with behind in average 100 subsessions.
My aim is, playing live/improvise by switching from one preset/patch/multi
to another…my personal “best of” not all! For that I have easy midi assigns to my hardware synthesizers (C0+B1)
in order switch to next or previous patch.
Since some weeks I test Cantabile 3 and work hard in understanding and learn the
best workflow for me
Meanwhile I work with linked racks coming from having for each patch/preset/multi a
song with an VSTi instance behind. My aim was to use the great preload function in C3.
But, using e.g. up to 50 Kontakt instances caused very fast RAM issues. I have only
16GB RAM. I don’t know, how many GB RAM I would need, to come with Kontakt not
into RAM issues.
I tested the same in placing 40-50 Kontakt instances into linked Racks. Naturally I
get the same RAM issues as with the song function.
The purge function in Kontakt doesn’t help, even I saved each rack state with the purge
of Kontakt. This surprised me: the RAM is high as without purgin the Kontakt samples.
C3 needs naturally loading times then preloading is activated. So my idea of spreading
my Kontakt songs over some setlists would cause longer setlist loading times in switching
from one setlist to an other.
The classical way would be - as in C2 - to load one instance as song or rack and
have for each patch of Kontakt a state or song. But, then I have for each patch loading
Has somebody an idea, how I should make that work in C3?
Or is it on the end naturally not possible switching fluid trough a lot of Kontakt patches?
I had yesterday the idea, if C3 would only preload the next and previous state/song, that I wouldn’t
have the RAM limitation, cause loading up to 10-12 Kontakt instances is not a problem for C3.
Even C3 doesn’t work in that way: do you have an idea for an equal workaround?