Happy to be added to the chat.

@JulesV GVST GTUNE is still incredible. I'm assuming OP is asking though because they want to build a tuner into part of a larger plugin, not because they think there's a gap in the market for a standalone.

TBH if we come up with a good solution, I'd love to use that code too.

@Christoph-Hart One thing, in the Neural Example in the docs it says this "It requires HISE to be built with the RTNeural framework to enable real time inferencing..."

I don't remember doing this explicitly when I built HISE, I just built it the standard way and it all works. I'm assuming this is just no longer a requirement? Otherwise could it explain the performance penalty?

@Lindon said in Plugin doesn't respect UI Zoom Factor onInit:

@ccbl said in Plugin doesn't respect UI Zoom Factor onInit:

@oskarsh how would that look in context?

inline function onFiftyControl(component, value)
{
	Settings.setZoomLevel(0.5);
};
Content.getComponent("Fifty").setControlCallback(onFiftyControl)

Do you define the value as 1.0?

I really don't know coding very well.

so like this:

inline function onFiftyControl(component, value)
{
    if(value)
        Settings.setZoomLevel(0.5);
};
Content.getComponent("Fifty").setControlCallback(onFiftyControl)

After flushing my %appdata% config this worked! Thanks!

@Christoph-Hart cool. Well like I said, if you want any kind of models for testing, let me know. I can do either NAM-wavenet or LSTM, of any size.

Something else coming back to the performance difference. I vaguely remember saying that there were optimisations pre-compiled when it came to inferencing certain architecture sizes. Given that Aida for example has a pretty specific pipeline that people use on collab, maybe they optimised that specific number of Layers and Hidden Size?

@orange OK sweet, I'll try some tweaks and report back.

@oskarsh how would that look in context?

inline function onFiftyControl(component, value)
{
	Settings.setZoomLevel(0.5);
};
Content.getComponent("Fifty").setControlCallback(onFiftyControl)

Do you define the value as 1.0?

I really don't know coding very well.

@orange Hmm I haven't where do you set flags? In the project settings?

@ccbl Is it possible the overhead is from defining the model in the script instead of loading it from a file?

@d-healey yeah it didn't make a difference. Do you think it could be the buttons being in a radio group that is messing things up? Or do you think that it's just the script doesn't read the state of the buttons until one of them is pressed for the first time?

Still a little puzzled why Settings.setZoomLevel(0.5); outside of the button callbacks doesn't correctly set the zoom level on init though.

@d-healey I'll give it a try. I used

Settings.setZoomLevel(0.5)

because the compiler said that

Engine.setZoomLevel

was depreciated.

@d-healey The 50% button is the default, and that is the one that is pressed upon export.

@d-healey Save in Preset is enabled yeah

Hey folks, so I've set up a few zoom levels that are controlled by button on a radio group. The default button engaged is 50%. But I found that when I loaded my plugin it actually defaulted to 100% UI scale. So I added a raw UI setting but that doesn't seem to work either. Any pointers?

I even tried setting non of the buttons to 1 on init, that had the interesting result of the first time the 50% button is pressed, nothing happened, but then after that the buttons all worked as expected.

Content.makeFrontInterface(1200, 900);

Engine.loadAudioFilesIntoPool();
Settings.setZoomLevel(0.5);

const var Fifty = Content.getComponent("Fifty");
const var Sevfive = Content.getComponent("Sevfive");
const var Hundred = Content.getComponent("Hundred");

/* This controls the zoom level of the plugin. By default it's set to 50% for people on smaller screens */
inline function onFiftyControl(component, value)
{
	Settings.setZoomLevel(0.5);
};
Content.getComponent("Fifty").setControlCallback(onFiftyControl);

inline function onSevfiveControl(component, value)
{
	Settings.setZoomLevel(0.75);
};
Content.getComponent("Sevfive").setControlCallback(onSevfiveControl);

inline function onHundredControl(component, value)
{
	Settings.setZoomLevel(1.0);
};
Content.getComponent("Hundred").setControlCallback(onHundredControl);

@ccbl Also I can see my sidechain meter (bottom) doesn't seem to work as intended, it appears to just show the input signal.

There also seems to be some delay and volume difference between left and right channels?

@Lindon hmm ok, how much of a performance hit is there, when you don't compile?

@orange Is that from within HISE itself? When I compiled the plugin and tested in Reaper I didn't get the behavior I expected.

The plugin only shows up with 2 inputs. When it should have four like the below example. And when I set the plugin to side chain mode it gates all the time.

Is there some other setting or flags I need do to make this work as an FX plugin?

@ccbl I think HISE is receiving from channels 3 and 4 though because I can hear that signal being output if I route a signal to those channels, which is also undesirable behaviour.