Anyone here with CbB, Focusrite, SSD5 ? (new 4.63.23 driver error)

[filo]

Hi,

is there anyone with the Focusrite interface and installed SSD5 VSTi who already has tried the new Focusrite 4.63.23 driver?

I have got error that CbB can't load SSD5 dll.  It happens even in "Run as Administrator" mode (Win 10) . I have zero issues with previous driver and can reproduce this error (Fortunately I have a backup Win10 with functional Focusrite driver)

 

Edited August 27, 2019 by filo

[Noel Borthwick]

Seems pretty unlikely that this would be related to the driver unless some dependency for that plugin got removed somehow.
Does the plugin itself scan ok? What if you switch to the onboard audio device (WASAPI) and try loading the plugin - does it work?

[filo]

Scan is OK, switch to WASAPI didn't help. I've tried to reinstall SSD5 Free too, no errors but the result is the same.

VstScan.log

Edited August 28, 2019 by filo

[Jeremy Oakes]

@filo : is this driver part of the newly released 3.2.1 package from Focusrite ? 

If so, there’s another fred where Ben Statton from Cakewalk confirms my op.

i still haven’t heard anything positive back from Focusrite.

J

[filo]

Don't know whether it is a part of package, I have downloaded just a standalone driver 4.63.23 here: https://customer.focusrite.com/support/downloads?brand=Focusrite&product_by_range=553&download_type=software

You have meant probably this thread, thank you for that.

 

[Jeremy Oakes]

No, its not the same as for the 18i20 second gen

https://customer.focusrite.com/support/downloads?brand=Focusrite&product_by_range=552&download_type=software

cheers,

J

[scook]

The scan log indicates the plug-in was skipped because it was previously scanned.

Try running a VST reset with "Generate Scan Log" enabled. This will force a scan of all plug-ins including SSD5.

[filo]

@scook: Weird, because this is exactly what I did (enable "generate scan log" and copy log file here)

Edited August 28, 2019 by filo

[scook]

The log indicates a regular scan not a reset.

No plug-ins were actually scanned according to the log. From the bottom of the log

Quote

VSTSCAN: Finished analyzing VST plugins - 0 of 38 VST plugins were scanned in this run
VSTSCAN: Delete untouched - Scanning for plugins to remove...
Closing log file
Wednesday, 28 Aug 2019, 06:42:23

Instead of clicking the Scan button, click Reset

[filo]

Now I see it. I have used Scan button after the checkbox tick, not Reset.  Thanks for a hint.

[filo]

So I did these steps:
1. Reset VST
2. Scan (way longer than normally)
3. Close CbB
4. reinstall SDD5
5. start CbB with generation of log

I think this is crucial part (at the end of the log):

VSTSCAN: ---- 34: c:\program files\vstplugins\SSDSampler5.dll ----
VSTSCAN: [ShortPath] c:\PROGRA~1\VSTPLU~1\SSDSAM~1.DLL
VSTSCAN: [RegKey] Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/vstplugins/SSDSampler5.dll
VSTSCAN: Previously scanned - NOT a VST plugin

 

I have rebooted into Win10 with older Focusrite driver (4.36.5.612), did Reset and Scan and here is the part for SSD5, there is not mention about "not a VST plugin" there.

VSTSCAN: ---- 34: c:\program files\vstplugins\SSDSampler5.dll ----
VSTSCAN: [ShortPath] c:\PROGRA~1\VSTPLU~1\SSDSAM~1.DLL
VSTSCAN: [RegKey] Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/vstplugins/SSDSampler5.dll

VstScan.log

VstScan-driver-4-36-5-612.log

Edited August 28, 2019 by filo
additional info

[scook]

The reset could have been performed after the re-install.

A reset is a scan except it clears the VST Inventory and scans all plug-ins as if they were just installed.

So, what is the status now? Is the plug-in available?

[filo]

@scook No, I have updated my last post meanwhile

[scook]

After changing drivers is the plug-in available?

[chuckebaby]

 

1 hour ago, filo said:

I have rebooted into Win10 with older Focusrite driver (4.36.5.612), did Reset and Scan and here is the part for SSD5, there is not mention about "not a VST plugin" there.

If what you are saying is "Its working" than put me on a list of people who are baffled by an interface driver not allowing a VST to be scanned.

[filo]

@scook If your mean the older one (4.36.5.612) then yes, SSD5 is present and fully functional. 

@Chuck E Baby Yes, that's what I'm saying. I have no problem with a "triangle" CbB-Focusrite (4.36.5.612)-SSD5. The problem is 4.63.23.

I already have written e-mail with description to Focusrite support.

 

Edited August 28, 2019 by filo

[filo]

I'm in a endless circle.

If I do  Reset and Scan, CbB make SSD5 record in registry as invalid  and SSD5 is not present in VST instrument tree in CbB.

then if I import the SSD5 key from "wealthy" Win10 instance (with older Focusrite driver)  I'm getting error as I  mentioned in my first post:

 

 

 

Edited August 28, 2019 by filo