I've reinstalled this " thing ", nmkeraj :

Sonible SmartEQ3 v1.2.0-R2R / NUMBER : R2R11082
​

I created 2 tracks in Samplitude, and loaded the plug-in in each one of them.
Tried to create a group : nothing happened.
=> Note : nothing on this PC goes online except what's authorized.

TinyWall ( firewall ) showed in its connexion window that Samplitude, with the plug-ins running, wanted to reach adress localhost 127.0.0.1. Which so, now, I unbloked.
And voilà : I was able to create a group - overimposed is the TinyWall window - :=>

http://ibb.co/m9zC3YP​

( Don't look precisely of any settings, they are there just to show that the plug-ins are working a bit; and one day I'll find out how to insert an image... )

I'm on WIN10 x64, Samplitude Pro X7.

 

Last edited: Aug 3, 2022

Came here to see if anyone figured this out yet so I went ahead and got it working in Ableton 11 on Windows 10.

Through your DAW, Sonible is trying to use a designated local multicast IP: 226.0.0.1 so you must allow it to access it on your local network for the Group function to work correctly.

1) You probably have your DAW/Ableton blocked in your Windows Firewall so go to your Windows Firewall Advanced Settings.
2) In your Outbound Rules, find the rule for your DAW/Ableton and right-click to go to Properties.
3) Click on the Scope tab and under LOCAL IP ADDRESS, you want to select "These IP addresses:" and click the Add button.
*Make sure you DO NOT change your Remote IP Address setting!!
4) Choose any dummy Local IP that your DAW/Ableton would never use. For example, I used 10.10.10.100
5) Now click the Ok button. Then click Apply button then Ok button.
6) Now do the same steps(2-5) for your Inbound Rules.

It should now work.

There probably is an easier way to allow 226.0.0.1 as an exception to the DAW/Ableton firewall rules but the above steps is how I did it.

 

The same concept applies to certain Mac plugins where it's basically looking for a loopback IP address. It's similar to the communication between plugin instances which these are capable of doing. Like how Neutron works. I'm not trying to explain it technically, I am just expressing an opinion that networking aspects do not seem nefarious.

 

So another plugin that uses network protocols to communicate within the same PC.
Instead of a proper IPC solution.

 

In my experience, when DAW is blocked (e.g.) Neutron works "out of the box", whereas Sonible did not last time I checked. So it may be the case, iZotope did something right. Now to use Sonible I'd have to refresh my fragile networking knowledge.. great!

It's literally the only thing that keeps me away from testing, and then probably buying their plugins..

 

I bet that might even vary from user to user depending on how paranoid the users firewall settings are, and maybe how it hooks into the OS.

one wrong compression ratio setting and zone alarm might randomly decide it is time to check out your data backup strategies.

 

The problem is if you use a network protocol you must allow the program to access the network even if it only needs to access another process in the same PC. I guess it's easier to program but it's like killing flies with a flamethrower.
If you use IPC (inter-process communication) you don't need a network. iZotope, Meldaproduction use it in its multi-input plugins.

Recently another plugin gave troubles for the same reason, there's a thread here somewhere. Perhaps it was the same Smart EQ3, a former version. Or that fancy Blue Cat's Audio Connector... it used UDP (TCP's cousin).

Other examples of IPC, for different reasons, are jBridge or Reaper when they bridge/firewall plugins. Oh, and the Kontakt Creator Tools that can modify a running instance of a Kontakt instrument, which is freaking cool.

 

Thank you mates, especially @DAW and @DontKnowJack for the detailed description and guide. I have done what you advised BUT...
It doesn't work. F*** knows what is going on. They are screenshots of the first instance

 

Last edited: Aug 20, 2022

And the second instance

 

And then two together

 

I have installed Live and smartEQ3 on my wife's laptop. And... BOOOM!!! Everything is working like a charm!!! WHY??? Hosts file? At first, the second instance takes the name of the track on which is loaded unlike on my computer where every plugin is named "Instance 1".
I have reinstalled my Ableton Live but still the same.

 

Last edited: Aug 21, 2022

Probably your wife's laptop Firewall is configured to not block by default. More relaxed settings.
Keep in mind that the solution is not trivial. You have to unblock a program, the DAW, in your Firewall. That's easy.
The difficult part is you only have to unblock it for your computer (localhost,127.0.0.1) and for both transmitting/receiving data (inbound and outbound).

For this you have to use some more advanced Firewall rules than usual. I'd always recommend TinyWall, a fantastic app. The one that @DAW used.

Or you can go to the advanced settings of the Windows Firewall like @DontKnowJack

 

@Xupito Agree with you. But I have done all of the things. I have removed all the firewall rules on Ableton. I have switched off the firewall at all, too.

 

It may be some hidden setting in the loads of network settings on your PC, as in every Windows PC.

That's why I hate when programmers resort to this instead of IPC like iZotope etc...

I'd still give a shot to TinyWall. It works at a lower level than the Windows Firewall service. It works at the Windows Base Filtering engine (BFE) level. The Firewall is built on top of that.
Also, you could reset the Windows Network settings.

 

Last edited: Aug 21, 2022

I 'll try that.

This article hasn't helped either:

https://help.sonible.com/hc/en-us/a...es-an-instant-crash-when-loading-an-instance-

 

smartEQ3 is working in Reaper portable on my computer!!! So what the heck is blocking the plugin in Ableton 10???

PS. The second run of Reaper stopped smarteq to work. Tinywall showed blocked 226.0.0.1.
The rule was added to Windows Firewall to block Reaper. I deleted this rule and Reaper and smarteq work well now. But Ableton can't start working. I removed rules of Ableton from Firewall. I press unblock in Tinywall as well.

 

Last edited: Aug 28, 2022

screenshot

 

Still says you have rules in place blocking UDP traffic for Ableton for the relevant addresses (127.0.0.1 -> 226.0.0.1)

Try adding an exception-rule for all programs for both TCP and UDP for traffic between those local addresses (and only those two addresses) in your firewall.

If that doesn't help, go over all the rules you can see in your firewall, not just the ones that say 'Ableton'. You may have some generic rule that catches Ableton.

If that doesn't help, hit Win-R and paste "%windir%\system32\WF.msc" in the box (without quotes).
It'll take you to Windows' own list of rules.
Flip through everything until you find the rule blocking Ableton (try sorting by 'Action' column).

 

@xorome Thank you. I have done your tips but NOTHING changed. No blocking rules in firewall. No rule about Ableton. I disabled TinyWall Firewall. Ableton - UDP - local 127.0.0.1 - remote 226.0.0.1 - Blocked - Out.
Can it be anything in Registry??

 

You need to allow 127.0.0.1 <> 226.0.0.1 TCP & UDP, not block it.

Please also check here: