@elemen8t I just did this myself trying to mimic the RC-20's Intensity knob. What I ended up doing was putting each of my scriptNodeFX's inside of another wet/dry node, then when you have that done, script one slider/knob on your UI to adjust all 'GlobalMix' knobs together. So if you have a scriptnodeFX with a wet/dry setup already, put the whole thing inside of another one and let that be your 'GlobalMix' parameter. I hope I explained that well enough.

Heres a working example.
Screenshot 2025-10-04 at 11.24.40 PM.png

Screenshot 2025-10-04 at 11.24.46 PM.png

Best way? idk but it works.

Screenshot 2025-10-04 at 11.32.17 PM.png

@Christoph-Hart @Orvillain One quick Follow up, how do I get seperate controls for the Value and the Intensity (as it is now two in one with the additional hover control below for the intensity).

Since the intensity in the property editor is the Intensity of the OSC module and not the connected ADHSR graph which I would need.

a138b584-c600-4fe7-ba18-aa7b6ae8e36a-image.png

@d-healey Awesome, thanks a lot!

@Straticah @Christoph-Hart

If I make the background of the web view animation transparent it still won't be transparent inside of HISE, but when it's exported in the DAW it literally takes a screenshot of the DAW UI as the background of the animation once you open the VST? I guess that's not how it's supposed to work.

0cd63d73-8719-45a5-b78c-3626e967afd3-image.png

728a0482-920f-4858-9569-34261d7c442f-image.png

@ustk @griffinboy are right the scripting portion doesn’t work for realtime. I’ve recently worked on something similar to this, you can perform the FFT analysis in a C++ node then broadcast the values to HISE using global cables.

@elemen8t loop points are not a standardized format so I'm doing a best guess to extrapolate whatever info is in the metadata. Can you upload a sample that doesn't detect its loop points, then I can improve the parser.

@elemen8t Christoph is currently working on fixing this, there are other posts on the forum regarding it and which version of HISE to use.

https://forum.hise.audio/topic/12325/the-big-bug-tier-list/64

@elemen8t Yessuh!

@HISEnberg Awesome thank you so much!

@d-healey Yes there are many ways and scripts to make that possible, but no ready-to-use-snippet so I thought I would provide that. :)

The input parameter is the shader file name (without the .glsl extension and the file must be inside the Scripts folder of your project (it will be embedded like any other script file when you export the project).

https://docs.hise.dev/scripting/scripting-api/scriptshader/index.html#setfragmentshader

// That's the image folder... const var glslPath = "{PROJECT_FOLDER}Images/bunny.glsl";

@rglides Thanks

@Lindon Yes I get that, but the initial problem is that it doesn't work in the DAW when it is exported without a sound generator like the audio loop player.

@Straticah Yup the table editor needs a big upgrade imo.