I use Wavelab 8.5 on OSX 10.9 and when loading a plugin I have the following problem.
It seems like Wavelab is not able to release the mouse after changing the value of a slider or a button.
Is there anyone else that has noticed a similar behaviour?
I have also tried to run Wavelab either with the “32-bit mode” (Applications → Wavelab → Get Info → Open in 32-bit mode) checked or unchecked.
However, this change does not seem to solve the issue.
Eiosis is aware of the problem and can reproduce it but I wonder if something can be done on the WaveLab side since it happens in more than a few plugins.
I wonder if PG can weigh in on whether it’s something to be fixed in WaveLab or if all these plugin developers have made the same mistake in this area.
Does anybody have a video example they can share. I see this intermittently with some (but not all) plugins. I think it’s always with VST3 plugins (VST2 seems ok but it’s VST2 ((old)).
Eiosis AirEQ and iZotope Ozone modules are the main ones in my collection.
It also sometimes happens on my PC. It is like the mouse pointer is stuck and can’t do its “normal” mousing.
I have also noticed that the mouse pointer seems to jump around in WL 8.5.3 like something else is controlling it. I am using a top of the line Kensington wired mouse and no other program exhibits this problem.
I have been having this problem for a while. I thought there was something wrong with my mouse. Glad to know it is a more wide spread problem but hoping there is a solution forthcoming.
A bit late in the game but I’ve been experiencing the same issues for years. Has anyone found a solution? It’s the most annoying problem ever. Wavelab 9 on mac-mini.