Korg Forums

Sampling, building multi samples, and editing samples require they be fully loaded in RAM. More RAM allow working with larger sample files when building. Some even unload all factory samples to free up even more memory during the building phase.

I suppose even with streaming if one were to have a ton more samples loaded than stock that extra RAM could get full. I suspect that's possible if there were a large number of large samples.

Geo

awesome! So, why do folks want increased RAM?

That's just the keyboardist version of saying "It goes to 11!"

Ok. So more RAM is helpful in a real large multi-sampled instrument building phase, if you are doing it all on the Kronos. I imagine one can build an instrument in a software editor, and then bring it into Kronos to bypass this limitation. So, although I'm not familiar with the Kronos, 3GB ram seems fine enough.

dsetto wrote:Ok. So more RAM is helpful in a real large multi-sampled instrument building phase, if you are doing it all on the Kronos. I imagine one can build an instrument in a software editor, and then bring it into Kronos to bypass this limitation. So, although I'm not familiar with the Kronos, 3GB ram seems fine enough.

That's correct. So far all my sampling has been done in the Kronos and memory has NOT been an issue...not even close!

Geo

Thanks, geo.

3GB is quite a lot, but people are spoilt with multi-GB software libraries these days. Kronos is the only mainstream board that can realistically load these if you convert them. And then suddenly 3GB isn't all that much.

As a side note, even if sounds are streamed, they do take up Ram - a lot less than the full sample size on SSD, but they take Ram nonetheless. When you buy (or get freebie) sample packs it's usually indicated how much ram the samples take when streamed. Example of such detail here http://thekronosblog.blogspot.be/2013/0 ... asses.html

SanderXpander wrote:3GB is quite a lot, but people are spoilt with multi-GB software libraries these days. Kronos is the only mainstream board that can realistically load these if you convert them. And then suddenly 3GB isn't all that much.

But, with the ability to stream both 3rd party & user-created multi-samples, and with only a small portion occupying RAM, 3GB sounds like a lot to me. I guess I'm currently only concerned with performance. I could imagine if sequencing, well, then limits are going to be hit. (I feel I've taken the red pill, after sticking with the blue for some time now.)

tomto66 wrote:As a side note, even if sounds are streamed, they do take up Ram - a lot less than the full sample size on SSD, but they take Ram nonetheless. When you buy (or get freebie) sample packs it's usually indicated how much ram the samples take when streamed.

Thanks. Can all stock sounds be streamed, or are some restricted to being loaded entirely in RAM?

For performance all samples can be streamed. Only for editing - as Sander indicated - you must load them completely in Ram.

3GB is kind of a lot, but for instance I have the Austrian Grand and the Legendary Strings and especially the latter takes up a LOT of RAM - it uses a lot of wavetables and round robin sets of samples, which adds up.

You can also imagine if you multisample a bunch of your favorite VSTs, it'd go quickly.

Still, it's very workable and I quite agree that it is a lot, especially by workstation standards.