@David-Healey Ah very nice, thank you! I will give that a try!

Hi everyone,

I've built an FX plugin with a “realtime” and a “long latency” option (Lookahead off/on), which means I can switch between them with a button, and depending on the setting, a different latency is sent to the DAW via Engine.setLatencySamples. That works fine. The default setting is “realtime”.

Now, if I change a few plugin parameters in the DAW and activate the “latency” mode, save the project, close it, and then reopen it, all plugin parameters load correctly (including the status of the latency button), BUT I can’t access the correct status of the button in the 'onInit' script to send the correct latency to the DAW when loading. This means the plugin always sends the “realtime” latency first, even though “long latency” mode is actually enabled. I’ve already tried using a timer to delay the query, but that doesn’t work either (though the query for the current sample rate does work there):

const var to = Engine.createTimerObject();
var timerStop = 0;

to.setTimerCallback(function()
{
	if (!timerStop) {
		getSamplerate(); //Samlplerate request function works
		if(ScriptFX.getAttribute(ScriptFX.Lookahead)>0) { // THIS DOESNT WORK, but why?
			Engine.setLatencySamples(lookaheadSmpl);
		}
		timerStop = timerStop+1;
	} else {
		to.stopTimer();
	}
});

to.startTimer(400);

Has anyone an idea? :)

New year, new luck... Anyone any thoughts/ideas/solutions on this topic? :)

Okay, I wrote a script where I did re-send the value of a knob, as soon as it is clicked (via Knob1.setValue(value); and Knob1.changed();). But that doesn't solve the problem.

Also I recognized that with any other plugin the corresponding automation track in Nuendo is highlighted "red" as soon as I click on any parameter (when the track is in "write" mode).

But with my HISE plugin, it doesn't. It also doesn't turn "red", when changing a parameter.
So there has to be some kind of message that the plugin should send to the DAW but isn't. Does anyone know something about that and maybe a way to fix that?

I found this post here: CMD + Click Event for Sliders

This triggers a function when a knob is clicked (I would use it without the "CMD" but the principle is the same), so that could work, doesn't it? Now I just need to know what to send to the DAW so that it knows that the knob is "touched" and how to script that couldn't find anything yet regarding that topic.

Hi there,
I'm starting to figure out HISE and it's amazing. But I stumbled upon a little problem with automation.

In my test-example, I have just one Knob (standart Slider) that is defined as a Plugin Parameter with a Plugin Parameter Name.

The Problem is, the Plugin does't send a "touch" information to my DAW. So when I try to automate it, it results in jumps (jitters) back to the initial value, every time I dont move the mouse but have the Knob on my Plugin still clicked. Other plugins signal my DAW that I "touch" a Parameter as soon as I click on it (even without moving the parameter).

I'm on Windows, the Plugin is VST3 and my tested DAWs are Cubase/Nuendo 13.

Is there a setting I'm missing or can I figure this out by scripting?

Hope you can help!
Thanks
Jonas