VST plugins won't work on 24.0

@Kevin-Monahan This has been fixed on the official PP release for a while. In beta it was working for a few months, but then broke again about a month ago. I don't plan on updating to 24.5 anytime soon since I'd lose the ability to bring the project back to a stable release.

Hi Kevin, Thank you very much for your reply but I dont use third party VST since I have this issue so I really dont know if the problem is solved or not.

VST 3.0 plugins mute audio tracks in Premiere Pro v 24.3.0

I have 'weddited' a luxury wedding, and used quality VST 3.0 plugins (TRacks ) in Premiere to master the audio tracks. (Lavalier mics, foley sound, music, etc). When exporting directly or via Media Encoder, the audio tracks with VST effects are silent. Why?

Yes, they seem to have found that discussion. Which is good, of course.

And especially for anyone having issues with interplay between Premiere and MediaEncoder for exports, about the first thing to check ... really, has always been ... is see if unchecking "import sequences natively" in MediaEncoder makes it better. As Matt notes gives a fix here also.

But of course, that only applies when doing Pr/Me pass-offs.

@R Neil Haugen OP isn't looking for your input on best practices or your history with broken plugins. He's looking for a solution to a problem which someone from Adobe has flagged as a bug in another thread. So let's just help the person out and point them in the right direction. 

And btw, I meant 24.0, not 22.4

Yes, there's a couple things that have been off with some audio things this version. Always are, I suppose sadly.

But VST plugins are still plugins ... not normally native to the app, that is. And anything not native is even more likely to have issues, over my years of experience in such things, than the native things.

I liked Matt's explanation of "import sequences natively" in that other thread, btw. Although between the "dynamic link" process that Ae and Au use, and the "direct link" process that SpeedGrade used to use ... SpeedGrade's process was vastly more stable and effective. But ... it's gone. Ah well.

In terms of this discussion, Lumetri is more like a plugin, replacing an app ... and one of the wondrous things many plugins do is extend an app's capabilities. At times dramatically.

But ... you will always have a struggle between plugins and the app on major updates. I've not seen a major version update of any app yet that hasn't had some. I've been through those wars over and over.

And ... I do wish integration between Au and Pr was more ... obvious? ... as some of the ways they interact don't seem to work right unless you know the secret handshakes ... sigh.

@R Neil Haugen I appreciate all the help you give on this forum, but c'mon. You are even part of a thread on here in regards to Waves plugins not working on AME export in 22.4 and someone from Adobe confirmed the bug. Instead of trying to instill good, albiet sometimes uneccessary advice about upgrading, how about point them to some information that would actually help them? VST/AU plugins don't break nearly as often as 3rd party video effects plugs from Maxon/Red Giant. 

@mozadak Hopefully this helps. It did for me.

https://community.adobe.com/t5/premiere-pro-bugs/audio-track-effects-not-working-in-pp2024-v24-working-fine-in-pp2023-v23-6/idc-p/14183333#M16514

When I said update, I was specifically referring to a Premiere update.

As when any app goes through a major version update, whether Premiere, Resolve, Baselight, whatever ... some plugins will work, without needing an update.

But many will not work without an update to the plugin from the vendor. That's been normal for years, and has to be. NO app maker is responsible for the performance of third party plugins past providing the appropriate API/calls for them to use. And notifying them of upcoming changes so they can redo their plugins as needed.