# VST3 Parameter Info -\> Better generic editor

**URL:** <https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131>\
**Category:** Audio Plugins\
**Created:** [January 2, 2014, 9:02am UTC](https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131 "2014-01-02T09:02:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![olilarkin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/olilarkin/32/7142_2.png) [@olilarkin](https://forum.juce.com/u/olilarkin)\
**Post date:** [January 2, 2014, 9:02am UTC](https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131/1 "2014-01-02T09:02:37Z")

</div>

I'm developing a host based on the demo host example. One thing that I'd really like to do would be able to have a generic editor that allowed textual input of non-normalized parameter values, and display of enumerated lists and boolean parameters using appropriate UI elements (e.g. drop downs and check boxes), rather than a slider for each parameter. I think this should be achieveable for VST3 and also AudioUnits.

Also it would be nice to be able to access information about parameter grouping (VST3 UnitInfo / AudioUnit Clumps).

If you're listening Jules, it would be great to have these aspects exposed in a generic way.

thanks,

oli

---

<div class="post-metadata">

**Author:** ![Pca](https://avatars.discourse-cdn.com/v4/letter/p/7ba0ec/32.png) [@Pca](https://forum.juce.com/u/Pca)\
**Post date:** [January 2, 2014, 10:01am UTC](https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131/2 "2014-01-02T10:01:17Z")

</div>

+1 !!!

I would love getting access to enhanced parameter description provided by the plug-in&nbsp;for my CopperPlug wrapper :-)

&nbsp;

---

<div class="post-metadata">

**Author:** ![rory](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/rory/32/534_2.png) [@rory](https://forum.juce.com/u/rory)\
**Post date:** [January 2, 2014, 5:43pm UTC](https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131/3 "2014-01-02T17:43:27Z")

</div>

You could just create a new generic editor class based on the exiting one. As far as I remember the generic editor class is pretty straightforward. Shouldn't take much to re-work it?

---

<div class="post-metadata">

**Author:** ![olilarkin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/olilarkin/32/7142_2.png) [@olilarkin](https://forum.juce.com/u/olilarkin)\
**Post date:** [January 3, 2014, 2:24pm UTC](https://forum.juce.com/t/vst3-parameter-info-better-generic-editor/12131/4 "2014-01-03T14:24:21Z")

</div>

that's what i am doing,&nbsp;but there are not enough AudioProcessor methods implemented in the plug-in format classes in order to get the parameter info yet.

for instance&nbsp;adding this to the&nbsp;VST3PluginInstance allows me to get the number of steps and default value.

```
int getParameterNumSteps (int parameterIndex)
    {
        if (editController != nullptr)
        {
          return getParameterInfoForIndex (parameterIndex).stepCount;
        }

        return 0x7fffffff;
    }

    float getParameterDefaultValue (int parameterIndex)
    {

      if (editController != nullptr)
      {
        return getParameterInfoForIndex (parameterIndex).defaultNormalizedValue;

      }

      return 0.;
    }
```

it'd be nice to be able to get all the information about a parameter from the&nbsp;ParameterInfo&nbsp;

oli

&nbsp;