How many patches in a song list?

[PeterPan8]

I had some problems loading too many patches in a song, which crashed my system. So I was wondering how many patches you can insert in a "song". It probably depends on the RAM size. I have 16Gb with a SSD, but I'm quite sure if I boost it up to 32Gb RAM I could put more patches in a song list.

Who's using TP with 32Gb, and how many patches can you insert in a song?

[FishmanSoftware]

I had some problems loading too many patches in a song, which crashed my system. So I was wondering how many patches you can insert in a "song". It probably depends on the RAM size. I have 16Gb with a SSD, but I'm quite sure if I boost it up to 32Gb RAM I could put more patches in a song list.

Who's using TP with 32Gb, and how many patches can you insert in a song?

There is no limit on how many patches can be in a song, but only some of them can be loaded into memory at the same time. You can tell that a song patch is loaded into memory when the name turns blue. The question might be, how many patches can be in memory at a time, and the answer is, normally max is 10, but whether this will work or not mostly depends on the sounds themselves. If you are using something like SynthMaster One, the sounds are pretty compact so typically 10 fit in memory with no issues. If you use deluxe sampled sounds, and you also use splits and layers, you might only be able to fit a couple/few patches in memory at a time. You can go to "Options/Preferences..." and turn off "Use Enhanced Cache" which will reduce the number of patches loaded at once to 4 (vs 10 when Enhanced Cache is enabled). This might solve the problems you are experiencing.

[PeterPan8]

Thanks for the tip about the cache. I didn't know the purpose, now I do!
My patches are usually a mix of many synth, Kontakt Orchestra, Omnisphere, Addictive Piano, among others.

I usually load all slots with various VSTs. I was wondering if 32Gb vs. 18Gb of RAM would make them load faster.

[FishmanSoftware]

Thanks for the tip about the cache. I didn't know the purpose, now I do!
My patches are usually a mix of many synth, Kontakt Orchestra, Omnisphere, Addictive Piano, among others.

I usually load all slots with various VSTs. I was wondering if 32Gb vs. 18Gb of RAM would make them load faster.

32 GB typically won't make them load any faster, but it does give them a better chance to all fit into memory. If you are loading all slots and using these "memory hungry" VSTs, probably you will need to disable "Use Enhanced Cache" to allow TP to work.

Each plugin manufacturer can (possibly) provide info about how much memory is used by a particular sound, then you would add it all together for all VSTs used at the same time, then realize some RAM is used by the OS and other apps, then you could estimate how many TriplePlay patches might fit into memory with 32 GB. Complicated, I know.

For advanced users, we probably could provide a setting where you can fine-tune how many patches are cached, so you could set it to (for example) 7, or whatever might work, rather than having to choose between 10 or 4.

Explaining it all here, I can see that we should (ideally) somehow detect how much actual RAM there is in your system, and also how much is used by each hosted plugin, and have a setting where you can say how much you want to allocate toward TP, and then adapt the cache accordingly. Maybe someday.

[PeterPan8]

Explaining it all here, I can see that we should (ideally) somehow detect how much actual RAM there is in your system, and also how much is used by each hosted plugin, and have a setting where you can say how much you want to allocate toward TP, and then adapt the cache accordingly. Maybe someday.

That would be a nice-to-have tool for sure!

I'll wait for it eagerly!