I’ve followed the instructions for purging samples from Session String Pro (Komplete 11), having reduced the sample load from 223Mb to just over 1MB. I then re-save the instrument to a new non-default location, e.g. my Desktop. I then re-export the rackspace.
But when I open Gig Performer and import that rackspace again, it loads the SSP instrument (the newly exported one) correctly, but with the sample pool back to showing a full 223Mb load.
This also happens if, instead of exporting and re-importing the rackspace, I simply save and re-open the gig file.
So it appears that sample purging is simply not working AT ALL for Session Strings Pro, which is a huge problem.
Windows 10, Cubase 10, Kontakt 5.8.1, Session Strings Pro 1.4.0
Purged samples, saved and re-opened Cubase project.
Sample pool shows 223MB - the full sample pool with no purging ;-(
Argh
In addition, saving as a new instrument with the purges done, then loading the new instrument loads up all the samples as though purge was never done.
NOTICE: The problem seems to be Session Strings Pro. I tested 2 other Kontakt Libraries: Alicia’s Keys and Kinetic Metal - BOTH properly recall sample purging!
It is extremely unlikely that this is a Gig Performer issue. All GP does is save and recall whatever state is supplied by the plugin. You should probably contact NI about this issue.
I don’t currently have a solution other than to replace all instances of Session Strings Pro across every rackspace I’ve ever created with a different VST.
I think you’re correct that the problem is with Session Strings Pro that comes with Komplete 11. It’s possible that the version of Session Strings that comes with Komplete 12 fixes the issue, but just upgrading will cost me a rather ridiculous $400.
In Komplete 11, I tested their Symphony Series and Symphony Essentials libraries, and purging works for them, so I guess I’ll either have to switch to one of them for everything or buy another string library, which doesn’t sound very appealing, cuz string libraries in particular are super pricey.
This is pretty depressing, but sadly, not all that surprising. NI has been truly disappointing of late. Witness Massive X. I think the X stands for disappointment.
If you don’t need the animations, I suppose you could create a new library from session strings pro by using a tool like SampleRobot to regenerate raw samples which you could then use to create a new instrument where purging would now work. SampleRobot isn’t cheap either but may be useful to you separately and so worth the cost.
Considered that, but if I’m gonna shell that much out, I want a guarantee that the updated version WILL handle purging properly, which of course, I won’t get - unless someone out there who has the updated version can confirm purge is working properly. Even then, I’d probably just shell out the rest for the full upgrade. Appreciate the heads up tho.
I just saw your post — I wonder — is this only happening on Windows? @pianopaul says it works fine for him (he’s on a Mac)…that might be a useful clue for Native Instruments.
