Nerdy Komplete Kontrol question: How to create subfolder e.g. for UVI libraries

I've recently completed NKSF mappings for all of my UVI libraries. It's not as elegant or elaborate as some of the incredible setups often shared here in the forum — just a straightforward, manually built mapping for each one.
At the moment, I have a central Falcon folder containing individual, properly named NKSF template files, which I can access without any issues.
Now for the real nerdy part: What I really want is to organize them into separate folders — one folder per library. But here's the catch: No matter how I try to set up folder structures, the NKSF files always end up showing up directly under the Falcon folder, rather than in their designated subfolders.
I'd really appreciate some nerdy advice on how to make this work!
Thanks in advance 😊
Best Answer
-
mac only…
I might look into making the app I have developed for PC available, the bank edioting part at least.
0
Answers
-
Short answer is you can't.
The "folder" (or banks as it is called" info is within the actual file and this is usually non editable.
The way I am able to do it is I developed my own custom tools that extracts the compressed binary data and edits and repackages it back into the NKS file, something that is not straight forward to do. Unless NI open this ability up to users it's not really possible.
If you want to save some time and have full browsable libraries, pretty much every UVI library is pre-mapped and browsable here
1 -
Actually there is a cheap third party tool that can do it (also works for Massive X)
that's what I use
We have been asking NI to open up bank/sub bank creation for years - maybe one day…watch this space :) (first they also need to fix sub bank display in KK3)
In the meantime we have to do it ourselves
0 -
mac only…
I might look into making the app I have developed for PC available, the bank edioting part at least.
0 -
Thanks as usual to you both.
0 -
That would be very cool, thanks
0 -
Hi. I am sure, this has been solved soooo many times. But I am not able to find the information.
Basically - I have done most of my mapping manually. But those found provided by the community have a different, more refined layout.
How does this work? Would I be able to do this myself, or is a hidden trick not open to the public?
thanks/ thom0 -
Refined in what ways? While things like bank naming and scripting NKS conversion require the use of additional tools and techniques like scripting, I think the actual job of doing the mapping is probably done the same way by all of us, using the NKS editing facilities in Komplete Kontrol (and for me I prefer KK 2.9.6 over KK 3 for this job - occasionally I also use Maschine 2).
I guess it just comes down to practice (I also prototype layouts for more complex synths in Bitwig as it has a better controller mapping editor)
0 -
Ok - I was referring to the actual scripting and hence the more refined layout structure. But from what I am gathering, that sounds a bit like a task. Than - maybe not. LOL Thanks anyway :-)
0 -
Can take a LOT of time and knowledge in making libraries, not just technical but also in how best to lay things out and in cases such as mine, I actually deal direct with a lot of developers for more technical info and suggestions on layouts as well as loads of feedback from users including visually impaired which have more of a sense of logical layout than most.
There is no simple way to script all plugins, some you can read XML/FXP/SQL data direct, some you can extract info from the plugins GUI and some are just too complex and need manual intervention. UVI is one of the more complex ones to make NKS for because as a start you have to host enable all the parameters to use via right-click context menu, sometimes this is completely lost between switching presets. There is no "next preset" button so it takes some sophisticated scripting, it's close to one of the more complex ones I develop libraries for and then there is the whole Falcon/Workstation part to manage if you want a library to open in both.
I have developed my own tools and methods over the last 10 years to design layouts so they come out in a uniform way trying to stick close to the original way NKS was designed but also expanding especially the control section to be more usable for people that cannot visually see a plugins interface which is not just simply cramming all controls into 40 pages, sometimes things need to be left out while other things have to be included to make it useful and each individual has their own ideas on how that should go. One complaint I often hear is most official NKS libraries are just too basic to be of any use to most blind users so that is always a key aspect.
It can consume huge amounts of time to just do some of the basics, a reason you just don't see NKS more widely integrated because it is a lot of extra work no matter how it is done. There are a few users figuring things out, but most just want to make music not ness around managing libraries, that is what those of us do who don't make music anymore and just collect plugins…
0 -
Thanks. That does not sound like I will go down that road
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 67 NI News
- 881 Tech Talks
- 4.5K Native Access
- 17.5K Komplete
- 2.2K Komplete General
- 4.7K Komplete Kontrol
- 6.2K Kontakt
- 1.1K Reaktor
- 404 Battery 4
- 906 Guitar Rig & FX
- 459 Massive X & Synths
- 1.5K Other Software & Hardware
- 6.3K Maschine
- 8K Traktor
- 8K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators