Syncing plug-in cache ...

Nothing changed after deleting Plugins.xml and koredb. Standalone Kore Player freezes and cubase crashes.

 

Hi arnekr and robojam,

as it seems the plugin scan of the integrated sound engines fails on your computer. In order to verify that this is the cause of the freeze it would be great if you could try out the following as a test:

Locate the following folder on your hard disc:

C:\Program Files\Common Files\Native Instruments\Kore Player\PlugIns

and rename the Plugins folder to something else (e.g. "Plugins1")

Restart and let me know if Kore Player starts then.

You should be able to "load" the KoreSounds now, but they are not really loaded and you will not hear anything.

Rename the Plugins folder again to its original name and try again if Kore Player freezes again.

If Kore Player will not start when the Plugins folder has a different name, there must be another problem involved which has actually nothing to do with the integrated engines.

 

yes, that's it. Without finding the plugins directory, it starts and asks me to activate.
---
...and after re-renaming it freezes again

 

Hi,

OK, can you first delete the following file then (it is also located in the Plugins folder):

BuildInEnginesPlugListTemplate.xml

This is just for speeding up the startup process for the very first time starting Kore Player. If this does not help, you can also try to remove all plugins from this folder and put them back one by one, if only one of these plugins causes the trouble.

If somehow this also not work, I would need the following information for each single plugin file in this folder:

- Exact size in bits

- File version (right click/Properties/Version tab)

Thanks a lot for helping to evaluate the reason for this problem!

 

Hi Marius,

there are three files that cause trouble:

Absynth4.dll 35.463.243 Bytes ver. 4.0.5.3
FM8.dll 35.450.880 Bytes ver. 1.0.3.3
Massive.dll 50.397.184 Bytes ver. 1.1.3.1

If any of them is in the Plugins folder, kore player freezes at startup.

Thanks for your help

 

Did you have demos of those plugins on your machine, perhaps? I could see that happening if you had demos of those plugins and the uninstaller left behind some items...

ew

 

No other versions of it installed. I scanned the whole harddisks. But i found a folder 'C:\Dokumente und Einstellungen\kronberger\Eigene Dateien\Native Instruments\Shared Content\Sounds' (it's the german version of 'My Documents') with exactly and nothing more than three empty subfolders called Absynth 4, FM8 and Massive.
Does that mean something?

Arne

 

That's where user content goes for those three apps. However, as far as I know, the player shouldn't be creating user content folders...

ew

 

I'm getting pretty much the same results, only I have no problem with the Absynth plug-in, yet I have problems with the Kontakt plug-in.

I don't have any of those folders that arnekr has though.

It runs fine if I remove a few plug-ins from the plug-ins folder, but won't start with them in place.

 

Maybe one difference between our installations is, that i installed the vst plug-in version, too. That could be the reason for different folders, couldn't it?

 

Absolutely not. Besides which, if I remember, robojam's got the plugin version installed, too...

There's only three reasons I can think of why you'd have those folders:

1) you have (or have had) the full version of those plugins installed
2) you have (or have had) the demo versions installed
3) you have (or have had) shall we say "not quite legal" versions installed.

ew

 

I installed standalone and VST too.
---

I had demo versions of programs installed before, but they were older than the current version, and I think I installed just about every demo at one point, but only some of these plugs are causing a problem.

For example, I'm pretty sure I had the demo of FM7, but the FM8 plug-in seems to be causing me a problem here.

 

It could definitely be remnants of the demos that are causing the problem; the only activation issue I've ever had with NI products were caused by remnants of a previous install, and the player could see those remnants as belonging to unauthorized versions of those plugins, or be confusing the plugin versions because of that.

Do you own any NI products? If not, I'd be tempted to uninstall the Kore player and do a search and destroy through my system for anything NI related (including hidden files and folders and the registry) if I were you. Then, I'd reinstall.

ew

 

I managed to activate it OK - that was a problem with the site that I got round by using Firefox.

It's just this plug-in folder that's the problem now. I already deleted everything I could find in the registry between installs a couple of days ago, so I'm not sure I have anything around anymore.

 

i have not and had not installed any other versions of ni products on this machine.

 

OK...well I managed to make some progress. I seached the registry again, but this time I searched by product rather than 'native instruments' and found a few more values. Looks like all of the plug-ins are fine now except for kontakt.

Maybe there are some kontakt entries in the registry using names other than kontakt. Any ideas?

 

OK, just one plug-in that doesn't work now - kontakt 3.dll. Any ideas?

 

OK, been doing some investigation. There are 3 Kontakt plugins that I can see, and only kontakt 3.dll seems to cause the problem. However, Pluglist.xml seems to have some odd entries for the other 2 Kontakt plug-ins. The company name for them seems to be 'crap' instead of 'Native Instruments'. Any idea why the file would be generated with that value set?

 

Anyone?

 

Hi arnekr,

- could you also check if you just get the freeze only when all of the three problematic plugins are located in the Plugins folder. Try to let always only one of these three plugins inside the Plugins folder. Let me know if it works then or not.

- you should also export the following two registry keys and send these to technical support:

HKEY_CURRENT_USER\Software\Native Instruments

HKEY_LOCAL_MACHINE\SOFTWARE\Native Instruments

- to do this open the registry editor (Windows start button/Run../Enter "regedit"), right click the key (yellow folder) and coose "Export" from the context menu.

Please put the link to this thread to your email and add my name so that the support agent who reads this, can assign this case to me.