HD1 ,User samples & Ram observations after OPS v2.02

[MarPabl]

So a new Live Kronos webcast is in order

[Yuma]

In other words data in User Sample Banks can be loaded into Sampling Mode (for editing)
and if your actual Ram contents are 5 Gb preloaded then Ram will overflow and will be
automatically loaded again in Virtual mode ! so you have to follow a complex strategy !
For me was quite easy but what about a simple User ?

interesting, as far as i understood from the manual the max size of a sample set that you can make is the limit of your installed memory, which is about 2.8 GB on a 3 gig expanded Kronos when you unload everything from the Kronos.

But if i read it correctly there is a way to create larger sets?

How do you do that :) ?

From what I understand, Antony is referring to the following example:

You have 5 sample sets:
Sampleset1.KSC, size: 1GB.
Sampleset2.KSC, size: 800MB.
Sampleset3.KSC, size: 600MB.
Sampleset4.KSC, size: 400MB.
Sampleset5.KSC, size: 100MB.

Start with 1GB of free RAM.

01) Load Sampleset1.KSC (clear all RAM).
02) Save as TotalCollection.KSC. It automatically saves a TotalCollection_UserBank.KSC as well. Let's say that has a pre-load size of 200MB.

03) Load TotalCollection_UserBank.KSC (clear all RAM), which fills 200MB of RAM, so you have 800MB free.
04) Load Sampleset2.KSC (append to RAM).
05) Save to TotalCollection.KSC. It automatically overwrites the existing TotalCollection_UserBank.KSC as well. Let's say that has a new pre-load size of 400MB.

06) Load TotalCollection_UserBank.KSC (clear all RAM), which fills 400MB of RAM, so you have 600MB free.
07) Load Sampleset3.KSC (append to RAM).
08) Save to TotalCollection.KSC. It automatically overwrites the existing TotalCollection_UserBank.KSC as well. Let's say that has a new pre-load size of 600MB.

09) Load TotalCollection_UserBank.KSC (clear all RAM), which fills 600MB of RAM, so you have 400MB free.
10) Load Sampleset4.KSC (append to RAM).
11) Save to TotalCollection.KSC. It automatically overwrites the existing TotalCollection_UserBank.KSC as well. Let's say that has a new pre-load size of 900MB.

12) Load TotalCollection_UserBank.KSC (clear all RAM), which fills 900MB of RAM, so you have 100MB free.
13) Load Sampleset5.KSC (append to RAM).
14) Save to TotalCollection.KSC. It automatically overwrites the existing TotalCollection_UserBank.KSC as well. Let's say that has a new pre-load size of 950MB.

15) Load TotalCollection_UserBank.KSC (clear all RAM), which fills 950MB of RAM, so you have only 50MB free.

So your TotalCollection_UserBank.KSC takes up 950MB in RAM, which fits in the 1GB free RAM.
Your TotalCollection.KSC will be 1GB+800MB+600MB+400MB+100MB=2.9GB in size, thus larger than the 1GB free RAM.

Going to Sampling Mode while having TotalCollection_UserBank.KSC loaded would give issues then.

[BasariStudios]

The good and the bad part is that THIS_UserBank.KSC does not Load the
PCG of that Set, Loads only Samples. Multiple of those can be Loaded and
all assigned to different PCG...no matter how many KSC files you have you
will still have the Complete Set Loaded. With UserBank you are not limited
to 1KSC, 1PCG, 1Folder system anymore like in the old KSC (which is not
true but its a lot harder to combine Multiple Sets). So Yuma, no, thats not
the way since at each Save process you will be overwriting the KSC thus
you will be deleting what was there before.
In plain Mortal Words would be:
1. Create one UserBank and Save it. Create the Second one and Save it.
THIS_UserBank.KSC and THIS1_UserBank.KSC.
2. Load them Both and create the Whole Program Set out of those 2 and
Save it as a PCG. Now, the Sounds of both those KSCs would be available
under one PCG or Set.
And as Anthony said it can be quite a complex strategy but its easy.

I think there is another way which i am still testing and working on it.

[Yuma]

So Yuma, no, thats not
the way since at each Save process you will be overwriting the KSC thus
you will be deleting what was there before.
In plain Mortal Words would be:
1. Create one UserBank and Save it. Create the Second one and Save it.
THIS_UserBank.KSC and THIS1_UserBank.KSC.
2. Load them Both and create the Whole Program Set out of those 2 and
Save it as a PCG. Now, the Sounds of both those KSCs would be available
under one PCG or Set.

It wasn't my suggestion to build one big .KSC-file.
I merely pointed out the situation that could happen if you build one big .KSC-file.
I would do as you wrote and make one PCG-file with several, separate .KSC-files loaded.