Reaper won't recognize Kontakt 7.10.5 - it loads 7.6.1

Wittmann
Wittmann Member Posts: 4 Newcomer
edited October 22 in Kontakt

At my wits end here. I've installed the latest version of Reaper, latest version of Native Access, and updated Kontakt 7 to the most recent version (7.10.5), but when I load up the Kontakt 7 VST in Reaper, it loads version 7.6.1 (and therefore won't let me load Hybrid Keys). I played around with file install locations and VST paths in Reaper's preferences, but cannot for the life of me have the VST version recognized as 7.10.5.

Anyone know what's going on?

Thanks!

Tagged:

Best Answer

  • Vocalpoint
    Vocalpoint Member Posts: 2,280 Expert
    edited June 22 Answer ✓

    Thanks for the update.

    First and most importantly - in Windows - VST3 plugins have a universal (and dedicated) location which is:

    C:\Program Files\Common Files\VST3

    This location is managed by the OS, and is used by all plugin vendors as a standard location.

    Native Access also uses this standard location - in fact it is so standard that you cannot even see this location in File Management. Here is my layout:

    Notice the VST3 location is not present.

    Yet - NA - installs ALL VST3 plugins to this standard location.

    Also - you mentioned:

    (C:\users\_____\Documents\VST Bank). I save any VST files I have to this location. Native Access is set to install to this location (all applications/content/32 and 64 bit VSTs)"

    This location ONLY covers VST2 plugins (both 32 and 64 bit).

    While you may have Native Access set to install to this location - it will not matter for Kontakt 7 as there is no such thing as a VST2 version of K7.

    Sounds to me like Reaper is NOT scanning the standard Windows VST3 directory mentioned above and if it is not - you are never going to see any VST3 plugs at all. Kontakt and everything else.

    Finally - here are the actual file specs on the Kontakt 7.10.5 VST3 file installed to my standard Windows VST3 location (2):

    Locate your Kontakt VST 3 and compared sizes, dates etc.

    Might be a good idea to review exactly why you are installing your plugins in non-standard locations and maybe consider trying some industry standard locations like I have listed in my NA dialog above and set those in Reaper for the go-forward.

    VP

Answers

  • Vocalpoint
    Vocalpoint Member Posts: 2,280 Expert
    edited June 22

    Questions:

    1. What is your OS?
    2. Where exactly is Reaper scanning for VSTs? vs where Native Access is installing VSTs (seen under File Management under Preferences in Native Access)
    3. How are you confirming you have Kontakt v7.10.5 (vs v7.6.1)
    4. Are you loading/using VST2 or VST3 in Reaper?

    VP

  • Wittmann
    Wittmann Member Posts: 4 Newcomer
    1. Windows 11
    2. I have one location set for Reaper to scan for VST's (C:\users\_____\Documents\VST Bank). I save any VST files I have to this location. Native Access is set to install to this location (all applications/content/32 and 64 bit VSTs).
    3. When I open the standalone Kontakt 7 and click the NI icon in the top right, it says 7.10.5 - when I do the same in Reaper is gives me 7.6.1.
    4. VST3 in Reaper.

  • Vocalpoint
    Vocalpoint Member Posts: 2,280 Expert
    edited June 22 Answer ✓

    Thanks for the update.

    First and most importantly - in Windows - VST3 plugins have a universal (and dedicated) location which is:

    C:\Program Files\Common Files\VST3

    This location is managed by the OS, and is used by all plugin vendors as a standard location.

    Native Access also uses this standard location - in fact it is so standard that you cannot even see this location in File Management. Here is my layout:

    Notice the VST3 location is not present.

    Yet - NA - installs ALL VST3 plugins to this standard location.

    Also - you mentioned:

    (C:\users\_____\Documents\VST Bank). I save any VST files I have to this location. Native Access is set to install to this location (all applications/content/32 and 64 bit VSTs)"

    This location ONLY covers VST2 plugins (both 32 and 64 bit).

    While you may have Native Access set to install to this location - it will not matter for Kontakt 7 as there is no such thing as a VST2 version of K7.

    Sounds to me like Reaper is NOT scanning the standard Windows VST3 directory mentioned above and if it is not - you are never going to see any VST3 plugs at all. Kontakt and everything else.

    Finally - here are the actual file specs on the Kontakt 7.10.5 VST3 file installed to my standard Windows VST3 location (2):

    Locate your Kontakt VST 3 and compared sizes, dates etc.

    Might be a good idea to review exactly why you are installing your plugins in non-standard locations and maybe consider trying some industry standard locations like I have listed in my NA dialog above and set those in Reaper for the go-forward.

    VP

  • Wittmann
    Wittmann Member Posts: 4 Newcomer

    Holy cow - very thorough response. Thank you!

    Primary reason for my non-standard approach to file management was: a) lack of understanding that there was a standard, and b) it felt like I had VST's everywhere on my hard drive and wanted to consolidate. Seems like this wasn't the best approach.

    I'll try out the things you've noted and see how it works. Thanks again.

  • Wittmann
    Wittmann Member Posts: 4 Newcomer

    Leaving a last comment that resting to using the proper/default install paths solved my problem.

This discussion has been closed.
Back To Top