Problem with every sampler.

I used a 2 kHz sine wave for testing purpose, and the audible difference was incredible.

My apologies. I didn’t mean to be rude. Thank you Squinky, Ahornberg, augment, jnorberg, k-chaffin, ablaut, LarsBjerregaard, Eurikon, synthi, pachde, and wacheski. If I don’t show my appreciation in the future, please understand that I always appreciate your help and ideas.

4 Likes

I’m sorry for hijacking the posting, but I wanted to follow up and thank you all again. Ahornberg’s suggestion of using a 2 kHz sine wav, mixed with Squinky’s suggestion of transposing seems to have worked.

When I mismatched the sine wav’s frequency with rack’s frequency, I was able to observe the effectiveness of the linear interpolation. Pretty cool stuff!

7 Likes

Ok, that took longer than expected… but it’s finally done… please check it out here:

6 Likes

Awesome, thanks! Looking forward to trying it out asap…

1 Like

“I have tried a baker’s half dozen of different samplers from different makers, and none of them have allowed me to load samples.”

I have the same problem. I have tested several wav samples from 2 to 5 seconds, none of them load in the different samplers. My OS is Windows 11 Pro.

I wonder if the problem is Windows 11 Pro. I remember it worked with the same samples in Windows 8.1.

Windows does have a knack for removing codecs in new OS releases for licensed/patented formats (image, video, and audio), but basic .wav formats, unlikely. To know more, you’d need to get specific about the sampler module you’re having an issue with, and the samples in question, perhaps sharing them so that they can be inspected.

yes, exactly. I know of no “problem” with windows loading samples.

Thank you for your help, but the problem remains the same regardless of the sampler or the wav file. Nysthi, Voxglitch, Lomas and so on… The “Upload” function doesn’t accept wav files.

I just tried voxglitch repeater. It seemed to load the first wav I threw at it. I’m running Windows 11, btw. If you would specify a particular module that doesn’t work, what the symptom is, and provide the wav file you are using I’m sure ppl would be happy to investigate.

1 Like

Wonder if there’s a utf16 file name issue for user

Is your path non-ascii? Containing cyrillic or kanji or emoji or the like?

I’ve been - outside of rack - battling the terrible choice and of having non utf8 paths on windows today so it may just be too of mind

1 Like

I had that bug with my sampler, but I made it work right before I released it. Anyone who has programmed a bunch has probably run into this issue, since it affects all software that can access the file system…

Funny that a spellchecker does not pick this up :grinning:

1 Like

well, “oath” is a noun, so…

1 Like

yes thats why i asked. “windows user can’t load any file into open source software which works for another windows user - windows user one has username :bacon::guitar:” is the thing I thought may be tripping up the devs of these samplers.

as I’ve said for decades - only an idiot would have a non-ascii user name. But of course it is a bug if a particular software doesn’t work in that case. But it’s a super common bug, as we both know.

As an aside, correct handling of non-ascii paths (in windows) is not at all easy. making quality software is hard!

Yeah the problem is less ascii than utf16 encoding for the file system. But loads of Cyrillic and Asian char set users have non ascii user names. I had to make an emoji named user on my dev box to test … and it’s not just user name it’s any non ascii Char in a windows path getting mis cast to a string

And confusing paths with strings is another problem

But the first sin is really the windows utf16 encoding.

Anyway wonder if this is even the problem!

1 Like

for sure we don’t know if this is related. and for sure utf-16 sucks. “first sin”? maybe. maybe it’s devs that don’t care enough to make this work? in any case, that’s a value thing…

yeah and in microsofts defense they had non-ascii support before utf-8 was finalized.

the reason its hard to make work of course is that if you get it wrong, ascii all still works. Sigh.

1 Like