Update....
Waves support remote accessed my computer, uninstalled Waves V10, and installed Waves 9.92. According to them, this is a pretty common fix right now and there are no technical differences between V9.92 and V10. Of course we did "Clear Cache and Rescan" and even the Waves Tech Support guy acknowledged this is required with Reaper and Waves.
I am still banging my head on the issue, using a session that has the new PA SSL Console 4000 E and SSL Console 4000 G VST3 plugins. Crash after crash with frustrating periods where I'll actually get the session to load and be useable 4-5-6 times, then crash after crash.
I'm beginning to suspect something about the RPP file itself may be corrupt in a really subtle way. Problem is this is my project template file with about 200 empty tracks everything prerouted the way I like it and plugins inserted but offline initially so I can do a good balance and pan mix before introducing plugins. If I open the RPP in safe mode with all plugins offline, yes it opens fine. Weirdly, if I remove the PA bx_console_4000 VST3 files from the plugin path, it opens fine, or if I remove the WaveShells from the plugin path, it opens fine.
I did system, memory, and disk diagnostics but all shows 100% functional no errors.
I'm getting zero mixing done trying to solve this.
I was on 5.92 and did upgrade to 5.93. Same thing happens. Irritatingly PA support claims there are no other users reporting issues with the new SSL 4000 console plugins in Reaper so I have to assume this is my problem.
Sigh.
__________________
PRS 2014 Brushstroke 24 / PRS 2008 Custom 24 / Axe-FX 2
Reaper / RME HDSP Multiface 1 / Tannoy 502s / Monoprice 10" Subwoofer
Hughes and Kettner Tubemeister 18 and 1x12 cab
|