Kazrog

Just a quick update: I've heard back from the Cakewalk team, and they're conducting an investigation on their end. I'll be watching my inbox for any further communication from them, but I was impressed by their response time.

Hey everyone, We're still in the process of investigating the issue. I've also reached out to the Cakewalk team and am awaiting a reply. Steinberg has changed the structure of the VST3 format in recent versions, where there is a parent folder with the .vst3 extension. See geeky developer documentation here. After investigating for the last day or so, it's my hunch that Cakewalk needs to update their implementation of the VST3 specification in order to support the new bundled format and manifest files. This will allow (in theory) for faster plugin folder scanning, and greater compatibility with all VST3 plugins going forward.

Hi Brian, Just wanted to say that we've become aware of this issue and are investigating it. Cakewalk hasn't historically been a host that we test in, and we don't usually have reports of issues from Cakewalk users. This new issue is due to recent changes in Steinberg's VST3 specification. While our plugins are working perfectly in other VST3 hosts at this time, for some reason, Cakewalk is having trouble loading them. In the mean time, we recommend all Cakewalk users roll back to the previous version of Kazrog plugins. Very sorry for any inconvenience!