Korg Forums

I have the Korg Kronos X 73 for about a year now, and have used several original user samples and combined some programs I downloaded.
Up until now I didn't pay attention to file management and just added KSCs to Auto Load.
So I want to know how I should organise the HDD of the Kronos & the KSCs so I'll have just one master KSC to auto load and delete all unnecessary files.
I also want to free up RAM and all factory samples that I don't use.
How should I approach it?

Equalizer23 wrote:I have the Korg Kronos X 73 for about a year now, and have used several original user samples and combined some programs I downloaded.
Up until now I didn't pay attention to file management and just added KSCs to Auto Load.
So I want to know how I should organise the HDD of the Kronos & the KSCs so I'll have just one master KSC to auto load and delete all unnecessary files.
I also want to free up RAM and all factory samples that I don't use.
How should I approach it?

I have never removed the 'factory ' samples since I will likely access some of them in the new future.

I think your strategy, is to have a custom PCG that will autoload your favorites, your must have samples.

This might take some time to construct. The downside to the custom PCG is , sometime in the future, you are looking for a factory program which relied on a sample, that you did not load. Then you have to revert back to your prior PCG to load it , then bring that to your 'custom ' PCG.

Lets see what forum experts suggest. There might be a software tool that will help out.

Equalizer23 wrote:How should I approach it?

The way I have organised my samples, is editing the KSC files with a normal text editor:

I assume you have all your user sample sets stored as Userbanks, and you leave them where they are on your Kronos HDD

1: backup your existing setup
2: load your desired samples as Userbanks, together with their programs
3: save your samples under a single NEW name, e.g. ALLMYSAMPLES; this creates a collection of your sample references, without copying your samples. it contains references to the Factory Sample banks as well, and/or any bought samples libraries when activated.
4: edit the resulting ALLMYSAMPLES.KSC and ALLMYSAMPLES_Userbank.KSC with a texteditor and remove the unwanted samples in both files; edits should be identical; careful with this process, since an incorrect KSC won't be read by Kronos at all
5. append your KSC files with sample info from other Userbanks, or use the 'load required samples' option in a desired program when the underlying multisamples are missing
6. set your resulting ALLMYSAMPLES_Userbank.KSC file as the single file to AUTOLOAD and perform the AUTOLOAD
7. See how much memory is left and add more samples to it if wanted

Like this I created a Userbank.KSC consuming the entire 1.9 Gb RAM that refers to ~25-30 Gb of samples on disk.

There maybe other ways to do this, but this works fine for me