[Solved] Platinum 64 Plugin Scanner Issue

Author
Post
Essentials Only Full Version
TEZ
Max Output Level: -90 dBFS
  • Total Posts : 44
  • Joined: 2003/12/05 01:55:29
  • Status: offline
2017/07/29 22:18:26 (permalink)

[Solved] Platinum 64 Plugin Scanner Issue

 
Splat 64 bit stalled after trying to load a 32 bit Instrument plugin and the prog had to be forced closed as the plug looked like it was malfunctioning. After the forced close the 64 bit plugin manager now scans new 32 bit instrument plugins but doesn't register them as plugins in the plugin manager at all and they don't show up in the browser, in both cases neither as instruments nor as an fx. I can see the scan taking place followed by a "Scan Complete" message showing 0 (zero) new plugins. I reinstalled the latest version of Platinum to no effect, so it feels like something has got corrupted in the registry.

Previously installed 32 bit plugins prior to the forced close are still showing up and load fine. Splat 32 bit has no problem scanning and registering any new 32 bit plugin, so I'm not sure if it's related to a the bitbridge or the plugin manager or just a registry issue for Platinum 64.

In the registry the new plugin shows up in the inventory, but nowhere else. Removing the plug also removes it from the inventory. At this point I'm reluctant to do a reset for fear of loosing the 32 bit plugins that are still available.

Any help would be greatly appreciated.
post edited by TEZ - 2017/08/02 06:31:40
#1

4 Replies Related Threads
    TEZ
    Max Output Level: -90 dBFS
    • Total Posts : 44
    • Joined: 2003/12/05 01:55:29
    • Status: offline
    Re: Platinum 64 Plugin Scanner Issue 2017/07/30 01:05:49 (permalink)
    It's worse than I first thought now the Splat 64 won't load the previously registered 32 bit plugins popping up a "failed to load" message!
     
    If there's a baker out there please help, I'm afraid that doing a reset will make things even worse, and right now I'm at a loss, none of the scan related posts seem to apply, and I use many of the 32 bit plugs with no 64 bit equivalents...
    #2
    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: Platinum 64 Plugin Scanner Issue 2017/07/30 01:46:21 (permalink)
    Did you change your scan paths set in preferences ?
    They should be looking in Program files/cakewalk/Sonar/VST Plug ins for the majority of Sonar plug ins.
     
    Im not sure why you are afraid to try a reset. have you tried opening a new project and checking the preferences/VST plug ins ?
    If all else fails, open a Cakewalk support ticket.

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #3
    TEZ
    Max Output Level: -90 dBFS
    • Total Posts : 44
    • Joined: 2003/12/05 01:55:29
    • Status: offline
    Re: Platinum 64 Plugin Scanner Issue 2017/07/30 02:17:57 (permalink)
    Thanks for the reply Chuck... My scan paths are just as they should be, this mess occurred as mentioned after a stalled 32 bit plugin in splat 64, caused a forced windows program termination. Up until then as far as bitbridging 32 bit plugs goes, no problems.  I'm worried about a registry corruption that a reset won't fix, or worse happening after a reset attempt... Unless someone has a solid insight as to what might of occurred I'll probably take your advice and open a  support ticket. All of this is compounded by the fact that my w10 just updated to the latest creators version 1703, hence the caution...
    #4
    TEZ
    Max Output Level: -90 dBFS
    • Total Posts : 44
    • Joined: 2003/12/05 01:55:29
    • Status: offline
    Re: Platinum 64 Plugin Scanner Issue 2017/08/02 06:53:16 (permalink)
    The anti-virus it seems, removed the bitbridge.exe when the plugin stalled. The first reinstall had no effect, It took a second reinstall with a fresh setup downloaded to a new location to clean up the installation. Anyone else had this sort of a problem??
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1