Dorico 3 Elements doesn't recognize Kontakt 5 or 6

See above. File too large to attach with the crashes folder included. :frowning:

Another thought, is that Kontakt.dll the real file, or is it maybe only a symbolic link? Our scanner has problems following symbolic links.

It is the real file, not a symlink.

And just the crashes folder zipped up is also too large?

Ah, no. That was just me being dumb. :slight_smile:

I have attached the report with only the crashes folder in it.
Dorico Diagnostics.zip (1.42 MB)

Ah, thanks. The crash is from the audio engine, but it has nothing to do with Kontakt getting blacklisted. I’m still don’t know what to suggest further. I guess I need a good night sleep over it…

I had another look at the XML files and noticed something. The VST2 Search Paths shows as first and last path
C:\Program Files\Steinberg\Vstplugins
C:\Program Files\Steinberg\VSTPlugins\Native Instruments

Is maybe a double scanning an issue? I’m just speculating. Already with the first search path every subfolder in Vstplugins shall get scanned. Then the last path points to one of the already scanned subfolders. Could be that the scanner gets confused by that. Could you try with taking out the last search path? (And also delete the blacklist again)

Coming back to what I just wrote before, can you please check in C:\Program Files\Steinberg, is there really only one folder VSTPlugins or is there a second one Vstplugins? Normally Windows would treat both names same but maybe that’s different on your machine…

I tried removing the C:\Program Files\Steinberg\VSTPlugins\Native Instruments from the VST2 search path and restarting Dorico. No luck with that, unfortunately. Also, there is only a single VSTPlugins folder present.

As mentioned in an earlier post, the weird thing is that Cubase 10.5 actually also blacklists Kontakt 6 (Kontakt.dll), but here adding it to the whitelist solves the issue. This does nothing for Dorico, unfortunately.

I will need to discuss this tomorrow with the guy who wrote the vstscanner. And will also get a trial installation of Kontakt 6 and see how that behaves with me. I’ll be back…

I have not experienced a difficulty using Kontakt 6; I did note that the new version merely appears as “Kontakt” without a number (and thus overwrote the subsequently superfluous Kontakt Player) which may cause some confusion.

[Attachment deleted by the admin because it showed the serial number of Kontakt]

I’ve not had a chance to talk to Mr Vstscanner as he is not in today, but I just installed Kontakt 6 Player to my laptop and had no issue at all with getting it going. Just installed via Native Access, then set the path to Kontakt and it was immediately recognized by both, Dorico and Cubase.

Jesper, what exact version of Dorico and Cubase do you have?

Found on the Native website following page: https://support.native-instruments.com/hc/en-us/community/posts/360006981157-Cubase-elements-10-Blacklists-Kontakt-and-Komplete-Kontrol-en-us-
What if you follow those instructions, do you at least get it to work with Cubase again?

In the user whitelist, just put the name of the VST (+ carriage returrn) withtout the path. It work !
Ex : Komplete Kontrol

I’m on Mac OS.
MacOs : Mojave 10.14.6

Dorico Pro 3 : 3.0.10.1051 (Oct 7 2019)
VSTAudioEngine3 : 3.0.10.132

Komplete 12
Komplete Kontrol : 2.2.1
Kontakt : 6.2.1
Kontakt 5 : 5.8.1
ScreenShotDorico.png

As mentioned earlier, I have already tried adding Kontakt to the whitelist - both via the text file and directly by copying information from the blacklist XML to the whitelist XML. No luck with that, unfortunately. As mentioned earlier, it does help in Cubase, where Kontakt is also blacklisted otherwise. Same procedure just seems to do nothing at all in Dorico, which is strange

Thing is, getting Kontakt to work in Cubase is not an issue for me, it is explicitly in Dorico that it does not seem to want to work. Odd.

But also in Cubase, Kontakt shall normally not get blacklisted. Neither should there be the need to explicitly whitelist it.
And once you have it properly working in Cubase, then it should be also no issue in Dorico.

That’s why we ask you to follow the instructions as given by the Native Instruments support, though it might be tedious to do so.

Also Mr Vstscanner thinks that your Kontakt installation is corrupted in some way.
And it is not a general problem, as you heard, there are so many other people with Kontakt installations without any issue.

Sorry, I did not mean to come across as annoyed, just wanted to clarify earlier steps. Written language is such an inadequate form of communication, even with the addition of emojis. :smiley:

I had some projects I needed to finalize first so, but I have now tried following the steps in the page you listed above (adding the step of also clearing the relevant folders in the VSTAudioEngine3_64 folder). Unfortunately, that did not help, Kontakt.dll remains blacklisted (and ‘un-whitelistable’) in Dorico, while whitelistning it in Cubase works in that application.

Thanks for all the help with this. I realize it is not a widespread, general problem. Not sure what is going on with my setup. I have no issues with Kontakt in any other applications (save for Cubase blacklisting it, where using the ‘Reactivate’ option alleviates the issue).

Well, in the new year we can have a look at “reactivating” plug-ins in Dorico. In theory it should be the same as in Cubase since Dorico’s audio engine is derived from Cubase, but we never had a particular focus on that feature, so might be that it is just easy. However, since we are all away from office you have to be patient. Happy holidays.

Workaround for MAC Users:

I solved the blacklisting of kontakt by disabling the System Integrity Protection

“System Integrity Protection (SIP) is a security feature of macOS originally introduced in OS X El Capitan designed to make it even more difficult for malware to access important system files, keeping them safe from unwanted modifications. In the early days of SIP, some developers ran into problems when the system would keep core functionality of their apps from working properly because those apps made changes to the way the operating system worked by editing the system files that SIP was now in place to protect.”

Keeping that in mind, do it at your own risk

Here’s how:

Click the Apple symbol in the Menu bar.
Click Restart…
Hold down Command-R to reboot into Recovery Mode.
Click Utilities.
Select Terminal.
Type csrutil disable.
Press Return or Enter on your keyboard.
Click the Apple symbol in the Menu bar.
Click Restart…

If you later want to start using SIP once again (and you really should), then follow these steps again, except this time you’ll enter csrutil enable in the Terminal instead.

p.s.
Make sure you’ve got rid of the “Vst2xPlugin Blacklist VSTAudioEngine3” file first