Done! Check your PM

 

Please. thank you.

 

I dare you to ask him also for omnisphere installation process

 

I asked for nothing. I was illustrating the lack of manners.

 

Thank you for all the effort here. I have installed Kontakt 6.2.2 [not r4e version], which only opens when I'm allowing it to use the internet connection. After many different aproaches I gave up.
I would be thankful if someone could give me the Sister link on PM to install a proper Kontakt [r4e].
Be careful with other Kontakts I had bad time with them

 

You have to create a firewall rule to allow only the loopback address (127.0.0.1).
No external internet connection are necessary.

 

Thank you, now it's more clear for me.
I have added to host file:
127.0.0.1 configuration.native-instruments.com
127.0.0.1 93.184.220.20
I'm using FL Studio and it still doesn't open up till i unlock FL from the firewall blockage, even when I have added it this hosts. What am I doing wrong?

 

I don't know, I actually use Comodo (but could be also any other) firewall to block kontakt.exe, no matter if using the dll as vst, in custom mode rules (warns you of attempts of connections).
Also win firewall can do that, but you must create this rule manually.

 

@orbitbooster If you block your daw, no plugin can dial out.

 

@Smoove Grooves thanks. I will unblock FL. Is it risky to unblock it? I'm just always scared about some crazy VST dials or sudden updates.

 

6.2.2 is broken, the "skip missing" command has been removed

 

Hi all, so I have 2 questions. First off I just want to say I have the latest release and with all libraries that can be opened from the library tab it works great.

1) In Cubase 10.5 (legit) Kontakt takes 4-7 seconds to open when I click the edit VST button (the keyboard symbol). No other plugin does this but Kontakt and that goes for when it's empty in a 1 track project as well. Is there anything that can be done to fix this? It's rather annoying.

2) Instruments opened through the explorer freeze the entire program and take a long time to open even after batch re-saving everything. This includes small libraries without a million files. I've seen some people mention re-saving NKI's with less clutter but that would be a pain in the ass doing all the libraries and as I said it affects small libraries with simple patches as well.

https://vi-control.net/community/th...romises-century-brass-too.69382/#post-4195996

 

Well, I block daws too, but I'm not sure 100% of what you said.
Some vst dll requires its executable, that is outside the boundary of daw, and that will try to connect.
Also, in my experience if you block all connections SOME vst won't work, Kontakt is one of them.

I create a simple set of rules:
1 - allow loopback
2 - (OPTIONAL) allow subnet mask (LAN)
3 - block anything else

 

If you feel unsecure, block daw and read above.

 

I have an important update about the kontakt firewall thing.

I was wrong about the link between kontakt dll and the exe, however I was right about the loopback:
daws (and standalone too) must be allowed on the loopback address in order to make kontakt vst work.

I tried to block all in Reaper and kontakt was crashing the whole thing.
Once restored the loopback address, all ok.

ONLY IF YOU WANT TO TEST IT:
if you have a firewall with connection alert, try to delete the rules for daw or for standalone, launch kontakt and you'll see that it will ask for 127.0.0.1. Block it, and it won't work.

 

But I said to block it. Not unblock it. Very risky, yes.

 

Strange. Not so here. Surely that's because you've blocked the plugin?
When I block the daw, if I go online and open Kontakt, my network monitor software will will be seen to block Logic from calling Native Instruments. No crashes.
When you block the plugin, it can't even embark upon that, thus the crash?

 

For windows (don't know about mac):
I don't know how to block vsts, ther're actually dll extensions of the daw, so daw and just in case standalone too, are what I have to rule.
If I block reaper.exe, kontakt crashes and also reaper crashes, period.

Instead, with this simple set of rules :

1-allow reaper.exe with 127.0.0.1;
2-deny reaper.exe with anything else

It works, period.

This behaviour is only for kontakt as long as I remember.
It probably relies on some server-client network paradigm, I don't care as long it works.

 

can i have the link please? Thank you.

 

Hi where I could get this version? Is it in this website? Baby steps explanation please!