Hello!

After a period of time (less or more 30 minutes), some notes will be mutated by the software.

The developers of IK MULTIMEDIA behave like those of Spectrasonics during the period when there was the time bomb on Omnisphere. The only thing they say is contact them privately. No patch planned to fix this, because there is nothing to fix. It's a voluntary time bomb.

https://cgi.ikmultimedia.com/ikforum/viewtopic.php?f=39&t=30449&hilit=issue&start=15

 

Is your computer connected to the internet, not properly set up with a firewall, or containing an incorrectly amended hosts file?

 

Hi,

After the time bomb, I wrote inside the Hosts file (inside : C:\Windows\System32\drivers\etc)

"
www.ikstore.com
txc.ikmultimedia.com

"

 

either you did not modify the file correctly, or they are using a different web address for this "feature". I saw one developer use a Domain and website that was for a house painting service. Probably the dev's other job, which he should keep; because the plugin sucked. You used to have to reboot a windows machine before hosts file changes would be reflected. I have been told this is different with newer machines.

 

Just block your whole DAW for outgoing Connections via Firewall then you can be sure no Plugin calls Home

 

I do not think this is accurate. The DAW application calls the driver file (plugin), but once the plugin is loaded into memory the DAW is no longer playing Nanny with it. Firewall your DAW (and not the plugin) and see if you can download anything like updates within the plugin itself. A plugin that you know has it's own update features inside it.

 

you should put 127.0.0.1 or 0.0.0.0 before the url

 

Last edited by a moderator: Jul 23, 2023

If DAW is blocked you can't update the plugins i know what you mean but it's a single click to unblock the DAW to Download updates and then another click to block it again.

 

It's better to set 127.0.0.1 because this is the Localhost so any adress set to it can not conntect to outside of your machine using 0.0.0.0 (which is technically the network segment broadcast address) will generally send the data to all devices on the local segment which would also normally be rejected, but would greatly increase the potential traffic on the local network if there is more than a single device on the network.

 

Last edited: Jul 23, 2023

I have some old version of this vst (maybe ver1?, I have to check) and there is the same/similar time bomb (skipped notes, if I remember correctly, I haven't used it in many months in a project). It is installed on a PC that was never connected to the web, so something else triggers it.
Still, it is usable with bouncing to wav.

 

I meant that you could update the plugins with the daw blocked. They can get around your firewall, otherwise everyone on here would just block the DAW application and you'd never hear about it again. It's why Hosts file gets used to block the entire domain, when attempts to create a firewall rule are not successful. And that is when the plugin files have been firewalled directly, and not just the DAW. It is probably because a different PID number applies to the plugin than the DAW, as source of the outgoing traffic.

 

My DAW (FL21) is blocked by the Windows Firewall and nothing is going thru. If a Plugin needs to Download Stuff like Shaperbox i need to disable the block otherwise no connection to the Server. Also i've checked it with Glasswire and no data from any Plugin or the DAW is going outside with Windows firewall blocked DAW. In my opinion Hostfile is the Way to go for Standalone Software.

 

the localhost is 127.0.0.1
The 0.0.0.0 (prefix) is considered the location of your computer, so when an entry listed in the HOSTS file is requested on a page you are viewing, your computer thinks 0.0.0.0 is the location of the file. When this file is not located it skips onto the next file and thus the ad server is blocked from loading the banner, Cookie, or some unscrupulous tracker, or javascript file.

 

I have tested with 127.0.0.0

Sadly, time bombe remains...

 

It can often be too late for firewall rules and hosts blocking, depending on what the dev has setup. As an example, they can go out to the web and download a blacklist/deny list with wget,curl,etc. Once that happens, you need to track down the file locally and delete it. Internet "Calling home" is one of the more common current methods, but it's obv not the only one. The differences between Loopback, 127, 0.0.0.0. exist; but for purposes of this, they usually do not make a difference.

 

Same issue with 127.0.0.1.

"Once that happens, you need to track down the file locally and delete it."
How I can do that?

 

That is just another example of the ways Developers use "home-calling". Any created file like that would probably have a very uninteresting and probably random looking filename. In such example, blocking with your firewall and hosts file is already too late by the time you are not able to open the plugin. Reinstalling the plugin will not fix it, because of the remnant file left on the computer which it checks for.
You would have to be good at guessing, using a process monitor program to log it happening, or have some other way to look at the coding. I am not suggesting that the issue you are seeing is caused that way. But the developers know common ways their programs get modified and "fixed" for release. Their checks are not all based on internet access to the program. You would need the application or plugin firewalled in correctly the entire time, or no internet access on the affected computer; to rule out "phoning home".

 

Last edited: Jul 23, 2023

You must uninstall the plugin delete every folder modobass 2 created on the harddrive.
And also delete every entry in registry
Then reinstall and use the keygen

 

It's best to disable all internet traffic and allow on a per-app basis. All GUI firewalls have a pop up notification function to help you. Plugins are just like any other piece of software. They're allowed to do anything they want. Including starting new processes that aren't subject to your DAW's firewall rules.

 

Isn't it 127.0.0.1?