You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the app starts and the user is not in range, we need a "popup" notification explaining the situation. The current functionality (everything works, but there's no audio) seems like the app is broken.
The text was updated successfully, but these errors were encountered:
Totally vital! Yet again, I have no idea why this doesn't exist already given that it's been a part of earlier apps. Maybe I didn't hand over the complete codebase or something initially...who knows, but it's worth poking around to see if this already exists, but is disabled somehow.
Out-of-range notification and functionality has been a long-term component. The way it is currently designed to work is if the app detects that the device is out of range (as defined by twice the max radius away from any active speaker for the project), the server returns a static stream url (out_of_range_stream) instead of a dynamic stream and said popup warns the user of the situation. Since it is quite common that people try to use RW apps when not at the site, this method at least gives them the opportunity to play around with the app and hear something representative of what they might hear on-site.
The fact that you are not hearing any audio at all suggests there is more wrong, or perhaps you were testing in the range between speaker max_distance and 2*speaker max_distance (which would result in the behavior you experienced, actually...no popup and no audio until you moved closer at which point it wound fade in). What url was returned by request_stream?
When the app starts and the user is not in range, we need a "popup" notification explaining the situation. The current functionality (everything works, but there's no audio) seems like the app is broken.
The text was updated successfully, but these errors were encountered: