@BWSounds did you start with a fresh git pull?

@GUJIAN No, but you seems to be trying to use Rhapsodist in the second image and the template in the first image.

@lalalandsynth said in Sneak Peak at my 'SLIDER BUILDER" app // Feature Requests anyone?:

@Lindon Why not ? Not all at the same time , just tabs to flip between knobs, buttons, sliders.

because you are throwing everything into one bucket when the problem you describe can be addressed by shared themes.

Thank you! That all makes sense

@Chazrox cool.

Another suggestion for the skirt it would be useful to be able to do a circular gradient , if that is the right term ? SO not up dwn , but from center.

Also snapshot would be more useful for me at least with transparent background.
Or if that is tough maybe to be able to set the background for the knob in the theme.

Or just a simple background color setting so you are making the knob on the same background color as your UI. EDIT: Found the BG color, perfect !

OR ...hehe, being able to import a screenshot into the background so you design the knob in situ as such.

.. When setting colors I mostly use hex but always have to flip though the other color options , maybe it could remember last used color selection method ?

Also, unless I am missing it, the arcs need a pan setting/ center .

@griffinboy

I realized that these plots are a little misleading.

The VCS3 filter is highly nonlinear and "bubbles" and so taking a measurement of frequency response is quite difficult since the filter is moving around on it's own accord all the time...!

Here is a more detailed FFT that shows how the filters do match more closely than the graphics in my paper would suggest.

.

Black is the slow accurate VCS3, Red is my optimized VCS3.
Not oversampled.

c4000_fb9_m42__one3_c050_k2.png
c10000_fb9_m42__one3_c050_k2.png
c2000_fb6_m42__one3_c050_k2.png
c10000_fb9_m42__one3_c050_k2.png

When oversampled, I found the proposed model to be perceptually close to the slower accurate model. The resonance and cutoff and gain values differ slightly, but the important aspects of the filter are retained.

Update!

Dual SVG capabilities for buttons such as this.
(shown compiled in HISE)
DualSVGButtonWorkingExample.gif

Both import methods and settings panels are identical but are independent from each other between button states.

Screenshot 2026-07-05 at 9.10.52 PM.png

Screenshot 2026-07-05 at 9.14.27 PM.png

And If you didnt already know...
You can also do some pretty nice LED's with the app as well! 👍

Screenshot 2026-07-05 at 9.17.58 PM.png

Screenshot 2026-07-05 at 9.17.25 PM.png

Screenshot 2026-07-05 at 9.18.37 PM.png
They're available now in the preset menu.

@ustk I'm indeed still on the latest stable release...
I read it as 4.10 instead of 4.1 so I was convinced I was on the latest version.
I'll compile from the latest develop branch instead and try again.

So what state is the mod matrix actually in?
Do some things work but others don't?
I'd just like to know what to look out for, if the documentation isn't super up to date.

What are PRs?

@dannytaurus That is a massive, massive bummer. I hadn't seen that. Guess I'm going down a rabbit hole trying to get the graphics portions working again, I 'just' need GLSL shaders working again, it worked fine in an older build of HISE so hopefully not too much to work out.

@lalalandsynth

Ah that makes sense,
yes indeed that was the only thing.

In that case, great work all round.
I'll keep you in mind for some upcoming projects.

@duma Try a different xcode version

@ustk Until July 7th anyway. Then I'll probably only use it for big tasks! 💰

@Christoph-Hart Looks like you deliberately chose to not expose the preset list to host. Can you remember why?

"Here be dragons" maybe? 😂

# hi_frontend/frontend/FrontEndProcessor.h int getNumPrograms() override { return 1;// presets.getNumChildren() + 1; } const String getProgramName(int /*index*/) override { return "Default"; } int getCurrentProgram() override { return 0; //return currentlyLoadedProgram; }

@David-Healey Makes sense 👍

@Oriah-Beats Enable one shot mode in the sampler's playback settings.

e0578f4f-f5c5-4dc6-ac61-199b6e8e48b8-image.png

@dannytaurus That being said, it only matters in a parallel track mixing context (but nowadays it's still very frequent, we parallel this and that everywhere...), but you don't mind such a small latency for instruments...

@Jeetender You can use setLatencySamples() to report the latency amount to the host, so it can compensate.

https://docs.hise.dev/scripting/scripting-api/engine/index.html#setlatencysamples

However, I think the tool to measure the latency of your plugin is currently broken.

Tools > Check latency of signal chain

https://forum.hise.audio/topic/14245/check-latency-broken-on-latest-develop-build?_=1783032811243

@David-Healey Dang. Shame they don't have a time-limited demo or something.