@David-Healey Quick update - Gemini helped me get me through Git and I replaced the files with those fixes. Filter works properly now.

Thank you again David, you're the support blessing. I wish all the best to you!

@David-Healey I’ll try with Gemini, will let you know if I got it right. Thanks!

@David-Healey https://github.com/christophhart/HISE/commit/840365a89ac14ce6b59d9017f066453ee0c6250c

do I have to replace it and compile Hise again? This is it?

@David-Healey Oh my, it's 3 weeks since that report, so it's not released yet?

Hello.
It seems like putting LFO in any module is not working (latest Develop version, macOS). Why is that, is there a bug or it's just me? I have an older version of Hise on Windows and it's working fine, but there's a problem with it on Mac.

I've been posting about it recently, that also moving the project from Windows to Mac removes the "show Text Box" property from the knob.

This is a completely new project - LFO is not making the frequency move. Neither do putting LFO on balance, volume or anything. What could be wrong?

Zrzut ekranu 2026-03-14 o 21.49.05

@David-Healey Wow haha. Works fine on PC, everything is fine there. I didn't feel the need to change it, since it was perfectly working for me. And sometimes updates cause troubles.

@David-Healey By this I meant the latest officially compiled version, from Hise website

@David-Healey I'll try it, I'm wondering what was wrong with 4.1.0, Apple removed a module or something? Looks like every macOS user has to compile to new version, cause 4.1.0 is clearly not working properly now. At least for my Mac.

@David-Healey
Correct.

No, but I tested it on two different projects. Both had the same issue. Older version (non-develop 4.1.0) doesn't have this problem, but it seems like it's not working with newest OS. Can you test it on your PC and Mac? Maybe the issue is, that on PC I'm using 4.1.0, and on Mac the latest Develop one.

Current OS has some compiling issues, so that's why the Hise update was needed. According to GitHub, the solution was released yesterday, and I compiled Hise today - so I'm beyond lucky,

You have to be AVID signed developer to be able to compile your plugins on AAX (and run it). It's not so easy. Imho not worth it, since there is a way to open vst3 and au on ProTools. Most of the PT users know how to do this and don't bother finding the exact AAX format. So if you'll be selling/developing the plugin, VST3 & AU should be enough

@David-Healey

Property showTextBox changes to unchecked. I didn't notice anything else, but maybe there is any change. My plugin seems fine compiled on Mac, so it might just be this.

Edit: This weird number on a scale is the way to show value using ultra micro scaling the knob and checking the showtextbox (we were talking about it). Also, changing the drag to Vertical/Horizontal makes the font editable, so you can change the color. In a new plugin I'm using the label, cause knobs are bigger but for small knobs it's working fine.

Hey!

I have an issue, not sure if it was before.
I got the latest version of HISE (compiled standalone) on my PC/Windows. When I move the project file to my macOS with opened latest Develop version, all „show text box” propeties disappear. Didn’t happen like that on the previous version (that was on older mac) Almost released a plugin with no knob values

@ustk I kinda figured it out I think, made another Simple Gain in the end of the line and linked to it on the meter, it's working

Hello,

Is there a possibility to create a Matrix Peak Meter, but for an Effect VST? Normal MPM works fine for samplers, synthesizers, etc. but it doesn't move when applied plugin to an audio track in VST.

Also, I'd like to see values of the meter, how can I do that?

Thanks

@David-Healey

A little update.

I plotted 16 VSTs with all 23 (46) knobs, with automation on every channel, playing like 50+ sounds at the same time, and nothing happened - for three hours of work I didn't even have a single RAM glitch, which is sometimes happening on a single channel with Serum, for example...

HISE is wonderful and perfectly optimized, so my way on displaying values is doing great. Editing knob's value is also very comfortable, you don't need to try hard to twist on the exact number you want.

Thanks for your help David!

@David-Healey today I learned how to edit knobs in knobman. knob jumping through actual values is much better looking than a normal 0-10 scale like in the original

I'm addicted to it right now

@David-Healey hope it won't cause the gpu eating, there are twice as many knobs

@David-Healey i created a second "knob" with the scale of 0.001 to make it invisible and scaled the tile to fit into the real knob, then - linked to it. one knob makes as a controller, the second one as display. had to make it with every knob, but hey - it's just 10 minutes

@David-Healey needed some time to figure it out

@pgroslou

Okay, Gemini helped me, but it can't solve a problem. Only components named Volume and Balance are giving the text, the rest is not reacing:

// 1. Pobieramy okienko wyświetlacza
const var Label1 = Content.getComponent("Label1");

// 2. Definiujemy jedną, wspólną funkcję dla wszystkich knobów
inline function onKnobUpdate(component, value)
{
	// Pobieramy nazwę z pola "text" komponentu i wartość z 1 miejscem po przecinku
	local name = component.get("text");
	local val = Engine.doubleToString(value, 1);
	
	Label1.set("text", name + ": " + val);
}

// 3. Ręczna lista Twoich knobów (wpisz tutaj ich ID)
// To jest najpewniejsza metoda w HISE
const var knobList = [
	Content.getComponent("Volume"),
	Content.getComponent("Gain"),
	Content.getComponent("Balance"),
	Content.getComponent("ReverbMix1")
];

// 4. Przypisujemy funkcję do każdego knoba z listy powyżej
for(k in knobList)
{
	if(k) // Sprawdzamy czy knob w ogóle istnieje
	{
		k.setControlCallback(onKnobUpdate);
	}
}