Hey there,

i bought the Sonible Smart Comp 3.
It´s good for me because, it really helps to stay creative without playing around so much.
I don´t want to advertise it so much, but it´s like Day and night for me.
I´m not a Pro Producer. Just for Hobby and it really fits my Drums and Percussions in the Mix now.

Now i found out, it needs to connect to the Internet, to do some Magic:
Host: accentize.com

When blocked, the UI Pad is not working.

I use Bitwig Studio and LULU as Firewall Software.
I block Bitwig and the BW Plugin Host.
When i open the Firewall, it´s working fine.

Do you know a way to allow The Plugin Host just for some specific Remote Hosts?
Or do i need another Firewall for this purpose?

Thanks a lot

 

I ran into the same issue using Sonible on Ableton / Mac with Lulu. With Lulu enabled and blocking Ableton, the Sonible plugins were giving me errors about connection to network.

I have Lulu blocking Ableton. Based on what I read on another forum, I added an additional rule for Ableton to open address : 226.0.0.1

This is apparantly the address that Sonible connects to for AI server

To my surprise, this actually worked... even while still blocking Ableton on all other addresses.

 

226.0.0.1 is a local adress. there is normally no reason to block those.

 

When BitWig pops up with a notification about allowing network access after you install a new plugin you say "allow". This allows SmartComp and other plugins that "network" to other instances within the DAW. I went through this with SmartEQ4 trying different versions from Moria. And furthermore, if you've been blaming it on Lulu and you were add/del rules left and right you may have two problems. Anyway, in my case I just have reminded myself that the BW notification is popping up bc Comp3 is asking for access so I say allow.

 

For Studio One I had to do something similar after googling the ports that sonible uses, bc S1 doesn't give you the option to allow access for internal plugin networking. But watching the live traffic as launch S1 on Lulu made it easy to find the culprit.

 

Right, I think these guys think the plugin has to connect to a Sonible server lol. It's just internal networking like you say and is a gateway for the plugins to talk to each other. AI server? lol

 

Don't block the plugin host

 

I don't use your daw nor Lulu but I do use little snitch and have no issue with sonible plugins. just finished a session with a few sonible plugins on it. I just have my daw set to not receive anything via little snitch. you can try blocking sonible via host file...
paste this into terminal: sudo nano /private/etc/hosts

I just checked mine, I don't have sonible in there but I do have safaripedels in there and screenstudio in there though

 

the principle of "rather block one thing too much than one too less" is not the worst you can do, especially when you do not know what something actually is.

what i wonder more is why that lulu app blocks local multicast adresses. my (very old version of) LS does not (or maybe i am lying and it can do that and i disabled it at day 1)

 

if you do not block the plugin host, you are either letting every plugin call home, or having to block every plugin you install.

You need to block outbound, not inbound. Homecalling is always outbound, aka data leaks.

If you block the DAW outbound in one rule, that does not mean you are unable to create a different rule for the LAN.

 

Thanks a lot guys
In the time i found out, that you can set Rules per Adress/port
So i allowed the BW Plugin Host to communicate with the 226.0.0.1 and accentize.com
Now The Sonible Plugs are working and the rest seems to be still blocked