| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Call base class's sink_event handler after handling GST_EVENT_FLUSH_STOP
event, so that base class doesn't get stuck in a 'flushing' state
https://bugzilla.gnome.org/show_bug.cgi?id=777097
|
|
|
|
|
|
|
|
| |
timecodestamper will post an element message which contains the current
timecode it just stamped. If a timecode was already found and not
replaced, it will still post it in a message.
https://bugzilla.gnome.org/show_bug.cgi?id=777048
|
|
|
|
|
|
|
|
| |
gst_pad_template_new() does not take ownership of
the caps passed to it, so we need to unref the caps.
https://bugzilla.gnome.org/show_bug.cgi?id=776790
https://bugzilla.gnome.org/show_bug.cgi?id=776787
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=776726
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=746018
|
|
|
|
|
|
| |
... rather than when determining when to end the frame.
The opportunity to do so might not come when forced to drain,
and it seems nicer anyway to do so at parse wrapup time.
|
|
|
|
|
|
| |
This happens if we had no CAPS event yet but e.g. got an EOS event. We
would then try to output a 0-sized buffer, but getting that from the
adapter will give an assertion, return NULL and then crash.
|
|
|
|
|
|
|
|
| |
If they were not ported after 4+ years it seems unlikely that anybody is
ever going to need them again. They're still in the GIT history if
needed.
https://bugzilla.gnome.org/show_bug.cgi?id=774530
|
|
|
|
|
|
| |
The return value has to be unreffed at some point.
https://bugzilla.gnome.org/show_bug.cgi?id=776334
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=776244
|
|
|
|
|
|
|
| |
Using the wrong enum there causes it to be randomly mixed with the docs
of the other enums.
https://bugs.debian.org/848297
|
|
|
|
|
|
| |
Compositor does not support it currently and it needs special support
for handling this correctly, and is rather non-trivial to implement for
all formats.
|
|
|
|
|
|
| |
The x/y coordinates could already be bigger than the configured
width/height, and adding the rectangle width/height could cause an
overflow.
|
| |
|
|
|
|
|
|
| |
Writing top-field-first vs bottom-field-first into the src caps
https://bugzilla.gnome.org/show_bug.cgi?id=775409
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=775072
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=774527
|
|
|
|
|
|
|
|
| |
Otherwise decodebin and applications are going to wait forever for pads
to appear, which is never going to happen.
Happens on this stream, which probably just need support for it added:
https://samples.mplayerhq.hu/3D/AVC_codec_in_m2ts_not_recognized/AVC_codec_not_recognized_right_video_sample.m2ts
|
|
|
|
|
|
| |
For frame->buffer, baseparse is doing that automatically for us. For
frame->output_buffer it doesn't and assumes that the subclass is already
doing that. Consistency!
|
|
|
|
|
|
|
| |
That is, aligned to the basic type for audio and to 32 bytes for video.
Fixes crashes if the raw buffers are passed to SIMD processing functions.
https://bugzilla.gnome.org/show_bug.cgi?id=774428
|
|
|
|
|
| |
Otherwise, sending an EOS event has no effect and the application waits
forever for something to happen.
|
| |
|
|
|
|
|
|
| |
Error out properly instead.
https://bugzilla.gnome.org/show_bug.cgi?id=775130
|
|
|
|
|
|
| |
Error out properly instead.
https://bugzilla.gnome.org/show_bug.cgi?id=775130
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It's completely unused currently but might be used in the future.
|
|
|
|
| |
overflow protection for error cases
|
|
|
|
| |
existing
|
|
|
|
|
| |
If the last value is already identical, there is no need in adding it
yet-another-time
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
buffers
This is useful e.g. if audio buffers should be exactly the duration of a
video frame, or if a audio buffers should never be too large because of
latency constraints.
The element is taking a fractional buffer duration, to allow working
with e.g. 1001/30000 as output duration and it accumulates rounding
errors in the buffer durations and compensates for them by making some
buffers one sample larger than the others.
https://bugzilla.gnome.org/show_bug.cgi?id=774689
|
|
|
|
|
|
| |
NAL arrays
https://bugzilla.gnome.org/show_bug.cgi?id=774896
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=774896
|
| |
|
|
|
|
|
|
| |
reading a section start
In some cases we ended up parsing sections without.
|
|
|
|
|
|
| |
And return FLUSHING instead of NOT_NEGOTIATED on flushing pads.
https://bugzilla.gnome.org/show_bug.cgi?id=774623
|
|
|
|
| |
by IQA
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We will allocate a screen area of width*height*bpp bytes, however this
calculation can easily overflow if too high width or height are given
inside the stream. Nonetheless we would just assume that enough memory
was allocated, try to fill it and overwrite as much memory as wanted.
Also allocate the screen area filled with zeroes to ensure that we start
with full-black and not any random (or not so random) data.
https://scarybeastsecurity.blogspot.gr/2016/11/0day-poc-risky-design-decisions-in.html
Ideally we should just remove this plugin in favour of the one in
gst-libav, which generally seems to be of better code quality.
https://bugzilla.gnome.org/show_bug.cgi?id=774533
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Some miscellaneous warnings about const-ness, either casting away const
where we know it's safe or removing const where it's not correct.
https://bugzilla.gnome.org/show_bug.cgi?id=774293
|
|
|
|
|
|
|
|
| |
Type cast has higher precedence than bitwise shift, so the third
argument will truncate to 8 bits and then shift right by 8 bits
resulting in constant zero.
https://bugzilla.gnome.org/show_bug.cgi?id=774293
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consistently use GST_ROUND_UP_4(width) as stride for
bayer buffers. Bayer data will usually come in widths
that are multiples of 4 anyway, so hopefully this
should not have any adverse impact on anyone in
practice.
Before, bayer2rgb required input buffers to are sized
accordingly, but then didn't actually round up when
calculating row offsets. rgb2bayer didn't use a rounded
stride nor buffer size.
https://bugzilla.gnome.org/show_bug.cgi?id=752014
|
|
|
|
|
|
|
| |
rawvideoparse wouldn't error out on not-negotiated,
but would just keep on going, because it didn't pass
the flow return value back to the parent class and
thus upstream, so the source wouldnt' stop streaming.
|