@Chazrox haha thanks it was just a small project for a class, now it’s just for running tests!

@d-healey Clever! Thank you!

@d-healey They are now in the docs: https://docs.hise.audio/scripting/scripting-api/scriptpanel/index.html#setmousecursor

@d-healey noted! Thank You! 🙏

@HISEnberg Sure

Ah you found it first :)

@Christoph-Hart yup. But I really just wanna compile my C++ node with 60 parameters and toss it in a hardcoded FX 😀

@d-healey @d-healey said in Sliders not responding to "Consumed" MIDI CCs:

setCustomAutomation

Now that I've had a bit more time, there are a number of hurdles with using this method.

Issues Encountered

MIDI Learn disappears
The "MIDI Learn" option no longer appears in the right-click context menu of knobs — unless an automationId has been manually assigned in the Properties panel.

automationId overrides control callbacks
Assigning an automationId disables the knob's regular controlCallback, which is where most of my knob logic lives (e.g., updating processors, linked components, states, etc.).

Workaround via automation callback
You can attach a callback to a specific automation and call the original controlCallback logic from there — but this adds boilerplate and breaks modularity.

Avoiding feedback loops crashes HISE
Trying to assign a knob as the target of its own automation (to bypass issue #2) results in an infinite loop that crashes HISE.

Controller numbers don’t carry over
If you switch the automationId to a new target, the MIDI CC assignment doesn't carry over. It must be learned again manually — making it difficult to share CC control across multiple processors or targets.

🤕

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

Link Preview Image The big bug tier list

@Christoph-Hart excellent. I'll give it a try now.

favicon

Forum (forum.hise.audio)

@DanH ah nice this will be useful for a current project I’m working on!

@musictop, thank you so much for your reply. I really appreciate it.

@d-healey Good to know! I have a bunch of 'consts' in my 'onNoteOn's. Im going to change them now and hope nothing breaks. Thank You! 🙏

@d-healey yeah something like JSON.delete(obj, key) is the easiest way, the delete syntax would require a real brain-twister with the current parser.

@Christoph-Hart someone recently released a framework for adding your own data, training on it and adding it to an LLM, which is much better than RAG which is very dependent on context size/accuracy performance, currently the leader here is Gemini but it's only benchmarked on recall (like recalling stuff from a book).

I'll see if I can find it.

But ultimately for this to be super useful, HISE would need to be completely scriptable, and then an agentic tool with Context7 might be able to get you some results.

Currently there's just no way around learning HISE.

@lijas90 I think this thread could help you

https://forum.hise.audio/topic/11218/making-button-flash-upon-mouseclick-and-midi-note/19?_=1737578349604

@twelvsquid This came up just the other day - https://forum.hise.audio/topic/12909/how-to-sign-and-authenticate-vst-and-au-plug-ins-for-mac

@d-healey In my experience, traditionally the term 'encode' means to convert from L/R to M/S and the term 'decode' means to convert from M/S to L/R.

So maybe it's the names of the modules that are wrong? Although I doubt that will get updated for legacy reasons.

Still confusing though! 😜

@d-healey worked perfectly! Thank you.

@d-healey said in HISE Meet Up:

@Christoph-Hart said in HISE Meet Up:

a new AHDSR envelope with loop mode & draggable curves

Noice! Release curve editable?

oh whilst we are asking for stuff: MSeg envelopes?