waves plugins writing unwanted automation on playback

[jmattchan]

i've been noticing some weird bug with waves plugins since upgrading to 7.3. if i have a waves EQ open and grab a node and move it around during a play-pass or do a write-to command... sometimes on the next play-pass it will start writing plugin automation, deleting whatever my previous move was.

i think it happens if i still have a node or plugin parameter focused in the plugin window when hitting play. but it seems to happen inconsistently.

has anyone else seen this?

matt

[epm]

yes. it's a bitch, i believe it's fixed in 7.4 though.

[Mundoz]

Yep, it sure is a nasty bug.

[kazoo]

Hi !

I have this problem too...
Sorry for my poor english, i will try to be clear:

I have this problem with Waves Plug ins and Protools in ALL configurations (Mac PPC or Mac Intel, Protools 7.4.2, OS X.5, and all Waves plug in version 5 or 6).

If in the Protools Preferences, the 'Allows Latch Prime In Stop' line is ON, Waves Plugs ins automation erase all your automations, even if you touch nothing, like if you were in 'Write' automation mode.

So, when you need automation with Waves plugs ins, you have to 'clear' the line 'Allows Latch Prime In Stop' in the Protools Preferences.


I send a mail to waves, and they know this problem... It's not fix with the V6, but they seem to work on that to fix it soon...

This is the response of wavesupport:
"This issue still exists in Version 6 I hope this will be resolved in the future."


Wait and see :-/

[Rick Sanchez]

I love the "hope" it will be fixed soon.

[kazoo]

Yes, it's not very professional....

Perhaps they have just discovered this problem....

[jmattchan]

i finally had time to call waves and they guy immediately said he was aware of it and that it would take at least a few months before an update was released....

ridiculous.

[Mundoz]

This bug is really getting on my mix.

[garret]

Yes I'm on 7.4.2cs3 with the latest waves update and i'm still getting this bug. It is a nightmare. Anyone hear when it might be fixed?

[jmattchan]

yeah we "just' installled the 6.03 update and the bug is still there.

when i asked them, they said they would fix it in their next release (which i presumed this to be).