![]() ![]() ![]() At first, this seems nice, since it can continue the yt-dlp session from the last known fragment downloaded for each file (audio and video separately) using the data in the. The problem is that during bugs in the download process such as race conditions in yt-dlp or other network failures that yt-dlp does not know how to handle, sometimes the yt-dlp has to be (manually, or by a script) restarted. ![]() yt-dlp handles this by only going back so far. When using the experimental feature "-live-from-start" in yt-dlp on a long running videocam livestream in YouTube, the available fragments on the YouTube side tend to fall off the soft cliff of available fragments, at least according to yt-dlp. Provide a description that is worded well enough to be understood I've read about sharing account credentials and I'm willing to share it if required.I've read the guidelines for opening an issue.I've searched known issues and the bugtracker for similar issues including closed ones.I've checked that all provided URLs are playable in a browser with the same IP and same login details.I've verified that I'm running yt-dlp version 2023.03.04 ( update instructions) or later (specify commit).I understand that I will be blocked if I intentionally remove or skip any mandatory* field. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |