exmatproton wrote: ↑
Sun May 26, 2019 7:11 am
Ok..now i am sure we are talking 2 different things here.
Yes, I am talking about how GUIs work, because I've made a few over the years, and you're talking about things that are completely irrelevant.
Go2 is running @ 17 FPS (when turning knobs), which make reading the values of a certain parameter inside the plugin a hassle.
How do you know what the refresh rate is and what aspects of the GUI it is affecting? If it is indeed 17fps, I will guarantee you that it only applies to the vector display and the graphical envelope displays, not to the knob animations.
In any event, if you are trying to set a precise value, a refresh rate of 17fps is going to be more than adequate, unless your hand is able to move with incredible precision at speeds that make it a blur to an observer. As I explained the other day, when you are looking for a precise value, you aren't looking at the knob, you are looking at the value display at the top of the GUI or listening for the right spot, so the refresh rate won't matter at all.
The main issue is input lagg when playing notes and turning knobs.
That's your audio latency, it has nothing to do with refresh rates. When playing notes, the GUI doesn't have to do anything, it's the sound engine that takes care of that. i.e. The sound engine doesn't have to wait for the graphic to change in order to execute a command.
There is nothing to say that the sound engine will have the same refresh rate for a parameter value as the GUI. It's entirely possible that even though the GUI is refeshing 60 times a second that the plugin is only updating the value twice a second to reduce the CPU load. Or maybe it is updating at 500fps to minimise "zipper noise". The two things do not have to be linked 1:1, as holding down SHIFT sort of demonstrates.
When i bridge the plugin, there is no such input lagg anymore. So it is kinda fixed with several plugins.
Are you serious? You add an extra abstraction layer between your hands and the instrument and you think that makes it faster? I think this proves that it's all in your head, that you've fixated on something irrelevant and drawn completely invalid conclusions.
chk071 wrote: ↑
Sun May 26, 2019 12:04 pm
And how relevant is that with most knobs and faders being able to be moved continuously, and not in 5 lousy steps?
But they aren't, that's my point. If the GUI is vectors then it will matter but if the GUI uses bitmaps, like the vast majority of plugins, then the knob movement is almost certainly a pre-rendered animation with a fixed number of frames. It could be two frames - on and off - or it could be 63 frames (an odd number of frames is required for the centre position to be precisely half-way). Most I've worked with have been 30-odd frames, which is usually plenty. Think of it like the second hand on a clock - most of them click from one second to the next, only a few sweep smoothly around the dial.
If you've got any fully skinnable plugins, go and have a look in the skin folders and see what the knob graphics look like.