# We are removing AudioProcessor-based parameter management

**URL:** <https://forum.juce.com/t/we-are-removing-audioprocessor-based-parameter-management/26032>\
**Category:** Audio Plugins\
**Created:** [January 18, 2018, 5:48pm UTC](https://forum.juce.com/t/we-are-removing-audioprocessor-based-parameter-management/26032 "2018-01-18T17:48:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lalala](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/lalala/32/8577_2.png) [@lalala](https://forum.juce.com/u/lalala)\
**Post date:** [January 18, 2018, 9:20pm UTC](https://forum.juce.com/t/we-are-removing-audioprocessor-based-parameter-management/26032/4 "2018-01-18T21:20:37Z")

</div>

I was secretly hoping this day would never come 🙂

> [@t0m](#):
>
> [methods] which act on a specific parameter will be stripped from the AudioProcessor class.

Note that those methods have the following comment :

`NOTE! This method will eventually be deprecated!`

So before you remove them you may want to actually mark them as deprecated for some time.  
Last year I did a poll about plugin parameters ([here](https://forum.juce.com/t/poll-how-do-you-handle-your-plugins-parameters/20674)), and 26% were still using custom parameter classes **not** inheriting `AudioProcessorParameter`. When using such custom parameters classes you can’t simply call `addParameter()`. Changes are much bigger, do not underestimate them please.

---

_[View the full topic](https://forum.juce.com/t/we-are-removing-audioprocessor-based-parameter-management/26032)._