Plugin Parameters aren't working (Rhapsody)

[A Former User]

VIDEO EXAMPLE

I'm not sure if this is Rhapsody related or HISE related but I can't get any Plugin Parameters working in Ableton. They all have isPluginParameter set (some programmatically, some manually) and all have individual names without any whitespace

I've run the Validation and Check Parameters tools without issues, not sure what's going on

Edit: in the video I open NP and show how it's supposed to work

[orange]

@iamlamprey said in Plugin Parameters aren't working (Rhapsody):

They all have isPluginParameter set (some programmatically, some manually) and all have individual names without any whitespace

Interesting.

FYI, the Plugin Parameters can have whitespace by the way. No problem with that.

[d.healey]

Parameters can't be added dynamically, this is a limitation of the plugin formats rather than HISE, as I understand it.

This is why Kontakt's automation system has a list of predefined macros that can be assigned at run time. I plan to add a similar thing to Rhapsody.

[Christoph Hart]

@d-healey I've recently added some preprocessors that forward the macro controls as plugin parameters so you can either hardwire them in the rhapsody project to anything or even make a dynamic system using the frontend macro stuff (in this case they will be added to the right click context menu where you can learn MIDI etc).

So you would have to compile Rhapsody with

HISE_MACROS_ARE_PLUGIN_PARAMETERS=1
HISE_NUM_MACROS=8 (or whatever)

I've implemented this for a particular project, but I tried to enable the use-case of Rhapsody (or other Full-Instrument players) with this too so let me know if there are some issues.

[d.healey]

@Christoph-Hart Oh that sounds great, thanks I'll look into it!!

But... could you fix this so Rhapsody will work with the latest commits? - https://forum.hise.audio/topic/8816/bug-loading-full-expansion-crashes-player-with-latest-commit

[A Former User]

So you would have to compile Rhapsody with

HISE_MACROS_ARE_PLUGIN_PARAMETERS=1
HISE_NUM_MACROS=8 (or whatever)

I've implemented this for a particular project, but I tried to enable the use-case of Rhapsody (or other Full-Instrument players) with this too so let me know if there are some issues.

@d-healey have you gotten around to this? ran into this issue again today

[d.healey]

@iamlamprey not yet, adding an assignable macro panel is still on my to-do list.

[A Former User]

@d-healey I just realized a pretty decent workaround is to assign relevant GUI parameters to CC messages, that way the end user can also right-click and bind/unbind whatever they want for automation AND if you stick to conventional CC (like assigning Attack to CC73), most workstations will label them automatically.