I will try to make a clean uninstall.

Guys, none of you have a muted notes issue with this plugs (Modo Bass 2.0.2 by R2R)?

 

Need to uninstall, block and re install.
A software like Revo Uninstaller or Bulk Crap Uninstaller can help you delete left over files.

 

That behavior is more typical of an expired demo. Maybe even take the computer offline during the install process. Modify hosts file and firewall it. It can't hurt.

 

Yes it it's My Bad

 

Yep... my bad too...

 

The Issue remains. I have made a clean uninstall with Revo, hosts, etc.

The app seems to trigger the time bomb after it reads midi notes
(after a random amount of time).
If the software remains on a track without ever reading the slightest midi note, there will be no time bomb.

 

Maybe you've got a program change or some other CC in your MIDI file..

 

I would check midi event monitor just in case

 

It could be this, if the midi file was imported rather than notes drawn in from blank piano roll (or played).

Midi event monitor may help, or even ProcMon. https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Other guessing type of things to check would be with Internet and Wifi off. Or network card disabled even. This is all a stretch though.

@OP, did this software ever work correctly? If so, how long was it working for, before this began?

 

Nothing special for the MIDI event...

Only notes. No CC.

If I add an another Modo bass 2 on the same track where a first Modo Bass 2 mutes my notes, this new Modo bass 2 plays all notes (some time before the muted notes arrive).

 

Did you have another version of Modo Bass installed previously? Also, have you flagged this keygen to be an exception to any Antivirus? (or temporarily turned it off).

The r2r nfo file states the protection types included WebAuth, but that could also just be related to the CustomShop features. There are two host file additions to block suggested in their notes, also. I would also look in your firewall rules, and see if you happen to have an "Allow" rule which somehow contradicts the rule you have blocking Modo.

Can you upload your hosts file or copy paste it's content? You could also screenshot the ruleset of your firewall.

There are lots of comments about this release, but none about it doing what yours is.

 

I do, I have to offline/online the fx periodically. I have never found the fix. I have tried installing again, etc.

 

Have you tried a previous version scene release (v1.5.2) to see if that works correctly?

 

Yes, it works great. No issue. But it's not the same soft and not the same sound...
Modo Bass 1 is not Modo Bass 2.

 

Maybe it's just something to do with that 2.x version scene release, especially since other folks seem to be experiencing the same issue?

 

Yes. There is probably a time bomb with the 2.x by R2R.

 

True, but both were released by the same Team. I would uninstall them both cleanly and try again. One could be interfering with the other.

 

Regarding what address to use: I have mine all set to 0.0.0.0.
I read someplace I trusted that it is better in some way.
Now i think i should switch them all back to 127.0.0.1, because I searched again and found these:

Spoiler

https://superuser.com/questions/1030329/better-to-block-a-host-to-0-0-0-0-than-to-127-0-0-1#:~:text=On Windows there is a,error code 1214 (ERROR_INVALID_NETNAME).
"On Windows there is a difference: packets sent to 127.0.0.1 will end up bombarding whatever server you have running on your computer (and you may be running a server without knowing it), whereas trying to send packets 0.0.0.0 will immediately return with error code 1214 (ERROR_INVALID_NETNAME).
---- TL;DR: Use 0.0.0.0"

Another:

Spoiler

https://www.tenforums.com/antivirus...t address and 127.0.0.1 is the current device
It is usual to use 127.0.0.1 as this routes packets (your data ), to a specific device (your current device) where it will be basically ignored
Using 0.0.0.0 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 were more that a single device on the network.
As the 0.0.0.0 address has an ambiguous usage it can act in various ways depending on the hardware in use
127.0.0.1 is always a specific address so should be used as a loop-back address to kill potentially problem data packets)

And here:

Spoiler

https://stackoverflow.com/questions/62500568/why-can-0-0-0-0-in-etc-hosts-block-a-certain-website
using 0.0.0.0 (=localhost) to block websites is just a trick that works for most client machines, as they most likely do not have a webserver listening on HTTP/HTTPS ports. You could use a non existing IP address as well, but using 0.0.0.0 is much faster because your computer already knows there is no web server listening, so the connection fails immediately (instead of having to wait for a timeout when using a non existing IP address). If you have a webserver on your computer, configure it to reject requests for domains it does not recognize to be able to use that trick

So, i am getting the idea that, so long as you are NOT running a server, 0.0.0.0 might be faster, but as was mentioned, one might not know about a running server.
Well, it seems the easiest way is to use 127.0.0.1 ... to avoid having to THINK about it - LOL

Most of all, I will mention BlueLife Hosts Editor. It makes opening, editing, or just enabling / disabling one entry so much easier. https://www.sordum.org/8266/bluelifehosts-editor-v1-5/
I also LOVE Easy Context Menu. One can customize it perfectly. I have used NirSoft ShexView to disable some context menu items (and to find and delete some in registry), but Easy Context Menu also lists some one can disable.

And you can see what firewall I like best in my sig ;)

 

Last edited: Jul 25, 2023

This hypothesis seems extremely unlikely and someone else has already tested the thing without success.

I had fun completely disconnecting my PC from the internet. Same problem.

At some point, I think we'll have to tell ourselves that the most likely hypothesis is the time bomb (or a bug), especially since I'm not at all the only one to encounter this problem of muted notes.