Ok..now i am sure we are talking 2 different things here. Go2 is running @ 17 FPS (when turning knobs), which make reading the values of a certain parameter inside the plugin a hassle. Sure, holding SHIFT (on windows in my DAW) is making the knob turn way more precise, so getting a knob to a certain value is easier that way. The scope is slow as well...BONES wrote: ↑Sun May 26, 2019 1:09 pm Go2 has known GUI problems but slow update rates isn't one of them. As fast as I flick a knob around, the GUI updates and the vector-scope display is very smooth, even when the waveform is changing rapidly. As I said, it is far more likely to be the fact they use a comparatively small number of frames in their knob animations. Try this - hold down SHIFT and turn a knob in Vecto. In Orion, Go 2 gives me fine control this way, hopefully Vecto will be the same in your host. I have to move the knob about one-third of the screen height just to see the knob tick over from one frame to the next. It will show you how far apart the frames are, which will give you an idea of how many frames there might be.
But that is not my main issue.
The main issue is input lagg when playing notes and turning knobs.
I, however, found a workaround in my DAW. When i bridge the plugin, there is no such input lagg anymore. So it is kinda fixed with several plugins. Go2 is still running at the same refresh rates, but at least the input is as immediate as with "fast" plugins.