@d-healey
.....wooooow, I feel dumb,
thanks!

@It_Used wow thanks that’s awesome ! I’ll be able to dig into all of this.

@It_Used said in Display slider value with custom font, size, and position:

@Yinxi create visual mockup your idea, and i maybe implement this!

Reply

I was thinking something like this : .

And when I change the slider value it will also change the value at the top left

@d-healey
That's very cool content
Thank you !

I actually double-checked this using a small Python script generated by ChatGPT, which reads the smpl chunk directly from the WAV file, it reports the exact same LoopEnd value that HISE shows.

However, I think it would make more sense if this value were interpreted the same way as in other sample-based plugin tools (like Kontakt or Falcon) to ensure consistent loop behavior across different samplers.

Both Kontakt and Falcon interpret the LoopEnd value in the same way, which is also consistent with the looping software I use to create my samples, unlike HISE, which appears to handle it slightly differently.

From a compatibility standpoint, this could become an issue if a company wanted to migrate a large sample library from Kontakt to HISE, since all loops might develop small clicks due to this off-by-one interpretation difference.

That said, I have to admit I don’t have the technical knowledge to fully understand where this 1-unit difference comes from.

@d-healey You can try with this sample if you want, this one makes the issue very obvious.

HISE shows the LoopEnd at 344278, but in reality it should be 344279.
When I correct the value in HISE, the click disappears.
For small projects it’s not really a problem, but for large projects with several thousand samples, it becomes quite annoying.
I’m wondering if I should add this thread to the bug reports list.

I can conclude that it’s a more Hise general issue rather than my project being misconfigured.

@d-healey Actually, I have to admit I didn’t use the sample that clicks the most, but if you play it at full volume you can still hear a small click in headphones.
However, the issue is still here, when I load the exact same sample into Falcon’s sampler, it sets the LoopEnd value correctly (263419 , not 18).

UVI Falcon info on the file :

@Yinxi I can send one of the samples if you want to test it on your side.

@d-healey I also thought it might be a sample rate issue, but all my samples are at 44.1 kHz, and the project settings are the same.

@d-healey said in Loop points clicking issue in HISE but not in other samplers:

you're making sample maps you should put them in the project's Samples folder.

Make a test project with 1 of the samples, compress it, export as a plugin or standalone and test if the issue is still there.

I started from a blank project with just one sample, exported it, and the issue was still there.
However, I think I’ve found the problem

When importing my samples, the LoopEnd value is always 1 sample lower than the value I set in my custom looping tool, which explains why I was hearing clicks on every sample on my project.

This difference only happens in HISE,
In Kontakt and Falcon everything was good, so it seems that HISE is always removing 1 unit from the LoopEnd value.

Kontakt :

Hise :

It might be interesting if other user could test this on their side to see if it’s a general issue or a small bug to fix.

@d-healey only in Hise, the samples are not compressed, and they are located outside of the project folder.

Hello,

I’m currently facing a pretty annoying issue...
I’m writing the loop points of my samples using my own external tool (outside Hise), and I’ve noticed that when I import these samples into HISE, the loops produce clicks.

I tested the exact same samples in UVI Falcon and Kontakt, and I don’t have any clicking problems there.

Has anyone experienced something similar?
I can see that the loop points are imported correctly, and the crossfades are already rendered directly into the samples, so I don’t really understand why it’s clicking only in HISE.

I really hope I won’t have to redo everything from scratch...

Hello,
Just wondering, what happens if you use Mono2Stereo on a stereo input?
Does it leave the stereo signal as it is, or does it sum it to mono first?

I’m trying to make sure it won’t cause any unwanted channel collapsing or weird phase behavior if I use it in a ScriptFX that might sometimes receive stereo input.

Thanks!