el-bo (formerly ebow) wrote:So we are on the same page, can you give me an example of the what you experienced as degraded performance. And, subsequently, what characterises, "performed flawlessly"?
Degraded performance for me was:
Sluggish UI updates - meters and knobs
Poor DAW performance
Strangely, I didn't have any issues when just one Waves plugin was open, but as soon as I opened two, Reaper did horrible things. I suspect it was because my graphics card wasn't OpenGL 2.1 compliant and either Waves OR the graphics driver was translating the OpenGL 2.1 calls to OpenGL 1 or something, putting a huge burden on the CPU. Yet, it was ok with just one Waves UI open (as far as I can recall anyway).
Bought a cheap but up-to-date card and they have performed flawlessly ever since.
This may not be your problem, but I do know that Waves are very graphics driver dependent.
I don't think what I am referring to is the same as what you, and others, are referring to.
This is not sluggishness/heaviness, and doesn't come with the kind of lag like, for example, dragging a window around the screen and the window trailing the mouse, leaving trails (you know what I mean, right?).
I am not experiencing any high load issues, no matter how many instances of the plugin. Each instance is just as light, or heavy, as the other fifty I could easily load up.
The controls move quickly (too quickly, in some cases i.e the mouse-acceleration curve that I also mentioned).
If you have time, load up any Waves plugin. Then start turning a knob, slowly, while watching both the knob move and how that correlates to the numbers in the accompanying box. You 'should' notice the numbers move smoothly and accurately, but also notice that you 'should' be able to adjust quite a bit before the knob actually makes any movement.
p.s My graphics card, despite being old, apparently supports Open-GL to 4.something, and I have just updated my drivers to the most latest that my current os will support