@David-Healey
@ustk
@HISEnberg
@ulrik

I've created my own little drag-and-drop implementation. Any suggestions for improvements?

HiseSnippet 1697.3ocuXE0aSbDD9tjbsXWPsHwOfE+P3bIXrSbRHJPaRbR.qRBVj.kHDBs4t02sMm205t0IwBgT+o0eR809T6L6dm8cN1zRDTKPw6Nyry2Ly2N6ttSrzikjHisrKe7v9LK6a5bzPgJrUHkKrZuqk8sbFDE0iJD6FSCr1YXeZRBy2x1d9mhpXWZAK8m+7m2gFQEdrwSYY8ZI2i8bdOtZ7rc15W3QQ6S8YGy6kS6la01SJZIijC.3LuScq9TuynArConZy4X8LZRnk8O5rd2UnqsZ2U7Vm0bYFk5e5pqsg+oqzXs0W4QrldT5iVsoWyMrr+l874JY7QJphkXYuvNR+gGEJuPXbvq4I7SiX3fFVGAd1L89xHeLDwYsZExi76jkmRrfUoy3r17lr1cbNf6yGM+3r2OnEPFaQ9Dn8bEg27EfWi7vqdN3MEHYmCRKXfzscNxKl2WMVBhmuyosPwh6Rg5TdnXz0Zt+pjyCeH4EQ76kPvB98D2a2XY+xsjfYBUsdzyX6GCCFsLtqTu9RjkWsd0MKWFrEClAIjWSi4T.7IkiYAjjKn8Ay5YTAW3.THoCUvhRJC08DE4bZLoudBxSHuMyiALUKYu9RALvsh1fFUptTYxT97IrY4qgMqbMroYkpuChxtxX29DtHMfpV9CkK0uVBS0AXFpWJGn3BlqQXmWBoNizCjCRXsnQQmBT+TwGzZBwChgpI3NIrRbQvynBeybUVhX19jT6hPthsDAKJebTNmzV3y8n.iyj3ym2EQ5pBKFx8SO7FqREXUGOpVBvXQShkQtcoQIrIDCAsLgq3RgKvTPxh9+o7kmSOs.RziaLSTXDiHv7Mb4cqnXWpfnuRkpSmgQzocRZduLWDA+gzcfvCgEIqN3FnKTA05Bcn1NJxsP5DKCAn+LyNR3oQPwxHzOldw1Q7.Ay+X.RtpPdBF.s8cqtDIazykdzncjCD9It0g4q3AgVLyuhoZgAPqPl2Yjiowf5WAtdnPiL2fH4ozn2rDw7kSv..onHAjCYw5aR3jGmFg0hXh.UHL08ueUsZeXD+NBAEQoWUvNiAukij4hpbIH0nFFKOU61rB7abgPnn5C+DpexUU+hBp+qbeU3UUJrfROiwCBUnVSnFWjv8YftoIIxO8D.8Kt3nwOFGeevmKt3T2mCeRSqnoCGa5InoCASCy4TdWWiGqVXwhYpAwBB2DDezne5jOnQ98mEXr585jrdAyfxdPKW14.4QSawUg0E0B5AGqLKDwMq2a0xk.DpUulWD26LlOFP20LSLlCagSC5AKVoYs8pTorEbDKoFW3yt7Ec0zc8N7FnherbIMnvSzln+SNn.aYBRcoopEnIXoaUtB8Bx4F6tbywVLblVbRNKFhV.+aF8l.+9.RC.7vxY9xn9TWwrbc7TwCXoQqIb6.mKJi6Yh3sE9D7.Tx1lxFN9kLvsj8NmEOD.sHHWxnGVzeU++eyGf2KzQ4RLETkb2m.zSjgLCg43USmsnS.zrDPWjwTAbdZmkLyeWV+QPTEhRlWmo34BpWyPHAUYyBDGJI9Y3vGwgrOKlpqEJo7LRen4MKccJxsEv8d2b108rS5lIeZhy5.BB1aezFXo3Poh8BgqduKHiLontcmprT.DwhmpX7R0weJCcEC5cJKdI3z1Hf5loHbwwh2F0Y12FM+kk8LGSmSQonsfqdQelXVWg1J8rc3aup8tTEEuBa5bfdPERwQHXuK6b3ADlKzVxYWVxYJYeK6uczEB.XpzRuU10cQliEGtT6MbLWVz5x7uHY33As2BZtBEzzVrf+9dG3Pex3Ir9L7yx48CequZ9YkYEO+N8KpeZNq34yzOeSQ+n2il5Gy90YEOa8aacAd7+nI9i3svc05mBl2CklUjbSmwaMQu3Xm5AyWRWcG66.CB0WhHaDbaudYuD8lNMWdilaTuw5qUOmfkmPx4YaOrm+yI7WdlzyQ.bxv20QeNcZKMn2F3JSGS3aPCTpPpBglQvSsuxqBg2iJ8GDgmAm+Qp3S4SE.8JJ7xP7gdvsZTCy+T+uXub8+JDusSGtxKb5XbtofQnixWCLl9d+a4rW2tLO0X.tfy9u4qyi6sLuZI3.pJlir3CGz6Hf.5w.uKvyIQV6bXWUy35YD7iXBe8f+F9jJrAN1NUXiLgV8ndwx26YNg.+EEtgdF.SB8u9RImCvwjFV5SMxmm6w84u2yq3RcECW95Z3JWWCadcMb0qqgqccMb8qqgO5e2P72eZ6AJYOy1FKqC5rm9HWa68D3CNzrUq+AfuNwBB

