I was curious if anyone on windows or maybe even mac… I use windows 10 if anyone is using the vst 3 plugin from sonarworks soundID , The vst2 version works fine, but the vst3 seems to make the cpu and memory spike and really slows down the visuals on wavelab 11 pro, even when loading a plugin the menu gets really sluggish and slightly pauses, with the vst2 version is smooth no issue, there support system is beyond garbage so before submitting a bug was wondering if anyone had this issue, I enabled and disabled the gpu setting same issue,
thx
Wave lab don’t work with SoundID, because wave lab use direct access to audio card and no mid point accept. Sound Id this is not plugin - this is soft for correlation audio end EQ.
Sonarworks sound ID Reference vst works fine with wavelab pro 11 in the playback processing section just like ARC 3 from i.k multimedia, its just that the vst 3 plugin was working a little sluggish compared to the vst2, was wondering if anyone else had that issue,
it’s worse for me it works perfectly with cubase but in wavelab impossible to change presets or do anything (vst3 version)
1 Like
I have the same problem. It is quite annoying 
Seems to be pretty stable with recent updates, but i’m on windows 10,
Did you ever find a solution to this? In Wavelab 12 clicking on any part of the Sound ID GUI causes an immediate Wavelab 12 crash.
I actually stopped using it, I purchased monitors with sonarworks built in and also purchased the ik multimedia arc studio box which is a blessing, but I can give it a try if you like to see if there are issues,
Thanks for the reply.
The last I checked, if I report this to Sonarworks, they are going to tell me to re-install a VST2 version which really defeats the purpose of why I upgraded from Reference 4 to Sound ID. It appears there are some known issues, but not specifically my issue.
Yes feel free if it’s not inconvenient to test. It’s an easy test. Open WL, insert Sound ID, open it, then with mouse, press anywhere on Sound ID. Once I press anywhere, WL crashes.
I can try PGs suggestion of generating a crash report and sending it to him which will be my next step this week.