Komplete Kontrol – Lost preset assignments in old projects after update (DAW FL studio)

Gibbéguionie

Hello,

I'm reaching out to report a critical issue I'm experiencing with Komplete Kontrol, which started occurring after a major update (likely within the past six months).

I work with the latest version of FL Studio and regularly use Komplete Kontrol in my music production projects.Since this update, all of my older projects have lost their Komplete Kontrol instrument assignments.The plugin loads, but no preset is recalled — and I can't even retrieve the name of the instrument or preset that was originally used.

This is a serious problem for me, as it results in the complete loss of the sonic identity of my tracks. Some presets were very specific, and I’m no longer able to reassign them by ear.I’ve tried inspecting the .flp files for metadata or preset identifiers, but without success.

All my software is fully up to date: Komplete Kontrol, Kontakt, Native Access, etc.I'm running Windows 10, and all my libraries are installed on my main SSD drive.

My main question:Is there any way to recover the preset name used in each instance of Komplete Kontrol in these older projects?If not, is there any technical method or tool that could analyze project files and extract this information?I’m also willing to share a .flp file if that can help with the investigation.

Thank you in advance for your help.

JesterMgee

The issue could be related to VST2 instances of plugins in older projects, however it could also be just tyhe V3 doing the terrible things it does best…

First question, are you using an MK3 keyboard? If not then it may save your sanity to simply uninstall KK V3 and go back and install the previous v2.9 which I believe you can now access via your NI web account download area.

Do you happen to recall in at least one project what plugin is missing? I do not use FL but in other daws I will typically name the track or add a note on the track the instance of the plugin and also the preset for this exact reason, not always to do with KK but as someone who owns literally a thousand plugins,. some of which maybe used once it can be a pain when you do not know what was used on a track so I learned from old DAWs that never told you what was missing to always record a note about it.

If you have reinstalled your OS at any point over the years maybe a plugin or 2 were not installed or maybe you have not set the path to all your VST2 locations. I know some people use to just click "next" when installing VST plugins and they end up all over your HDD so maybe the ones in question are not scanned into your KK software.

The old KK before v2.9 did not save the info of the plugin name at all, it only saved the "Plugin ID" which means nothing to a human but from what I have seen in the NKS code the vendor and the plugin name are now saved (after we complained for ye3ars about this exact issue) so maybe new instances "can" report what plugin is missing, however every support thread I have seen always suggests KK just loads blank without any hint of what plugin is missing. In any case, the actual preset name is likely not stored at all since when you save a VST plugin instance the DAW simply requests a plugin snapshot which is just the state of the plugin. Some plugins (usually ones that are sample library based) will dump info about the preset / library used in the plugin state and some are binary dumps that have no readable info. Issue is tho, this info will be embedded in your FL project file which itself is likely a binary format so it's not a simple case of just looking within it and finding the answers.

First what I would do for one project is rack your brain for the plugin that it should be loading then start investigating if you have both the VST3 and VST2 versions installed and available in KK. Once the plugin is available and can be loaded the preset should load fine.