Scrambled Parameter IDs // Radio Group to Index Number

[nadir_222]

hi there,

I'm working on a project where i need two multitoggles for my hardcoded master FX, so at first I used the combobox (with two parameters that take and index number) but then wanted to do a customized version with its own design and all options visible with no pop up.

I achieved this by using nine buttons each and two radio groups (this time with nine parameters each with on/off which gets parsed back to an index number within my code) which works fine.

However when I added more parameters HISE seems to have a problem with assigning Parameter IDs to UI elements .

For example if I assign Button1 to ParameterID 'one' it controls ParameterID 'four' etc (note that it appears to be random not offset by a particular number). This didnt happen when I still had 19 parameters but started happening when I reached 21 paramters.

So I'm wondering if theres a limit for number of parameters for hardcoded master FX or if thats a known bug and if theres a solution for it.
Or if I can somehow parse the values from each button in a radio group to an index number in HISE and link it with a parameter in my hardcoded master FX.

thanks in advance

best regards
Jan

[nadir_222]

ok after some further analysis, there is an offset by 2 it was just hard to tell.
This leads me to believe that the maximum amount of parameters for a hardcoded master FX is 20.

So this just leaves the last part of my post:

is there a wave to convert the values of buttons within a radio group to a single index number and then assign it to a ParameterID?

[d.healey]

@nadir_222 You should use the parameter names rather than numbers. That way it doesn't matter if more parameters are added or if they are moved around.

[nadir_222]

hi david,

thanks for the quick response!
but I think you misunderstood me due to me poorly naming parameters.
Ill attach a screenshot from one of the tests ive done.
i named the paramters in my hardcoded fx 'one', 'two', 'one_1' etc.

whats basically happening is that if i set the parameter ID in property editor of Button named "one" to parameter ID "one" it actually ends up controlling a paramter ID named "two_1".
as you can see in the screenshot these are two steps apart in how the hardcoded master FX list the parameters.

[d.healey]

@nadir_222 I'm not sure what the solution is but I recommend you use a panel instead of multiple buttons for a setup like this.

[nadir_222]

@d-healey my idea would be to move what I have in RNBO for converting the individual button states to an index to HISE.

where "param" would be replaced with button names and "out" controls a parameter on my hardcoded master FX.
Not sure how to do this though because like inline function can only take one component.

[d.healey]

@nadir_222 I don't know anything about RNBO so I'm not much help here.

[nadir_222]

@d-healey I managed to figure it out, maybe not the most elegant solution but it works.