| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Expose SEI data in the H.264 bitstream parser API and
extract closed captions and other things that are not
specified in the H.264 spec itself in the videoparser.
Based on patch by: Mathieu Duponchelle <mathieu@centricular.com>
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/940
|
|
|
|
|
|
|
|
|
| |
NTP timestamps are supposed to match the expected presentation
time, prefering the DTS to compute them was incorrect.
<https://www.onvif.org/specs/stream/ONVIF-Streaming-Spec.pdf>
Section 6.3.1: NTP Timestamps
|
|
|
|
|
| |
For example, when plugged after rtpgstpay, serialized events will
have neither.
|
|
|
|
|
|
| |
https://www.onvif.org/specs/stream/ONVIF-Streaming-Spec.pdf
6.3 RTP header extension
|
|
|
|
|
|
|
| |
when computing timecode metas. Depending on the value of that flag,
n_frames is to be interpreted as a number of fields or a number of
frames. As GstVideoTimeCodeMeta always deals with frames, we want
to scale that number when needed.
|
|
|
|
| |
This transforms time code SEIs into GstVideoTimeCodeMeta
|
|
|
|
|
| |
This transforms time codes from the timing SEI into
GstVideoTimeCodeMeta
|
|
|
|
|
|
| |
This debug code will help determine why certain instances of closed
captions that are present in the Picture User Data are not actually
processed by the pipeline
|
|
|
|
|
| |
VUI is an optional for SPS parse, some HEVC file has incorrect VUI
parameters but still can be decoded
|
| |
|
|
|
|
| |
It's deprecated. Just use 'inline'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 7c767f3fcd5a7b40d205bb4d588dad6c6275c729 , stream creation was
refactored to occur before potential program creation. This created
issues with pipelines such as:
gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640, height=640, framerate=25/1 ! \
x264enc ! hlssink2 target-duration=1
eg.: gst_buffer_copy_into: assertion 'bufsize >= offset + size' failed
As this reordering was actually not needed for the purpose of allowing
to specify a PCR stream, this reverts the reordering part of the
initial commit.
|
| |
|
|
|
|
|
| |
The structure passed through the prog-map can now contain a
PCR_<prog_id>=sink_<PID> key-value pair.
|
|
|
|
|
|
|
| |
The MPEG-TS packetiser should use the upstream DTS for
skew correction when running in that mode, as the DTS
carries the upstream arrival time. The PTS (if it's
set at all) is less useful, and can be invalid.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gstladspa.c:360:5: error: zero-length ms_printf format string [-Werror=format-zero-length]
vad_private.c:108:3: error: this decimal constant is unsigned only in ISO C90 [-Werror]
gstdecklinkvideosink.cpp:478:32: error: comparison between 'BMDTimecodeFormat {aka enum _BMDTimecodeFormat}' and 'enum GstDecklinkTimecodeFormat' [-Werror=enum-compare]
win/DeckLinkAPI_i.c:72:8: error: extra tokens at end of #endif directive [-Werror]
win/DeckLinkAPIDispatch.cpp:35:10: error: unused variable 'res' [-Werror=unused-variable]
gstwasapiutil.c:733:3: error: format '%x' expects argument of type 'unsigned int', but argument 8 has type 'DWORD' [-Werror=format]
gstwasapiutil.c:733:3: error: format '%x' expects argument of type 'unsigned int', but argument 9 has type 'guint64' [-Werror=format]
kshelpers.c:446:3: error: missing braces around initializer [-Werror=missing-braces]
kshelpers.c:446:3: error: (near initialization for 'known_property_sets[0].guid.Data4') [-Werror=missing-braces]
|
|
|
|
|
|
|
|
| |
The way FlowCombiner combines the FLUSH doesn't work in the case
we have several "sinkpads" since any flush return FLUSH. But in the
case we have a seek where on one branch flush is done, we should
just say OK otherwise we might return FLUSHING to a src that has already
been seeked and is ready to process new buffers
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
/usr/bin/ld: .libs/libgstremovesilence_la-vad_private.o: in function `vad_set_threshold':
./gst/removesilence/vad_private.c:108: undefined reference to `pow'
/usr/bin/ld: .libs/libgstremovesilence_la-vad_private.o: in function `vad_get_threshold_as_db':
./gst/removesilence/vad_private.c:114: undefined reference to `log10'
|
|
|
|
| |
https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/138
|
|
|
|
| |
https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/137
|
|
|
|
| |
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/457
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
silence thresold was hardcoded to -60 dB, now it is configurable
using this new property
Closes #63
|
|
|
|
|
|
| |
time/buffers
Closes #63
|
|
|
|
| |
Closes #63
|
|
|
|
| |
Closes #63
|
|
|
|
|
|
| |
allows to output buffers without timestamp gap when silence is removed
Closes #63
|
|
|
|
|
|
| |
vps/sps/pps in codec_data shouldn't be considered as inband data.
Otherwise, h26{4,5}parse never insert them to nal when transform
(packetized to byte-stream) use case
|
| |
|
|
|
|
|
|
| |
infinite loop
Fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/844
|
|
|
|
|
|
|
|
|
| |
Similar change as the on I did in h264parse. We want to process SEI
recovery point as keyframe so muxers will mark them as seek points and
decoders will be able to start decoding from them rather than waiting
for an IDR.
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/790
|
|
|
|
|
|
|
| |
Don't do anything with them yet. I just copied the parsing and
processing logic from h264parse.
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/790
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The spec states that "recovery point SEI message assists a decoder in
determining when the decoding process will produce acceptable
pictures for display after the decoder initiates random access or after the
encoder indicates a broken link in the coded video sequence."
Mark those as keyframes so muxers will mark them as seek points and
decoders will be able to start decoding from them rather than waiting
for an IDR.
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/790
|
|
|
|
|
|
| |
Don't need to manually insert VPS/SPS/PPS since inband data could be useable.
Also fixes #824
|
|
|
|
|
|
| |
Don't need to manually insert SPS/PPS since inband data could be useable.
Fixes #824
|
|
|
|
|
|
| |
Mix of single and double precision leads to zero-by-zero divide
for upper 64-bit of the xmm register, even though they are not
used.
|
|
|
|
|
|
| |
Return the size / total duration as a ballpark estimate.
https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/60
|
| |
|
|
|
|
|
| |
The variable blend_mode is GstCompositorBlendMode but it is
assigned to a GstCompositorOperator enum value.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the crossfade-ratio property and replaces it with an
operator property. Currently this implements the following operators:
- SOURCE: Copy over the source and don't look at the destination
- OVER: Default blending of the source over the destination
- ADD: Like OVER but simply adding the alpha instead
See the example for how to implement crossfading with this.
https://bugzilla.gnome.org/show_bug.cgi?id=797169
|
|
|
|
|
| |
There's no reason for having this separate apart from making things less
discoverable.
|