![]() ![]() These can all use 5GHz WiFi in a way that interferes with nearby devices. First, do you have any wireless audio devices? In particular, non-Bluetooth systems like wireless surround sound systems, a sound bar with a wireless subwoofer, or wireless gaming headset. That could be any number of things, so let me just suggest a couple things to look at. On the other hand, you also said things got worse when other people's devices got closer to you, which suggests it's a local WiFi-specific problem. But, the fact that your speed tests at the time were consistent suggests it might be an issue deeper inside your ISP's network. It can be really frustrating to debug an issue like this. The Streamer is tuned to perform optimally under "typical" conditions. All of that said, I'm sure it's possible to improve the performance of the Streamer component, and I'm sure Google monitors how often the Streamer runs into trouble that ends up being visible to the user. ![]() ![]() This is a classic engineering tradeoff between maximizing quality and minimizing the probability of visible glitches. In general, this works pretty well, but if the link capacity is changing quickly, the Streamer may not always be able to react in time. Instead, the Stadia "Streamer" component attempts to track the effective available bottleneck link capacity and preemptively reduces the bitrate (by shifting to a lower resolution or just using a lower quality level at the same resolution) when it detects a reduction. Increasing the traffic load under these conditions exacerbates the problem. Wireless interference is another form of congestion. Hello of the issues you describe are caused by different forms of congestion – basically, one or more links are being asked to carry more data than they have capacity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |