Waves Plugins - Really bad graphical response?

[cprompt]

Old video card, outdated drivers or operator error?

Now we're cooking

That definitely was a problem for me a couple of years ago. Waves uses OpenGL 2.1 (I think it is) for its graphics and an old graphics driver that does not fully support it will degrade performance. I upgraded my graphics card (nothing fancy, £20 I think it was) and the plugins have performed flawlessly ever since.

[el-bo (formerly ebow)]

Old video card, outdated drivers or operator error?

Now we're cooking

That definitely was a problem for me a couple of years ago. Waves uses OpenGL 2.1 (I think it is) for its graphics and an old graphics driver that does not fully support it will degrade performance. I upgraded my graphics card (nothing fancy, £20 I think it was) and the plugins have performed flawlessly ever since.

Thanks for the info.

Just 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"?

[cprompt]

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.

[el-bo (formerly ebow)]

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

[Klinke1]

Yes..but does the chainsaw in Doom perform really smooth when you slice up some monsters?

[el-bo (formerly ebow)]

Yes..but does the chainsaw in Doom perform really smooth when you slice up some monsters?

Fortunately for you, Native Instruments do know what they are doing. However, if you want the next iteration of your delay to have knobs that move like a granny with arthritis and fat ankles, perhaps you could make a special request to them

[Klinke1]

I just suggested/implied, that supporting OpenGLxy does not tell alot about the performance.

[el-bo (formerly ebow)]

I just suggested/implied, that supporting OpenGLxy does not tell alot about the performance.

I think this OpenGL/performance theory, as pertains to the particular issue I am referring to, is a red herring.

Do you own any Waves plugins?

[Klinke1]

I think this OpenGL/performance theory, as pertains to the particular issue I am referring to, is a red herring.

Do you own any Waves plugins?

20 when you also count the free VU-meter. All V9

Windows10 with NVidia card

[el-bo (formerly ebow)]

Forget it

[Klinke1]

"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."

The knob and value reacts instantly when slightly adjusted with mouse.
(It can get a little jumpy when you dial fast like i explained earlier)

----
Chainsaw performance matters.. the blood must flow really smooth.
Or you cannot be sure your Waves plug-ins work alright. (but that's common sense...obviously.. )
Imho...

[el-bo (formerly ebow)]

The knob and value reacts instantly when slightly adjusted with mouse.
(It can get a little jumpy when you dial fast like i explained earlier)

so, for every slight change in numerical value, there is a movement from the knob?

[simon.a.billington]

I was going to suggest update the graphics card drivers, see if it has an effect, but I think someone got in here before me.

Waves have been known to have some compatibility issues with some graphics cards. Look into it, if you haven’t already.

[poleda]

Old video card, outdated drivers or operator error?

Now we're cooking

Any chance you could upload a video showing how your Waves plugins are working?

Seems like an odd request for a long standing issue are you truly trying to help or be a distraction?

[el-bo (formerly ebow)]

Old video card, outdated drivers or operator error?

Now we're cooking

Any chance you could upload a video showing how your Waves plugins are working?

Seems like an odd request for a long standing issue are you truly trying to help or be a distraction?

My contention is that the whole graphics card/Open-GL/outdated drivers angle is a red herring, and therefore the distraction. I may be wrong, but it seems that the performance issues that people are having are just that - performance issues.

I am not having any performance issues, per se. I feel this is a totally different issue altogether. And seeing as it has already been discussed that Waves engineers had the similar issue (And we can assume that their systems are perfectly spec'd to run their plugins), I'm trying to get some kind of visual corroboration to finally lay the issue to rest