After some libraries have installed in the Spitfire App, you may see an Optimise button. This feature is very useful when it comes to our dedicated plugin libraries, as it will improve the loading speeds on your machine. The optimise function rewrites the sample files to move meta data to the head of the file, which means that the content of the file can be read with much less jumping about on disk (which when multiplied by potentially thousands of files adds up to a much quicker load).
How To Optimise
1) Open the Spitfire App and log in, in this example we will optimise the BBC Symphony Orchestra
2) Browse to the BBC SO plugin iand click Optimise
3) Once selected, another window will ask you to be sure your DAW is closed. From there, click Optimise again
4) The optimisation process will begin. The time this will take varies depending on your system. Be sure to not use the libraries whilst the optimisation process is happening.
Comments
9 comments
I did this and no longer see my presets at all in the Kontakt (6.2.0) browser. In the appropriate folders (which worked, pre-optimisation) there are now .zpreset, .zmulti and .zconfig files. But none of them are visible in Kontakt. I see no .nkc or .nkr files.
I'm trying to do this with the BBCSO Professional library, and it seems to stop at file 194 of 138271. I left it overnight and it didn't finish.
With BBC SO Core, I get the same issue as Johm - my user presets are no longer visible in the plugin, after optimising. Also, is this still relevant for SSDs? There should be no jumping around, should there?
Please be aware, even on an SSD (if it's useful?), this will take hours for a library such as BBCSO Pro. Would be nice to put a warning in the main text about this.
is it possible to interrupt the process and finish it later?
I'm just curious as to why the sample files aren't provided in this optimised format to begin with?
Hi All,
My apologies for the slower responses on this particular article. If those unanswered questions above are still relevant, please do get in touch with us via the "help" button.
Thanks
Jack
This takes literally as long as the library took to download, at current rate I'm looking at 19 hours... I'm not sure why there wasn't a default re-written batch sold to customers (like myself) who purchased the product after you discovered the hiccup.
So, 5 months on from the first query about the time to Optimise, I have calculated 26 hours to Optimise a newly bought SSD. Surely this should be sorted beforehand?
Please sign in to leave a comment.