Looking for some avid sampler users

I found interpolation modes very similar in CPU load, but I didn’t do precise tests.
Actually I’d leave only hermite interpolation, that seems to work good with 2x oversampling, but I left anyway Linear1 because it has the same response of Nysthi’s, and Linear2 that makes a slight low pass. So they’re there only for letting options, not for CPU load purposes. Maybe in the future I’ll think about 3rd order and 4x oversampling, but for now I have to make it work without bugs and it’s not simple for me :slight_smile:
Thanks for the parameter suggestion!
Polyphonic: yes, module cycles through v/Oct cable channels. There’s also a context menu option to leave the out polyphonic or mix it.
Sample load while playing: in effect I had crashes, but now it seems stable to me. Module stops playing before sample load function is called.
Note on the code: I know it’s very “BasicV2”, because at the moment I can’t program in c++ style, yet. I don’t know anything about compilers, but I’d really like to compare performance between the same module written in my bad way with the same one rewritten like it “has to be”… . But it’s another kind of discussion

1 Like

Thanks for the reply. I’ll PM you or enter a github issue if I have more stuff. btw, hermite interpolation is of course third order interpolation :wink:

Oooops! Thanks to you!

@sickozell It would be awesome if the context menu for sampleplayer and drumplayer could display directories or folders. For example, with Surge XT Wavetable module, it’s possible to add a directory to the context menu, which makes it much faster to load wavetables by simplifying navigating the files in the added directories via the context menu.

1 Like

Thanks for suggestion, I’ll think about that.
My current project is to code a sampler with recording feature.
But maybe I’ll create a specific wavetable player that could implemet what you’re asking for.

2 Likes

Cool, thanks for considering

A lot of ppl ask for this, and it’s not just for wavetables. It might be that the folder has 10 totally unrelated wave files, but the user wants to load them all up and maybe select them at playback time from a CV or something.

It would be worth looking around for for what people are doing with their folders of samples.

1 Like

To do that I’m afraid of folders with 3000+ (or even 100) files, and thinking how to manage these situations.

Look at the competition and see what they do. Also - once you have loaded enough, just stop. Whatever limit you set, just stop. I would think the limit would be in megabytes, not number of files? But whatever it is…

I was firstly thinking of loading the samples in memory on demand, so a limit in number of files makes sense. In effect it would slow down sample availability, so a massive initialization load could be a better way, and in that case a limit on memory would be preferable.
Sorry… But… what competition?

At least how Surge Wavetable does it, the files are navigable via the context menu but not loaded into memory. Loading a bunch of samples into memory for CV navigation is possible in modules like Lomas Sampler and VoxGlitch wavebank, but not something I was thinking of specifically here.