Player makes range requests, YouTube responds with incorrect content lengths #750
Comments
|
This has since been reported by a couple other folks as well. Testing a broken URL with curl returned an empty response body (with the incorrect I wouldn't be surprised if TeamNewPipe/NewPipe#2623 also fixed this issue. Unfortunately I'm having trouble getting a new link to test with, so I expect this is likely resolved. |
|
My mistake, I can still reproduce this on some videos. YouTube appears to only be returning the first chunk in this case (which normally includes metadata/initialization info). It may be an issue that the video is still being processed, although I'm able to reproduce it on videos that are week+ old. 🤷♂️ |
|
What's the reason not to use MPEG-DASH by default? It yields a much better quality anyway, and the player can adapt to the network more easily. |
|
See #616. The main reason is because streams need to be proxied, which puts more load on the instance. |
|
Interesting. Not sure why proxying would be needed, NewPipe doesn't proxy either. But I guess you have your reasons. |
|
There's some more info in this comment as well. Browsers enforce CORS which means it isn't possible to work with streams from YouTube directly, at least for the APIs needed to combine audio+video. youtube-dl, FreeTube, NewPipe, etc. don't have to worry about this, since they have much more control over the requests they make. |
|
Ah, I see. Was looking for a reason in the issues, but must've missed that comment. Makes perfect sense, and is really annoying. Proxying is kind of dangerous, depending on the copyright laws this might be serving unauthorized copies... I guess we finally need a desktop app built upon NewPipe(Extractor) or whatever backend that can handle CORS issues. |
|
Testing a bit more, I'm only able to reproduce with files in format |
|
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
|
This issue has been automatically locked since there has not been any activity in it in the last 30 days. If this is still applicable to the current version of Invidious feel free to open a new issue. |
As mentioned over at TeamNewPipe/NewPipe#2615 (comment), I discovered an issue with a few selective videos on YouTube which I tried to play back on invidious. I couldn't recall the exact URLs I used back then, but after looking a bit, I found one that is broken.
On https://invidio.us/watch?v=ppuKO2W9D_8, the following log is produced:
My initial assumption that YouTube was trying to be annoying here seems to be unsubstantiated, since the DASH playback version (
&quality=dash, which by the way should IMO be the default) works just fine.I couldn't find any other broken videos any more, nor could I find out why this is occurring, it just seems to me that YouTube has an issue on this one specific video that is unrelated to invidious. Nevertheless, as @omarroth invited me to post it here, I wanted to do so. Please let me know if you need any further information. Might as well be one of my privacy plugins, I can't tell for sure (they're all the same on all computers). I can try on some other setup later, I plan to test some stuff in some live ISO VM environments where there's vanilla browsers.
The text was updated successfully, but these errors were encountered: