@voxuer1 yes global_cable is the best way, mod output => global_cable in scriptnode, then register the callback with AsyncNotification, then it's automatically polled and just updated when the value changes.

@voxuer1 which commit of HISE, from github

@duma you need to select the font you loaded

@boim98208 @Christoph-Hart Do Flex AHDSR Envelopes require connecting to a floating tile? The issue I have of Flex AHDSR not triggering the samplers was also an issue when I did a compiled build

@David-Healey also don't forget the buddy of HISE_MACROS_ARE_PLUGIN_PARAMETERS:

HISE_NUM_MACROS. Help text in the upcoming docs:

HISE_MACROS_ARE_PLUGIN_PARAMETERS

Publishes every macro control as a dedicated plugin parameter in front of the scripted automation slots.

Default Hot Reload Auto Config 0 yes no

When enabled, the exported plugin advertises one plugin parameter per active macro slot before any custom automation slot or scripted plugin parameter, which lets the host automate macros directly instead of routing through a UI component. The plugin parameter index reported to the host changes because the macro slots occupy the first positions, and macro state no longer restores from user presets when the preset system is running in exclusive mode (which matches how plugin parameters are normally managed by the DAW rather than by the preset). Combine this with a reduced macro count to keep the parameter list compact.

Read at runtime from the Extra Definitions, so no HISE rebuild is required. Pair it with HISE_NUM_MACROS so the number of exposed plugin parameters matches the macros you actually use.

See also: $API.MacroHandler$ -- macro slots exposed as plugin parameters are the ones managed through this scripting object, $MODULES.MacroModulationSource$ -- every macro slot is mirrored as a front-of-list plugin parameter when this is on, $PP.HISE_NUM_MACROS$ -- determines how many macro plugin parameters the host sees

HISE_NUM_MACROS

Number of active macro control slots that the project exposes on the master chain.

Default Hot Reload Auto Config 8 yes no

Sets how many macro slots are visible to scripts, to the macro handler, to the Macro Modulation Source synthesiser and to the macro plugin-parameter publishing path. The default of 8 matches the original HISE layout and the UI panels that show a fixed eight-knob strip; values between 1 and the project-wide ceiling let you trim a compact product or scale up to a modular rig with many assignment targets. The value is read at runtime, so changing it in the Extra Definitions and reopening the project is enough to see the new slot count without a HISE rebuild.

Must not exceed the project-wide macro ceiling of 64, otherwise compilation fails with a hard error.

See also: $API.MacroHandler$ -- slot count seen by every scripting call that enumerates macros, $API.Engine.setFrontendMacros$ -- setFrontendMacros expects a name list sized to this value, $MODULES.MacroModulationSource$ -- chain count of the macro modulation source synthesiser matches this value, $MODULES.MacroModulator$ -- macro modulator slot index is validated against this value, $PP.HISE_NUM_MAX_MACROS$ -- hard upper ceiling that this value must not exceed, $PP.HISE_MACROS_ARE_PLUGIN_PARAMETERS$ -- determines how many plugin parameters are published when macros become plugin parameters

@duma Use local look and feel instead of global.

Put your code in code tags so it's easier to read - this button: f5964321-82e0-41c8-a04b-3f6a7a167b37-image.png

Image.load("{PROJECT_FOLDER}Images/BASSLBL.png");

This isn't a function. Follow what I showed in the expansion column video for setting up the look and feel object and loading images.

@Christoph-Hart Hi Christoph,

The mail has been sent.

Thank you again

I think Claude got it this time.

4375aef7-38e1-49d3-8aa2-67876313b26a-image.png

I've finally finished the UI design for the VST.

Instead of going with a traditional interface, I decided to aim for a highly stylized fantasy aesthetic.

The layout is mostly set, featuring the Main, Atmosphere, Tuning and Mix tabs at the top. I've tried to keep the essential performance controls (like Tonal Shift, Lid Position and mechanical noises) easily accessible without cluttering the artwork.

Would love to hear your thoughts on the design and layout.

@David-Healey Thank you!!! It must get old being "the man" here lol. But wow. That is amazingly simple and it totally works for what I want. I really do learn from these snippets as every other issue in my plugin was fixed just by searching the docs and forums. I forced myself to learn on my own, so I really had to weigh the time I've spent against the "ok, I've looked long enough" thing. Again, many thanks and much appreciation!

@David-Healey yes thank you - perfect.

@David-Healey Yeah, I keep meaning to look at the stats for gender. I doubt I need my age range to go up to 65 either 😂

@David-Healey Thank you so much, it's working. Really thank you, I am learning. I am going to import like this everytime

@dannytaurus Nice! Checking this asap 👍

@ustk ahh. makes sense. Thank you.

bump bump - need mouse scroll callback on panels

Solved, HISE_BACKEND_AS_FX was disabled by default in the plugin version of the Jucer. Shouldn't be...