PT 11.1.3 - Bizarre plug-in behavior

[toddsorensen]

We can post all we like. The real problem is that Avid has not placed the engineering staff on fixing problems but is redirecting them to new products. This is occurring while we wait for things like PT 11 Delay compensation bug, which is very well documented to continue without a resolution, or even acknowledgement.
As a Pro Tools Certified Instructor I have not been able to suggest to my students that they purchase PT 11. Its a shame but How can I tell them to buy PT 11 when they can't even use it for composing at this point…...

[Jperkins]

Originally Posted by connor@@vid

Already watching them and collating the list of known affected (so far) 3p plug-ins into the bug for this one. Thanks, to both of you, for the clear repro steps. We're on this one.

Can there be a pinned or sticky post with a running list of the affected plugins? This is a serious (and seriously annoying) bug.

Are multi-mono plugins the only ones affected by this bug?

[Njal Frode Lie]

I've got the same problem with Space, stereo.

I was thinking of transforming to 11 from 10, in the start of an album I'm mixing, but when going from that session from 10 in PT 11., Space loose settings all the time, so it is unusable for now, for me, so back to 10 for me for this album.

(tip; if you want to test out for yourself, make a copy of the song-folder before you try, and work on the copy, as it looks like it 'destroys' some settings)

Njal Frode

Originally Posted by Jperkins

Can there be a pinned or sticky post with a running list of the affected plugins? This is a serious (and seriously annoying) bug.

Are multi-mono plugins the only ones affected by this bug?

[Eric Lambert]

Is it safe to assume that this exact issue wasn't a problem in 11.1.2? If it was, I didn't read about it.

[Farmer Dave]

Originally Posted by Eric Lambert

Is it safe to assume that this exact issue wasn't a problem in 11.1.2? If it was, I didn't read about it.

I had very similar issues in every version of PT11, though didn't spend the time to track it down until 11.1.3.

I would be wary of any version of PT11.

[Njal Frode Lie]

Don't know, 11.1.3 was the first version of 11 I tried.


NF

Originally Posted by Eric Lambert

Is it safe to assume that this exact issue wasn't a problem in 11.1.2? If it was, I didn't read about it.

[ZEUSS]

So maybe this should not even be up for download?? How can you have a release where plugins are not recalling their settings??? Its like they are saying no big deal. We don't care if your work doesn't open up and play back correctly??

It should be pulled.

[TimNielsen]

I agree, would sure be nice to know more about the 'scope' of this bug. Does it ONLY affect plugins in automation off? If so, I can live with it, since I never put tracks in off myself.

But what the heck. We're supposed to be mixing a film in the box in PT11 in a couple of weeks, would sure be nice to know if we really need to quickly downgrade to PT10.

[connor@@vid]

This issue is under investigation as a bug affecting certain third party multi-mono plug-in implementations. The specific behavior is that parameter values on an automation playlist may not recall correctly or change after playback after first opening a session. This has been reported to not occur if a value is written for all parameters using write to all selected at some point on the timeline. The plug-ins reported to be affected in this way so far are DMG EQuick, Fabfilter Pro Q, Izotope Alloy 2, McDSP ML1, Brainworx BX Digital V2, and MDW EQ.

The AIR Multi-Delay and Space reports are also logged, but tracked separately.

[Farmer Dave]

Originally Posted by connor@@vid

This has been reported to not occur if a value is written for all parameters using write to all selected at some point on the timeline.

I tried this and the behavior is still the same. I was hoping that was another workaround but it didn't fix it here.