search

lordmulder / DynamicAudioNormalizer

Dynamic Audio Normalizer
Other
251 stars 36 forks source link

Parameters Initialisation in VSTHost #5

Closed zeroinformatique closed 8 years ago

zeroinformatique commented 9 years ago

Hello, I'm using your super plugin in VSTHost : http://www.hermannseib.com/english/vsthost.htm It works great, except that it doesn't initialise its parameters on load. I have to open the parameters box and fiddle with them to set them everytime I open the application.

capture

lordmulder commented 9 years ago

Hello,

you need to be aware that there are two "flavors" of VST plug-in's: VST plug-in's that draw their own fancy GUI (graphical user interface), and VST plug-in's that simply expose a number of configuration parameters to the host application. The Dynamic Audio Normalizer belongs to the latter category.

This means that the configuration dialog that you see in VSTHost is actually created by VSTHost itself. It is not created by the Dynamic Audio Normalizer! And it looks totally different in other host applications.

For example, in Adobe Audition, the Dynamic Audio Normalizer configuration looks like that:

And in Acoustica, by Acon AS, it looks like this:

Simply put, the host application can ask the VST plug-in which config parameters are available. Also, for each parameter, the host application can read the current value or set up a new value. But that's it!

All the rest is up to the specific host application! Most host applications will "remember" the last config values of a VST plug-in that you used before. And they will restore those values when the same VST plug-in is loaded again. Usually the host application will also offer the user a way to save the current config values to a "preset". Then, a previously saved preset can be restored at a later time.

If the application "VSTHost" doesn't implement these features, there is nothing that can be done on the side of the VST plug-in. You really would have to ask the author of VSTHost to improve these things...

zeroinformatique commented 8 years ago

Thank you for that detailled answer. I understand now that the problem comes from the host, not the plugin. I indeed get it to work by restarting the audio one or two times through the host.