| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755459
|
|
|
|
|
|
|
|
|
|
|
| |
have a static list of segments
Otherwise we'll crash, trying to derefence NULL. And if we have no static list
of segments, we can't have repeated segments anyway.
Regression introduced by cfe2871a5e3c5b1db20470927642b776e055a87a
https://bugzilla.gnome.org/show_bug.cgi?id=755411
|
| |
|
|
|
|
|
|
| |
Otherwise we will get an ASSERT.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=755249
|
|
|
|
|
| |
557ca6fda5f831be4aba5819bf7b30b296e575cd didn't change to the
necessary gst_gl_window_resize() call for the dispmanx backend.
|
|
|
|
|
|
| |
When stopping the sink we should always hide the window.
https://bugzilla.gnome.org/show_bug.cgi?id=755249
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We might've queued up a GAP buffer that is only partially inside the current
output buffer (i.e. we received it too late!). In that case we should only
skip the part of the GAP buffer that is inside the current output buffer, not
also the remaining part. Otherwise we forward this pad too far into the future
and break synchronization.
|
|
|
|
|
|
|
| |
This a workaround until the incompatibility with CVOpenGLTextureCache
and opengl3 contexts is fixed.
https://bugzilla.gnome.org/show_bug.cgi?id=754786
|
|
|
|
|
|
|
| |
When in live mode, the queue needs to hold the currently processed
buffer and one more at least.
https://bugzilla.gnome.org/show_bug.cgi?id=754851
|
| |
|
| |
|
|
|
|
| |
Fixes compiler warnings when extra debugging is enabled at compile time.
|
|
|
|
|
|
|
| |
It was only added during 1.5.x so we might just as well remove it
immediately.
https://bugzilla.gnome.org/show_bug.cgi?id=754686
|
|
|
|
|
|
| |
Keep old define around for now.
https://bugzilla.gnome.org/show_bug.cgi?id=754686
|
|
|
|
|
| |
The state change function was implemented, but not installed,
making the compiler complain about the unused function.
|
|
|
|
|
| |
Disable code that warns about unused variables when G_DISABLE_ASSERT
is defined, as it is in tarballs and pre-releases.
|
|
|
|
|
| |
557ca6fda5f831be4aba5819bf7b30b296e575cd introduced the queueResize
call without implementing the selector
|
| |
|
|
|
|
|
|
|
|
| |
GstVideoDecoder has its own logic for detecting when to reconfigure
which ultimately calls decide_allocation and results in a new
texture cache that has not been configured from our reconfigure check.
https://bugzilla.gnome.org/show_bug.cgi?id=755156
|
|
|
|
|
|
|
| |
Fixes incorrect aspect ratio on OSX when changing caps or the 3d
output mode.
https://bugzilla.gnome.org/show_bug.cgi?id=755111
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- glimagesink needs to be able to resize the viewport on aspect ratio
changes resulting from either caps changes or 3d output mode changes.
- Performing a glViewport outside the GstGLWindow::resize callback
will not have the winsys' stack of viewports required to correctly
place the output frame.
Provide a function to request a resize on the next draw event from the
winsys.
Also track size changes inside the base GstGLWindow class rather
than in each subclass.
https://bugzilla.gnome.org/show_bug.cgi?id=755111
|
| |
|
|
|
|
| |
small typo s/width/height/
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755142
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755140
|
|
|
|
|
|
|
|
|
| |
Derive from GstVideoSink so that preroll frames will automatically
get rendered too, unless the show-preroll-frame property is set to
FALSE. Fixes intervideosrc only picking up frames if intervideosink
is in PLAYING state.
https://bugzilla.gnome.org/show_bug.cgi?id=755049
|
|
|
|
|
|
|
|
| |
Fix the negotiation of GstVideoOverlayComposition by checking
intersection with the peer caps, rather than just accept-caps,
which might only check the pad template.
https://bugzilla.gnome.org/show_bug.cgi?id=755113
|
|
|
|
| |
Implements negative repeat segment fields, defined in 5.3.9.6.1.
|
|
|
|
|
|
|
|
|
| |
The spec defines these as signed in 5.3.9.6.1.
Since we don't support this behavior, warn and default to 0
(non repeating), which is the spec's default when the value
is not present.
https://bugzilla.gnome.org/show_bug.cgi?id=752480
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=752480
|
|
|
|
| |
Fixes flashes/incorrect aspect ratio when resizing glimagesink on OSX.
|
|
|
|
|
|
|
|
|
|
|
| |
dashdemux seeks each live stream to its current fragment in the beginning, but
the base class does not know about this. Update the demuxer segment with this
seek so we generate the correct SEGMENT event and can actually play the
stream.
This needs some refactoring at some point.
https://bugzilla.gnome.org/show_bug.cgi?id=755047
|
|
|
|
|
|
|
|
| |
opus decoder can convert from different number of channels, no
need to check, just let it negotiate and create a new decoder if
needed.
https://bugzilla.gnome.org/show_bug.cgi?id=755059
|
|
|
|
|
|
|
| |
Prevents overwriting other conditions that would be more important,
such as EOS.
https://bugzilla.gnome.org/show_bug.cgi?id=755042
|
|
|
|
|
|
|
|
|
| |
Even if it doesn't actually advance the subfragment in the default way
for streams that have subfragments, it can help the base class to return
EOS when there is no more fragments instead of signaling it that it should
continue downloading.
https://bugzilla.gnome.org/show_bug.cgi?id=755042
|
|
|
|
|
|
|
|
| |
when allocating memory. Fixes crashes with avdec_h265 in the AVX2
code path which requires 32-byte stride alignment, but the
GstAllocationParams only specified a 16-byte alignment.
https://bugzilla.gnome.org/show_bug.cgi?id=754120
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=755012
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have to queue buffers based on their running time, not based on
the segment position.
Also return running time from GstAggregator::get_next_time() instead of
a segment position, as required by the API.
Also only update the segment position after we pushed a buffer, otherwise
we're going to push down a segment event with the next position already.
https://bugzilla.gnome.org/show_bug.cgi?id=753196
|
|
|
|
|
|
| |
position
https://bugzilla.gnome.org/show_bug.cgi?id=753196
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have to queue buffers based on their running time, not based on
the segment position.
Also return running time from GstAggregator::get_next_time() instead of
a segment position, as required by the API.
Also only update the segment position after we pushed a buffer, otherwise
we're going to push down a segment event with the next position already.
https://bugzilla.gnome.org/show_bug.cgi?id=753196
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=753196
|
|
|
|
|
|
| |
either
https://bugzilla.gnome.org/show_bug.cgi?id=754222
|
|
|
|
|
|
| |
include the period start timestamp
https://bugzilla.gnome.org/show_bug.cgi?id=754222
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=754222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each period will start again with pts 0 + period presentation offset, which is
also going to be the presentation time inside the container stream if any.
However all periods together should form a continuous timeline, with regard to
stream time and running time.
For making this possible we keep track of the "user requested segment", i.e.
the seek events, inside the demuxer without adjusting anything and taking this
demuxer segment only as orientation for modified segments per stream.
This per stream segments will have their segment.start at pts that would be
produced for this stream in this period, and the segment.base/time adjusted so
that this pts maps to the running and stream time this period should have in
the context of all other periods.
https://bugzilla.gnome.org/show_bug.cgi?id=754222
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 626a8f0a74f8ea748b811b74ba9e7ae2baea2cca.
This allows us to get the plain presentation offset and the period start time
separately. We have to adjust the timestamp by the presentation offset, but
the period start time should only adjust the stream time and running time.
https://bugzilla.gnome.org/show_bug.cgi?id=752409
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
all cases"
This reverts commit e671ad25a989cb21c62c7a5867c2090890ce49ba.
The timestamps should restart at 0 again for each period, but we have to
adjust the segment to map those timestamps to the actual stream time and
running time of that period.
Otherwise we would have timestamps that conflict with the ones from the tfdt
inside the MP4 container, which are restarting at 0 for each period.
https://bugzilla.gnome.org/show_bug.cgi?id=752409
|
|
|
|
|
|
| |
Otherwise we play only the first repetition of the last segment and then EOS.
https://bugzilla.gnome.org/show_bug.cgi?id=752480
|