Continue the Duration query handling even if gst_pad_peer_query fails.#15
Open
jadarve wants to merge 2 commits into
Open
Continue the Duration query handling even if gst_pad_peer_query fails.#15jadarve wants to merge 2 commits into
jadarve wants to merge 2 commits into
Conversation
Member
|
It appears that there's no segment event coming from upstream. Because duration query is a fallback. Is your source supposed to be live? If there's segment event but we still use duration query then I'd prefer we don't set this duration property (with |
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
2 participants
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.
When using
intersink/srcelements to create complex pipelines, thegpacsinkhangs, and it's not able to move from PAUSED to READY.Tracing the events of the element, it seems to be an early return from the duration query handler that prevents the element from working.