Tip - Disabling unwanted plugin pages

With some plugins you get some really useless plugin pages in Kore 2, with hard to read parameter names and of course not sorted in any way, and especially with plugins with a large list auf automation IDs, I didn't wanted these to use up even more of the automation IDs, which I already created with some userpages.

So here is a pretty simple solution to this:
Just put the attached ndp.-file in your "Kore Controller" Folder

(Mac: "Mac HD/Library/Application Support/
Native Instruments/Shared Content/Controller Pages/Kore Controller/"
PC: "C:/Program Files/Common Files/
Native Instruments/Shared Content/Controller Pages/Kore Controller/"

or create a "Kore Controller" Folder under

Mac: ".../username/Documents/
Native Instruments/Shared Content/Controller Pages/"
PC: ".../Documents and Settings/username/My Documents/
Native Instruments/Shared Content/Controller Pages/" )

and RENAME it to the name of the plugin
(for example to Fabfilter Twin 2.ndp) !

The next time you load the plugin in Kore, you've get rid of the
automatically assigned plugin pages by Kore.

Hint: This does only work, BEFORE importing or saving the plugin presets as Kore sounds, otherwise the plugin pages have been saved as a part of the kore sounds !

Hope, It's of some use to you
Cheers

 

That's why you can rearrange your user pages in the sound manager- so the automation IDs are in the order you want them.

ew

 

Right, but I ain't talking about user pages, but about getting rid of the plugin pages, those you see, if you click on the button "Plugin" in the Controller View.
Except for plug-ins, which have predefined
controller pages (like Massive, for example, with parameters sorted by groups), I'm finding them pretty useless with 3th party
plugins, for which Kore doesn't include a controller page.

Would be nice, if one could get rid of them via the sound manager, though, or even better, to create some own custom plug-in pages (like those found in Massive).
It's possible by using an editor, modifying or creating a ndp.-file
(in fact a plain simple XML-file), why not via an internal function
inside the sound manager ?
Imho the functionality of the sound manager is pretty limited as it is now and could be vastly improved