Hi Juce Team,
Would it be possible to update the range and default value for parameters on parameter info changes as well instead of just names
See enclosed diff (Would be great to see the same thing in AAX)
VST3param.diff (2.9 KB)
Thanks !
FWIW this helps for NKS support when you have runtime assignable automation 
bump
new bump
How would this work in a saved session?
For example If I record my hit song with a plugin, using the DAWs automation feature to move a parameter from 10% to 50% over some time period.
A year later I load the session, but the newer version of the same plugin now has a different range on that parameter, and my recording now sounds very different because that parameter has a different range, and therfore a different interpretation of â50%â.
This is not this use case.
The rationale is when you have N slots of automation and allow to dynamicaly assign your plugin parameter to it.
Useful if you have a non fixed topology.
bump
I donât think that the VST3 spec allows for this use-case. Passing kParamTitlesChanged to restartComponent indicates that âParameter titles, default values or flags (ParameterFlags) have changedâ, according to the docstring. I donât see anything requiring hosts to refresh the stepCount.
If you need this functionality, it should be fixed in the specification first, so that hosts and clients can agree on the expected behaviour.
default would already be something good (same thing in AAX)
step count works fine as well FWIW (at least in Komplete Kontrol).
Or it wonât work but it doesnât break anything
I suspect step count is still implied in the docs.
1 Like
Treat the stepCount field as kind of a flag, thus you can indicate to the host that this has changed.
1 Like
Thanks for the clarification. Please could this information be added to the docstring in the next release?
Sure, I did just that.
3 Likes
This behaviour is now implemented on the develop branch for both hosts and clients:
Thanks !