@pcs800 Oh ok that's what you want... So the answer is no, you don't need to connect it to the parameter in order to get the value to the UI. As @griffinboy said, the global cable is meant to be grabbed anywhere in Hise using the Global Routing Manager.

On the top of this, you don't even need to "read" the value since you can directly tie it to a callback that is called anytime the value changed.

Check this snippet:

HiseSnippet 1696.3ocuX0saaaCElJIzo1MqXcqnWazqbGxLrbTbRPwvZ9eFsI0HNqn2EPKQaSXZRMJ5j3Mz62E68X2umf8.rGl8Fzcnjrkjib9wncJ.I5vy4H9c9kGlVJoKMHPpPVkNerOEYsFt8Xgt+98ILAp4AHqmfOgDnopxQKs2XeRP.0CYYs7wlErJtBJ74e+w8HbhvklrDB8dIyk9V1PlNY0Vu9MLN+HhG8b1vTR675ltRw9RtbDfmkw0P9D2AjdzSIFwVBi9IRPej02gItaXWqlSCuM5PHc7puiSW5FMZ3XuQ2cp4P1gzn1NMp4XirJbnGSKUs0DMM.9n6I8F2tu7JQzF7dV.qCmZHrQsgcNZYz98YbuVSbNAHj0JsRbUKG4pdF9DlGa55ItruNjQ4DMR6zrV51fj8C.RVofzJQP5o31tJluNgiAOOF2T.QvtDH1jFJQxhV5erv6KAID5pCICnGo.hoZToQsZqWF90KeUoRP7IPW9Rhp7wmcR4en7ghdLAsZOp9XtrCgelbjlI5cBQ.gMUEPkDMB7YBAUsOArNPU3CXzKjrxK54dQL+WjceZGs5aDc.clfRidxg9RAPT4EIhDpaozaTUEsGyj9tOgy6.oSU5NR3pYRQkKI7QzWV52JUL4CTMfpeuY8XtupTwReb8x6FLV3dpTy5xbIFke4ql7YJKE.C56DUB+Tk9Xoxyxpa2b4YLFkjyM9obXapMT2lhUDiF1gpVubhgXDDxExlfU39kf4F4aSInTzTvzuymFSejj6YRbLueyzQTbvAd6mad.QSLYnwqAx4SUZlANVGPuD5IDkuVDe.MXfV5GJabDEYspNj6ShylayYdTEh4E1dZZvBc8zdG+M+0iSSDPtj1TzRQg3oIS+JlmF5bfs9CfeeJqWe8DJzMqhf5Wo2HNQmsn1ztKlADHxTIYpVDAL83zsCe.U50t0J86KDeJtES61OeLtTNXDBQeIvXb+wuBeX2tTWcB.WAezGVzlg0dvMCKEm9.6oYyWKlr7QevNu1fV+NNoJyWQ8IJ54xVbx3JAjg9b5Y.FWubGtzcPa1uRuYooeDD1yHQE29DHOkGrHUvE9BdDQtYNOBe30ZEw9tRX9blTO8rBshAUx3SGMrMbxuKc+XOmoBcISikH5ZFZCHZSEdgDeBdhYZanshYZOgYpdRmR0WIUCBcJwuClcTdQPXBvEcuFfOUEXJbrVEWqJ7CZWNWdko0DKtjBRXBWqkjO1uuTvbMKEIwDnu6P4HgdB9SpG2aRtyDSAFn4bBia71sGE.cZ8dmnM7cBmhxTdbpzCda0iHtfOebKhoK1Swld0Pnipp5NMDlwLRBiFmez7SYDvDwZQT.C3rwfXwf8ZxzWQvCrpggMjgYurV1vOx+EBpBlcsDdnzKBDYv3yRgwoRjGpR8Atu6+Jo1+0vx.WXZRS5L5FdIEsZJ146TRIvcA.SPlSudxgaGvB7gtC6MB5xEUskYEftovidsos22CmXlxcCfeJE79ILQ3PGvtZx5PmPtdJsCP2VS8iyZv1.swvKXJionL5c.sKYDWmYMTpM5QIazy.lvHzgO1N6Ty1tgcp88aw1fxY4lfhbUt8.5UQAfHApWeGXV7MaTu9FNau01aFOI5QJ5uLBxuGiNmds9bY3FBkoWByGXvXZIR.S0Y2srlZdvEMOOrcFObArci43hWKDJkOyT5hxn9rNZ6Ybz2ZD0dtQzigVpel2HyGdUbq9j.5bb3OGepTMjvAz30hBsegx1dOvDK78AFEBGfBkJAr911vE01XKmchdli4lL7HBkpzuHNf0qNz8Hac+SvCg+VcBu7J5Sz7Np3WJSMq0C0hWEGsz8vWNGar.1mRFj0.ebTisPF4Ycw5bGl1JImJcNQAWnJHddcA0M5btvydZ5Y7n8Bub2EtlaTkD2M7lXhnOe8FmqyXFbjwo7brJZbhpYjIO+yLelz9ohE9y+53OcyF+oQT3LUFJXrnkhZSjxqEGVWCmbg1Y57uvYQ4Ubr6HsDR2mdqrbBpy22likzL38FttD9DKAlfYtvuXD7dK8RJGkXJEv0yZKEgEfGSeu65PBv.R+O.BlJkpDDdpqz.SL.oRlPm2Ltj388detx2fc1bK6pau0VNN1N0ZTeyLU.Kp6ZOobvPR3nlKzMg+eYv3gDWk7B2n6gXLtGEtB30EwsHOwPW1FcYbLb5UFGx7XW35l8ScCEqunJtwhpnyhp3lKphMVTE2ZQUb66VQy+5w31BlxEnmPqCCSBsrNTDU1.2r.8e.amNDjB

