There is a bug in the current release (0.10.2) that causes an incorrect mapping of plugin parameters to the host automation. All plugin parameters, regardless of their range, should be getting mapped to a [0, 1] range in the DAW. The bug is causing the value to be applied directly, rather than mapped. This means that parameter value above 1 in the plugin will be clamped to 1 in the DAW, and anything below 0 in the plugin is clamped to 0 in the DAW.
The zip contains the 64 bit Mac VST, and the Win32 and x64 versions. With the fix, plugin values are correctly mapped to the [0, 1] range. So, if the parameter has range [-100, 100] and the value is set to 0, it will be mapped to 0.5 within range [0, 1] in the DAW.
To be clear, mapping all plugin parameter ranges to [0 - 1] instead of the original range is a separate issue and is something we are currently investigating.
