Generic Parameters - Update Name

[dpynes]

            p.push_back(std::make_unique<juce::AudioParameterFloat>(
                juce::ParameterID{ kThresholdStr, kVersion },
                "Limiter - Threshold",
                0, 1, 1
            ));

I have some generic parameter defined in the start of the program, like the one above.

Let’s say I want to re-use that zero to one value with a different mode - like a compressor’s threshold - is there away to send a notification to the DAW to relabel the parameter when the use case has changed? such as “Limiter - Threshold” to “Compressor - Threshold”…

It would be very convenient to reuse parameters, when possible, instead of having to layout a bunch of generic parameters just so they can have unique labels…

Cheers fam.

[gertius]

You can subclass AudioParameterFloat and reimplement
juce::String getName(int maximumStringLength)

This thread has more info on the topic:

How can I change the name of parameters dynamically?

not sure if you can really just change the name, since, as you already mentioned, it’s const. but you can totally just define any behaviour in the lambda that draws the value to the screen as string in the daw. say you have an lfo’s rate parameter and a switch for free/tempo sync (i suppose the most prominent example for this problem?), you’d just put a reference to the switch’s parameter into the string lambda of the rate-parameter and say if it’s value > .5 it will draw the temposync-related v…

[xenakios]

There’s unfortunately no guarantee the hosts will re-query the parameter names once the plugin has been loaded even if you call updateHostDisplay etc.

[dpynes]

Thanks for referencing that thread…That’s what I was looking for.