vst parameter hacking
-
- KVRAF
- 2029 posts since 21 Jul, 2004
Is there some sort of vst loader that can let you go to values past the pre-defined limits? Not really that important to me, just wondering. I mean, is it even possible to create something like that for vst plugs? I just got to thinking about that when I was using the polac vsti wrapper for Buzz and saw that there were some parameters not on the gui you could change in the parameters menu (was a synthedit vsti though so there could have been controls beyond view). Got me thinking about what sort of limits a vst really puts on the inputs it recieves.
Do not lick the fablanky
-
- KVRian
- 769 posts since 2 Apr, 2005
No - I don't believe it would work. VST code is like other program code - it's not possible to change the parameters (variables) because they aren't made accessible to outside code. Unless the developer wants to give you access. All hell would break lose if that was possible! Take something like a simple delay. The programer would have designed a buffer large enough to hold the audio stream for as long as the largest possible delay he designed it for. Lets say that was 2 seconds. Even if you could access the variable for delay time and make it 10 instead of 2, the buffer would overrun anyway.
But - you can get creative and mix and match different plugins to do what you want. Only got a 2 second delay but want 10 seconds? Insert 5 instances into your host, all set to 2 seconds and 100% wet - that would give you 10 seconds delay. The possibilites are huge if you start thinking about plugins that way ...
But - you can get creative and mix and match different plugins to do what you want. Only got a 2 second delay but want 10 seconds? Insert 5 instances into your host, all set to 2 seconds and 100% wet - that would give you 10 seconds delay. The possibilites are huge if you start thinking about plugins that way ...
-
- KVRAF
- 1981 posts since 29 Feb, 2004
Each VST parameter accepts a floating point value between 0 and 1, this is fixed in the VST plugin specification.
This value (per VST parameter) is translated by the plugin code to the real usable values used internally by the plugin.
The parameter-translation is fixed inside the plugin-code by the plugin developer...
This value (per VST parameter) is translated by the plugin code to the real usable values used internally by the plugin.
The parameter-translation is fixed inside the plugin-code by the plugin developer...
-
- KVRist
- 362 posts since 11 Sep, 2002 from Scotland
Well, theoretically there's nothing to stop a host letting the user alter parameters outside the 0->1 limit. Some plugins might clip values to within that limit, but I'd imagine most don't bother, since there isn't (to the best of my knowledge) a host which lets you operate outside the limit anyway.
Of course, there's a good chance you'll get all sorts of weird things happening (crashes etc.) if you did this to plugins which don't handle the possibility of parameters set to values outside their limits.
- Niall.
Of course, there's a good chance you'll get all sorts of weird things happening (crashes etc.) if you did this to plugins which don't handle the possibility of parameters set to values outside their limits.
- Niall.
-
Programentalist Programentalist https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8597
- KVRian
- 657 posts since 21 Aug, 2003
As does FL Studio I might add...asseca wrote:energyXT, Chainer and TobyBear's midiHost all let you access the VST parameters a plugin broadcasts to the host...
And now it's done
-
- KVRist
- 362 posts since 11 Sep, 2002 from Scotland
NiallM wrote:Well, theoretically there's nothing to stop a host letting the user alter parameters outside the 0->1 limit. Some plugins might clip values to within that limit, but I'd imagine most don't bother, since there isn't (to the best of my knowledge) a host which lets you operate outside the limit anyway.
- Niall.