Dynamic Plug-In Processing is broken [PT-279941]

[K Roche]

Well dammm
I can report that on my system on 2021.7 DPP does not work on mono or stereo

I followed the menu in tmuzik post #27 and it did not matter mono or stereo the system usage meters stayed up while playing

I was on a 24 bit 96k session and I tried the Pro Multi Dynamics and then also removed that and did the Dyn3 Comp/limeter with D-verb and Tape Echo same same .. But this was a completely blank session (no audio)

I will install 2021.10 and try again

__________________________________________________ _______________________________________
Ok just got done installing 2021.10 and running test again
Here is what I found as per others
Works blatantly obvious on mono tracks
Works sort of but much less obvious on stereo tracks

Here is what did for the mono session
64 tracks 64 instances of Pro Multi Dynamics
I imported a short mono vocal section about 10 seconds worth, which I put on 32 of the 64 tracks
And placed it to start at bar 4

So start play back and system usage shows the same as at idle (about 2%) stays like that until the it hits the audio, goes up to about 25-30% AND as noted goes back to 2 % some 8 to 10 seconds after past the audio

Stereo session
64 Tracks 64 instances Pro Multi Dynamics
Import short stereo acoustic guitar vocal about 10 seconds on 21 of the audio tracks
Placed at bar 4

Idle shows 3 % hit play and it jumps to 38 to 41%. ---hits the audio goes up to about 48 to 53 % after it gets past the audio goes back to 38-41% or so after 8-10 seconds

Wonder WUWT ?????

[Tweakhead]

what an awesome piece of detective work by tmuzik.
confirmed here too. mono DPP works, stereo doesn't.

although it takes a good 10 seconds after a clip ends for the CPU usage to ramp back down. seems a little long to have much effect on a real-life session.

[Tweakhead]

Something else I just noticed . . .

If Tracks are muted, they still use DSP (mono or stereo)
ok, I can see that for fast manual unmuting of track mute switches I guess

but, if Clips are muted, they also still use DSP.
eg. if I have a guitar track for which I only use the solo section, I have to delete everything else rather than mute in order to benefit from DPP ?
c'mon now . . . that's just silly.

[resonatee]

Acknowledged by Engineering Team as PT-279941. (Dynamic plug-in processing does not work on tracks wider than mono)

Please refer to support portal so we can have this fixed as soon as possible!

[dominicperry]

Originally Posted by resonatee

Acknowledged by Engineering Team as PT-279941. (Dynamic plug-in processing does not work on tracks wider than mono)

Please refer to support portal so we can have this fixed as soon as possible!

What kind of testing are Avid doing that means this is broken for ages, and when they finally come to fix it, they only check mono tracks? Absolutely scandalous.

Dominic

[ZEUSS]

Originally Posted by dominicperry

What kind of testing are Avid doing that means this is broken for ages, and when they finally come to fix it, they only check mono tracks? Absolutely scandalous.

Dominic

What’s worse is it’s been broken for some time now! The OP brought it into more attention. Unbelievable.


Sent from my iPhone using Tapatalk

[resonatee]

Yes, it seems the Pro Tools framework is pretty shaky. That's what you get when you have to hold on to years of backward compatibility, i guess.

Anyway, let's focus on solutions and escalate!
Anyone with a support plan, file a bug report and refer to PT-279941! They will fix it.

[Rectifried]

Bump this issue

[Tweakhead]

which makes me think of the subject of renewals. mine is about to expire, and I am seriously considering not paying $400 for yet another year of updates which take one step forward and two steps back.
however this particular bug is such a major issue I feel that I am being goaded into renewing so that I can get a fix. I don't want to be stuck with my permanent license for what is currently a broken version.

this either already is, or could become a tactic for getting people to continuously keep paying for updates in order to fix various things that are endlessly broken/getting broken.
isn't there a law about this kind of thing ?

[tmuzik]

Hi Everybody,
I just want ask the members to please tap the brakes a bit and let's not let this thread turn into an AVID bash fest, pretty please.

I am soooooo glad AVID is addressing this issue.
We have all gotten along with it not working quite right for some time. So the fact that this is now being addressed is a giant leap forward.

Just an FYI another very popular DAW (Apple only) DAW has/had the exact same issue (I haven't checked the past few releases) - only their plugin issue effects the returns and not the tracks. No DAW is perfect, and that can be said with certainty.

On the bright side.
Because of this plugin issue, I fell in love with the classic, old and green McDSP plugins all over over again. The only thing they really lack is the harmonic content which can be added quite easily.

Since I moved to 88.2k and found this issue, my CPU got smacked pretty hard. I really did a lot of testing of plugin CPU efficiency vs sound quality to determine if all those extra cpu cycles were worth the result. Matching curves of eq and compressors, checking harmonic content with plugin doctor. Then bringing the matched settings into sessions and A/B-ing. It was quite interesting.... well... to me anyway.

Anyway, let's hope AVID get's the complete fix on the next release.

Looking forward to a great new year, let's not look backwards. Onwards and upwards.

Thanks Jeffro for expediting the issue.