That seems to me to be a bit of a snippy attitude to a volunteer helper on here who is one of the best 'heavy workflow' experts around here ... and Macs too.
Not only snippy but ridiculous ... what possible benefit is Warren getting for "inflating his post count"? Not a blame thing!
A bit of public politeness is all that is asked of those who post here.
Says the guy who is constantly criticized for his snappy attitude lol. Hypocrite much?
Anyways, if he's here to help then he should help. Dropping useless links that leads to nowhere is not helping.
Copy link to clipboard
Matt from the Audio team. I wanted to chime in here to try to help with this issue. I'm going to post some common trouble shooting issues, and some best practices for the people here, and for anyone that searches for a similar issue and stumbles across this thread. Remember, this is a general “This is how it works and how to trouble shoot” type of post, not anything more. I’m just trying to help here and if this is information you already are aware of, please ignore.
Premiere should fully work with all 3rd party audio effects that are VST2.4, VST3, and Audio Units. We do support Waves, and work with them regularly. We only test with relatively new versions of the Waves effects though. Usually the latest 3 major versions. That said, there should be no real issue with older versions, it just isn’t something that we regularly check on.
On to the helpful bits. With any 3rd party audio effect, Premiere and Audition, and by proxy AME, need to know about the audio effects on the local machine and that database of effects needs to be updated fairly regularly. This is updated my running the Audio Plugin Manager from “Preferences>Audio>Audio Plug-in Manager…”. The Audio Plug-in Manger will run on first launch of Premiere when there are no preference files on disk. If you see this appear, it is perfectly normal, and I suggest that you let it run.
Occasionally, you should rescan for effects, and rebuild Premieres internal effects database. If you notice any issues with 3rd party audio effects, or have recently updated to new versions of effects, or even updated the host Operating System, you should re-scan your audio effects. I’ll detail how to do this below:
That is the basics of how to rescan, and what the different sections do. This would be the first thing you should try when you have any 3rd party audio effect related issues. The scanner runs as an external executable, so don’t be alarmed if you see a process appear called “dvaaudiofilterscan”, that is the name of the process we use to protect Premiere from hangs and crashes when scanning audio effects.
With Apple’s transition to Apple Silicon, the audio effects scanning was affected. Due to the ability to run the Premiere Pro executable as either an ARM or Intel, this affects how Audio effects are scanned on handled. I you have an M1 (or M2 now) based Mac, you will need to scan for audio effects for each required processor architecture. So, if you run both the ARM and Intel version, you will need to launch Premiere under each and do a separate scan for each Processor type. Note that AME is affected similarly also, but will use the effects database of the processor architecture version that is currently launched. So if you Run Premiere under ARM, but AME under Intel, you could potential have a mis-match. Both sets of effects databases will be retained between launches, but may differ. Example: If you have an Intel only effects, launching Premiere under ARM may cause the effect to be missing. This all allies to Audition as well.
One very last thing. Premiere (and Audition) does not support scanning of legacy Waves VST (VST2.4) effects. You will only see VST3 and Audio Units effects after scanning.
Please, if you have any questions or feel that I’ve made a mistake here, respond to this post. I’d love to help.
Copy link to clipboard
Same problem here, Premiere Pro 23.4.0, Waves Clarity working in Premiere but not in export... since i really needed to render something urgently and all the solutions mentioned here did exactly nothing, i made a copy of the premiere project file and opened it in premiere pro beta. interestingly enough, the export worked there with the vst plugin active... maybe it helps someone 😉
Copy link to clipboard
Hey, was having this problem but then finally this worked for me:
I downloaded the Waves Central desktop app from the Waves website. Once installed, I was able to see that I was due for an upgrade on my plugin. I upgraded, restarted. And my audio FINALLY came out with the plugin working. So annoying but grateful to have this worked for me.