Korg Forums

I would love that Korg would make a nice Electribe 2 editor app for both devices but most Gear companies are 2 lazy doing that.

So we all know the ES2 has around 24mb of sample memory

there's like around 421 stock sounds that take up 16mb of memory so u got like approx 8mb of sample memory.

If you erase the stock sounds there's 273 seconds available which is about 4.5 minutes and seems like if your samples are longer it doesn't matter how much memory it has cause the taking up is based on the amount of sample seconds u have that means that if you got longer samples and they take up all the sample time u still can have a couple of mb over.

I've been testing many sample converting apps mainly on OS X, Switch, myriad , pro audio converter Audacity etc...

and I do have a file where I was able to fill it up almost to the 999 samples...

but then u have 2 convert em to a low sample bitrate and khz... what makes the sounds more distorted and or noisy...

I do wonder how Korg managed to get like 400 samples at 16–bit 48kHz including loops in those 16mb

does any1 has an idea on that?

oh man.. you're on fire!
you have Korg attention!



more seriously
if you want that your samples take up as little memory as possible, you need to reduce the resolution, work with short samples, mono etc.
no secret to respect the 24mb limit..

do you know this app?
http://www.appification.de/ElectribeSampleManager/

If you record your samples at the target resolution from the beginning instead of down-converting them you will most likely get better results. Try re-recording them from one device to another. Or just play them into the Audio-In.

yeah I use that app but it has no convert function...

yann_ wrote:but it has no convert function...

Yes ... unfortunately there is no very complete editor for the moment ...
personally I use this one, and also the one developed by Brakio
but no ideal editor for E2S for now...

If you look at the sampling frequencies of the Korg samples, you will see that they optimized the memory a lot by tuning it finely. Most of them are less that 33KHz.

It was a plan to optimize the sampling frequency in my editor, but I don't know when I will have time to develop this: it requires some signal processing to design and use efficient interpolation filters and I prefer to not use external dependencies like numpy for instance (that would make the executable size grow by 30Mb just for this).

But maybe using Numpy is an option if the executable size is not a problem for the users.

You are aware that you can create multiple all sample files - ?

My workflow - and I'm sure many others - for months has been to dedicate one allsample to one song.

Its a very different machine once you get used to doing that.

Also being that there sample time is not that long dont know why there is no option to change the bit rate like we had on the roland boss boxes.

It would be nice to have the following options:

STANDARD: 44.1 kHz
LONG: 22.05 kHz
LO-FI 11.025 kHz