Yesterday, when I had to close and reopen Cubase, I saw this message, which isn’t unfamiliar.
“Do you want to allow public and private networks to access this app? The Windows Firewall has blocked some features of Cubase 15 on all public and private networks.”
You can allow it or leave it blocked.
From experience, I know that if it’s blocked, many programs won’t start at all. So I allowed it.
It works.
But why does this message even appear? I haven’t even updated it.
Why does Cubase need access?
Is there a list (preferably on my local network) to check what Cubase is sending and receiving?
Cubases itself potentially requires acces to the internet e.g. for the hub (fetching webcontent, which you can disable) or for VST Connect. Some plugins use local networking for inter-plugin communication and more often want to acces the internet for update checks or similar. Product like VSL Ensemble Pro or Audiogridder require networking for communicating with their own server apps.
Oh, I didn’t know that @fese ! I routinely disable internet when tracking. I guess from what you’re saying, that can’t be done while using Audiogridder?
