Korg Forums

Hi everybody,

i have a little thing to ask.

I work now with a lots of own samples. And i thing this is the big thing, that made the difference between other workstations.

So, i go to Global>KSC Autoload and add my sample,choose a load method. The Thing is,it does not matter if I choose KSC or virtual memory, the needed RAM size is the same.

I've understood that when I choose virtual memory, that the needed Ram is less then if i choose KSC.

Anyone understands why this is so?

Only for Info: I use the actually OS

Thanks a lot

Regards

Tomy

For example:

It looks to me like this parameter gives you a chance to override the load method stored in the ksc file. If the file already has a embedded preference for virtual memory, you would not see a difference between KSC Setting and Virtual Memory.

AlchemistMusicStudio's annotated graphic images are so good that he doesn't even have to accompany them with explanatory text! Nice!

Tomy wrote:So, i go to Global>KSC Autoload and add my sample,choose a load method. The Thing is,it does not matter if I choose KSC or virtual memory, the needed RAM size is the same.

When you save your sample set, the Kronos will create two KSC-files for you.
One is called xxx.KSC and the other xxx_UserBank.KSC (where xxx is the name of your sample set).
To stream your samples, you will have to (auto)load the xxx_UserBank.KSC file, not the normal xxx.KSC file.

Some additional info:
The normal xxx.KSC file contains all the samples, whereas the xxx_UserBank.KSC file contains references to the normal xxx.KSC file.
Basically the references in the xxx_UserBank.KSC file enable you to stream the samples straight from the SSD drive into the Kronos memory.
To stream samples you will always need these two files. If you would delete the xxx_UserBank.KSC file, then the samples would be gone.

Load method [RAM, Virtual Memory, KSC settings]
The Load Method sets the preferred way to load the KSC’s samples: load them entirely into RAM, or use Virtual Memory.
Note that if the data is extremely large, and would not fit into RAM regardless of which other samples were loaded, the data will use Virtual Memory regardless of this setting.
These settings apply only to EXs and User Sample Bank data; Sampling Mode data is always loaded into RAM.
RAM: The samples will be loaded into RAM. This has the advantage of allowing reverse sample playback.
Virtual Memory: The samples will use Virtual Memory. This generally allows you to load more large samples at once. Note that the samples may still require a significant amount of RAM.
KSC Settings: KSCs can store separate load method settings for each Multisample or Drum Sample, based on the settings when the KSC was saved. You can view and edit these settings on the Global Sample Management page. Setting Load method to KSC Settings uses these individual settings.

Hey Guys,

Thanks for the lots of answer.

I think, it's a good idea to show what i mean with 2 photos:

Please have a look at:

PCreek D6 AC_Userbank.KSC

I chanced the Load method

So, in the first photo i choose KSC settings.

In the second i choose virtual memory.

As you can see, the RAM size did not chance.

Does anybody know why?

Thanks and greetings

Tomy

The _UserBank.KSC file already has its KSC settings set to virtual memory use.
So it doesn't matter in this case whether you set it to KSC settings or to Virtual Memory.

As I explained above, when saving a sample set, the Kronos created two files: a xxx.KSC file and a xxx_UserBank.KSC file.
The xxx_UserBank.KSC file is the streaming sample set, using references to the xxx.KSC file.

in Global-KSC auto-load page

I have changed load method of my sample "name_UserBank.KSC to RAM

then I performed "do auto-load Now"

but the samples are still in virtual memory because I can't see it in sampling mode !

I can only edit samples when I do load name.ksc from disk mode

at this point : why "load Method = RAM " exist for ???
what is the usage for it ?


thanks


roberto...trying to understeand

Redrain wrote: at this point : why "load Method = RAM " exist for ???
what is the usage for it ?

danatkorg wrote:Load method [RAM, Virtual Memory, KSC settings]
The Load Method sets the preferred way to load the KSC’s samples: load them entirely into RAM, or use Virtual Memory.
Note that if the data is extremely large, and would not fit into RAM regardless of which other samples were loaded, the data will use Virtual Memory regardless of this setting.
These settings apply only to EXs and User Sample Bank data; Sampling Mode data is always loaded into RAM.
RAM: The samples will be loaded into RAM. This has the advantage of allowing reverse sample playback.
Virtual Memory: The samples will use Virtual Memory. This generally allows you to load more large samples at once. Note that the samples may still require a significant amount of RAM.
KSC Settings: KSCs can store separate load method settings for each Multisample or Drum Sample, based on the settings when the KSC was saved. You can view and edit these settings on the Global Sample Management page. Setting Load method to KSC Settings uses these individual settings.

danatkorg wrote:

Redrain wrote: at this point : why "load Method = RAM " exist for ???
what is the usage for it ?

danatkorg wrote:Load method [RAM, Virtual Memory, KSC settings]
The Load Method sets the preferred way to load the KSC’s samples: load them entirely into RAM, or use Virtual Memory.
Note that if the data is extremely large, and would not fit into RAM regardless of which other samples were loaded, the data will use Virtual Memory regardless of this setting.
These settings apply only to EXs and User Sample Bank data; Sampling Mode data is always loaded into RAM.
RAM: The samples will be loaded into RAM. This has the advantage of allowing reverse sample playback.
Virtual Memory: The samples will use Virtual Memory. This generally allows you to load more large samples at once. Note that the samples may still require a significant amount of RAM.
KSC Settings: KSCs can store separate load method settings for each Multisample or Drum Sample, based on the settings when the KSC was saved. You can view and edit these settings on the Global Sample Management page. Setting Load method to KSC Settings uses these individual settings.

no, I use load method = ram but I don't find anything in ram !

maybe i have problems to read in english

Redrain wrote:

danatkorg wrote:

Redrain wrote: at this point : why "load Method = RAM " exist for ???
what is the usage for it ?

danatkorg wrote:Load method [RAM, Virtual Memory, KSC settings]
The Load Method sets the preferred way to load the KSC’s samples: load them entirely into RAM, or use Virtual Memory.
Note that if the data is extremely large, and would not fit into RAM regardless of which other samples were loaded, the data will use Virtual Memory regardless of this setting.
These settings apply only to EXs and User Sample Bank data; Sampling Mode data is always loaded into RAM.
RAM: The samples will be loaded into RAM. This has the advantage of allowing reverse sample playback.
Virtual Memory: The samples will use Virtual Memory. This generally allows you to load more large samples at once. Note that the samples may still require a significant amount of RAM.
KSC Settings: KSCs can store separate load method settings for each Multisample or Drum Sample, based on the settings when the KSC was saved. You can view and edit these settings on the Global Sample Management page. Setting Load method to KSC Settings uses these individual settings.

no, I use load method = ram but I don't find anything in ram !

maybe i have problems to read in english

I think there may be a confusion between "RAM" and "Sampling Mode."
To load into Sampling Mode, load the non-User Bank KSC.

- Dan

I cant' believe that all this is only for reverse sample playback !

I believe that loaading in ram is for editting use also...

ok excuse me