Greasy Fork

Hey, does it still work? I am never sure if it does. The HQ logo appears in the top right, but if I check in the player's video quality menu, it always shows the "auto" option being selected. And it's also apparent because many videos would either start or eventually switch down to low quality. Only way to avoid this is to manually select the target quality, and that makes the script redundant. Please let me know, thanks.

You can update to the latest version. The HQ logo has been replaced with a target quality dropdown menu; you can select "Best" to force the highest quality.

I checked and apparently I have it at that. But when I check the actual player's setting, it's still set to Auto. Is that just a UI quirk and it's actually set to the target quality? Not sure because of the auto change in quality I mentioned before. It only stops doing that if I manually set the quality in the player itself, away from Auto.

Sorry about that, but I'm not seeing any quality settings on my X. What browser and OS are you on? If X has already rolled out that feature for you, then this script probably won't do much.

I'm using Waterfox (a couple versions older than latest, but all these versions don't have any significant changes in them) on Win 10.

Which feature? Are they expected to roll out something?

The player's manual quality selection feature you mentioned—I don’t have it on my end. In fact, the lack of that feature is exactly why I developed this script. Since you have it now, either X is doing a grayscale rollout, or they’re offering different features depending on the browser. Regardless, the loading mechanism likely differs from my script's logic. I won't be able to make specific updates until X rolls this feature out to my account. My apologies that the script currently isn't working for you.

Oh interesting; very unexpected! So it's rolled out to specific accounts? It feels like it's been around for quite a long while, several months now, but who knows. I guess we'll see once you get it as well. No need to apologise, thanks for the effort! I'll put it as working since it more or less does work, so hopefully when you get the feature you can more thoroughly look at it.

Just to update an observation - I don't know if it helps, but anyway - I noticed that the videos would go down in resolution automatically when there would be buffering from server side. i.e. my connection is very fast, but maybe some video is on some older server of twitter, or they experience some CDN issue, or the video is not a commonly viewed video so it sits on a slower cache (or not on one at all), so that ends up being treated erroneously as "user has slow connection" and therefore switches to lower resolution. I mean, this happens most often on videos that only have 270p and 480p in its options, while I can get 2160p ones running fine. Maybe just a line of code that enforces the desired resolution upon detecting that it's switched can stop this from happening - perhaps it's a sloppy thing in twitter's own player that it doesn't realise it's blaming the wrong thing for the buffering.