@pcs800 First, drag the connector of this parameter to any node parameter you want to control (Frequency in your case?) then, if the range doesn't match, a little warning icon will show aside the parameter, click on it and accept the popup, this will automatically set its range to match the node parameter.

Then to access it from the UI, it works exactly like for any other module (be it from a slider property connection or from your UI script)

@pcs800 You'll need to add a sig2mod and a peak node

@resonant absolutely:

function(sampleRate, blockSize)
blockSize = buffer size

@griffinboy @resonant Oh wait! Actually there's a broadcaster for this!

// Broadcaster definition
const var SamplerateChanged = Engine.createBroadcaster({
  "id": "SamplerateChanged",
  "args": ["sampleRate", "blockSize"],
  "tags": []
});

// attach to event Type
SamplerateChanged.attachToProcessingSpecs("");

// attach first listener
SamplerateChanged.addListener("", "md", function(sampleRate, blockSize)
{
	Console.print(sampleRate);
});

@griffinboy you don't need a cable, just read a global var that updates from any scriptFX module

function prepareToPlay(sampleRate, blockSize)
{
	g_SAMPLERATE = sampleRate;
}

from there you can compare to the old value and create your own callback

@resonant There is no callback that can be automatically called when the audio state changes, but you can periodically call Settings.getCurrentSampleRate()

EDIT: or like @griffinboy suggested by getting it from the audio thread...

@David-Healey stash, fetch/pull, then restore stash should do, no?

@Solocky You might be interested in the C++ API https://docs.hise.dev/cpp_api/index.html

@Sifres For Faust I had the same issue recently. Is your Faust node in a frameProcessing container by any "non-chance"?
That was my case so I've made a PR to fix it (in fact I made it then it was removed because I was fiddling around because I was trying stupid thing with git because I'm an idiot because... Well, I just re-pushed it)
The export wasn't processing the signal as frame, only as blocks...

@David-Healey Ah yeah! I've seen the projucer being replaced at some point during my crappy manipulations! Checking this, thanks Dave!

I have manipulated branches and realised I have no VS config anymore in my Jucer, be it 2022 or 2026... Thinking it was my mistake, I just downloaded the raw jucer file from develop but all I see is XCode and Linux

I can try to add one manually, but is it as simple as clicking the button? There might be a few things to adjust, right?
And there's no 2026 option...
I confess I'm a bit confused here

It turns out it was a frame processing issue in the wrapper.
Fixed by PR https://github.com/christophhart/HISE/pull/928

So I get my Faust node working in the network, but once that network compiled and loaded in a Hardcoded FX, the Faust inside doesn't seem to affect the signal.

The network parameters are well showing in the hc FX
The environment is not polyphonic (simple FX)

@pelle You need to use Message.sendToMidiOut() in the script that is sending the message in order to forward it to the output of the plugin

For this to work, you'll also need to allow it in the settings:

@Sampletekk yes, chat it is

No matter what I do, the still appears as not compiled even though I get a compile 100% success from Hise exporter (and the hardcoded DLL is not appearing either). Same thing if I compile straight from XCode.

All this is working fine in Hise standalone...

Should I compile the plugin version of Hise with a specific Jucer setting for this to work?

It is to be noted that I removed the mpopcnt flag that was preventing me to compile Hise plugin. Could it be the reason for the C++ node to fail compiling? I doubt that because it's a x86 flag that seems to be now rejected by ARM which is my config, but who knows...

@Christoph-Hart Bump bump (as in when can we expect the current bugs to be solved so we can deliver a product using the Matrix Mod )

@veryveryhaps You can try to paste the error log in chatgpt/claude to see what it spits out