Open lnw opened 6 months ago
I suspect that this is https://github.com/yt-dlp/yt-dlp/issues/7666, but the withdrawn API is now getting 404 (no idea what you mean) instead of 410 (used to know this but not any longer).
Could be. There are some differences and I don't know the underlying structure enough to say whether it is the same underlying issue.
Whichever issue at yt-dlp it was, back-porting the latest master fixes the problem:
$ python -m youtube_dl -vF 'https://www.ardmediathek.de/video/Y3JpZDovL3N3ci5kZS9hZXgvbzIwMDQ0NjI'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-vF', u'https://www.ardmediathek.de/video/Y3JpZDovL3N3ci5kZS9hZXgvbzIwMDQ0NjI']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 625736974
[debug] Python 2.7.15 (CPython i686 32bit) - Linux-6.1.0-18-686-pae-i686-with-debian-12.5 - OpenSSL 1.1.1a 20 Nov 2018 - glibc 2.1.3
[debug] exe versions: ffmpeg 5.1.4-0, ffprobe 5.1.4-0
[debug] Proxy map: {}
[debug] Using fake IP 53.85.116.57 (DE) as X-Forwarded-For.
[ARD:mediathek] Y3JpZDovL3N3ci5kZS9hZXgvbzIwMDQ0NjI: Downloading JSON metadata
[ARD:mediathek] 13159047: Downloading m3u8 information
[info] Available formats for 13159047:
format code extension resolution note
http-main-0 mp4 unknown [deu] SD , H.264
http-main-1 mp4 unknown [deu] Full HD , H.264
hls-main-378 m3u8 480x270 [deu] 378k , avc1.4d401e, 50.0fps, mp4a.40.2
hls-main-570 m3u8 640x360 [deu] 570k , avc1.4d401f, 50.0fps, mp4a.40.2
hls-main-906 m3u8 960x540 [deu] 906k , avc1.4d401f, 50.0fps, mp4a.40.2
hls-main-1567 m3u8 1280x720 [deu] 1567k , avc1.640020, 50.0fps, mp4a.40.2
hls-main-2796 m3u8 1920x1080 [deu] 2796k , avc1.64002a, 50.0fps, mp4a.40.2
http-main-2 mp4 unknown [deu] HD Ready , H.264
http-main-3 mp4 unknown [deu] SD 480p , H.264 (best)
$
Indeed, the yt-dlp master (069b2aeda) works!
Verbose log
Description
I can't describe much more than what is written above. I'm not located in Germany, but I get the same error with a slightly older ytdl version from a machine that is located in D, so I don't think this is a geoblocking issue.