Karel wrote:This has been fixed in the upcoming update. Using the VST2 version of VE Pro probably avoids the problem, so if you can't wait, that's a temporary option.
So putting the vst3 offline should do it?
EDIT. Tested. It seems that Vienna Ensemble Pro VST3 is indeed the culprit here. I put it offline and reconnected the VST2 to an existing metaframe and project hosted on our MacBook Pro.
The problem with this of course is that the VST3 and VST2 are completely different identifiers to Cubase and as such
there's zero recall for projects saved using the VST3 (the default when both are present in the system)
This means the only useful way to get correct playback is to manually load the metaframe and project and reconnect EVERYTHING which is an enormous pain and obviously is the opposite of convenient.
Could that fix come a little sooner please?