1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Komplete kontrol- Waves Instruments - I broke it

Discussion in 'KOMPLETE KONTROL SERIES' started by stewart hannah, Apr 23, 2020.

  1. stewart hannah

    stewart hannah NI Product Owner

    Messages:
    43
    Ok no idea what I have done but I have broken my Kontrol app install. I have Waves Central CODEX synth and the icon shows on the left but it now refuses to load the instrument - the dreaded - plug in not found.

    I have done all I can think of,
    scanned registry - nothing found
    removed rebooted added plug in paths rescanned NOTHING

    It knows waveshell dlls are there you can see them during the scan but when complete NOTHING

    I have uninstalled reinstalled Waves Central and reinstalled CODEX nope that did not work

    Now I know CODEX is wrapped around the waves api so I guess it needs to see both waves shell and CODEX to load CODEX.

    ANYONE got a clue what folders I need to add and should they be in any particular order in location?

    It worked before but I was doing some more housekeeping on my files and folders and I have screwed it up big time. Is there a log file directory for the scans so I can see what/where it is trying to scan and what if anything might be missing? Compare old one to newer one? I cant find any
     
  2. Goon

    Goon NI Product Owner

    Messages:
    884
    KK only needs to see the Waveshells, ensure you are pointing KK to the x64 waveshells, at a guess I would say you probably may also have duplicate waveshells, which also confuses KK.
     
  3. stewart hannah

    stewart hannah NI Product Owner

    Messages:
    43
    My house keeping appears to fix one problem and break 2 others. Not helped cos some plug ins decide for themselves where they will dump their files and then the confusion over dll and vts3 extensions. I used to have 3 plug in folders one for VTS3 64 (vst3 extentions) and another for the VST2 64 (older dll extension) I gave that one up and combined them, aaaugh I keep the x86 in another u guess it VST3 32

    Kontrol appears to locate and register folders I never wanted it to look for even in places I never asked it to search and scan. I wish you could scan each location individually rather than a full scan every bleeding time.

    Think I will uninstall the damn thing and start again or go back to a system restore point. This is doing my head in, I have a test computer and I cannot see what the difference is between the two yet one works fine the other is broken
     
  4. Goon

    Goon NI Product Owner

    Messages:
    884
    Dont know what OS/DAW your on & using, but with Windows 10 VST3 usually reside on program files/common files/VST3.

    Currently KK doesnt use VST3 either,

    You should take control of your installs a bit more carefully, most plugin installers have an option for where to install the VST. The exception is Waves.

    On my Windows 10 setup, I have a VST folder on my main drive C:\VST.
    I only use 64 bit VSTs, so I install all my vst's into their own folders within the above folder, for example C:\VST\Native Instruments. Mixing 32bit and 64bit VST dll in same folder is NOT a good idea, and will cause many problems as you are experiencing.
     
  5. stewart hannah

    stewart hannah NI Product Owner

    Messages:
    43
    I have installed my Windows 10x64 boot partition on M2 and the VST folders are on a separate SSD. I have a new computer that has M2 on the motherboard (2 in fact) and I have a couple of SSDs for faster access over the slower SATA3 drives.

    I created vendor specific folders for respective vsts files and I have split the newer VST3 from older VST2 dlls So I am back to square one having done a system restore from a couple of weeks ago. I have not mixed 32 and 64 bit VSTs I have them in separate folders VST3 32 and VST2 64 and if the option is available I don't install the 32 bit versions.

    I have 3 folders for VST plug ins
    VST3 64 (VST3 extensions)
    VST2 64 (64xdll extensions)
    VST3 32 (86xdll extensions)

    I have the VST3 files on SSD and use a sym link to make them visible in the VST3 folder in common files that works fine. Everything is fine cos the restore was before I tried to transfer Waves\CODEX onto the new computer. Just cleaning up the folders\files before I attempt to install Waves\CODEX again.
     
  6. Goon

    Goon NI Product Owner

    Messages:
    884
    Ensure KK does not try to scan those 32bit folders as well. Remove the scan links that are pointing to 32bit folders in KK
     
  7. stewart hannah

    stewart hannah NI Product Owner

    Messages:
    43
    I finally fixed it after Waves support told me I had to uninstall clean the computer and then reinstall. It has taken me all night !!!! But finally it is now working. As for the x86 folders\files none of the apps I use point to them as I never use x86 given the option I always decline to install them in the first place.

    My Kontrol app only points to the 2 VST folders program Manager\vstplugins where the waveshells are and then to one I created called VST3 64 where I custom locate my x64 plug ins, into their Vendor specific folders. The issue was a bad install of Waves but what the heck, its a silly program anyway I just like CODEX why I have no idea I just do.