# VST3 parameter name changes don't work

**URL:** <https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313>\
**Category:** Audio Plugins\
**Created:** [June 29, 2018, 9:05am UTC](https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313 "2018-06-29T09:05:26Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\
**Post date:** [May 14, 2020, 9:45pm UTC](https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313/22 "2020-05-14T21:45:54Z")

</div>

Hi, I can’t see any methods available to set parameter name and range on AudioProcessorParameter - how are people changing the name?

thx

---

<div class="post-metadata">

**Author:** ![pflugshaupt](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pflugshaupt/32/13206_2.png) [@pflugshaupt](https://forum.juce.com/u/pflugshaupt)\
**Post date:** [May 14, 2020, 11:31pm UTC](https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313/23 "2020-05-14T23:31:21Z")

</div>

I have a subclass of AudioProcessorParameter for my own plugins. It overrides AudioProcessorParameter::getName(…) and just returns the current name, but when I need to change names, it’ll return a different name and I call AudioProcessor::updateHostDisplay() to make the host fetch the new ones. Which would be okay, if it would work correctly for VST3 as well, but unfortunately it always sends kLatencyChanged along with the needed kParamTitlesChanged which is a problem for some hosts.

---

<div class="post-metadata">

**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\
**Post date:** [May 15, 2020, 8:57am UTC](https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313/25 "2020-05-15T08:57:25Z")

</div>

got ya - thx

[Previous page](https://forum.juce.com/t/vst3-parameter-name-changes-dont-work/28313.md?page=1)
