SoundFlow offline after waking computer from sleep
SoundFlow offline after waking computer from sleep
System Information
SoundFlow 5.8.1
OS: darwin 22.6.0
ProductName: macOS
ProductVersion: 13.6.4
BuildVersion: 22G513
Steps to Reproduce
Expected Result
SoundFlow online after waking computer from sleep
Actual Result
SoundFlow offline after waking computer from sleep
Workaround
Quitting and reopening SoundFlow
Other Notes
Time of SoundFlow being offline was 11:41:34.
Laptop woke up maximum 1 minute before.
Laptop went to sleep around 09:51 +- 5 mins.
Links
User UID: RZnxlDkkM6MB7ZucflXsNj7mZFu1
Feedback Key: sffeedback:RZnxlDkkM6MB7ZucflXsNj7mZFu1:-O4ZsyZE0yfHnLnev6ab
Feedback ZIP: +/aS7tVMpvYgSAETAKZ+gKkWql4Cci9Sfsn92aG0B5hSjknFrum3v0b5G5C/uVzObrc5gm/kzVGmwCBVl9ETIzi5B66vL6KRzAvGUSxrs7BeCtDyunr6zQhd7WLguaCzLPxRz3TKyO0mlC+OaKXuKwx+r8Hz0FZGzbRya4ovdKmh0TfYM/04OqXPJ6vRuvBNNp1wacMZg9nQdNXV6PVeuNQ34xVOPoonkfZ5LECo/HUBUhvThQ0MPSn6sFUJ3cZiJ5YN9BCAa7EGyEaIG1eyAL/19kvbKgMYj4TiHGtFJ1fegK4yfq10RFsVz+KFNSyRYX1pll8AgzRTS2LSvMkHji4b+JiX+/oP78xebB13Cl4=
In reply toJascha_Viehl⬆:Christian Scheuer @chrscheuer2024-08-19 10:27:47.900ZThanks, Jascha.
Definitely weird things going on in the log. I can see that at this time the computer went to sleep:
17.08.2024 20:10:15and then it woke up correctly on18.08.2024 07:02:02. Soundflow received the normal "wake up call" from the OS at that time.Then, it went to sleep again at
18.08.2024 09:47:43, but then, around18.08.2024 11:37:27when you woke the computer up again, SoundFlow did not receive any notifications from the system that the computer woke up. This is what causes it to never update the online state.Can you think of any differences with how you made the computer sleep in those 2 instances?
- JJascha Viehl @Jascha_Viehl
The long sleep overnight probably was with my docking station switched of.
The short sleep probably not.
I also switch of the studio room, with several devices attached.
Over night I typically additionally also switch of my audio rack containing the Fireface 800.
The speed with wich I manage to switch these off might also differ. Managing it before the computer went to sleep or afterwards.If I have the docking station switched on during computer sleep. I also have trouble with external drives being ejected and mounted multiple times. To me it seems as if the laptop wakes up every half hour or so.
Christian Scheuer @chrscheuer2024-08-19 20:28:17.578ZThanks so much. Good point re. the docking station. Perhaps it keeps the computer in a "not quite full sleep" mode which then confuses macOS / SoundFlow upon "wake-up" so we never get the signal that it's actually woken up (possibly because the "go to sleep" actually failed, but we weren't told about that).
Definitely an interesting case. I'll think about if there's anything we could do on our end to work around this particular oddity.
- JJascha Viehl @Jascha_Viehl
Hey,
had the exact error mentioned above again.
How can I share logs without opening a new support case?
Send an extract via mail for now.
- Christian Scheuer @chrscheuer2024-09-02 01:07:57.142Z
Hi Jascha,
It's fine to open a new one, we can link them on our end :)
- SIn reply toJascha_Viehl⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-1413
- JIn reply toJascha_Viehl⬆:Jascha Viehl @Jascha_Viehl
Any news on error SF-1413?
I'm still getting this regularly and with this SoundFlow is costing instead of saving time.
Now I couldn't even "wake up" Soundflow even with quitting in / relogging in.
Also created a new support case to submit logs.- Christian Scheuer @chrscheuer2025-04-22 15:48:32.028Z
Hi Jascha,
Thanks for bumping this. Since you reported this, we've not seen any other user reports on this issue, so we've not been able to prioritize it yet, as it appears it's only happening on one computer.
I'll take a look at your new log files, but from what we learned last time, it seemed that we identified the specific USB hub you're using to be the source of the problem. Do you think that's still the case?
- JJascha Viehl @Jascha_Viehl
Hi Christian,
I don't think it has to do with the USB hub, because even when the computer is waken up and SoundFlow was completely restarted, it still couldn't connect and even not send any support any support cases.
So the connection to the SoundFlow server was broken and only worked when starting the whole computer.
That shouldn't be related to the Streamdecks and USB peripherals in any way, right?I had this on my old Mac Pro 5.1 and the new MacBook Pro M2 Max.
As far as I remember both where using different peripherals.I've had this error a long time but didn't report it.
Maybe other users are not reporting it because of the effort it takes, or because they don't know if it's a OS or a SoundFlow issue.Maybe as a quick fix you could also "wake up" SoundFlow manually again on Clicking "Restart SoundFlow" in the menu, or maybe even better on every launch.
- Christian Scheuer @chrscheuer2025-04-23 16:15:59.559Z
Hi Jascha,
Thanks for the additional details. If you're seeing problems after fully restarting SoundFlow, then that definitely indicates something else is going on.
Are you restarting SF by clicking the SF icon and choosing "Restart SoundFlow" from the 2nd page - or are you completely restarting it by clicking Quit and relaunching from Applications?One other thing that could be causing this is if your computer for some reason is slower than normal to acquire its network address when waking up which could cause SF to be unable to connect for some time after startup. FWIW, I'm on a Macbook Air M2 and go on/off various wifi networks in many different locations every day and am generally not seeing any issues with connectivity - but it may be that something specific on your network or computer causes issues.
The next time you see an issue that's unrelated to the "waking computer from sleep" and is more that it generally can't do things, would you be able to send us a new report so we can compare the log files?
- JIn reply toJascha_Viehl⬆:Jascha Viehl @Jascha_Viehl
Even the support case function can't connect to the SoundFlow servers after the wake up.
Here's the support zip folder:
https://www.dropbox.com/t/CFGXsdHw4KjlpK8c
- Christian Scheuer @chrscheuer2025-04-23 16:18:45.806Z
From these recent logs, we're getting these issues:
22.04.2025 07:54:40.05 <info> [Backend]: [SF_FIREBASE_WS]: Couldn't connect to wss://soundflow-4533b.firebaseio.com/.ws?v=5&ns=soundflow-4533b&yQXDPxrrHIMc1F3bIenhoDn4VHY4y5SP (Attempt #70) - timed out, so let's try againThis indicates that your network is not allowing SoundFlow to connect to its core server, even after trying 70 times in a row.
This could indicate there's either a network filter (firewall, software or hardware) or network configuration that's blocking the traffic for an extended period of time.
