When bringing mac studio to new location, soundflow does not work for a unspecified amount of time
System Information
SoundFlow 5.7.8
OS: darwin 22.5.0
ProductName: macOS
ProductVersion: 13.4.1
BuildVersion: 22F82
Steps to Reproduce
- bring mac to a different location and plug in
- soundflow commands dont work
- No idea what to do to fix it, it just seems to work eventually
Expected Result
Key commands should work
Actual Result
?
Workaround
No
Other Notes
Links
User UID: Z3dP4yzeLES0iBqN5TpSoQXs2pm2
Feedback Key: sffeedback:Z3dP4yzeLES0iBqN5TpSoQXs2pm2:-O3b9LGRQkN_QKDJTGJv
Feedback ZIP: doTZwhJ280SWKfbP/54wFtj59E7IeVIN4ddjFCjW3Jp902XbVE4CC6ugUodDG46Hl0BkjODzBaj2xBEuTBnBlHlDvTVYO35G5O0hKdPnF96tvsT9PnAfuVMQ+8vRb8SiDxSx8J3NBOAmoVR1WiJv3cqt4QxKdKO8DqndFlD+RPGa3vz4171msbqYvvt7WjPcH9N2KhejwsDvJU3h3uexC9oUE7FlzLOY2sazUi7Ent/dQcBjIvYsBLYtZE7lXqThnFOzyQpRM45lcPsGDBo5JjsTQr45QYDCI5HmT27NQ2jSwfsrQKa6xh/zF/4pKRptmIJ3Tvw/z+EoCFd0AJqTCfR2kGcr6fjQy1HjwT7jtbI=
Linked from:
Christian Scheuer @chrscheuer2024-08-06 11:06:15.523ZHi Gray,
Thank you for letting us know about this issue.
Can you help me with a bit more context, then I'll investigate from here?
- Was this report sent from the machine operating from the new location?
- Is this new location a studio/company where you're connecting through a firewall / corporate network / VPN?
- What is the physical location you're in / city / country?
- Does the problems only happen once when you start up your computer, or repeatedly?
Would you be open to doing a Zoom session with us to try to replicate this issue so we can hopefully fix it?
- GGray Aletter @Gray_Aletter
Hey Christian. The first time it happened was at Warner Bros so I had to assume it was their firewall. TBH I can't remember how I got around it. I have a VPN but I'm not sure turning it on solved it.
I've just got back to my London flat (home studio) from 6 weeks in Toronto. No issues back there but now that I'm back in my flat, I'm having the same issues. No firewalls here or anything. Trying the VPN doesn't seem to help.
Open to Zoom if need be.
Thank you,
Gray
Christian Scheuer @chrscheuer2024-08-06 11:31:29.496ZThanks, Gray, for the added info. Please contact me at support@soundflow.org and we can set up a time to connect.
- Christian Scheuer @chrscheuer2024-08-06 13:55:00.284Z
To anybody reading this, we found the culprit:
- The date/time of the computer had been set manually. The macOS system settings appeared to have a problem setting the date/time correctly to the user's physical location, so there's some kind of confusion in the macOS date/time settings.
- Setting the date/time back to "automatic" solved the problem of SoundFlow not working properly - but it remains to be solved why macOS didn't correctly understand the user's location (unrelated to SoundFlow).
We'll try to investigate if there's a way for SoundFlow to ignore the system's current time (including manual adjustments) so that this issue can be completely marked as solved.
- Christian Scheuer @chrscheuer2024-08-07 15:20:09.280Z
I looked further into the custom date/time setting. What happens in this case, where the user manually specifies the date/time based on the computer understanding the timezone incorrectly, is that the system ends up adjusting the base UTC clock, thus the system actually thinks the global (UTC) time is hours different from the real time, because the timezone is being manually compensated for. The only way to fix this properly is by ensuring the system has the proper timezone set.