Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
YT lying about 22(best) 720 avc+mp4a file availability, cuts connection, dupes youtube-dl into broken download #16140
Comments
|
Most likely processing was not finished at the time of downloading. Anyway address this question to Youtube not here, |
|
Like I already said in the report : It cant be a case of partially processed file (encoding error/crash) because file size was valid (270258567) WHILE it was dropping connections. You cant already know the resulting file size before finishing muxing. Size is from content-length header = file is sitting on the server visible to www deamon. Not to mention files from other reports are still inaccessible. Are you saying Its not a YT problem per se, videos work fine on their website, they seem to stopped using itag 22 internally. Its more of a YT induced problem touching youtube-dl users. youtube-dl Its almost as if Google started booby trapping itag 22, or one of the services responsible for it is failing invisibly to monitoring because nobody uses it anymore on the backend. |
I've verified and I assure that I'm running youtube-dl 2018.04.09
At least skimmed through the README, most notably the FAQ and BUGS sections
Searched the bugtracker for similar issues including closed ones
Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser
Bug report (encountered problems with youtube-dl)
Description of your issue, suggested solution and other information
"-f best" defaults to 22 when available in manifest. Here is what I got:
totally something shady server side, wget gets same connection dropped
Meanwhile after searching for this bug on the net for ~30 minutes:
Magically works 100% ok.
In #14866 user @dstftw said "Format 22 is not available at Youtube side.". This is not entirely true, YT lists this format, and partially downloaded files look ok, but server arbitrarily blocks downloading. It cant be a case of partially processed file (encoding error/crash) because file size is valid (270258567), so why close connection? File size is not even from clen tag, its returned by the server in content-length header, same server that closes connection on us! :0
I even tried MOSrkm0r-Co clip from #14866 and it still drops connection after ~700KB serving start of a valid 720 avc+mp4a file. I got curious and forced YT player to serve h264 files, but that clever beast just used separate 136 + 140 streams bypassing 22 altogether. #14733 is same problem.
Is YT suppressing this format? is 22 deprecated on YT backend and only for backward compatibility with some fringe old devices? Why would google mess with serving 22 while its clearly present server side (correct content-length header = file was there from the start).