Add delay to wait until YouTube resource is ready to be played - #1087
Open
SpazeDev wants to merge 1 commit into
Open
Add delay to wait until YouTube resource is ready to be played#1087SpazeDev wants to merge 1 commit into
SpazeDev wants to merge 1 commit into
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For a while now I have noticed that some YouTube links could not be played.
After some debugging I noticed that the started ffmpeg process exited with the error:
Error opening input files: Server returned 403 Forbidden (access denied)But when testing the same command extracted from logs manually it always worked without a problem.
After some searching I found out that at least yt-dlp contains a
available_attimestamp that matches the new delay YouTube makes us wait before a video starts.Parsing and waiting for that delay has fixed playback for me.
I'm not entirely sure if this is the best location for the check.. but moving it somewhere else would require more refactoring.