@tsempire you need to place your elements inside a Split container, and then create two branches using Chain containers.

@tsempire
Sure

HiseSnippet 1631.3oc6Y0zaaTDFdV6rNItETKTtwAK0CjhpB1INoMBgrarioVTmZpSSa4RYxtiiG4cmY69QRbQbpbnWPbD0aHwUNvUtke.EIj5gdsHwOfxu.Xlcm06t1qiWahKpRwQJZm2Yd244848i4isoIUAYYQMARY2omABHcd4V8H1cpzAhIf5UARuqbCnkMxLmmnM6Y.srPp.IozeNWfzhyAb+85RaB0fDETfH.XWJVAcKrN1NPZyxeAVSqFTEsCVOznKVttBkTgpQcX3IsbdfAToKbez1P9vRICtIzpCP5ikWakUUJpdM0UVYsMVWAtNZi1v1sKrpZwhqe8MJr5FvhWecT90.RY1REaSMaYCsQV.o41jp1qUG5gDuIXWrEdOMDuQAPK1L6ItFUSkahbofJcvZpM8IJK.6szLf1R6QaWRtAVE2Wd.8cA2NxEnQXBTJUT3kNB7JDFd4CAuXfjTHHMmGjtnbKESrgcPOb7bN45Dl2rMj4mBCEuwBjNVtBkM.h8x5vtnZlrF8UXo0ym+p4X+6JeZaGhhMlRxQIaSsQ2lrzUx9MYWL62lM2fc0tcr8wmFSplFxL1t4gFlmjhKQbz2CYd0bG.0bP8GHy7ixoxilSC6xU7r5PCjRpSv121.QFUf.PPUrmta8pPaH2QHjwFmAxzFygfTUzArz.O2xhxUQVcsoFrDgg7YrnEppiFzNZHDOQSzAiCh323NGhE1tW3DwSs3pjBwKJ2DaqzIdLlJFLxXpYAFEYiui7VsaiTrC.3bx0t+atTurhTO1bxm7yKZlq18KDaR2SkCBvMLQFPSzNzlZvdKYA0MzP2ggwqlaOMpR2V3GiFNqvvCBaxGwRJcfDBRyZZRdxjXVovI6TtC0wFS1uAz1DeDKKbaG8Vr55JnJBzwjIkhmC40NOuMOtnEhn513eX+DcVf2VRzYA+NCk9sMx9PpYWW2g3Yfz7dbeUKCeQ6hLs3AmRyKmeY1efanoQOrBU2.KBaYNEWYMoZ8L5PIXEtHuQ3C8anScXyp.+r0j1Ah03w4sbrXUKTuMoEavtKDxiy1lpxdZ9ZPEFw1qIztCOegWugEbhLWVoePZDrFDmvYXuk.iL.960ewROpiAScNevWpj6zZBMYpwJdyqAkRJMWCOJxERY3y47xVFZrUmGI775NbTqGV7U7jggT5PEBA.eDjJDBVP1kAJ.FCCMLD5q4jfA27UdKV0nTdrdcqc48p.0.6xyG3rEHdxZ+gQ54XH0Ds79wiQeUFCDSEglB433n2uEyhafIBHFTIsA7nAj8fiaYiL3kJDx9om8reqTqtnC8PtP5w6+qePYtckwcEFvPu4pn1PGM6gjeCGapNqBga0cPH7MehvW4enbhv2W+9UeQIuMszRmRs6vJnLHHKVNdPVr7Xv0CNdXdiUfYh3syKeGjERL0Il8h3dAQBu7hzm3DAeEmk4AyEIk0Dc.xbuASDZezxhNhKYUz0oSlPxhzX6EZ.OpmWdPOp6H4VFa2YrUbiIN6Ukh2c9pRfIO+bRQ07x2Cqxn3DioQlfNi.XFY2wNk3KRj0d3G4.UiFYcA41XMdPvxhdiK7Rz0DsdDegcMzQ96cul2rD7HO0fnhNxeKGaw10jJ6ngtJ3uMjHwnYNYxtX4gH6m9hxIhrK+D8eWTMrlI5QNrcXzCLTg0XYbl7DWxt7pq9hRC.xie9yubx.I3x+8e3BxzxeIXnfp3CGdcowTpdkXJUuR4IMBcxVhCLyp0L1U0J+mO96hipbkOE35RwPUutzIQUM3IjuoopSBRKJuEAxN3g5DDSEppxhhhCEl3xJAZdVckypqbVckS+5Jix681PckLtGtaRNNnPiY1oAOMNUyYmF7+uSCNxFRxgM.wQUL68I2CYCN82SeeUa98+H48dxqFY1f68cSPtWun6E6DzTbKO0UCtDj9l.WnHLCDqFh7jXUXPhXA4a0LWEmYJO7QEV3W9vu5uRLOHEqU0+PJQrqvq6FiwcyYtwk8k+rwmk8k+GMtfsJkbqy+fsyPiab0ySpmSb6EQrMe3OjcINO7aolk.8fo45h1jR6pCcuJ9o6ih8l3CGnCULoOTw6agvMtEbkvVckH10eCd6bE.GLn6SGqhenhRzW0PJtxzp3pSqhEmVEWaZUb8oUwqMsJd8wqH+isK1OBORmkt0bKuCUI4uSO1dw.+KrpNUkH

@tsempire
Like this

@tsempire
You can use Scriptnode for that, you can add a filter after your reverb module. I think the Scriptnode reverb and the default one are actually exactly the same.

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!

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

@d-healey
I added below my message a screen of the code where I set the slider style (style: Vertical) using setPropertiesFromJSON.

@d-healey
I did it that way, but it doesn’t solve the problem

Hello,
I’m having trouble getting my filmstrip to show up when I export my project as a VST3.

It only appears if I manually change the numStrips value (for example, from 125 → 124 → 125 again , then it works, at least in the Interface Designer). Otherwise it stays invisible.

I unchecked showTextBox since I know it can be buggy, and I also tried loading the filmstrip through JSON in the code editor, but it still doesn’t show up, not even in the interface preview.

I’m sure the number of frames is correct and same for the location. Is there another setting I need to enable/disable to make the filmstrip export properly?

Also, as soon as I hit Compile in the code editor, the filmstrip disappears again.
(Attached a screenshot of my slider properties in case it helps.)

It’s interesting, but I don’t know what it changes for Hise users. Does it just mean that we don’t have to pay for a Steinberg developer license, or does it go further than that?

Hi,

I noticed that text in HISE looks smaller than in Figma, even when the interface size and font size are exactly the same.
For example, a 12 font in Figma looks bigger than 12 in a HISE Label, even though my .makeFrontInterface() matches the same pixel dimensions as my Figma export.

is there a ratio to calculate so the font sizes match visually between Figma and HISE?