PT 11.1.3 - Bizarre plug-in behavior

[Farmer Dave]

----------------------------
10.8.5
11.1.3.325
10.3.8.378
2.66 Ghz Quad-Core Intel Xeon
16GB RAM - 1066 MHz DDR3

Eucon 3.1.2
Artist Mix
Artist Transport

Audio Hardware - Coreaudio Aggregate MOTU HD Express & 828mk3 Hybrid

ATI Radeon HD 4870:
NVIDIA GeForce GT 120:
----------------------------

I've been seeing this in previous versions of PT11 too, so not new.

The main plug-in I notice this on is DMG Equick.

1) I have a multi-mono instance of EQuick (1.07) on a 7.1 Aux.
2) Automation on this aux is OFF.
3) The setting I have for EQuick recalls with the session, but the moment I press PLAY, EQuick sets to a completely random setting. It will then stay there - ie - doesn't change the next time I press play.

[Farmer Dave]

I can verify the exact same thing happens with Fabfilter Pro Q.

The session opens up and the plugins are set as I saved them. But as soon as I press play, a random setting occurs in both EQuick and Fabfilter Pro Q.

[DetroitT]

EQ7 try as it sound like a plug-in issue, clear the AAE pref to rescan plug-ins.

[Farmer Dave]

Originally Posted by DetroitT

EQ7 try as it sound like a plug-in issue, clear the AAE pref to rescan plug-ins.

EQ3 behaves fine

Confirmed now to occur in at least 3 different 3rd party plugins:

EQuick
Fabfilter Pro Q
Alloy 2

It looks like failure on multi-mono plugin instances, even on stereo tracks. The plug-in "usually" recalls the settings upon session opening, but will set to a random setting once transport is engaged, even though the track is set to automation OFF.

This does NOT occur if the session is opened in PT10.3.8

Here is a copy of a fresh session that shows this behavior, with:

mono - WORKS FINE
stereo (with Stereo plug-in instance) - WORKS FINE
stereo (with multi-mono instance) - FAILS
LCR (with multi-mono instance) - FAILS
5.1 (with multi-mono instance) - FAILS

https://dl.dropboxusercontent.com/u/...all%20test.zip

And here is a screen capture of this occurring. The 2 instances of the plugin on the left are not multi-mono. The 3 on the right are multi-mono and ALL three show this behavior.

https://dl.dropboxusercontent.com/u/...callError2.mp4

As stated, EQ3 does not show this behavior, but multiple 3rd party vendor plugins do. I've been seeing this in all versions of PT11, but it doesn't happen in PT10.

[Farmer Dave]

Add McDSP ML1 (again Multi-mono) to the list.

This is really problematic, and is one of the reasons I keep having to postpone the switch to PT11. For those of us in Post, multi-mono plugins are a must dealing with tracks that are LCR and up in track count.

[Farmer Dave]

This ALSO occurs after an offline bounce, with the multi-mono plugins generating a random setting.

I'm going to have to go back to 10.3.8. I can't risk this any more.

[TimNielsen]

Confirmed that if I take Dave's session to a Mavericks machine, 10.9.2 and pt 11.1.3, can reproduce every time. Simply opening that session and hitting play, the settings randomly change, and don't change the same way each time.

Seriously dangerous bug.

[philip888]

Ok sorry for you guys.

Glad I am holding off.

[Danny Caccavo]

Originally Posted by TimNielsen

Confirmed that if I take Dave's session to a Mavericks machine, 10.9.2 and pt 11.1.3, can reproduce every time. Simply opening that session and hitting play, the settings randomly change, and don't change the same way each time.

Seriously dangerous bug.

I have regressed it, written it up and reported it to Avid

FWIW, I'm finding this problem with Brainworx BX Digital V2 in all versions of PT11. With MDW I could only reproduce it in 11.1.3.

[Farmer Dave]

Originally Posted by Danny Caccavo

I have regressed it, written it up and reported it to Avid

Thank you Danny!