-
Notifications
You must be signed in to change notification settings - Fork 10k
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
[curiositystream] Downloading entirely broken due to API changes #26845
Comments
your link https://curiositystream.com/video/3818 works ok for me |
If you do that without providing a username/password you'll get only a sample video. Attempting to download it with a username and password will give the original error I posted. |
have you tried using the cookies option ?? |
It's not a authentication problem as far as I can see. I've downloaded the source code and get the correct API responses and can even get it to download by making some modifications however it appears they've made some changes to their API that means there are now mpds(when the file to download is a .mov), a V1 and V2 api and when downloading collections sometimes those collections have collections inside them. |
* https://github.com/ytdl-org/youtube-dl: [cbssports] fix extraction(closes ytdl-org#28682) [jamendo] fix track extraction(closes ytdl-org#28686) [curiositystream] fix format extraction(closes ytdl-org#26845, closes ytdl-org#28668) release 2021.04.07 [ChangeLog] Actualize [ci skip] [youtube] Fix videos with restricted location (closes ytdl-org#28685)
Checklist
Verbose log
Description
From what I can see the API now returns a url to a MPD file instead of m3u8. There is also a V2 API that is required for accessing collections. At present accessing a url such as https://app.curiositystream.com/collections/2 via the V1 api actually refers to an entirely different set of videos.
There also appears to be a few extra headers that are required to have the API return the correct data when doing the extraction.
I've been able to make changes to a local copy of youtube-dl to fix it however I'm not 100% sure on how to structure the changes to allow access to both the V1 and V2 apis.
Happy to provide any other information about what is required to get this to work.
The text was updated successfully, but these errors were encountered: