MW Equalizer bug?

[stringtheory]

i have a track with an instance of MW eq, plus a few other plugs. the mw eq is in Insert B, Insert A is empty. there is bypass automation info for the mw eq in the track, in the drop-down for viewing automation in the SE, i see "Insert B: MW Equalizer [Bypass]" as i should. BUT: if i add another instance of MW EQ into Slot A, the bypass automation moves to that slot! by itself! in other words, if i go back to the drop-down menu i see "Insert A: MW Equalizer [Bypass]" on the layer. if i select any other plugin for Slot A, that does not happen.

submitting a tech link...

[stringtheory]

tech link submitted - already got a reply that they can reproduce this with a number of plugs, it has been referred onwards and is "in progress."

[Phil O]

Thanks for the heads-up ST. I haven't looked at the new bug report thread lately, but if it's still active you might want to post this over there. No one can debate bugs confirmed by MOTU.

[Robert Randolph]

I was about to add a bug report thread for this, but it would be helpful if stringtheory could add one.

I'm not exactly sure how to describe this exactly, but it's clearly an issue.

[sjn]

I am seeing this problem with MW EQ in DP 8.0.7 too - so it's been around for a while.

I also see it with Waves MondoMod (and from what I read on a much earlier thread, lots of other plugs exhibit it too)

But I found a simple workaround that might help if your system isn't already maxed out: If you can run the problematic instances in 'real-time' (i.e. selected in those particular effects' mini-menus), bypass automation seems to work fine again. Working so far, anyway.....

Steven

[Rick Cornish]

I've experienced this with Waves plug-ins, but not with native MOTU plugs. I found that creating a new sequence solved it, so you might want to try that.

[tommymandel]

I am having problems with MANY DP (and other) plug-ins - as far as their Bypass status is displayed. In the event list window, moves I make to bypass/enable ARE displayed - but the red Bypass indicator in the upper right hand corner of the plug-in does not change - ever. And the Insert Effect's name in the Mixer Window also does not reliably change from Italic (bypassed) to non-Italic (enabled).
I've just noticed this with the 2nd 9.13 update, though I'm not 100% certain that's when the aberrant behavior began.
It happens with Floating selected or not, and also with Real-Time selected or not.
I have checked my Automation Setup and Event Chasing settings, and they are set to ALL on.
I have checked with a completely new Sequence, since I first noted the 'bug' in a fairly elaborate and long one of mine.
Some of the plug-ins that exhibit this are MW Equalizer (DP) and AC30 (DP). Also PlugIn Alliance's De-Verb Plus, though that seems more intermittent, and in the Event List Window, sometimes the Bypass status is just 0 or 1, and not listed as "Bypassed" or "Enabled."
I almost began this as a new thread, but thought it better to append it to an existing one. I hope this is the proper way to do this.

[FMiguelez]

I am having problems with MANY DP (and other) plug-ins - as far as their Bypass status is displayed. In the event list window, moves I make to bypass/enable ARE displayed - but the red Bypass indicator in the upper right hand corner of the plug-in does not change - ever. And the Insert Effect's name in the Mixer Window also does not reliably change from Italic (bypassed) to non-Italic (enabled).

I see this all the time, and it REALLY irritates me!

And this has been going on for a while already. I can't believe MOTU doesn't fix all these old bugs

Oh, and and 85% of the time, the Bypass automation in plug-ins, even MOTU's own plugs, will NOT work.
But sometimes it does, with no discernible pattern, which makes it totally unreliable.

[Rick Cornish]

FWIW: I was experiencing this quite a lot, especially when trying to automate plugin bypass. After some testing (including trying in new sequences and a test user account, where bypass worked fine), MOTU tech support suggested creating a new user account. Once I started in on that and realized what was involved, I decided to go one step further and wiped my HD and did a clean install of everything from the OS up. Since then, no problems (so far).

I'm guessing it might be a corrupted prefs or support file, or maybe something deep in the OS… but that's just a wild guess.

[tommymandel]

Thanks, Rick, for pointing me in a potentially fixit direction, although I'm not really ready to go back that far yet LOL. And thanks FM, for convincing me (at least for this morning) that I'm not totally bonkers.
MotuNation Rocks! (so thanks, James, too!)

[mikehalloran]

If a clean install fixed this, then Console.app should be able to help diagnose the offending library or extension.

[stringtheory]

i just reported this to MOTU a couple days ago: i noticed that the de-esser plug was not indicating it's status correctly. it was functioning correctly but the bypass button was not indicating properly. confusing. they said "I've seen this before and have brought it to the attention of our engineers" and "This is definitely a strange issue. I'll give this a bump to our engineers and will let you know if it will be fixed in a future update."

[philbrown]

Just had something happen with bypass automation the other day. I set an automation point to un-bypass a delay a few seconds before the next vocal line but it would kick on midway through the line at a random point each time. Had to split those lines out to a separate track to get around it. DP 8.07 in my case.

[Rick Cornish]

I just remembered one more tidbit that may be of use as a workaround: I was automating plugin bypass from the Events List. When no bypass control for a plug appeared there, sometimes I could access it from the Sequence Editor.