Warning, Bypass automation can fail in DP 9

[toodamnhip]

DP 9 and 9.01:

Bypass automation on plug ins can fail unexpectedly.
(I have only tested in AU plugs)

At 1st I though this was only an issue with Waves, but when DP’s own EQ’s started failing to bypass, I thought I would post to all.

There are two phenomena. One is the Bypass status in the mixer window will disagree with the bypass status in the plug in window itself. (In that case, it’s hard to know if the plug in is working or not. But I think it works in that case). For ex, in DPs parametric EQ 2, the bypass stays read in the actual plug in, but I can see the parameters go from light to darker showing me the plug in is indeed working). The second phenomena is that the plug in won;t automate bypass at all.

The simplest way to check for this is to look at the automation event list inside the SE window or any other window. If Dp is failing on bypass, (or another type of automation),, you will see the far right part of the parameters description BLANK. For ex. in a waves EQ, a CORRECT listing would say: Insert A/B/C/D: (Bypass). A broken automation would read: Insert B: (without showing “(Bypass)"
And as you will notice, there are no brackets and no “bypass” category.

Also, if you use the pull down menu in the SE window and pull down to the missing bypass category, the words “Bypass” and “In” at the left most part of the track window won;t show. You might still see the actual bypass automation in the track itself, but the plug in will not be responding to it.
This will make more sense when you run into the failure and see it for yourselves.

So for now, look through your automation parameters and see if any seem to lack a category in their bracketed names. You might see a list of bracketed names and one that has NO name. That is the broken automation. That parameter will not automate.

The fix for this is also problematic. Sometimes a re-start fixes things, as in many waves EQs. But embarrassingly enough for DP, I cannot get ParaEQ 2 band stereo) to work on some tracks as far as bypass automation, and thus, I have to manually turn it on at each session start, and I erased the bypasses so that it just stays on once manually set.

If any of you have a mix you recall suddenly sound funny, and you had bypasses on plug ins, this may be why. By the way, this issue has been verified by by 3rd party manufacturers.

[MIDI Life Crisis]

Have you tried with both AU and VST plugs? I wonder if it's one or the other that has the problem or if it's both.

[cuttime]

Seems to be a confirmed bug:

http://www.motunation.com/forum/viewtop ... automation

[toodamnhip]

Seems to be a confirmed bug:

http://www.motunation.com/forum/viewtop ... automation

YEs, confirmed. I will post a list soon of the plugs that seem problematic. I have already lost a bunch of money workign tonight, but I want to finally get organized about it as now I have to check these problematic bypass tracks every time I open a mix...once I have the list, I will post. And it should probably be a sticky at the top of the forum. Which Waves, which Do plugs have automation issues. The problem is, they are not consistent. For ex- SSL EQ can fail and then work upon re start. This is a confirmed bug that CHANGES upon any given re start. That is a sucky bug.
So further recommend that one uses “notes” and ANY time one has an issue with a plug in, one adds that track to notes to be checked upon re opening the project.
Again, the “easiest” way I have found to check this is to use the pull down window and look for missing automation names in the brackets at the end of each type of automation in a track.

[toodamnhip]

OK, for what it’s worth, heres a list of problematic plug ins, (by no means complete, and, subject to change when re opening any given session file).

Problematic Plug Ins; do not Bypass automate
Waves:
Vitamin
SSL EQ
Puig CHild EQ
RComprressor
Q2 EQ

DP
Parametric EQ 2band

[toodamnhip]

MOTUs own, newest plug in, FET-76, doesn’t automate bypass properly.

Yikes.

Time for an update/fix!

[Gravity Jim]

It's so simple create a second track (output to the same buss) sans plug-in and place the portions of the track you want unaffected there. I've never even tried to automate plug-in bypass.

Waiting for that glory morning when you find even one thing in DP that consistently works for you. Bog And All His Holy Angels will surely ring in the End Of Days.

[HCMarkus]

It's so simple create a second track (output to the same buss) sans plug-in and place the portions of the track you want unaffected there.

It sometimes simpler to simply automate bypass. I've never had an issue, but I'm on DP8 and Mountain Lion.

[toodamnhip]

It's so simple create a second track (output to the same buss) sans plug-in and place the portions of the track you want unaffected there. I've never even tried to automate plug-in bypass.

Waiting for that glory morning when you find even one thing in DP that consistently works for you. Bog And All His Holy Angels will surely ring in the End Of Days.

I’m waiting for the “Glory days” when DP’s mute and snap shot automation worked properly. With a variety of plug ins going in and out of bypass on a multitude of tracks, your advise would not work, but thank you for the thought. If it was a simple EQ coming in one or two times, or just one plug in, your solution might work. But not in a complex mix where any given track amongst over a 100 has various plug ins turning on and off or automating.

DP plug in automation is broken in various ways. The newest issue being mutes. It is not about what “works for me”or my happiness.
The purpose of this post is to warn others so that they can make informed decisions about using DP 9 or automating mutes. Had I known clearly that Waves Q2 stereo fails mute automation, I could have used Q 4 which does not have such issues. I would have welcomed such a warning. Perhaps this post will allow others to NOT use Q2 until MOTU fixes it’s mute automation issues.

I will add that upon re-start, Q2 went a bit whacky due to inde L-R automation data, and the fix was to delete it from the track and place a new one back into the track. So if any of you have an issue with a plug in and automation, try deleting it and putting it back into the track. It seems DP then refreshes the plug in with correct automation.

[MIDI Life Crisis]

MOTU must face (and will...).

[Phil O]

Thanks for the heads up, TDH. I checked and can confirm that the issue exists on my system as well. Let's hope 9.02 brings some happiness.

Phil

[Henry Robinett]

Great. Just what I wanted to hear. I mixed and mastered my CD. And it's out. I did gave sine automation issues. But in not sure I ferreted them all out.


Sent from my iPhone using Tapatalk

[vsoprod]

Just updated to 9.02 and still having no luck with a lot of Waves plugins and Softube tla 100 bypass. Haven't tried enough to know if there are any that work now that didn't but still enough that I am used to using bypass on that I can't use DP9 yet. Anyone else having any luck?

[toodamnhip]

Just updated to 9.02 and still having no luck with a lot of Waves plugins and Softube tla 100 bypass. Haven't tried enough to know if there are any that work now that didn't but still enough that I am used to using bypass on that I can't use DP9 yet. Anyone else having any luck?

My experience was that some bypass automation has improved such as in Renaissance EQ's that now work, while others still do not work. I was going to test it but then I realized that it will take a long time and I did not have time . This is because there are various iterations for every plug-in. For example, the stereo version might bypass correctly, while the mid side version will not. Crazy
I was going to post of this when 9.2 first came out, but then I realized that various members here would give me a hard time and call me ungrateful, say it is only happening on my system etc. And to be honest, I wasn't in the mood so I didn't say anything. But your post has made me come out of my hybernation and mention this issue is still a problem. It is a bit sad when one does not want to report on issues due to rabid fan boys LOL .

[Michael Canavan]

Hopefully all of you have started and updated your tech links on the issue?
I bothered to call about my issue with VSTi MIDI out, and it did seem to help it along the path.