NKS User Library
Comments
-
Aberrant DSP Digitalis - a rather fun and unique FSU/Bitcrush/Distortion/Spectral Filtering Effect - all presets converted to NKS and tagged etc
2 -
This is a first draft - not done graphics/database files yet and I have tried to keep this to a reasonable level of comprehensiveness vs usability so it includes some of the mods but not all
https://www.dropbox.com/s/79uzcd77ngbun16/FabFilter%20Twin%203%20VST3%20template.zip?dl=0
0 -
Whats with the VSTs that migrate as far as sound, but don't recall the preset names? Seems to be an issue among different plugins. Also sometimes the same plugin recalls names for some banks but not others.
0 -
It seems to me there is a lot of variation in how plugins save patches across plugin types. Natively VST2 and VST3 plugins don’t even have the same patch file type (fxp vs vstpreset) but it seems even in plugins using proprietary file types sometimes VST3 plugins seem to use different approaches to patch recall to their VST2 equivalents. Thankfully in those cases KK/Mas seem to actually manage to still recall the preset / plugin state itself pretty well, but the patch name, or automated params get lost.
This isn’t just a migration issue though, I have several plugins where the original preset name saved with the NKS patch is not being recalled properly by the plugin (SPC Arcsyn is a good example). Sometimes you just have to ignore that and go by the NKS name
0 -
The issue is not a KK/NKS issue, it is how plugins manage the data and presets, which is hugely varied as Kymeia said.
When you save a NKS file (or a DAW project) a request is made to the plugin for its "PluginState" which is a full dump of every parameter and setting of the plugin. This is basically the equivalent as a "cue sheet" in a studio from decades ago where maps of all gear and the dial positions/settings were hard written into a master document for a project and would have to be reset when setting up the project again.
Sometimes the preset name is dumped into the capture but sometimes not so when you load a preset, if there was no preset name dumped it cannot display it and just loads the state of the plugin.
In some cases (like some Korg Plugins such as Monopoly, PolySix) instead of the preset name, they appear to use some kind of "preset table position" such as "bank 2, preset 15". Big issue with this is the way the table seems to work is if you add just 1 extra preset into the plugins browser (by a preset pack or a user saved preset) it throws all of this data out of whack and now you have NKS files loading the correct sound, but the name off the preset displayed showing is completely wrong and differs between users. It's pretty poor programming and something I reported and even had confirmed by Korg 2 years ago but they are top of my list for most useless support since after it was confirmed to me they ignored every email I sent asking if this would be fixed so don't hope on that ever being fixed
So basically, it's just how it is with some plugins.
1 -
Thanks - done :)
Can't be because Preset Magician is a Windows app - I did it on my old laptop (which admittedly runs a very modded Windows 7 so that could be the cause)
0 -
Windows 7? ...so, definitely it is not Preset Magician the problem, but the Windows 7! Which were good 12 years ago but a total ****** for today. You should update to Windows 10, i think it is still free.
0 -
Updated template and library for Audiodamage Phosphor 3 VST3 - resaved and tagged all presets and made previews
Works nicely in Komplete Kontrol but is very flaky in Maschine at the moment - hopefully will get a fix but AD are a bit slow
0 -
I've been updating and fixing all the Unfiltered Audio plugins that were in the NKS User Library and also those that Plugin Alliance/Unfiltered Audio provide factory NKS for, as in all cases the VST3 NKS versions were badly broken with no params working. First up is LION - I also took the opportunity to improve on the original mapping by PA because it sucked.
I have not added graphics or database files for this as they already come with the plugin. You have the choice to install these into the User section of Komplete Kontrol (which is why I have included the previews still) or the factory section - but be aware that the risk of installing them or anything in the factory section is if you update the plugin it could result in those files being over written by the installer so keep a backup. See the 'read first' text file for where to put them if you want to do that.
To come: TRIAD, BYOME, ZIP, SpecOps, Sandman Pro, Fault and Dent 2 - I aim also to do Silo and LO-FI-AF but that's another project
1 -
Now TRIAD - same as with LION this is one that comes with its own factory NKS files but they no longer work with the VST3, so this doesn't come with graphics etc as there is no need. Sorry the mapping for this (and even more, BYOME) is so limited but unfortunately PA have seen fit only to create automation targets for a few parts of the interface, which is pathetic but I have managed to map everything that is available to map at least.
0 -
BYOME - also one that comes with NKS factory presets already but broken with the VST3 (btw with all of these if you are fine with the VST2 I would carry on using that, these are just for pole wanting to use the VST3 or who have no choice if they are on Mac and want to be Silicon native)
1 -
Here is SpecOps - this is a factory NKS one too (broken in VST3) but I had already created a template for it well before PA decided to make it NKS compatible and my template is more comprehensive so I used that but rebuilt with the VST3
1 -
Last of the PA/UA NKS factory ones is UA ZIP - which is a bit different from the others as it's more of a mixing/mastering plugin (so probably of less value in Komplete Kontrol but maybe in Maschine? tbh not one I use a great deal but I got it in a bundle)
1 -
This one is a complete NKS conversion for UA Sandman Pro - no idea why they have made some of their plugins 'NKS ready' and some not but this is one of the 'nots' :) So this also comes with graphics and database files and needs to be in the User Content section
Original factory bank for the VST2 was generated I think by Plopseaw from the old forum but now all updated with a newly made VST3 template by myself
2 -
Here is one for UA fault
Original factory bank for the VST2 generated by Plopseaw but now updated to VST3
1
Categories
- All Categories
- 18 Welcome
- 998 Hangout
- 56 NI News
- 497 Tech Talks
- 2.7K Native Access
- 12K Komplete
- 1.4K Komplete General
- 3.1K Komplete Kontrol
- 4.1K Kontakt
- 1.4K Reaktor
- 307 Battery 4
- 641 Guitar Rig & FX
- 332 Massive X & Synths
- 808 Other Software & Hardware
- 4.2K Maschine
- 4.9K Traktor
- 4.9K 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