![]() ![]() So now I'm just running doubles of all the Sable string patches, Div A and B, and the Universal Sordino is applied to group tracks for each section - One for normal and one for Sordino, routed as sends from the VI tracks in Cubase (I just manually draw in automation to mute or unmute). IN kontakt's browser pane, go to the Monitor tab, then to Engine to see the memory breakdown. Bottom line is my overall ram use doubled from that, but the sample memory didn't increase. ![]() Then when I got the Universal Sordino plugin, I doubled that again routed to a 2nd Kontakt output. I loaded 3 copies of each, used the tune/transpose trick to make divisi's A,B, and C of all 4 of those patches. There are 4 patches for each string section. I really went to town on loading multiples of the same with my new template, especially for Sable strings. Something related that I did discover recently is loading multiple copies of the same patch (ie, to use the transpose trick to make players 2,3, or string divisi) may not use more sample memory, it sure adds a TON of ram to the Object Memory total. I'm using the lowest pre-load buffer possible, so that may explain. I am running an all Spitfire template from SSD, and I find that purging samples doesn't actually reduce ram usage at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |