Uh oh!
There was an error while loading. Please reload this page.
[GStreamer][MSE] Removes the use of timeouts to detect data starve and last sample stages - #21
Merged
Conversation
| void AppendPipeline::handleEndOfAppendDataMarkNeeded() | ||
| { | ||
| GstEvent* event = gst_event_new_custom(GST_EVENT_CUSTOM_DOWNSTREAM, gst_structure_new_empty("end-of-append-data-mark")); | ||
| m_appendIdMarkedInSrc = guint64(gst_event_get_seqnum(event)); |
calvarisforce-pushed
the
calvaris/timeouts
branch
from
February 10, 2016 16:36
e0d312c to
b35e2a4Compare| return GST_PAD_PROBE_OK; | ||
| guint id = gst_event_get_seqnum(event); | ||
| TRACE_MEDIA_MESSAGE("custom downstream event id=%d", id); |
calvaris
commented
Feb 10, 2016
MemberAuthor
Thx for the comments, I'll fix these tomorrow morning. There seems to be also some other typos, like "reinsterting". |
For this we use custom events. Signed-off-by: Xabier Rodriguez Calvar <calvaris@igalia.com>
They only assert if reached.
Instead of deferring to the main thread with timeouts, we always put the message through the bus as an application message. We get the message and move the state if we are in Sampling instead of Ongoing.
This method does not blindly declares the end of the append operation, it does the checks that were done in some cases before calling that method. Also, we reset to 0 the mark received at the sink when it was dealt with.
In some cases current custom events can go thru the appsrc src pad before the buffer itself, causing that the buffer is not processed. Now we send a probe for buffers in the appsrc src pad and when a buffer goes thru, we engage the process of marking the end of the append. The end of the append is done at the main thread by sending an application message thru the bus.
This renames the appsink probe functions and attributes.
calvarisforce-pushed
the
calvaris/timeouts
branch
from
February 11, 2016 10:39
b35e2a4 to
ebd0852Comparetypefind is causing problems by swaling some buffers and not letting that information go through
In same rare cases, specially in test 30, where appends happen with not enough data, qtdemux stalls waiting for data and append never ends. This is a case that should happen very rarely so I reinstated the timeout to resolve that issue while we find and alternate and more robust solution.
According to Phil's review.
calvarisforce-pushed
the
calvaris/timeouts
branch
from
February 11, 2016 10:43
ebd0852 to
dc98ea8Compare| public: | ||
| enum AppendStage { Invalid, NotStarted, Ongoing, KeyNegotiation, DataStarve, Sampling, LastSample, Aborting }; | ||
| static const unsigned int s_dataStarvedTimeoutMsec = 1000; |
Member
There was a problem hiding this comment.
The lower this value is (while keeping things working), the better.
MemberAuthor
There was a problem hiding this comment.
Yes and no. This case is triggered only in cases happening not very often at all so it is not a performance loss and you also told me that having these low timeouts could cause issues in Debug mode, etc. Because of these reasons I increased the value and I think 2s is ok for the cases it has to be triggered.
philn added a commit
that referenced
this pull request
Feb 11, 2016
[GStreamer][MSE] Removes the use of timeouts to detect data starve and last sample stages
zdobersek added a commit
that referenced
this pull request
May 12, 2016
README.md: improve instructions
Closed
This was referenced Mar 30, 2021
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The timeouts were kept and raising an error and an ASSERT to be able to detect any possible regressions in the near future. If this goes were, we can remove the timeouts.
This implementation was based on an initial one by @eocanha and I corrected the pending issues.