NKS compatible "Spitfire Audio Plugins" no longer shown in "Komplete Kontrol 3.0"

Options
12346

Comments

  • Kymeia
    Kymeia NKS User Library Mod Posts: 3,967 mod
    edited January 21
    Options

    btw I see no difference between BBC Symphony Orchestra (Free) behaviour in KK2.9 (VST2) and KK 3.1 (VST3) - I have both on my system and the expanded view opens in both using the clickable arrows in the top right of the GUI, and in neither do I see any additional controls in Komplete Kontrol - not in the view menu nor a plus in the header (which NI use to expand their own plugins). Maybe this is only a problem with the more advanced versions?

    From reading the manual I see you can also set Expanded view to open in all instances of all Spitfire plugins (that use their own plugin) in options

  • ZenBen
    ZenBen Member Posts: 6 Member
    Options

    In my case, like others, with Komplete Kontrol 3.1.1, when using the "Spitfire" brand tab, I am still not seeing:

    Abbey Road One, Abbey Road Two, BBC Symphony Orchestra Pro, Eric Whitacre Choir, Eric Whitacre EVO Grid, Hammers, HZ Strings, Orbis, Cimbalom, Acoustic Soft Piano, Firewood Piano, Rare Flutes, Polairs.


    What they all have in common is that they are all spitfire players that do not use Kontakt.

    FWIW, I am using Sonoma on a Mac Studio M2, though I also had this issue when using Ventura and KK 3.01 a few months ago.

    My solution has been that I created a Keyboard Maestro shortcut that types in the word "Spitfire" in the search bar in Komplete Kontrol and that then shows every library associated with Spitfire, whereas clicking on the brand-tab for search does not.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 3,967 mod
    Options

    Wonder why the BBC Symphony Orchestra free version appears under the brand tab when the full version doesn’t?

  • MyStudioOne
    MyStudioOne Member Posts: 264 Pro
    edited January 31
    Options

    BBCSO only shows as 1 thumbnail because the Spitfire plugin MODE button allows you to freely swap between Discover, Core and pro from within the plugin (depending on your licence of course). If you own PRO, you get access to Core and Discover automatically. Many users use Discover to start a piece (light on resources) and then switch up to Core when the want ALL the articulations and PRO is mainly addition of a million mic position options.

    If I recall correctly, my Discover thumbnail didn't update from the white skin to the Pro black skin when I updated to Pro. It only updated later when I deleted the database and did a fresh rescan.


  • jottweh
    jottweh Member Posts: 34 Member
    Options
  • Azu
    Azu Member Posts: 3 Newcomer
    Options

    Hi all,

    Is anyone else not having Lightguide in Komplete Kontrol with BBCSO?

    Thanks!

  • Danix78
    Danix78 Member Posts: 32 Member
    edited March 26
    Options

    Yes, here too the lightguides no longer respond on BBCSO Core.

    I only installed Core but the Presets are shown as Discover (???).

    Loading a Discover Preset makes the Lightguides work but I have to manually switch to Core by selecting a Preset, even the same one.

    If I switch to Core (manually) I lose the lightguides.

    All this makes KK useless.

    KK 3.2.1 - Windows 11

  • chpiatt
    chpiatt Member Posts: 41 Member
    edited May 30
    Options

    If you have just the native Spitfire plugins installed, they will show up under the brand 'Spitfire Audio' no problem. Likewise, if you have just the Kontakt Spitfire instruments installed those will show up under the 'Spitfire Audio' brand (with some exceptions I've found like Chamber Strings essentials that show up under 'Native Instruments' brand).

    The main issue comes when you have both Spitfire native plugins and Spitfire Kontakt instruments installed. In this case, from my experience, the native plugins will not show up under the 'Spitfire Audio' brand - just the Kontakt instruments.

    In addition, some presets just don't load at all for me. Albion Colossus just gives me the dreaded VST2 to VST3 migration error. @Matthew_NI

  • chpiatt
    chpiatt Member Posts: 41 Member
    edited June 2
    Options

    My short-term solution was to use https://denivel.blogspot.com/2023/12/nimbank-tool-update-v53.html to rename the vendor to 'Spitfire' instead of 'Spitfire Audio' for the native plugins and now I at least have a tab where I can see all of the native plugins. It's not ideal because what I want is to just have one tab where I can see all Spitfire Audio content in KK.

    Spitfire developers are obviously doing a bad job at maintaining their NKS presets, but I think this particular issue with the clashing of namespaces for Kontakt vs native plugins with the same vendor name is most likely on the Native Instruments side to fix

  • spicemix
    spicemix Member Posts: 67 Member
    Options

    When I asked Spitfire said there's some kind of update to the VST format they are waiting Steinberg to finish and then they will update everything at once. It is disappointing that they let this go so long, who knows if the Steinberg thing is real, maybe just getting me to go away, but this at least is a strand of hope for those of us with Spitfire player things.

    Spitfire is also working on a new Labs Plus thing that offers a paid subscription for fancier things like the Originals but no keyswitching at least so far in the previews they've shown. Maybe that new plugin will support NKS or maybe they will just give up on NKS for their non-Kontakt products, would be sad.

  • chpiatt
    chpiatt Member Posts: 41 Member
    edited June 10
    Options

    Pretty sure this is bogus. Seems like they are on the path towards deprecating NKS support just like Orchestral Tools, Cinesamples, Softube, etc. Honestly, I blame Native Instruments though. It should be a no-brainer for these companies to support NKS, but everything I hear about the development process is that it is overly complex/expensive and that Native Instruments is extremely slow at approving official NKS partner plugins.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 3,967 mod
    Options

    In the case of Softube all they need to do is add support for migration, I’ve been in touch with their support for many months over this, they acknowledge the problem but are just very slow at updating their plugins. I even made fixes myself for the FX I own and Heartbeat by saving them with new templates for the VST3, it isn’t hard, just time consuming.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 3,967 mod
    edited June 12
    Options

    For the Kontakt libraries afaik NI have made it easier to add NKS2 support as it’s part of K7’s development tools so if anything I’d expect to see more Kontakt products with NKS2 support, Spitfire unfortunately seem more like Softube and slow to address issues with existing products, preferring to churn out new ones

  • Keith Cocker
    Keith Cocker Member Posts: 125 Advisor
    Options

    I agree. Spitfire make superb libraries but are extremely poor at keeping them updated let alone dealing with bugs. Many Spitfire libraries were sold as NKS compatible and they are just not compatible now. This has been dragging on for quite some time now.

  • MyStudioOne
    MyStudioOne Member Posts: 264 Pro
    Options

    If I had to predict the future, I would guess that the plugin/library software industry will continue to become more fragmented. As I delve outside of NI's ecosystem, I am realizing more and more that there is so many options from developers who have their own players which are worth taking a look at. The Opus plugin player blew me away in terms of functionality/options. Others like Musio give access to entire catalogs without the need for 2tb of library storage by allowing you to load what you need whenever you need it. Well priced too.

    My point is, that I feel like Spitfire seems more focused on doing their own thing. It is no coincidence that all the new libraries are not Kontakt supported. All the bigger companies with their own players are moving away from Kontakt to varying degrees.

    So I find it ironic that Komplete Kontrol is the glue that is keeping Native Instruments in the game and I use KK a lot.

    But NI is taking a big gamble by tinkering under the hood to the point where developers need to do a ****** ton of work to keep all the legacy NKS libraries working in Kontakt in the way end users have come to expect. And I think what we are seeing is that many of them don't consider it to be high priority any more.

    I am heavily invested in Spitfire libraries and were it not for KK's preview feature and the MK2 light guide for Orchestral libraries in particular, I would simply use the standalone Spitfire player.

    I have found spitfire to be glitchy in many ways in KK 3.x. It always seems like something is buggy which is increasingly frustrating to me. And all we ever see is finger pointing and little changes over time.

Back To Top