Hey Christian Like we discussed. this is morning startup routine waited about 3 minutes after everything loaded to open soundflow.
Hey Christian Like we discussed. this is morning startup routine waited about 3 minutes after everything loaded to open soundflow.
System Information
SoundFlow 5.3.0
OS: darwin 20.6.0
ProductName: macOS
ProductVersion: 11.6
BuildVersion: 20G165
Steps to Reproduce
Expected Result
Actual Result
Workaround
Other Notes
Links
User UID: QcDHvsmnPGY0bQTEirW05dHPdM52
Feedback Key: sffeedback:QcDHvsmnPGY0bQTEirW05dHPdM52:-NPLfACryqI1_aYrHAki
- Christian Scheuer @chrscheuer2023-02-28 08:23:45.684Z
- In reply toPierre_van_Caloen⬆:Christian Scheuer @chrscheuer2023-02-28 08:24:56.940Z
Hi Pierre,
Thanks so much for sharing this. I don't understand why this is happening.
Are you connecting to SoundFlow from behind a firewall or VPN by any chance?
- PPierre van Caloen @Pierre_van_Caloen
Nothing but my isp's firewall but that's very limited
Christian Scheuer @chrscheuer2023-02-28 10:15:41.293Z
Ok, gotcha. Please note that it's not supported to use SF from behind a firewall without the use of our Proxy solution.
This type of issue has been known to happen behind firewalls as they might block or delay some of the HTTP requests that SF makes. That could explain what you're seeing.- PPierre van Caloen @Pierre_van_Caloen
I doubt that would be an issue. It's basic DDOS protection and port filtering on the ISP router.
You would have that issue with basically all you customers on commercial ISP.My bet is that it has something to do with the transfer of my account to MOS or the profile I deleted.
Thx,
PierreChristian Scheuer @chrscheuer2023-02-28 16:43:31.880Z
Hi Pierre,
I just checked a copy of your account here and it loads just fine on my computer. It did show up momentarily empty (for less than a second) but this is normal and just part of normal SF loading. I didn't have to press anything to get it to load.
Please try logging into your account from another computer somewhere else and double check if you're still seeing the issue there.
Without that troubleshooting step, I don't think there's much we'll be able to do at this point.