NKS Development Discussion

1129130131132133135»

Comments

  • chpiatt
    chpiatt Member Posts: 110 Advisor
    edited February 23

    Yeah, of course it's always a risk using an officially unsupported hack like this, but this is a real bummer for my workflow. Probably going to request a downgrade of my KK version from support if I can't figure it out. I really like having all of the Factory presets (including the ones that originally don't have NKS versions that I create myself or find here) in one tab. I save only sounds that I myself create in the User tab.

    I always could move all of my unofficial Factory presets to my User Content folder and have them show up there, I just don't want to if I don't have to.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,439 mod

    I understand, the real solution would be for NI to make it possible to search both tabs in one go

  • chpiatt
    chpiatt Member Posts: 110 Advisor
    edited February 23
  • chpiatt
    chpiatt Member Posts: 110 Advisor
    edited February 23

    OK, after banging my head against the wall for quite some time today I was finally able to get my precious "Factory" presets back. Don't ask me how or why it worked or even exactly what worked, but after dumping the komplete db a few times I started messing around with the .plist and xml files. Eventually, after modifying my original .plist file to add an InstallDir of Macintosh HD:Library:Audio:Plug-Ins:VST3: and creating a second .plist file that linked to a specific plugin within my NKS Presets directory with values:
    - ContentDir = Macintosh HD:Library:Audio:NKS Presets:Crow Hill:Cosmos:
    - InstallDir = Macintosh HD:Library:Audio:Plug-Ins:VST3:
    - ContentVersion = 1.0.0

    Komplete Kontrol (somewhat inexplicably) started indexing all of my presets as Factory presets again as intended. Crisis averted 😅 Maybe this will help someone. Sorry I can't really explain why it worked, it just did for me. No guarantees!

    .plist files:

  • Diam
    Diam Member Posts: 336 Advisor

    Update from u

    he re: TyrellN6 UI


    Post
     Sat Mar 22, 2025 10:16 am

    So, the current skin was provided by Amazona. We can not maintain it ourselves as its designers have no work relation with us. That's why some errors in it (some wrong labels IIRC) were never fixed.

    We will eventually create a new design for Tyrell N6, because we need to add things over time, e.g. if we manage to add MPE support, if we wanted to add new features, for our efforts to become accessibility compliant.

    Sure, the current skin may look great to some, but it does not fit our design principles. So as we need to eventually do our own design, we'll probably go for something closer to our more recent designs such as Colour Copy or Twangstrom or Filterscape.

    Furthermore, we're moving away from bitmap based UIs to vector based ones as the gap between small screens and 8k monitors widens. Bitmap based UIs are fast becoming CPU draining performance bottlenecks.

  • Diam
    Diam Member Posts: 336 Advisor

    Was meant to say, update from uhe re: Tyrell N6 UI. For some reason this forum crashes my messages mid flow and won't allow me to make edits.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,439 mod

    I just use the free Mona skin from Plugmon that makes it look like the MiniDiva that it is

  • Diam
    Diam Member Posts: 336 Advisor

    I mention as most of the current skins are not updated for the new beta. They work, but there are some minor additions that are not implemented into the existing third party skins. Either way, I will just create some new graphics when this arrives. ;)

  • Diam
    Diam Member Posts: 336 Advisor
    edited March 23

    In last months dev roadmap thread, I saw the following in relation to Kontakt development:

    "We’re also working to make Kontakt integrate with 3rd party hardware from the NKS Hardware Partner program (see above) so owners of those devices will get a seamless workflow and access the thousands of instruments built for the world’s largest virtual instrument platform."

    Makes me wonder if they will extend this integration to Komplete Kontrol mk2 users, as some, if not all of the 3rd party keyboards listed are less capable of this task in a compatibility sense, therefore it would make sense to provide this accessibility to owners of older NI hardware devices also.

Back To Top