Ticker

6/recent/ticker-posts

The YouTube videos you launch have a very poor image quality? It doesn't come from you

The YouTube videos you launch have a very poor image quality? It doesn't come from you

Several users have noticed that YouTube videos are playing in a very low resolution despite a sufficient internet connection. The platform has acknowledged the bug.

The YouTube videos you launch have a very poor image quality? It doesn't come from you

In the vast majority In some cases, you watch your YouTube videos at the maximum resolution available on them, if your screen's resolution is sufficient. With 5G and fiber, we no longer even ask ourselves whether our Internet connection will be able to support this. Moreover, the streaming platform can automatically switch to a lower resolution when it detects a drop in speed, which allows you to continue watching without interruption.

But when it does this for no reason, it's problematic. This is what users have noticed in recent days. On Reddit, for example, one Internet user complained that every time he "opens a video or YouTube Short, it opens in a very, very poor quality like 144p". Others experience the same thing with a start in 360p before returning to 1080p after a few seconds. Each time, they suspect their connection, yet it is not at fault.

A bug forces YouTube videos to launch in very low resolution

Technically, those affected can manually change the video quality. Except that this triggers a waiting time due to buffering which shouldn't normally be this long. Worse: some people can't touch the setting, no matter what it does. “Even when I manually choose 720p, which my connection is perfectly capable of[…],[the video]refuses to go above 144p“, writes one annoyed user.

Read also – YouTube: the app automatically launches Shorts? Here's how to fix it

These two phenomena are visible in the YouTube app on iOS, the website and the dedicated app for smart TVs. Both "classic" videos and Shorts are impacted. YouTube has officially acknowledged that this is a bug. At the time of writing, the service teams posted about this 15 hours ago. They are currently working on the resolution of the problem, without giving a time frame.

Post a Comment

0 Comments