Plugins that Kore knows about

So I fire up Phoscyon in Kore, right... I'm like, ok, let's make a cool templa- wait, what? EA1? EA2? What sort of shenanigans are these? Where do these mappings even come from, there was no previous entry for it in the database cache or anywhere before I installed it, so Kore must be programmed to make these user pages when it sees the instrument at first...

Know of any other plugins from that period which Kore can recognize, out of curiosity?

 

Maybe you've got the Plugin pages open, not the User pages.

 

nah, the Plugin pages are removed, it's all tidy and ready to go, just like the NI synths - I'm like

conversation inside my Kore right now...
-Hey omg lol Phoscyon what's up old buddy
-I was just chilling on the kvr marketplace for a while, just got bailed... Holy crap haha am I in a Kore? wow, I bet I'll make some sick lines in here
-Hell yeah, can't believe it bro. Here, I kept your mappings handy!
-Dude, no way!!
*a gnarly acid jam ensues*

 

I'm not sure we're "on the same page"
The Plugin pages appear when the "plugin" button is red. On the Plugin pages the available host automation parameters are mapped automatically, using the names that the plugin uses for host automation parameters. They are not always convenient, you're lucky if they're tidy and ready to go
On the User pages you can map them the way you want.

 

right, normally there are the 8 plugin pages, but here there are none, only the two EA user pages.
I know it's hard to believe, but I'm not joking around bro, Kore is serious business for me

I'll have to make a new template anyway because some parameters changed places when they updated the plugin in the many years that have passed since. still, pretty cool. I wonder if there are others.

 

We were on the same page! That's cool

 

Yeah Kore always came with a bunch of pre programmed mappings for various most commonly used plugins so it could auto map to them out of the box (it did this better than Komplete Kontrol does) - other examples include Korg legacy collection and NIs own synths such as Massive. They are not stored as ksd files though and not in the database - instead they are stored in a different format (ndp) in the controllers sub folder. These were not intended to be user editable which is a shame because unlike ksd they are not patch specific which has some advantages. However you can open and edit them as xml, I rewrote the one for Massive (and posted it here) because the NI one had the macros spread over 2 EA pages (EA just means easy edit pages, they are not full mappings) which was dumb, I put the macros all on the first page and use that for all my Kore Massive patches. So if you're feeling adventurous you could try editing the Phosycon ndp to make it work again, it should just be a case of copy pasting sections around and changing a few numbers to fit the new layout better.

 

Lol, after all these years still stuff I don't know about Kore xD

 

Me too - it's such a deep app

Anyway here's where I posted the Massive ndp - you can use this as an example of how they are setup, just open it in any xml editor (or even a decent text editor like Atom)

https://www.native-instruments.com/forum/threads/kore-patches.36357/page-23#post-1100754

 

Interesting. Hmm. Search isn't finding any .ndp files on my system. Can't seem to find the folder where it goes. Did you mean the Controller Pages folders in the Shared Content locations? Those are all empty for me...

 

Yes the controller pages folder, I think there are 2, you want the factory location not user I think. At least one of them can't be empty or Phosycon wouldn't have one by default.

 

ah, found it. weird that search wouldn't see them. the mystery is solved.
there's quite a lot of stuff in there, wow. it reminds me that I wish I had vokator and spektral delay, missed out on that.
seems like they made some effort at least for Kore to be welcoming towards plugins, but I bet many people dismissed its potential for serious control after seeing these rather minimalistic EA pages.