VST3 automation point value

[Rohkmar]

Hi!

There seems to be an issue with VST3 automation point values.

Steps to reproduce:
- Start a VST3 plugin
- Create automation for any parameter that doesn't use the range 0 to 1
- Create an automation point and right-click it and input 0.5 for example

It will take the value 0.5 as meaning 50% of the maximum range instead of just accepting the value "raw".

This issue doesn't seem to be present in the VST2 version of the same plugin.

Does this happen to anyone else?

Thanks!

 

[Stuart Welwood]

Welcome to the forum , Rohkmar.

It might help to provide an example of the plugin you're having a problem with. That way, you would give others a chance to try and maybe duplicate what you're seeing.

 

[Rohkmar]

Thank you.

I've tried various ones, but one example would be Helm as it's free.

And then automate Transpose as an example, (-24 to 24 range) and try right-clicking a node in the automation lane and input any integer between -24 and 24 (will not work properly) and then input anything between 0.0 to 1.0 instead and you'll hopefully see what I speak of.

Cheers!

 

[Jens]

AFAIK, the plugin reports the range to the DAW. Any VST3 plugins I tried with SP work as expected. You could also try another DAW with the same plugins and post screenshots for comparison.