ceez

I have this problem with Saturation Knob and TSAR-R1 Reverb. Trying your suggestion. I did open a support ticket with Softube, as well.

I just did a find in Windows file explorer, and found two copies. One in Cakewalk Core, and one in the path identified above. They had different mtimes and sizes. I renamed the older Sonar file. And now the message is gone and I can apply the theme. Still wondering why CbB is scanning the older filetree.

So, I have my old Sonar Platinum release still installed on the same system, I have Bandlab installed on. (Primarily so that I can continue to use some of the add-on I had purchased, like Dimension Pro, Rapture, etc., and load older projects, just in case). After the last update, I keep getting an error splash when I start CbB complaining about the Tungsten Theme.fth. (attached) Only problem is that it's the wrong filetype and in a different tree. Is this a registry setting, and is there a way to prevent the Bandlab release attempting to load this? I should mention that I have both the Cakewalk and Sonar Theme Editors, as well. But, I have almost never started any of the Sonar stuff in the past year.

I'm presently running 2020.09, and marking it "Disabled". With one of the last 2 or 3 updates, Schoeps Double MS started throwing this warning/error (screenshot attached). "The failure point was reported as: release" Log file showing this: VSTSCAN: ---- 718: c:\program files\common files\vst3\Schoeps Double MS.vst3 ---- VSTSCAN: [ShortPath] c:\PROGRA~1\COMMON~1\vst3\SCHOEP~1.VST VSTSCAN: [RegKey] Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/common files/vst3/Schoeps Double MS.vst3 VSTSCAN: ---- Loading VST plugin c:\program files\common files\vst3\Schoeps Double MS.vst3 ---- VSTSCAN: Exception in function [Load VST3 Plugin], failure point[Load VST3 Plugin] VSTSCAN: VST plugin successfully scanned VSTSCAN: WRITE VST DATA... VSTSCAN: WRITE VST DATA - successfully wrote complete VST plugin inventory record... VSTSCAN: WRITE VST DATA... VSTSCAN: WRITE VST DATA - successfully wrote complete VST plugin inventory record...

Noel would you mind me putting you in touch with person at IK Multimedia working on this, on their end? Seems like it should be a simple fix.

@Noel Borthwick - It seems very repeatable. I was selecting the enable it anyway option, and it seems to work. Not sure it's stable, haven't stressed it, yet. What's the location of the scanner? I'll check the metadata on it. Other significant changes this weekend, I did the cumulative .Net Framework update (KB4522741). Not sure if I tried the plugin with Cakewalk before that upgrade.

I've been using 201909 for several weeks, finally ran into a plugin bug. I just recently acquired the IK Multimedia Hammond B-3X VST, and it's the first plugin that I've had a problem with. I've also contacted IK's support, as well. I'm not seeing this problem with Reaper or Studio One.