"This Version of PT Does Not Support VCA Masters" error in 12.2

[Seafoam_Green]

Originally Posted by john1192

this is good to know ... thanks for reporting and for escalating to bug status ... avoid until further notice ...

Originally Posted by deanrichard

So they gave vanilla users VCAs in 12.2, but they don't work?

Better re-evaluate that QA process, Avid. That stuff should be caught in the first level of system testing.

Would this bug fix require waiting another 3 months until the next quarterly update

[Bob Olhsson]

Originally Posted by Venshield

Thanks jeffro!... I'll have to leave the VCAs alone for now... When I reload songs with VCAs in them, the fader levels change quite a bit...

I'm getting the warning screen when I reopen a session but am not seeing any fader levels change. If you have a session file this happens with, I'm sure the support folks would want to see what's going on with it.

[jeffro]

You'll see it when you adjust a VCA Master. No need to provide a session, we have a solid repro case. Thanks.

[noiseboyuk]

Does this bug affect everyone or just vanilla?

[Rosco1969]

When will we get a fix though? Surely not another three months????

Installed 12.2 Tried a VCA... worked fine..

Closed protools..

Came back later..


"This version of Pro Tools does not support VCA Masters blah blah blah"

And now I can't even get output from those tracks...

[Steviebhoye]

Possible temporary workaround - works for my workflow anyhow!

Problem seems to occur when sessions are saved with VCA master faders at anything other than 0db (Unity)

I simply add a volume automation point on any VCA tracks at 0db (Unity) at the session start and another at exactly 0db at session end.

You can still then automate volume in between these two points as normal.

Return playhead to song start before saving session (VCA's return to 0db)

No annoying messages on launch or coaleced automation.

[Seafoam_Green]

Originally Posted by Steviebhoye

Possible temporary workaround - works for my workflow anyhow!

Problem seems to occur when sessions are saved with VCA master faders at anything other than 0db (Unity)

I simply add a volume automation point on any VCA tracks at 0db (Unity) at the session start and another at exactly 0db at session end.

You can still then automate volume in between these two points as normal.

Return playhead to song start before saving session (VCA's return to 0db)

No annoying messages on launch or coaleced automation.

You done well Steve (or happy accidental) to figure out that temporary workaround

[jclark5093]

And great work helping to squash this bug, I'm sure! Nailed it down even more for the team, way to go!

[jeffro]

Originally Posted by Steviebhoye

Possible temporary workaround...

Thanks for this! I added it to the bug report.