Dude...easy.BONES wrote: ↑Fri May 24, 2019 2:56 pm 12fps was the default animation speed for Flash content when it first hit the internet and most people were fine with it. For the kinds of things that it matters for in a plugin UI, I'm sure it would be more than adequate.No, what's stupid is what I've just quoted above. The "smooth" functioning of a graphical knob will in no way be affected by the rate at which the UI is being redrawn. It is a product of the way the application is programmed to respond to input and the number of frames in a knob's animation. e.g. If the knob uses a 20 frame animation then there are only 20 possible positions for that knob and the refresh rate will not, in fact cannot, change that. If the value represented by the knob's position is programmed to go from 0 to 100% when your mouse moves a distance of 5mm on your desktop, it will feel less smooth than if it's programmed to do it over a distance of 2cm.exmatproton wrote: ↑Fri May 24, 2019 7:19 amThese days it is just stupid not to run a plugin @ high FPS levels (IMO). Especially when moving knobs etc, it should go smooth.Again, you are completely wrong. Firstly, parameters aren't set at positions, but at values, and the position of the knob is only a visual guide as to the value that has been set. If we use a 32 frame knob as an example, for a MIDI parameter that has possible values of 0 to 127, then for any given position of the knob, denoted by one of the frames, the setting could be any of four different values. So the centre position might be 62, 63, 64 or 65 before the knob changes to a different frame. Again, if the application is programmed to allow long mouse travel, then it will feel smoother and be easier to set a precise value. Also, most applications will allow you to fine tune to the nearest value by holding down the SHIFT or CTRL key (or something similar) so that you can set a precise value. The knob won't necessarily move, it is just there to give you a rough visual indication of the value, nothing more. It is your mouse movement, or the movement of a control on a MIDI controller, which sets the value.Otherwise it is truly finicky to get parameters at the right position.If that's true, you're an idiot, or at the very least you sound like one.Really, not joking. I like to work fast with high refresh rates and i notice i rarely use synths that are just sluggish.Again, if that's true, your experience is worthless because it is completely clear that you don't have the first idea how any of this actually works. The refresh rate will make things like a real time waveform display look slicker (or jerkier) but, as I said, even 12fps will look good enough for something that is just eye candy anyway.BTW, it is not about animations, it is about update rate of the UI. So everything is affected, epsecially turning knobs and moving sliders can be a real pain in the ass with slow updating UI's (in my experience)No, you are wrong. I'd suggest it is the required mouse travel that imparts that joy, nothing more. Even if a plugin is updating at 120fps, your screen is still only going to update at its standard 50 or 60Hz anyway, so you won't actually notice it. Those extra CPU cycles are completely wasted.Yorrrrrr wrote: ↑Fri May 24, 2019 2:22 pm Fast frame rates is something really important to me. Just makes GUI usability a more joyful or fun experience. It's just a comfort thing. I think FabFilter stuff runs at a decent frame rate and as such I find a them a joy to use, not only because of their look, layout, etc.
I am experiencing this without being an idiot.
The difference between rapid @60 and the finicky operation of let's say Vecto is really there.
If you disagree; fine. But there is really no need to name me things...
Nuff said