• SONAR
  • How to change "filename" shown in Plug-in Manager?
2017/10/25 03:25:32
motayba
Inside Cakewalk Plug-in Manager x64, all of the plug-ins in the VSTi category are showing bad "Filename" filepaths (at the bottom of the window), and are not showing up in Sonar despite the fact that the correct folders are listed in the VST Scan Paths in Preferences. Where is the Plug-in Manager getting those filepaths or how do I change them?
 
(Edit: Seems they won't let me include the screengrab I wanted to place here since this is a new forum account.)

Also, the "Scan" button is grayed out in my VST Settings. How do I manually force it to scan the listed folders, which are correct?
 
Thanks in advance. I'm diving into Sonar for the first time. I managed to fix the latency/delay on my USB keyboard, now I just need instruments!
 

2017/10/25 03:31:36
scook
The links are not images. They are the pages that contain images. To add an image to a post, the image must have an extension. Notice the urls in your post lack image extensions.
 
Is this a Steam-based installation?
2017/10/25 03:37:19
motayba
Yes. Should have mentioned I have the 2016 Professional version from Steam, but it would be obvious in the image!  
 
Thanks for the tip about images.
2017/10/25 03:47:30
scook
A grayed out Scan button means SONAR cannot find the VST scanner. This could be due to a bad path to vstscan.exe in the registry or the program is missing. Since this is a Steam install, you may want to post on the SONAR Technical Assistance discussion area on Steam. There are a few users here who have Steam-based installs but most do not. While the product is the same, Steam installations are different from products purchased from directly from Cakewalk and other resellers. This seems like an installation issue.
2017/10/25 03:52:11
motayba
Thanks, I'll do that. Any idea where the plug-in manager would be getting that information in the normal installation? Off the top of your head, is there a config file I should look for?
2017/10/25 03:55:29
scook
I have not seen a Steam install of any product.
2017/10/25 04:01:24
motayba
By "normal" installation, I meant "non-Steam" installation. I figured our Plug-In Managers might work similarly and you could tell me where you would look to solve the problem in a non-Steam installation.
 
Anyway, thread posted over on the Steam forums.
2017/10/25 04:05:58
scook
I can tell you the plug-in paths shown in the plug-in manager are from the VST Inventory records built by the scanner. At some point the scanner must have been run or there would be no VST entries in the plug-in manager. Somehow the vstscan.exe is no longer available to SONAR. SONAR relies on a registry entry to find the scanner. This entry is setup during installation.
2017/10/25 04:50:31
motayba
Thanks very much for that. I've had a previous version installed and after checking out the registry keys, I saw that old file paths were riddled throughout. So I killed them all and am going to try to reinstall from scratch. Here's hoping!
 
Edit: The VstScan.exe was sitting right there in the same "Shared Utilities" folder as the Plug-In Manager. I'm surprised Sonar was able to function as well as it did like this.
2017/10/25 05:06:09
scook
Here are the current clean install instructions. The Steam install is mentioned.
 
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account