Hi Greg
This is what I’ve observed in my own setup. Others may debunk this, but it is all about the song. Example…in song #1 I use a piano rack, and an organ rack, using 25% CPU. In song #2, I use an amp sim, compressor, reverb, and chorus, using 36% CPU. In song #3, I use a synth rack and a huge Kontakt sampled piano rack using 51% CPU.
If i run them seperate…no problem. But, if I put them all into one song, that adds up to 112% CPU. All the crackling, and dropouts would lead to a crash. Yes, I could put everything into one basket, and pick and choose, which would take quite an effort to deactivate the ones I wouldn’t use. When pre-loading, it’s all in memory, but I only use a small part of that memory when using songs to control what you use. Otherwise, everything is active and pushing CPU. I reuse several racks throughout the set list, so not as many things loaded in memory.
Again, others may debunk this, but that has been my experience since I started using Cantabile in 2016. I averaged 4 gigs a week until Covid, and I learned through experience what works well for me. I was in 6 bands at one time, and each one had a approx. a 120 song repertoire That’s roughly 720 songs that I had to keep up with. With my setup, I could load the night’s setlist for the respective band, and be on my way with no problems. I was always ready for the next song before a guitarist could reset his pedalboard.
BTW…no need to feel stupid. We were all in that position at one time or another, because there is quite a learning curve to this. I still feel that way when others come up with their elaborate bindings. Hope this helps you.
Cheers
Corky
P.S. I usually have a song at the end of each setlist that contains a rack with an organ, piano, synth, horns, in case of requests, or a guest is invited onstage. Those are ready in case I need it quick. They usually cover most anything thrown at me.