At this time, Beacon just plays all sounds as soon as the client receives the message to play it. This sometimes creates dissonance between sounds. Especially when two nearby computers have different internet speeds.
Whilst this is amusing, and to me personally adding to the atmosphere, synchronizing sounds could have an even bigger emotional impact.
Suggested was; Send a timestamp for when the sound should be played. This due to how beacon interacts with sounds, should then also occur for alert screens / broadcasts.
[ ] Send Epoch along with broadcast
[ ] Have broadcast queue
[ ] optional allow SL to preprogram alerts with specific times
[ ] optional schedule PSA's on a rotating cycle with random frequency intervals. (not every 15 minutes. but every 30+randomoffset)
I like it! We could pre-load the "standard" noises by just having them always available rather than in the dynamic HTML of a broadcast, especoally since the filesizes are tiny anyway
Discussed at the IT meeting on 28/02/2021
At this time, Beacon just plays all sounds as soon as the client receives the message to play it. This sometimes creates dissonance between sounds. Especially when two nearby computers have different internet speeds.
Whilst this is amusing, and to me personally adding to the atmosphere, synchronizing sounds could have an even bigger emotional impact.
Suggested was; Send a timestamp for when the sound should be played. This due to how beacon interacts with sounds, should then also occur for alert screens / broadcasts.