New 2016.09 update broke vst scan? [Solved]

Author
Post
Essentials Only Full Version
Russ.15
Max Output Level: -90 dBFS
  • Total Posts : 31
  • Joined: 2015/04/11 02:15:47
  • Status: offline
2016/10/08 16:19:57 (permalink)

New 2016.09 update broke vst scan? [Solved]

Maybe a newbie question, but... I'm trying to use a new VST plugin. I copy the .dll file to the VST folder (verified it's the correct path in Preferences), but Sonar fails to recognize the new plugin, even with a manual rescan. I've tried a couple different plugins, with the same result.
 
Has anyone else seen issues with installing new plugins? Is there something I might be missing as far as registering new a new plugin? 
 
Thanks for any help!
 
----------------
 
Edit 10/12/16 - Monday's update seems to have fixed the problem. Kudos to the bakers for coming through so quickly!
post edited by Russ.15 - 2016/10/13 00:33:15
#1

8 Replies Related Threads
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/08 16:33:21 (permalink)
    It is possible to create a scan log by holding the SHIFT key while clicking the scan button. It may help to review the log.
    Here are some possibilities other than broken scanner:
    • The plug-in is scanned OK and shows up with an unexpected name. There is a variable in Cakewalk.ini which controls what value SONAR uses for plug-in names.
    • The plug-in scanned OK and shows up in an unexpected list. Check both FX and synth lists using different sort options.
    • The plug-in failed scanning and is in the excluded list. The excluded plug-ins may be seen in the plug-in manager. Usually the scanner skips failed plug-ins. There is an option in preferences and the plug-in manager to force rescanning of failed plug-ins.
    • The plug-in is not installed correctly, not activated or requires elevated privileges
    #2
    pinguinotuerto
    Max Output Level: -71 dBFS
    • Total Posts : 976
    • Joined: 2009/12/01 18:46:41
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/08 18:31:57 (permalink)
    Apparently something is not working properly in the VST scan in the update and will be fixed soon. See this thread:
    http://forum.cakewalk.com...spx?m=3495549&fp=1

    HP DV7-3085 Laptop (Intel Core i7 720 1.6 GHZ, 6 GB RAM, 1333 MHZ FSB, 2 500GB 7200 RPM Internal HDs, 17" screen), HP 2009m Monitor, 2TB Ext Drive
    Line 6 UX8 with PodFarm 2 Platinum
    2 Joe Meek VC6Q British Channels
    Sonar Platinum & X3e Producer (64 Bit)
    AD2 w Roland V-Drums (TD4KX2)
    Windows 7 Home Premium (64 bit)
    KRK VXT 8 Monitors
    Frontier Alphatrack, Razer Naga Mouse, nanoKontrol2     
    #3
    Russ.15
    Max Output Level: -90 dBFS
    • Total Posts : 31
    • Joined: 2015/04/11 02:15:47
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/08 21:55:30 (permalink)
    Thanks both of you. Scook, I double checked the things you mentioned (misnamed, excluded, etc.), but still no joy. I did try pressing shift while scanning for new plugins, but I'm not sure where to look for the log file. 
     
    Pinguinotuerto, that post seems to confirm my suspicions. Hopefully the fix coming "soon" means days, not months. 
    #4
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/08 22:22:34 (permalink)
    There should have been a TOAST message advising

    VstScan Log Created.
    %APPDATA%\Cakewalk\Logs\VstScan.log

    the second line is the log path and name.
    #5
    Russ.15
    Max Output Level: -90 dBFS
    • Total Posts : 31
    • Joined: 2015/04/11 02:15:47
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/08 23:00:42 (permalink)
    Hmm... Didn't find it. I'll have to try again later.
    #6
    Keith Albright [Cakewalk]
    Max Output Level: -68 dBFS
    • Total Posts : 1117
    • Joined: 2006/07/10 15:44:42
    • Location: Boston, MA
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/09 09:30:44 (permalink)
    Noel mentioned this will be addressed soon in another thread.
     
    http://forum.cakewalk.com/FindPost/3495745
     
    Keith
    post edited by Keith Albright [Cakewalk] - 2016/10/09 09:53:26

    Keith
    #7
    schwa
    Max Output Level: -88 dBFS
    • Total Posts : 118
    • Joined: 2003/11/18 18:34:55
    • Location: Boston
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/10 00:27:50 (permalink)
    This may be related to my recent thread.  It seems that vst scan is broken.

    HP Envy 850, MOTU 424/2408, MIDI Express, NVidea GTX970, Project Studio 6 monitors, Mackie Control and Ext, Frontier Transport
    Solid State Logic Alpha VHD, UA LA-610, DBX 566, TC M One-XL, POD XT, Roland XP-30
    Shure KCM-44, SM-7, SM-81 (pair), SM-57
    Martin D28 Marquis, Strats, LP's, Carr Mercury, and Marshall Amps
    SONAR Platinum, Rapture Pro, Pro Channel Pack, Waves Gold, L3, L2, TH3 (Full), Amplitube 4
    #8
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: New 2016.09 update broke vst scan? 2016/10/10 09:30:12 (permalink)
    This bug would seem to apply only to 32-plugins, so perhaps not?


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #9
    Jump to:
    © 2025 APG vNext Commercial Version 5.1