@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.

@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 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 👍

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

@David-Healey I have not sorry, gonna spend all 5 hours on this. Thanks!

@David-Healey Ok , thanks

@ulrik of course. Git is the single tool across all software development that pays off. I couldn‘t imagine doing any non toy project without version control. How are you tracking your progress?

@David-Healey yep great, and dumping the quarantine worked for me so thanks.

@Christoph-Hart not that I'm aware of, I didn't even know this macro 🤷♂
I checked and it's 8 as it should...

@David-Healey Ahh cheers dude. Yeah I get it now. So I've done this for my factory content and it worked fine. I need to figure out expansion packs, but I would guess it is a similar approach; making sure my expansion pack installers put the files in the correct place, and having the plugin scan on startup.

@David-Healey Thanks David

Also, worth remembering... a compiled plugin CANNOT use the builder - at least for the most part. So what I've also got is a PluginStateData namespace, which maintains a key:value dictionary of module id's to module references. This runs on plugin instantiation, retrieves all of the actual object references, and stores them in a const dictionary.

You should only use the builder to build the module tree. You should not use it for retrieving or storing id's or object references.

@xxx 100% they can. It's not the best method and doesn't show you how to interact with a server or WooCommerce, it's just a starting point for within HISE.

Just did these renderings for Genki Instruments that just released their Katla synthesizer.
Mostly been working on watch animations, getting a bit bored with that, if anyone needs either a UI design or 3d renders/animations of their plugin, I am available :)
Still 2025-11-06 172656_4.1.10.T.png Still 2025-11-06 172656_4.1.8.T.png Still 2025-11-06 172656_4.1.6.T.png Still 2025-11-06 172656_4.1.12.T.png Still 2025-11-06 172656_4.1.4.T.png