| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
Use 'copy' keyword to avoid meson warning message.
Note that 'copy' keyword in configure_file() is available
since meson 0.47.0
https://bugzilla.gnome.org/show_bug.cgi?id=797298
|
|
|
|
|
|
|
|
|
| |
If the first audio buffer to be dropped started right between two video
buffers (after the end of the first but before the start of the second,
as is often the case with N/1001 video frame rates), we would miss
sending the dropping=true message.
https://bugzilla.gnome.org/show_bug.cgi?id=797248
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tsdemux expects a custom descriptor (GST_MTS_DESC_AC3_AUDIO_STREAM)
to detect a stream as AC3 and not EAC3.
Note that tsdemux expects this descriptor because mpegtsmux writes
a stream with a HDMV registration descriptor.
Fixes:
gst-launch-1.0 -v audiotestsrc ! avenc_ac3 ! ac3parse ! mpegtsmux ! \
tsdemux ! ac3parse ! avdec_ac3 ! audioconvert ! autoaudiosink
https://bugzilla.gnome.org/show_bug.cgi?id=797220
|
|
|
|
|
|
|
|
|
|
|
| |
Previously it was dispatched before the last video buffer, and audio
buffers would follow afterwards. It's misleading to send the
dropping=true message before both streams have really stopped, it can
lead to races when someone is e.g. waiting for that message to send EOS.
Also added some debug output.
https://bugzilla.gnome.org/show_bug.cgi?id=797145
|
|
|
|
|
|
|
| |
Apply the commit ef71b61
See also https://bugzilla.gnome.org/show_bug.cgi?id=742212
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
|
| |
Apply commits 0c04e00, bf0d952 and a0876aa to h265parse.
See also https://bugzilla.gnome.org/show_bug.cgi?id=766803
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 48a1f27
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 69c09c3
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 9b50a12
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 14f6fcd
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
|
| |
Apply the commit 7d44a51
See also https://bugzilla.gnome.org/show_bug.cgi?id=732203
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
See also https://bugzilla.gnome.org/show_bug.cgi?id=732203
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Direct applying the commit 7bb6443. This could fix also unexpected
nal dropping when nonzero "config-interval" is set.
(e.g., gst-launch-1.0 videotestsrc ! x265enc key-int-max=30 !
h265parse config-interval=30 ! avdec_h265 ! videoconvert ! autovideosink)
Similar to the h264parse, have_{vps,sps,pps} variables will be used
for deciding on when to submit updated caps or not, and rather mean
"have new SPS/PPS to be submitted?"
See also https://bugzilla.gnome.org/show_bug.cgi?id=732203
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
|
| |
Adopt h264parse's _collect_nal() behavior.
See also commit 5601c87 and https://bugzilla.gnome.org/show_bug.cgi?id=732154
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 36a2aca
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
|
|
| |
Apply the commit 10ffa08
https://bugzilla.gnome.org/show_bug.cgi?id=754124
|
|
|
|
| |
get/set_property method should have been static.
|
|
|
|
|
| |
Was checking if fps_d == 60000 (instead of fps_n), causing 60000/1001 to
be always falsely interpreted as non-drop-frame
|
|
|
|
|
|
|
| |
We have a GST_DEBUG_OBJECT, which prints a guint64 with %lu which gave a
compiler warning. Used G_GUINT64_FORMAT instead.
https://bugzilla.gnome.org/show_bug.cgi?id=797036
|
|
|
|
| |
Not that the private struct is really needed here.
|
|
|
|
|
|
| |
disconts
The output is always a continguous stream without any gaps.
|
| |
|
|
|
|
|
|
| |
If we drain after a discont, the discont time given by the stream
synchronizer is already the time after the discontinuity. But we need to
drain all pending data based on the previous discont time instead.
|
|
|
|
|
|
| |
for accumulated errors
https://bugzilla.gnome.org/show_bug.cgi?id=796981
|
|
|
|
|
|
| |
Also add test to meson
https://bugzilla.gnome.org/show_bug.cgi?id=796977
|
|
|
|
|
|
|
| |
Previously negative values had the same effect as 0.0, which was
confusing.
https://bugzilla.gnome.org/show_bug.cgi?id=796845
|
|
|
|
| |
The decoder data is freed when we read more data.
|
|
|
|
|
|
|
|
| |
The case is properly handled a few lines below by dropping the buffer.
We shouldn't perpetually block the audio chain function until the
target-timecode is reached.
https://bugzilla.gnome.org/show_bug.cgi?id=796906
|
|
|
|
|
|
|
|
|
| |
This change allow setting timestamp on streams that would otherwise have
no timestamp. This is useful to make a video from bunch of JPEG files. An
example of such pipeline would be:
gst-launch-1.0 multifilesrc location=%05d.jpeg caps=image/jpeg,framerate=30/1 \
! jpegparse ! fakesink silent=0 -v
|
|
|
|
|
|
|
| |
The only plugins remaining are those that haven't been ported to Meson
yet, and msdk. Also, the tests are still automagic.
https://bugzilla.gnome.org/show_bug.cgi?id=795107
|
|
|
|
|
|
|
| |
The rest will be converted later, these are necessary for gst-build to
set options correctly.
https://bugzilla.gnome.org/show_bug.cgi?id=795107
|
|
|
|
| |
crossfading
|
|
|
|
|
|
|
|
| |
It works like a valve in front of the actual avwait. When recording ==
TRUE, other rules are then examined. When recording == FALSE, nothing is
passing through.
https://bugzilla.gnome.org/show_bug.cgi?id=796836
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
255 will easily become 0 in the blending function as they expect
the maximum value to be 255.
Can be reproduce with
gst-launch-1.0 videotestsrc pattern=ball ! c.sink_0 \
videotestsrc pattern=snow ! c.sink_1 \
compositor name=c \
sink_0::zorder=0 sink_1::zorder=1 sink_0::crossfade-ratio=0.5 \
background=black ! \
videoconvert ! xvimagesink
crossfade-ratio +/- 0.001 makes it work correctly and the same happens
at e.g. 0.25, 0.75, N*0.0625
https://bugzilla.gnome.org/show_bug.cgi?id=796846
|
|
|
|
|
|
|
| |
... not in getter. Otherwise, video-converter will not be updated
with new width/height
https://bugzilla.gnome.org/show_bug.cgi?id=796828
|
|
|
|
|
|
|
|
|
|
| |
Adds AV01 FOURCC to the list of allowed media files, in order to allow
parsing the IVF Container holding AV1 content.
At a later point dynamic resolution change can be supported - therefore
the sequence header OBU and frame header OBU of AV1 file must be parsed,
which can be done in future with the help of gst-lib gstav1parse.
https://bugzilla.gnome.org/show_bug.cgi?id=796677
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=796623
|
| |
|
|
|
|
|
| |
* If the seek was handled upstream, use that SEGMENT seqnum
* Use the proper invalid default value
|
|
|
|
|
|
| |
This field is not used and will be removed in 2.0 API.
https://bugzilla.gnome.org/show_bug.cgi?id=761462
|
|
|
|
|
|
| |
This moves all the conversion related code to a single place, allows
less code-duplication inside compositor and makes the glmixer code less
awkward. It's also the same pattern as used by GstAudioAggregator.
|
|
|
|
|
|
| |
And also trigger renegotiation if the value has changed.
https://bugzilla.gnome.org/show_bug.cgi?id=795836
|
|
|
|
|
|
|
|
|
| |
struct
The aggregated_frame is now called prepared_frame and passed to the
prepare_frame and cleanup_frame virtual methods directly. For the
currently queued buffer there is a method on the video aggregator pad
now.
|
|
|
|
|
|
| |
Not every subclass will want to expose the pads via the interface.
https://bugzilla.gnome.org/show_bug.cgi?id=739011
|