New plugin parameter system

[d.healey]

I know this was only pushed a few minutes ago, but I have a question :)

Will I be able to use this with full expansions? So I can assign plugin parameters within Rhapsody and all the expansions will be able to use them (via the MIDI learn menu or something)?

What is the gesture support, is it MPE related?

[Christoph Hart]

@d-healey I've written a huge doc section about plugin parameters, so once the CI build is through, it'll rebuild the docs.

Will I be able to use this with full expansions?

If you compile Rhapsody with HISE_MACROS_ARE_PLUGIN_PARAMETERS=1 then yes.

What is the gesture support, is it MPE related?

Nope, it's a feature in most plugin APIs that tell the host that the user is currently moving a control (mostly so it can deactivate automation lanes while the user drags the knob etc). It's not supported by all hosts, but it will make some hosts behave better.

[Christoph Hart]

Alright, here it is:

https://docs.hise.dev/glossary/plugin-parameters.html
https://docs.hise.dev/ui-components/floating-tiles/hise/pluginparametersimulator.html

[aaronventure]

This looks like it could be exactly what I need.

This is a native solution for enabling automation for panel-based components. Finally, panels become the omni-component (well, except for the bug with the left click dropdown)!!

I recently bumped the thread requesting the MIDI channel property be added to the MIDI automation object so that a certain control can be made to respond only to a single (or multiple) channels.

Here I see allowMidiAutomation, but no mention of MIDI in the rest of the example. Is it done through the MIDI Automation handler? Does it, then, still require the channel property?

Therefore, it’s critical that your parameter handling logic is thread-safe

Nice to have this clarification. Does this mean that any repaints or interface interactions that might happen in a control's callback should instead happen in a listener of a value change async broadcaster? Has this always been the case for controls that you expect will get MIDI-automated?

[Christoph Hart]

Here I see allowMidiAutomation, but no mention of MIDI in the rest of the example.

yeah, the example is all about plugin parameters, MIDI is a different concept. But it's listed here:

HISE | Docs

(docs.hise.audio)

It basically replicates the enableMidiLearn property of the UI component but for the automation slot.