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.
REQ: build information cache; combined search #858
Comments
|
+1 for the second ability: multiple filters, so i can search for a specific video from a specific user [: |
|
To avoid issues here on GitHub from becoming too messy, we ignore all but the first request per issue (unless the requests are related). Luckily, your second request is already implemented - As to the cache: The problem with any form is cache invalidation. In most of the youtube feeds I watch, the videos get uploaded with a title like I'm not saying a cache could not be useful, although I do wonder what a cache of say the video uploader would be useful for. Why would that help you? Can you elaborate a bit on your usage scenario, e.g. what fields you need for what purpose, how do you use youtube-dl (Python API, command-line, ...), what a typical command looks like? |
|
Simple. I'd like to subscribe to a channel with several thousand videos and I want to check for updates, say, hourly. Now that means redownloading and -parsing loads of metadata on every update. And I have quite some channels I watch, which exaggaretes the problem even more. On the other hand I think I don't watch even one channel where metadata gets changed after publishing so the problem with cache invalidation would be tiny to non-existant. Besides wouldn't it be possible to fetch the video IDs sorted by date and wouldn't this date be updated when metadata like the title changes? Even if not you could make the cache optional. It's just that it feels insane to download and parse over 5000 video metadata items every hour. And that's just ONE channel! |
|
Just saw that youtube-dl now seems to have a Command line: Expected result: cache of metadata is created and successive calls don't re-download the metadata. Actual result: no cache what-so-ever is created and successive calls download metadata all over again. |
|
|
|
The commit doesn't clarify anything. Still one can't know what is actually cached. What does this cache then do? I haven't actually seen youtube-dl write anything in the cache location - not a single file with whatever content. Also: I hope the elaboration of my use case was detailed enough. |
I'd love to use youtube-dl to completely automate my day-to-day youtube needs ;) However it misses some functionality, that is:
with these additions one could automate downloading regular videos from users and only download those that one's interested in... also the cache would speed things up imensely if the ids are retrieved sorted by date...
cheers