Shithappenz
commented
2 years ago Thanks to @dirkf: It seems, that the API request 'http://vas.sim-technik.de/vas/live/v2/videos/%s/sources/url' % isn't working.
I can see the same issues.
In the first case, from the UK I get "video unavailable" but using --geo-bypass-country DE gives a log similar to yours. I can't see what's happening, except that the API request to
http://vas.sim-technik.de/vas/live/v2/videos/%s/sources/url % clip_idisn't working. Since no data is retrieved for any of the three failing sources, there are no formats. Why that might be is unclear: no such API calls occur when I fail to be able to play the show in the browser (presumably, proxy needed).In the second case, which doesn't need --geo-bypass-country DE, it's initially straightforward. Here is the data returned from the "videos JSON":
{u'duration': 0, u'sources': [], u'is_protected': True, u'id': u'6237106'}
Because video['is_protected'] is True, the DRM error is raised. But if it hadn't been, there are no sources (video['sources']) and so, as before, there would have been no formats, without the trouble of even asking for non-existent sources.
The extractor isn't completely broken as its tests 0, 7, 8, which are the only ones expected to pass, do succeed.
I don't have a big knowledge about programming, but I looked in the network communication of the browser: the clipid looks very strange in the videos of the 404-Error:
For example the clip https://www.prosiebenmaxx.de/anime/shakugan-no-shana/video/115-preview-folge-15-eine-neue-flame-haze-clip produces a 404 Error, too. In the source code there could be find this clipid (seach the world 'clipid').
The request http://vas.sim-technik.de/vas/live/v2/videos/%s/sources/url % clip_id failed to get the json-file. Maybe the extractor doesn't choose the right clipid or this request code doesn't exist anymore. The json-file has a token https://vas-v4.p7s1video.net/4.0/getsources?token= , but I have no idea, how the site create this token...
pukkandan
dirkf
H852ing
Checklist
Region
Germany
Description
I founded two bugs / errors on prosiebenmaxx.de: There is a Error 404 and a mafunction in the drm-protection-check. I posted both logs above. Maybe you need the geo-bypass-function to confirm these bugs. Last month the extractor worked fine. There are some clips, where I get the 404 Error (e.g. the link in the verbose log). I tryed to download it serveral times, but yt-dlp answered the same 404 Error. Maybe in the extractor there are some lines, that are not working anymore? Futhermore the drm-protection check is not working. For example yt-dlp answered, that the clip is drm protected. In the header of the side, one can read, that there is no drm protection: meta data-react-helmet="true" property="video:drm" content="0" I downloded the clip manually and vlc can play that clip. I am sorry, that I can't do more than to report the bug. I hope, we can fix it :D
Verbose log