No longer enable/disable any plugins since 2017.01 update

Author
Post
Essentials Only Full Version
Rayman
Max Output Level: -90 dBFS
  • Total Posts : 31
  • Joined: 2006/09/06 13:49:05
  • Status: offline
2017/02/14 23:31:43 (permalink)

No longer enable/disable any plugins since 2017.01 update

Been Emailing back and forth with Cakewalk support, so far no solution.
Tried the FB User Group, no solution.
 
I can no longer enable any plugins that were disabled at the time of 2017.01 update. All plugins show as active in the plugin manager dialog but will not show up in the FX insert list. I tried disable and enabled but still will not show up. So far no solution from Cakewalk.
 
I already did a VST reset and re-scan and same issue.
 
Only the plugins that were active at the time of the update are showing up in the FX insert list.
Also the plugin mgr shows all plugins as active which is completely wrong.
 
Anyone have any suggestions?
#1

2 Replies Related Threads
    artturner
    Max Output Level: -87 dBFS
    • Total Posts : 187
    • Joined: 2014/10/16 12:59:07
    • Status: offline
    Re: No longer enable/disable any plugins since 2017.01 update 2017/02/15 01:26:59 (permalink)
    I assume you have checked the different plugin layouts? Can you go to "Manage Layouts" and find them all?
     
    (Right click in FX bin, insert audio FX, Plugin Layouts, Manage Layouts)

    ASRock X99 Extreme4 with Intel i7-6800k 3.4 Ghz
    32 GB DDR4 Ram | Windows 10 Pro x64
    Sonar Platinum x64 | RME Babyface Pro
    Soundcloud
    #2
    Rayman
    Max Output Level: -90 dBFS
    • Total Posts : 31
    • Joined: 2006/09/06 13:49:05
    • Status: offline
    Re: No longer enable/disable any plugins since 2017.01 update 2017/02/15 06:45:03 (permalink)
    I use Layout by manufacturer. For example take UAD, all their plugins show up as active since the update but I only see in the FX Insert List the ones I make active back in December which was my last plugin purchase. Several people on the FB user group are now saying it has to be a windows registry issue.
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1