Slicing engine on OP-XY

OP-XY
1

For god’s sake please please, add a proper sample slicing engine on OP-XY.
it’s something so easy to implement given the features already present!

I know there is a workaround, like loading the same loop over and over on the multi-sampler, but i suppose that would consume loads of RAM uselessly…

does anybody know any better workaround ?

3 Likes
2

I’d be surprised it would use anymore ram since it’s the same file.

3

I don’t know the insights, but i think it would use more memory.

when you load a sample in the multisampler, it can’t know if it’s the same sample you’re loading, or a different one.

so in my understanding it would load the sample again.

i haven’t tried (gonna check that out) but i assume that when you store the multisampler preset, inside the preset folder it will create all the files with the same sound:

mypreset_c1.wav. → (myfile.wav)
mypreset_c#1.wav → (myfile.wav)
mypreset_d1.wav → (myfile.wav)

and so on..

so they would be as single files that get loaded.

this is just my theory, it’s worth checking.

4

Behind the scenes it probably knows the file is already loaded into memory so it doesn’t need to load it into a different memory location.

I’m not sure how to verify this though.

5

i hope so. not saying that’s not possible. they might be calculating a hash for each file in the preset and effectively recognize the sample is already loaded in the pool.

they might have thought to optimize memory in some similar way.

haven’t had the chance to test it, i will when i have a few mins.

6

the logical step is to have an iPhone/iPad app like the opz that addresses all the concerns. are you listening TE?