@David-Healey Thanks David

Personally I use panels in most cases as well.

In your case, I know all of my components begin with a prefix indicating their type.
Examples:

knb: knobs btn: buttons lbl: labels

I do this to be able to assign LAFs. control callbacks, etc. as I want.
Assuming you did something similar, it would be simple enough at the outset of your project to format all the labels as you want:

const var labels = Content.getAllComponents("lbl"); for (l in labels) l.set("editable", false);

Editing the HISE source code is a quicker, more permanent recommendation.

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid

@HISEnberg Thanks for the information. I will look into it.

@David-Healey A plugin developer we know, made a plugin that is daw locked to Mixcraft. However, he does not use Hise. I will see if i can find any info on that, and post here

@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

@David-Healey I've worked around the issue by deleting the Strength knob, assigning the macro, then re-adding the deleted knob

@young60 how did you connect the LFO to the macro, and how did you link the dummy slider to the filmstrip knob?
Can you provide a snippet?

@David-Healey It sure does, thanks David.

@David-Healey Yes, I figured that out. It's odd, though, that you have to use 6 images for a momentary which has no permanent on position.

@David-Healey I found the issue.
ParamEQ.setAttribute(band * 5 + 4, bandColors[band]);
band * 5 + 4 is an invalid attribute index for the CurveEq

@pcs800 Or an array of buffers for stero/multichannel

@pcs800 Never mind, I got it working.
I forgot to connect the modulation target
Thanks for the help.

@pcs800 Looks like I may have found my own answer.
File.writeAudioFile(var audioData, double sampleRate, int bitDepth)

@pcs800 Awesome! 🙌

I'm using Activity Watch to track time on an app.
ActivityWatch - Open-source time tracker https://share.google/Edb7SuzvFWQrHf5ZR

Maybe you can borrow some code

@David-Healey Ok, I will keep that in mind

@pcs800 I found two related threads that might help

https://forum.hise.audio/topic/7976/wrap-midi-node-in-compileable-dsp-network
https://forum.hise.audio/topic/4364/snex_node-needs-to-be-wrapped-into-a-compileable-dsp-network

@Christoph-Hart I updated to the latest dev build and the crashing no longer happens

@pcs800 well 95 samples would make hardly any difference at all... whats the measured latency of your plugin?

oh hang on youve already said:

95.9ms, that's great. But how do I get the plugin to report that to the daw?

Go read what @ustk said above.....