@brucerothwell said in HISE 4.1: Obtaining Peak/RMS Values from Script to a Scripted UI Meter?:

DisplayBuffers be accessed from scripting

They can be but I dont think thats what you're looking for in this instance.

@observantsound You can use a global modulator for this I think

https://youtu.be/Y2XhAEE1IBI

Also you can use a single sampler for sustain and release - in most cases. I posted a video about this on Patreon recently: https://www.patreon.com/davidhealey/posts/how-to-create-156513314

@Christoph-Hart I'm also still encountering this issue.
I've also tried all kinds of formats
"{PROJECT_FOLDER}/Scripts/test.js"
"{PROJECT_FOLDER}/Scripts/ScriptProcessors/test.js"
"{PROJECT_FOLDER}/test.js"

I also get onControl cannot be parsed.
My test.js is a file I saved after adding a blank script processor to my container.

1:
"Right-click/connect to external script": Works!
"Rick-click/reload connected script": Works!

2:
Adding script via Builder.connecttoScript: On Control cannot be parsed.
"Rick-click/reload connected script": Does not work "because connected script is not a valid HISE script. OnControl( cannot be parsed"

function onVoiceStart(voiceIndex) { "Hallo"; } function onVoiceStop(voiceIndex) { } function onController() { } function onControl(number, value) { }

@svkpowa Aha ok, just took a look at it and it's probably not needed for new projects.

@HISEnberg @David-Healey Yup that works! I get it now. I've been compiling like a mad man lol

FIXED!!!!!! 😭 😭

Screenshot 2026-06-05 at 7.22.38 PM.png

@David-Healey @HISEnberg @dannytaurus OMG! A Year of trying and it was a stale template file....I wanna cry. lol

Finally made it to this window:

Screenshot 2026-06-05 at 7.25.10 PM.png

and compiled dll successfully !

Screenshot 2026-06-05 at 7.37.24 PM.png

@David-Healey :Hahaha 👍

I'm looking for documents and examples to guide you and I am seeing this is rather poorly documented.

Basically DspNetworks folder works like this:

DspNetworks/Binaries: The compiled DLL. When you compile networks to .dll, HISE is launching and creating a mini-project of just your FX networks, so it contains a .jucer, XCode or VisualStudio file, etc. DLL (Dynamic Link Library) is, to put it crudely, a pre-written and formatted library that contains the DSP code which HISE can load at runtime (for example, load into the HardcodedMasterFx). You can simply delete the entire Binaries folder before compile to DLL for a fresh start (in fact it is a good idea). More info here: https://docs.hise.dev/scriptnode/manual/third_party.html

DspNetworks/CodeLibrary: I don't look here much, but it's usually where a lot of the faust and snex networks are saved to.

DspNetworks/Networks: Where scriptnode networks are saved as .xml. So you can actually look at these in a code editor and see the same structure flow and module settings (it is fairly human readable). This is what is saved and recalled when you are launching networks (it's very similar to how a User Preset works).

DspNetworks/ThirdParty: Mainly for C++ files if you are working that way. I think Snex headers are stashed here as well (I can't remember). You'll also notice HISE will autogenerate headers depending on what you are using, example for Faust.

AdditionalSourceCode/nodes: This is also important. When you go to compile networks you see the menu below. Basically it is autogenerating some headers that are stashed here for when you are ready to compile the entire project. They help link the compiler to the necessary DSP files. You don't really ever need to bother with this folder, but for a completely fresh build, you can just delete the "nodes" folder before compiling the networks to DLL.

Screenshot 2026-06-04 at 6.58.44 AM.png

@David-Healey There might be a bad parsing at some point. Without really knowing, the hex might be first parsed as string by the property editor...

@Christoph-Hart I can breathe again....and move much faster now lol

@Christoph-Hart
Here is a demo gif.
It's about the blue animation above the magician, which changes based on the large knob.
Everything works perfectly in HISE. However, it's still unstable in the compiled plug-in.

webViewDemo.gif

PS. I also want to build a xy-pad with a web view...

@emmanuelbuccheri Loading a sample map always stops the audio engine.

To cross fade load the sample maps into two samplers at the start and crossfade between them. Or load the samples into multiple groups in the same sampler and use the group xfade feature.

I have an old video that shows some techniques here: https://youtu.be/0cn1l8231n4

@MicheleBonventre What's different between the test plugin and the original project?

Also you might try with PluginVal to see if it gives any hints about the issue.

@Lindon well there was a problem in one of my includes, that neither HISE player nor HISE expansion projects was prepared to report.... so moving on for a bit...

@ScreamingWaves https://docs.hise.audio/scripting/scripting-api/transporthandler/index.html

@David-Healey no they need to ring out. i will probably limit it around 16 voice cards or something like a real synth would have

I don't want the user to see the combobox it's just to have presets stored correctly

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

@duma It will appear near the top of the list - not in alphabetical order.

These are custom fonts I've loaded (below Source Code Pro)

20adaa6a-fa7b-4e6a-921b-2a4e779c37fe-image.png