Update: From our testing, it looks like only certain iZotope VST3 plug-ins and at least one VST3 from Waves are affected. We changed the way we initialize a VST3 plug-in in order to fix a bug for a plug-in from a different vendor. The change was within the VST3 specification, but it turns out there are certain plug-ins which have issues with being initialized in this different way. If you're crashing when loading a pre-existing session (Audition), or a pre-existing project (Premiere Pro), you can launch and manually trigger an audio plug-in scan. Instructions below. Audition: Launch Audition Effects > Audio Plug-In Manager... Check the "Res-can existing plug-ins" checkbox Press the "Scan for Plug-Ins" button Premiere Pro: Launch Premiere Pro Open a project which doesn't have these plug-ins, or create a new project Navigate to the Effects tab. Open the fly-out menu for that tab, choose Audio Plug-In Manager... Check the "Res-can existing plug-ins" checkbox Press the "Scan for Plug-Ins" button Following these steps will re-scan all audio plug-ins, and the ones which are crashing will be labeled as "Not Working" and be skipped. You can then open your previous Session or Project, and swap them out with a different plug-in, or in some cases, the same plug-in but with a different plug-in architecture (e.g. AudioUnits or VST). Only VST3 is affected.
... View more