Great sharing. Assignment help at Myassignment.services covers a wide range of academic subjects and writing tasks. Students can explore different approaches to essays, reports, research papers, case studies, and other university assignments. Academic tasks often require subject knowledge, proper research, clear explanations, and organised writing. Understanding these elements can help students improve their academic performance and develop better writing habits. We offer subject-based assistance for students dealing with different academic requirements and deadlines. Whether working on a complex topic or a regular coursework task, students can explore suitable academic solutions to manage their studies more effectively.

Spending two years learning HISE to release two plug-ins in the same few months the market is FLOODED with AI plug-ins has been a bit disheartening, and I did start to slopcode for a few weeks, but found I was wasting too much time trying to understand/correct the code.

Learning from Davids vids and the forum has been enjoyable in that it is a challenge and feels like progress I am making. My plug-ins are very much based around samples from vintage gear and samples, so still feels HISE like a good option. I also want to have a strong understanding of what I am doing without being reliant on AI so I can continue to offer support and upgrades to customers.

Interested to see where this convo goes, as I do feel uneasy using AI for ethical reasons like environmental harms.

Hope it continues to be enjoyable for you @Christoph-Hart!!

My Plug-Ins if anyone would like to check them out! --> https://partybagplugins.com/

@David-Healey Thank you for doing this. It really helps me in my Hise Sampler quest!

@dannytaurus I don't know, I was just told Golden Gate, it's not my customer it's a third-party's

@David-Healey Oh, you mean like this? 😂

CleanShot 2026-08-29 at 13.12.10@2x.png

Claude says:

It's painting the warning in the wrong tab, and it's a false positive from conservative metadata.

The metadata classifies every sendRepaintMessage variant as unsafe wholesale; a finer classification ("warning: fine to call, just don't do it per-sample") would be more accurate.

The two points are: (1) ApiDiagnostic needs the callback id so the editor can place the marker in the right tab, and (2) sendRepaintMessage's callScope should probably be "warning" rather than "unsafe".

Glad I don't use the HISE script editor anymore. That would confuse the hell out of me! 😜

@David-Healey 👍

@David-Healey That's fixed now, it now respects the scope of anonymous functions within a namespace like this.

@dannytaurus ah that makes sense. I'm just getting Claude to help with small little tasks so I haven't gone to the trouble of setting up a remote repo, etc.

@combamusic Thank you!

@David-Healey Looks great! I kid ye not, I'm noodling on my website redesign now and used very similar colours and layout!

Total coincidence! 😂

CleanShot 2026-06-18 at 19.05.42@2x.png

CleanShot 2026-06-18 at 19.05.32@2x.png

@Lurch Not sure if it affects compiling networks

My network contains a lot more than just some gains so recreating it all via scripting is a pain and means I don't get to work with the nice GUI. Is there a simple build network from JSON type thing? Edit: dsp.createFromJSON might be it..

Another option I thought of is I can park all the chains in the multi as unused nodes, then in the script use this to add them for just the number of channels:

const dsp = Engine.createDspNetwork("SimpleGain"); const numChannels = dsp.getNumChannels(); const multi = dsp.get("multi"); const numPairs = numChannels / 2; for (i = 0; i < numPairs; i++) dsp.get("chain" + i).setParent(multi, i);

This works for my multi channel simple gain because each channel has its own chain, but I don't think it would be a good general solution for all networks.

@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

@ulrik sure