-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: 80% of videos get loaded as legacy #5370
Comments
By the way: sometimes the same video, not loading as DASH can be reloaded (F5 / Ctrl-R) and load as DASH, or then load as legacy low-res again. |
This sounds like #5350. |
Indeed sounds like it. @RevAngel7 could you check for red errors in the dev tools (ctrl + shift+ i).
|
shift-ctrl-i video OK after pressing ctrl-r: |
It's a 403 (forbidden) from youtube (not like #5350 ) |
I started having this problem too, and this is different from my own issue at #5350. Unlike my own issue which would stop randomly regardless of where in the video progress, I have been experiencing this issue when clicking a video and it would not play at all and display the error from the comment above #5370 (comment) |
So you can get a 403 forbidden (from youtube) in mid-video when skipping (over the point of already preloaded) segments? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Is this issue still present on v0.21.1? |
Wow, what happened to your name @efb4f5ff-1298-471a-8973-3d47447115dc (efb4f5ff-1298-471a-8973-3d47447115dc)? Nevermind. Tested v0.21.1 with about 30 videos and none gave the issued behaviour. Thank you for your efficient work and all you have done for the project, to all people involved! |
Of course, number 31... 403 error, as before. Here the video link and the error screenshot: CTRL-R could resolve the problem, DASH was loaded. |
|
It looks like this is not a phenomenon that touches this app only. This is a German new article from heise online: Translation into English: |
I have been getting the same inconsistent behavior. Watching this video I got there from the channel page, and I had seen the video before. Reloading the page loaded as a non legacy video |
2024-07-25 zero functionality of freetube. |
see #5456 (comment) |
v0.21.2 Beta works again. |
This issue IS fixed. We are going to do a release soon! |
For updates follow #5502 |
OK, sorry. Maybe I just had to be a bit more patient without the information about the new release. |
Functionality restored with version v0.21.3 Beta. |
Guidelines
Describe the bug
Expected Behavior
If DASH formats are available (e.g. via youtube directly) it should load these formats, not fall back to legacy low res.
Issue Labels
feature stopped working, race condition
FreeTube Version
v0.21.0 Beta
Operating System Version
Ubuntu 24.04
Installation Method
.deb
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
v0.21.0 Beta
Additional Information
I guess youtube is getting wiser with blocking freetube out by providing lower resolution than selected (in my case 1080p) and only legacy video formats to freetube. There is no error message about loading a different format, because legacy is the "right" fallback if DASH cannot be loaded.
Expected behaviour would be that when DASH is selected as the preferred video format, that it loads that video. But I guess youtube found a way to prevent this somehow. Now I am watching videos that just look awful, cannot change (or view - "show video statistics" does not work also) the video resolution, but realize that it is half (720p) or below that by the looks of it.
I think it has not so much to do with version v0.21.0 Beta, because on release date I did not have these issues. My guess is that google / youtube reacted somehow, to mostly provide low res and legacy formats to freetube.
Am I the only one getting this? Or are there more users that realize these issues?
Nightly Build
The text was updated successfully, but these errors were encountered: