I have a couple versions of Native Instruments Komplete (11 and 13 Ultimate)and Aururia V collections (4, 6 and 8) installed on my computers. I just purchased updates to Komplete 14 Ultimate and V collection 9.
My rackspaces reference and load older VST versions of Kontakt 5 and 6, amoung some other VST’s used from these libraries.
If I update my Kontakt and Aurturia programs to the latest versions and uninstall the previous versions, will the latest versions of the synths/samplers automatically be called up as the embedded VST in the rackspace? Or will I have to go in and replace every VST program with the latest version?
Wanting to clear up drive space, but with 5 bands and many programs/patches amongst them, looks like a daunting task if I have to replace every one with the updated VST version.
When the state of the plugins which is stored in the gig file is compatible with the new version of the plugins then there is no issue.
When you use now Kontakt 6 and install Kontakt 7 and remove then Kontakt 6, you will have a problem
I think after Aurturia 4, they changed how their library structure was. Couldn’t locate custom patches I made for the newer versions.
What is the change between Kontakt 6 and 7 that would not make them a compatible/load instead?
Do I need to remove Kontakt 6 first, then install 7?
Gig Performer tries to load Kontakt 6 and then loads the stored state.
Now when you deinstall Kontakt 6 Gig Performer will not automatically load Kontakt 7.
Best is to save your Kontakt instruments or Multis on the disk.
This saved files you cAn load with Kontakt 7.
You can install Kontakt 7 without deinstalling Kontakt 6, so you have both in parallel
In general, new major versions of plugins should be compatible for presets you can save within the plugin.
The stored state of a plugin is rarely compatible with a newer major version.
Most every patch I use in Kontakt is custom named and saved in a new folder I made for each band. Even if it a stock sound. I save each separate patch and multi (custom named for the song and band they are for).
For the “stored state” what specifically are you referencing? Example?
The complete patch of Kontakt, not the samples are stored as a state within the gig file.
As an example:
Load Kontakt, load an instrument and save the gig file.
Now make some changes to the instrument and save it within Kontakt under the same name.
Do not save the gig file.
Now reload the gig file.
You will notice that it is not the sound in Kontakt what you saved as instrument.
It is the sound of the unchanged instrument.
That is because Gig Performer and in general all other VST hosts or DAW do not load presets, they just recall the saved state of the plugin.
If you create a rackspace and you load/setup sounds in all the plugins in the rackspace and then you save your gigfile and then reload your gigfile another time, you’ll get back all the same sounds that you had previously created.
That happens because the host (Gig Performer but generally any host) saves the information needed for each plugin to get the same sound back.
If I make changes to the VST in a Kontakt patch/multi, I also save/export the rackspace file. That is a routine I have always used.
Make a change, save everything.
I treat rackspaces as “songs” and GIG files as “sets” for each show. Rarely reuse a GIG file, as the sets change.