Well, you are probably not really understanding the technical complexities of limiting the frequency range of an automatable parameter. Automation envelopes will not be scaled automatically by the host if plug-in's parameter range changes - there is no infrastructure available in VST for physical value range variation of automatable parameters.
As for the upper frequency limits in the plug-ins, it's a matter of minute choice - I do not see any "standards" for this applicable.
I do not understand why you are sticking your critique to 24000 Hz frequency - it's as high as a filter can go. If you set it to 23999 it would not work as well for a high-pass filter. But going above 24kHz is not possible. I understand that high-pass filter is most "weird" in this aspect, but you can get the same weirdness when using peaking filter, for example - it can't be defined above 24kHz as well, so it has to be auto-bypassed.
I think you are asking for convenience where it is not possible. The best choice would be hardlimiting the frequency range to 20kHz, but this won't please a lot of users.
Just to make sure we are talking about the same thing here:
I was merely commenting on the LowPass-Filter response which equals a cutting of high frequencies (high cut). I never talked about the HighPass-Filter response @ around nyquist which is a purely academic scenario imho (why would you ever do such a filtering in real life scenarios?).
may I suggest doing this for all parameters (in all your new plugins)? So that a new groups will always use the same parameters we set as default in the first group? Would be dope!
This topic was last updated 180 days ago, and thus it was archived. Replying is disabled for this topic.