Sample Robot - >virtual memory ++ solved ++

[BlackForest]

Am sure this worked before, what am I doing wrong?

Am using Sample Robot, the Korg + wave edition. Am recording something with it, export at KMP file.
Copy from USB stick all the files onto the SSD.
Then adding in sample management this KSC to the auto load list.
But it only loads it into the RAM , wasting space.
Changing the parameters on the right to ksc or virtual memory doesn't make a difference. It's always loaded into the RAM.

Which step am I missing?
Something in the Kronos, or within Robot (even though there is nothing along these lines of virtual memory to be found)

[KK]

Not sure I understand what you mean correctly, but I'll try a guess. BTW, when you select a new setting between RAM and VM (Virtual Memory) in the KSC Auto-Load tab, the numbers in the little blue, red and green boxes don't change right away, you have to reload the KSCs to see the numbers change. Also when you export sounds using an external software, the import must be saved in the Kronos (using the famous Save Sampling Data option).

Once new samples are saved, you should end up with a ***.KSC file and also a ***_UserBank.KSC file. For your new recorded sound, add the ***_UserBank.KSC file to the Auto-Load list. It should then by default load in VM. You can also change settings in the Sample Manage tab, but I would start with that to keep things simpler.

[BlackForest]

Hm, maybe I should write to SRobot.
SR is meant to export everything ready made, the ksc, ksf (I think), etc.
I haven't used it in a while though. I am sure one didn't have to bother with sampling data.
The numbers regarding the memory which should change are the ones right next to the ksc. Am not close to the Kronos now, but am sure it does show changes right away there with my other ksc.
I'll write to the guys from SRobot and post their solution here, should there be any.

[Mike Conway]

I know nothing about Sample Robot, but if your contents are in RAM, then do the following:

Select DISK, then SAVE SAMPLING DATA. This should save your RAM samples as KSC, and USER_KSC files.

Add the USER_KSC to your KSC auto-load in GLOBAL. The USER_KSC has no actual samples, but rather it points to samples in the KSC file so that they can stream. You'll need to restart or select DO AUTO LOAD NOW to have it go into effect.

Note: the KSC files must be saved to your Kronos internal hard drive in order to stream. External drives won't work.

[KK]

Hm, maybe I should write to SRobot.
SR is meant to export everything ready made, the ksc, ksf (I think), etc.

When you complete an export with your SR version, check if there are two KSC files like I mentioned earlier (in dark red). If not, their software might export in Korg format, but the Kronos requires a few additional things to digest the sample data correctly. I use an earlier version of SR and export in SF2. My custom libraries work just fine, but only after I complete a few tasks to satisfy what the Kronos needs.

[BlackForest]

Just to close this subject for future reference, from mikelees is the full explanation, which I was not doing correctly:

http://www.korgforums.com/forum/phpbb2/ ... ab1414cac4


"I find it very usable. My normal workflow into Kronos is:
1. Export from Sample Robot in Korg Kronos (KMP) format on the computer. This creates a .ksc file and a directory with the same name containing the samples. Sample Robot truncates the name of the .ksc file to 8 characters, ending 000, so there are 5 useable characters. I name Sample Robot projects with deliberately short 5-character names so I can tell which ksc is which.
2. Transfer the .ksc file and the directory to a USB drive. Keep a mental note of the amount of data the computer said it transferred (e.g. 100Mbyte).
3. On the Kronos, in the Disk mode, Utility tab, copy the .ksc file and the directory (using multiple select) from the USB drive to a directory on the Kronos SSD.
4. In Disk mode, Load tab, load the .ksc file, using the "clear all" option.
5. In Disk mode, Save tab, chose Save Sampling Data, choosing the "Sampling Mode Data" and "All" options, and save a new _Userbank.ksc into the same directory on the Kronos SSD. Here, you can re-name the .ksc with a more useable name again.
6. In Global mode, KSC Auto-Load tab, add the _Userbank.ksc that I've just created to the list of ksc files to auto-load. The size of the ksc file to auto-load should be roughly the same size as the amount of data transferred in step 2 - this is how I check everything has gone OK up to this point.
7. Hit the "Do Auto-Load Now" button in the KSC Auto-Load tab. Takes a few minutes.
8. Create a new HD1 program with the Osc 1/2 pointing to the new sample ksc as required.

At the moment, I don't bother to delete the original ksc I transferred from USB, so that in the future if I need to combine multiple ksc files into a single _Userbank.ksc to speed up the startup I can do that. This might change if I get close to running out of SSD space on Kronos!"