summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim-Philipp Müller <tim@centricular.com>2019-01-17 02:38:28 +0000
committerTim-Philipp Müller <tim@centricular.com>2019-01-17 02:38:29 +0000
commitda512c2fdcc6cec0a78e88c68537e73e50b42a10 (patch)
tree253219d2eb9d02a45278586005456ceb31cab9cf
parent09ad21b26c765a642f532e27e586f45a15aaa6fd (diff)
Release 1.15.11.15.1
Diffstat
-rw-r--r--ChangeLog657
-rw-r--r--NEWS1051
-rw-r--r--RELEASE34
-rw-r--r--configure.ac6
-rw-r--r--gst-omx.doap10
-rw-r--r--meson.build2
6 files changed, 1702 insertions, 58 deletions
diff --git a/ChangeLog b/ChangeLog
index 60616dc..ab2689d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,660 @@
+=== release 1.15.1 ===
+
+2019-01-17 02:38:28 +0000 Tim-Philipp Müller <tim@centricular.com>
+
+ * ChangeLog:
+ * NEWS:
+ * RELEASE:
+ * configure.ac:
+ * gst-omx.doap:
+ * meson.build:
+ Release 1.15.1
+
+2018-02-20 10:57:42 -0800 Varunkumar Allagadapa <varunkum@xilinx.com>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: Add dynamic IDR insertion support on zynq
+ As the pi, the zynq has its own API to request keyframe.
+
+2019-01-07 13:29:37 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.com>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxbufferpool.c:
+ omxbufferpool: fix race when releasing input buffers
+ If buffers were released from the pool while
+ gst_omx_video_enc_handle_frame() was waiting for new buffers,
+ gst_omx_port_acquire_buffer() was never awaken as the buffers weren't
+ released through OMX's messaging system.
+ GQueue isn't thread safe so also protect it with the lock mutex.
+
+2018-11-15 11:17:59 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxbufferpool.c:
+ * omx/gstomxbufferpool.h:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omxbufferpool: fix early input buffer release
+ We used to track the 'allocating' status on the pool. It is used while
+ allocating so output buffers aren't passed right away to OMX and input
+ ones are not re-added to the pending queue.
+ This was causing a bug when exporting buffers to v4l2src. On start
+ v4l2src acquires a buffer, read its stride and release it right away.
+ As no buffer was received by the encoder element at this point, 'allocating'
+ was still on TRUE and so the the buffer wasn't put back to the pending
+ queue and, as result, no longer available to the pool.
+ Fix this by checking the active status of the pool instead of manually
+ tracking it down. The pool is considered as active at the very end of
+ the activation process so we're good when buffers are released during
+ the activation.
+
+2018-12-05 17:24:48 -0300 Thibault Saunier <tsaunier@igalia.com>
+
+ * common:
+ Automatic update of common submodule
+ From ed78bee to 59cb678
+
+2018-11-23 12:57:15 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.com>
+
+ * omx/gstomx.c:
+ omx: fix OMX_EventBufferFlag OMX_API_TRACE struct
+ The GType was missing from the second field of the struct.
+
+2018-11-05 05:43:43 +0000 Matthew Waters <matthew@centricular.com>
+
+ * .gitmodules:
+ * gst-omx.doap:
+ Update git locations to gitlab
+
+2018-09-18 16:50:11 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: rename OMX_PERFORMANCE debug cat to OMX_API_TRACE
+ This debug category can now be used to track more OMX calls and events
+ so best to rename it to something more generic.
+ https://bugzilla.gnome.org/show_bug.cgi?id=797171
+
+2018-08-21 17:35:04 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: log OMX commands with OMX_PERFORMANCE debug category
+ It has been useful to have a clear raw and structured view of the gst
+ <-> OMX exchanges when debugging.
+ https://bugzilla.gnome.org/show_bug.cgi?id=797171
+
+2018-08-21 16:50:38 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: factor out gst_omx_component_send_command()
+ No semantic change. I'm going to add extra debug in this function.
+ https://bugzilla.gnome.org/show_bug.cgi?id=797171
+
+2018-08-21 15:14:09 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: log OMX events with OMX_PERFORMANCE debug category
+ It has been useful to have a clear raw and structured view of the gst
+ <-> OMX exchanges when debugging.
+ https://bugzilla.gnome.org/show_bug.cgi?id=797171
+
+2018-08-22 12:51:30 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: rename log_omx_performance() to log_omx_performance_buffer()
+ I'm about to log more things under this category
+ https://bugzilla.gnome.org/show_bug.cgi?id=797171
+
+2018-09-07 22:57:30 -0400 Nicolas Dufresne <nicolas.dufresne@collabora.com>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: Remove spurious locking
+ The method we call in the context of pushing a buffer are all thread
+ safe. Holding a lock would prevent input buffers from being queued while
+ pushing.
+ https://bugzilla.gnome.org/show_bug.cgi?id=715192
+
+2018-09-07 23:09:29 -0400 Nicolas Dufresne <nicolas.dufresne@collabora.com>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: Remove unneeded size check
+ We only enter this branch if nFilledLen > 0, there is not need
+ to check again.
+ https://bugzilla.gnome.org/show_bug.cgi?id=715192
+
+2018-09-07 22:55:41 -0400 Nicolas Dufresne <nicolas.dufresne@collabora.com>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: Remove spurious unlock in error case
+ This was forgotton in previous patch. We no long hold the lock when goto
+ invalid_buffer is called.
+ https://bugzilla.gnome.org/show_bug.cgi?id=715192
+
+2018-08-31 17:28:03 -0400 Nicolas Dufresne <nicolas.dufresne@collabora.com>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: don't hold the stream lock when trying to push a frame
+ The base class methods will lock this properly when needed, there seems
+ to be no need to lock it explicitly.
+ This allows the patch in gstvideodec for unlocking the stream lock
+ when pushing buffers out to work.
+ https://bugzilla.gnome.org/show_bug.cgi?id=715192
+
+2018-07-31 13:22:31 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: don't import OMX buffers from downstream
+ We already have code configuring the encoder stride and slice height
+ when receiving the first buffer from upstream.
+ We don't have an equivalent when the encoder is exporting its buffers to the
+ decoder.
+ There is no point adding it and making the code even more
+ complex as we wouldn't gain anything by exporting from the encoder to
+ the decoder. The dynamic buffer mode already ensures 0-copy between OMX
+ components.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-15 11:59:26 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxbufferpool.c:
+ * omx/gstomxvideoenc.c:
+ * omx/gstomxvideoenc.h:
+ omxvideoenc: implement dmabuf export on input buffers
+ Propose pool upstream so input buffers can be allocated by the port and
+ exported as dmabuf.
+ The actual OMX buffers are allocated when the pool is activated, so we
+ don't end up doing useless allocations if the pool isn't used.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-08-13 15:10:37 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxaudiodec.c:
+ * omx/gstomxaudioenc.c:
+ * omx/gstomxaudiosink.c:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omx: allow gst_omx_port_acquire_buffer() to not wait for buffers
+ Will be needed to implement GST_BUFFER_POOL_ACQUIRE_FLAG_DONTWAIT.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-31 15:04:33 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: don't import non-dmabuf when dec is in dmabuf mode
+ Fix 'omxh264dec ! videocrop' pipeline.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-08-02 11:29:12 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: factor out gst_omx_try_importing_buffer()
+ No semantic change, just make the code clearer and improve debug output.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-26 16:30:08 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: fix gst_video_info_from_caps() caps assertion
+ The "use buffers" code path uses gst_video_info_from_caps() which is
+ asserting if caps is NULL (because pool was rejected).
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-26 16:22:50 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: fix pool caps reference stealing
+ gst_buffer_pool_config_get_params() doesn't ref the returning caps;
+ so gst_caps_replace() was unreffing the reference owned by the pool.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-25 09:57:20 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: prevent timeout when shutting down because of pending out buffers
+ The OMX transition state to Loaded won't be complete until all buffers
+ have been freed. There is no point waiting, and timeout, if we know that
+ output buffers haven't been freed yet.
+ The typical scenario is output buffers being still used downstream
+ and being freed later when released back to the pool.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-24 15:14:31 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxbufferpool.c:
+ omxbufferpool: reference the OMX component
+ Now that the pool is responsible of freeing the OMX buffers, we need to
+ ensure that the OMX component stay alive while the pool is as we rely on
+ the component to free the buffers.
+ The GstOMXPort is owned by the component so no need to ref this one.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-07-24 15:06:01 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxaudiodec.c:
+ * omx/gstomxaudioenc.c:
+ * omx/gstomxaudiosink.c:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ turn GstOMXComponent to a GstMiniObject
+ Will use it for refcounting.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-28 12:20:45 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxbufferpool.c:
+ * omx/gstomxvideodec.c:
+ omxbufferpool: deallocate OMX buffers when stopping
+ The pool is stopped when all the buffers have been released. Deallocate
+ when stopping so we are sure that the buffers aren't still used by
+ another element.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-24 16:28:21 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: call gst_omx_buffer_unmap() when handling BUFFER_DONE
+ When using a input buffer pool, the buffer may be released to the pool when
+ gst_omx_buffer_unmap() is called. We need to have buf->used unset at
+ this point as the pool may use it to check the status of the pool.
+ {Empty,Fill}BufferDone is called from OMX internal threads while
+ messages are handled from gst elements' thread. Best to do all this
+ when handling the message so we don't mess with OMX threads and keep
+ the original thread/logic split.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-25 14:44:16 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omxvideo{enc,dec}: stop calling shutdown() in change_state
+ This is no longer needed since we implemented close() vfuncs as the
+ encoder/decoder base class already take care of calling close() (which
+ is calling shutdown()) in its own change_state implementation.
+ We also move the shut down of the component from PAUSED_TO_READY to READY_TO_NULL.
+ By doing so upstream will have already deactivated the pool from the
+ encoder and so won't be preventing the OMX state change as the buffers
+ will all be released.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-15 16:21:26 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxbufferpool.c:
+ omx: factor out gst_omx_buffer_get/set_omx_buf()
+ Move the qdata code to helper functions as I'm going to need them in
+ omxvideoenc to implement dmabuf export.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-15 11:01:13 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: factor out gst_omx_video_enc_set_to_idle()
+ No semantic change. We'll have to use this when the input pool is
+ activated so we can allocate buffers.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-15 09:56:10 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: factor out gst_omx_video_enc_deallocate_in_buffers()
+ Will add extra code when adding input buffer pool.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-05-14 15:16:38 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: add pBuffer to OMX_PERFORMANCE logs
+ Can be useful to check the fd being passed when using dmabuf.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-03-21 12:43:33 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omx: factor out gst_omx_port_set_dmabuf()
+ No semantic change. I also made the debug message a bit clearer.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796918
+
+2018-08-22 15:56:18 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: wait for flush complete and buffers being released when flushing
+ When flusing we should wait for OMX to send the flush command complete event
+ AND all ports being released.
+ We were stopping as soon as one of those condition was met.
+ Fix a race between FillThisBufferDone/EmptyBufferDone and the flush
+ EventCmdComplete messages. The OMX implementation is supposed to release
+ its buffers before posting the EventCmdComplete event but the ordering
+ isn't guaranteed as the FillThisBufferDone/EmptyBufferDone and
+ EventHandler callbacks can be called from different threads (cf 2.7
+ 'Thread Safety' in the spec).
+ Only wait for buffers currently used by OMX as some buffers may not be
+ in the pending queue because they are held downstream.
+ https://bugzilla.gnome.org/show_bug.cgi?id=789475
+
+2018-08-22 15:52:23 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: factor out should_wait_until_flushed()
+ No semantic change. Makes the code easier to understand and I'm about to
+ change the waiting condition.
+ https://bugzilla.gnome.org/show_bug.cgi?id=789475
+
+2018-08-28 13:10:35 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: pause component when flushing
+ As stated in the spec ("6.1.3 Seek Event Sequence") we should pause
+ before flushing.
+ We were pausing the decoder but not the encoder so I just aligned the
+ two code paths.
+ https://bugzilla.gnome.org/show_bug.cgi?id=797038
+
+2018-07-12 12:41:18 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: fix vertical padding in NV16 formats
+ My previous patch to calculate the vertical padding was always halfing
+ the height of the chroma plane which is incorrect for NV16 formats.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796749
+
+2018-07-05 15:13:47 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: include vertical padding in nFilledLen when copying
+ According to the OMX spec (3.1.3.7.1) nFilledLen is meant to include any
+ padding. We use to include the horizontal one (stride) but not the
+ vertical one if nSliceHeight is bigger than the actual height.
+ The calculated nFilledLen was wrong as it didn't include the padding
+ between planes.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796749
+
+2018-04-26 12:30:47 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ * omx/gstomxvideoenc.h:
+ omxvideoenc: implement decide_allocation
+ Increase the number of output buffers by the number of buffers requested
+ downstream.
+ Prevent buffers starvation if downstream is going to use dynamic buffer
+ mode on its input.
+ https://bugzilla.gnome.org/show_bug.cgi?id=795746
+
+2018-04-26 12:29:16 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: implement propose_allocation
+ Tell upstream about how many buffer we plan to use so they can adjust
+ their own number of buffers accordingly if needed.
+ Same logic as the existing gst_omx_video_enc_propose_allocation().
+ https://bugzilla.gnome.org/show_bug.cgi?id=795746
+
+2018-05-17 09:54:11 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ * omx/gstomxvideoenc.h:
+ omxvideoenc: always signal drain cond when stopping streaming loop
+ Similar change as the one I just did in omxvideodec.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796207
+
+2018-05-16 17:06:29 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideodec.h:
+ omxvideodec: always signal drain cond when stopping streaming loop
+ If for some reason something goes wrong and we stop the streaming loop
+ we may end up with other threads still waiting on the drain cond.
+ No more buffers will be produced by the component so they were waiting
+ forever.
+ Fix this by always signalling this cond when stopping the streaming
+ loop.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796207
+
+2018-05-16 17:02:01 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideoenc: factor out gst_omx_video_enc_pause_loop()
+ No semantic change. I'm going to use it in more failure cases.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796207
+
+2018-05-17 14:24:52 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * config/zynqultrascaleplus/gstomx.conf:
+ zynqultrascaleplus: enable 'ensure-buffer-count-actual' hack
+ https://bugzilla.gnome.org/show_bug.cgi?id=791211
+
+2018-04-27 16:26:36 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ * omx/gstomx.h:
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omxvideodec/enc: add hack updating nBufferCountActual before allocating
+ The OMX specs states that the nBufferCountActual of a port has to default
+ to its nBufferCountMin. If we don't change nBufferCountActual we purely rely
+ on this default. But in some cases, OMX may change nBufferCountMin before we
+ allocate buffers. Like for example when configuring the input ports with the
+ actual format, it may decrease the number of minimal buffers required.
+ This method checks this and update nBufferCountActual if needed so we'll use
+ less buffers than the worst case in such scenarios.
+ SetParameter() needs to be called when the port is either disabled or
+ the component in the Loaded state.
+ Don't do this for the decoder output as
+ gst_omx_video_dec_allocate_output_buffers() already check
+ nBufferCountMin when computing the number of output buffers.
+ On some platform, like rpi, the default nBufferCountActual is much
+ higher than nBufferCountMin so only enable this using a specific gst-omx
+ hack.
+ https://bugzilla.gnome.org/show_bug.cgi?id=791211
+
+2018-05-28 15:02:13 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omxvidee{enc,dec}: refresh input port definition after setting format
+ Setting the input format and the associated encoder/decoder settings
+ may also affect the nBufferCountMin of the input port.
+ Refresh the input port so we'll use up to date values in propose/decide
+ allocation.
+ https://bugzilla.gnome.org/show_bug.cgi?id=796445
+
+2018-05-07 11:59:08 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ omx: always consider component in 'invalid' state when an error occured
+ gst_omx_component_get_state() used to early return if there was no
+ pending state change. So if the component raised an error it wasn't
+ considered in the invalid state until the next requested state change.
+ Fix this by checking first if we received an error.
+ https://bugzilla.gnome.org/show_bug.cgi?id=795874
+
+2018-05-25 01:35:58 +1000 Matthew Waters <matthew@centricular.com>
+
+ * meson.build:
+ * meson_options.txt:
+ meson: Update option names to omit 'with_omx' prefixes
+ Companion commit to:
+ https://cgit.freedesktop.org/gstreamer/gstreamer/commit/?id=4fb02fc85b70be631f5331b2547e5dc61ef7a43a
+ https://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=1e1a5d658e4a031535c44823fd398d3052ca2000
+ etc...
+
+2018-03-21 13:52:23 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ omxvideodec: pass a GstOMXBufferMode to gst_omx_buffer_pool_new()
+ The output_mode is supposed to be a GstOMXBufferMode, not a boolean.
+
+2018-05-03 09:27:15 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * config/zynqultrascaleplus/gstomx.conf:
+ zynq: remove 'no-disable-outport' hack
+ No longer needed with newer version of the OMX stack.
+
+2018-03-13 16:15:30 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxh264enc.c:
+ * omx/gstomxh265enc.c:
+ omxh26{4,5}enc: don't pick default 10-bit profile
+ The OMX stack of the zynqultrascaleplus (the only one supporting
+ NV12_10LE32 and NV16_10LE32) will now pick the proper profile if none
+ has been requested. Best to rely on its default than hardcoding a
+ specific one in gst-omx.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794319
+
+2018-03-06 14:16:56 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxh264utils.c:
+ omxh264: sync with supported profiles on zynqultrascaleplus
+ Add extra supported AVC profiles and remove extended and 4:4:4 profiles
+ which are actually not implemented.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794177
+
+2018-03-06 10:45:14 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxh264enc.c:
+ * omx/gstomxh264utils.c:
+ * omx/gstomxh264utils.h:
+ omxh264: factor out gst_omx_h264_utils_get_profile_from_enum()
+ Move the profile <-> enum mapping to one place. Make changes easier as
+ I'm about to add extra profiles.
+ No semantic change.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794177
+
+2018-03-06 11:02:44 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxh265utils.c:
+ omxh265: add format range extension profiles on zynqultrascaleplus
+ The zynqultrascaleplus OMX gained support for more format range
+ extensions profiles (A.3.5).
+ https://bugzilla.gnome.org/show_bug.cgi?id=794177
+
+2018-03-06 10:45:14 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxh265enc.c:
+ * omx/gstomxh265utils.c:
+ * omx/gstomxh265utils.h:
+ omxh265: factor out gst_omx_h265_utils_get_profile_from_enum()
+ Move the profile <-> enum mapping to one place. Make changes easier as
+ I'm about to add some profiles.
+ No semantic change.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794177
+
+2018-03-08 12:22:26 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: add NV16 support
+ NV16 format wasn't supported on encoder input while it was on decoder
+ output.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794175
+
+2018-03-08 12:09:38 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideo.c:
+ omxvideo: display port number when listing supported formats
+ More convenient when debugging.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794175
+
+2018-03-29 16:42:40 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.h:
+ * omx/gstomxvideoenc.c:
+ * omx/gstomxvideoenc.h:
+ omxvideoenc: restore OMX default target-bitrate if requested by user
+ 0xffffffff is the magic number in gst-omx meaning 'the default value
+ defined in OMX'. This works fine with OMX parameters which are only set
+ once when starting the component but not with configs which can be
+ changed while PLAYING.
+ Save the actual OMX default bitrate so we can restore it later if user
+ sets back 0xffffffff on the property.
+ Added GST_OMX_PROP_OMX_DEFAULT so we stop hardcoding magic numbers
+ everywhere.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794998
+
+2018-03-29 11:36:00 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: use gst_omx_video_enc_set_bitrate() when setting bitrate in set_format
+ We weren't using the usual pattern when re-setting the bitrate:
+ - get parameters from OMX
+ - update only the fields different from 0xffffffff (OMX defaults)
+ - set parameters
+ Also added a comment explaining why we re-set this param.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794998
+
+2018-03-29 11:26:04 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: factor out gst_omx_video_enc_set_bitrate()
+ No semantic change, I'm about to re-use this function in set_format().
+ https://bugzilla.gnome.org/show_bug.cgi?id=794998
+
+2018-04-20 11:54:14 +0100 Tim-Philipp Müller <tim@centricular.com>
+
+ * meson.build:
+ meson: fix miscellaneous meson warnings
+ cc.has_header*() doesn't have a 'required:' kwarg.
+
+2018-04-18 12:42:55 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideodec.c:
+ * omx/gstomxvideoenc.c:
+ omxvideoenc/dec: fix handling of component enabling failing
+ - Report the error from OMX if any (OMX_EventError)
+ - If not report the failing to the application (GST_ELEMENT_ERROR)
+ - return GST_FLOW_ERROR rather than FALSE
+ - don't leak @frame
+ https://bugzilla.gnome.org/show_bug.cgi?id=795352
+
+2018-04-16 10:53:41 +0100 Tim-Philipp Müller <tim@centricular.com>
+
+ * common:
+ Automatic update of common submodule
+ From 3fa2c9e to ed78bee
+
+2018-03-14 14:53:50 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomx.c:
+ log_omx_performance: convert pointers to strings
+ G_TYPE_POINTER are not serialized in logs.
+ https://bugzilla.gnome.org/show_bug.cgi?id=794331
+
+2018-04-02 15:14:51 +0200 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: remove duplicated debug message
+ We already have the exact same message at the beginning of
+ gst_omx_video_enc_handle_frame(). Having it twice is confusing when
+ reading/grepping logs.
+ I kept the earlier one to keep the symetry with
+ gst_omx_video_dec_handle_frame().
+ https://bugzilla.gnome.org/show_bug.cgi?id=794897
+
+2018-02-22 11:27:03 +0100 Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
+
+ * omx/gstomxvideoenc.c:
+ omxvideoenc: add 'roi' qp-mode on zynqultrascaleplus
+ New QP mode used to handle ROI metadata.
+ https://bugzilla.gnome.org/show_bug.cgi?id=793696
+
+2018-03-20 10:31:10 +0000 Tim-Philipp Müller <tim@centricular.com>
+
+ * NEWS:
+ * RELEASE:
+ * configure.ac:
+ * meson.build:
+ Back to development
+
=== release 1.14.0 ===
2018-03-19 20:31:02 +0000 Tim-Philipp Müller <tim@centricular.com>
diff --git a/NEWS b/NEWS
index 5366a0d..1e860c4 100644
--- a/NEWS
+++ b/NEWS
@@ -3,23 +3,19 @@
GSTREAMER 1.16 RELEASE NOTES
-GStreamer 1.16 has not been released yet. It is scheduled for release
-around September 2018.
+GStreamer 1.16 has not been released yet. It is scheduled for release in
+January/February 2019.
-1.15.0.1 is the unstable development version that is being developed in
+1.15.x is the unstable development version that is being developed in
the git master branch and which will eventually result in 1.16.
-The plan for the 1.16 development cycle is yet to be confirmed, but it
-is expected that feature freeze will be around August 2017 followed by
-several 1.15 pre-releases and the new 1.16 stable release in September.
-
1.16 will be backwards-compatible to the stable 1.14, 1.12, 1.10, 1.8,
1.6, 1.4, 1.2 and 1.0 release series.
See https://gstreamer.freedesktop.org/releases/1.16/ for the latest
version of this document.
-_Last updated: Tuesday 20 March 2018, 01:30 UTC (log)_
+_Last updated: Monday 14 January 2019, 13:00 UTC (log)_
Introduction
@@ -34,63 +30,705 @@ other improvements.
Highlights
-- this section will be completed in due course
+- GStreamer WebRTC stack gained support for data channels for
+ peer-to-peer communication based on SCTP, BUNDLE support, as well as
+ support for multiple TURN servers.
+
+- AV1 video codec support for Matroska and QuickTime/MP4 containers
+ and more configuration options and supported input formats for the
+ AOMedia AV1 encoder
+
+- Support for Closed Captions and other Ancillary Data in video
+
+- Spport for planar (non-interleaved) raw audio
+
+- GstVideoAggregator, compositor and OpenGL mixer elements are now in
+ -base
+
+- New alternate fields interlace mode where each buffer carries a
+ single field
+
+- WebM and Matroska ContentEncryption support in the Matroska demuxer
+
+- new WebKit WPE-based web browser source element
+
+- Video4Linux: HEVC encoding and decoding, JPEG encoding, and improved
+ dmabuf import/export
+
+- Hardware-accelerated Nvidia video decoder gained support for VP8/VP9
+ decoding, whilst the encoder gained support for H.265/HEVC encoding.
+
+- Many improvements to the Intel Media SDK based hardware-accelerated
+ video decoder and encoder plugin (msdk): dmabuf import/export for
+ zero-copy integration with other components; VP9 decoding; 10-bit
+ HEVC encoding; video post-processing (vpp) support including
+ deinterlacing; and the video decoder now handles dynamic resolution
+ changes.
+
+- The ASS/SSA subtitle overlay renderer can now handle multiple
+ subtitles that overlap in time and will show them on screen
+ simultaneously
+
+- The Meson build is now feature-complete (*) and it is now the
+ recommended build system on all platforms. The Autotools build is
+ scheduled to be removed in the next cycle.
+
+- The GStreamer Rust bindings and Rust plugins module are now
+ officially part of upstream GStreamer.
+
+- Many performance improvements
Major new features and changes
Noteworthy new API
-- this section will be filled in in due course
+- GstAggregator has a new "min-upstream-latency" property that forces
+ a minimum aggregate latency for the input branches of an aggregator.
+ This is useful for dynamic pipelines where branches with a higher
+ latency might be added later after the pipeline is already up and
+ running and where a change in the latency would be disruptive. This
+ only applies to the case where at least one of the input branches is
+ live though, it won’t force the aggregator into live mode in the
+ absence of any live inputs.
+
+- GstBaseSink gained a "processing-deadline" property and
+ setter/getter API to configure a processing deadline for live
+ pipelines. The processing deadline is the acceptable amount of time
+ to process the media in a live pipeline before it reaches the sink.
+ This is on top of the systemic latency that is normally reported by
+ the latency query. This defaults to 20ms and should make pipelines
+ such as “v4lsrc ! xvimagesink” not claim that all frames are late in
+ the QoS events. Ideally, this should replace max_lateness for most
+ applications.
+
+- RTCP Extended Reports (XR) parsing according to RFC 3611:
+ Loss/Duplicate RLE, Packet Receipt Times, Receiver Reference Time,
+ Delay since the last Receiver (DLRR), Statistics Summary, and VoIP
+ Metrics reports.
+
+- a new mode for interlaced video was added where each buffer carries
+ a single field of interlaced video, with buffer flags indicating
+ whether the field is the top field or bottom field. Top and bottom
+ fields are expected to alternate in this mode. Caps for this
+ interlace mode must also carry a format:Interlaced caps feature to
+ ensure backwards compatibility.
+
+- The video library has gained support for three new raw pixel
+ formats:
+
+ - Y410: packed 4:4:4 YUV, 10 bits per channel
+ - Y210: packed 4:2:2 YUV, 10 bits per channel
+ - NV12_10LE40: fully-packed 10-bit variant of NV12_10LE32,
+ i.e. without the padding bits
+
+- GstRTPSourceMeta is a new meta that can be used to transport
+ information about the origin of depayloaded or decoded RTP buffers,
+ e.g. when mixing audio from multiple sources into a single stream. A
+ new "source-info" property on the RTP depayloader base class
+ determines whether depayloaders should put this meta on outgoing
+ buffers. Similarly, the same property on RTP payloaders determines
+ whether they should use the information from this meta to construct
+ the CSRCs list on outgoing RTP buffers.
+
+- gst_sdp_message_from_text() is a convenience constructor to parse
+ SDPs from a string which is particularly useful for language
+ bindings.
+
+Support for Planar (Non-Interleaved) Raw Audio
+
+Raw audio samples are usually passed around in interleaved form in
+GStreamer, which means that if there are multiple audio channels the
+samples for each channel are interleaved in memory, e.g.
+|LEFT|RIGHT|LEFT|RIGHT|LEFT|RIGHT| for stereo audio. A non-interleaved
+or planar arrangement in memory would look like
+|LEFT|LEFT|LEFT|RIGHT|RIGHT|RIGHT| instead, possibly with
+|LEFT|LEFT|LEFT| and |RIGHT|RIGHT|RIGHT| residing in separate memory
+chunks or separated by some padding.
+
+GStreamer has always had signalling for non-interleaved audio, but it
+was never actually properly implemented in any elements. audioconvert
+would advertise support for it, but wasn’t actually able to handle it.
+
+With this release we now have full support for non-interleaved audio as
+well, which means more efficient integration with external APIs that
+handle audio this way, but also more efficient processing of certain
+operations like interleaving multiple 1-channel streams into a
+multi-channel stream which can be done without memory copies now.
+
+New API to support this has been added to the GStreamer Audio support
+library: There is now a new GstAudioMeta which describes how data is
+laid out inside the buffer, and buffers with non-interleaved audio must
+always carry this meta. To access the non-interleaved audio samples you
+must map such buffers with gst_audio_buffer_map() which works much like
+gst_buffer_map() or gst_video_frame_map() in that it will populate a
+little GstAudioBuffer helper structure passed to it with the number of
+samples, the number of planes and pointers to the start of each plane in
+memory. This function can also be used to map interleaved audio buffers
+in which case there will be only one plane of interleaved samples.
+
+Of course support for this has also been implemented in the various
+audio helper and conversion APIs, base classes, and in elements such as
+audioconvert, audioresample, audiotestsrc, audiorate.
+
+Support for Closed Captions and Other Ancillary Data in Video
+
+The video support library has gained support for detecting and
+extracting Ancillary Data from videos as per the SMPTE S291M
+specification, including:
+
+- a VBI (Video Blanking Interval) parser that can detect and extract
+ Ancillary Data from Vertical Blanking Interval lines of component
+ signals. This is currently supported for videos in v210 and UYVY
+ format.
+
+- a new GstMeta for closed captions: GstVideoCaptionMeta. This
+ supports the two types of closed captions, CEA-608 and CEA-708,
+ along with the four different ways they can be transported (other
+ systems are a superset of those).
+
+- a VBI (Video Blanking Interval) encoder for writing ancillary data
+ to the Vertical Blanking Interval lines of component signals.
+
+The new closedcaption plugin in gst-plugins-bad then makes use of all
+this new infrastructure and provides the following elements:
+
+- cccombiner: a closed caption combiner that takes a closed captions
+ stream and another stream and adds the closed captions as
+ GstVideoCaptionMeta to the buffers of the other stream.
+
+- ccextractor: a closed caption extractor which will take
+ GstVideoCaptionMeta from input buffers and output them as a separate
+ closed captions stream.
+
+- ccconverter: a closed caption converter that can convert between
+ different formats
+
+- line21decoder: extract line21 closed captions from SD video streams
+
+- cc708overlay: decodes CEA 608/708 captions and overlays them on
+ video
+
+Additionally, the following elements have also gained Closed Caption
+support:
+
+- qtdemux and qtmux support CEA 608/708 Closed Caption tracks
+
+- mpegvideoparse extracts Closed Captions from MPEG-2 video streams
+
+- decklinkvideosink can output closed captions and decklinkvideosrc
+ can extract closed captions
+
+- playbin and playbin3 learned how to autoplug CEA 608/708 CC overlay
+ elements
+
+The rsclosedcaption plugin in the Rust plugins collection includes a
+MacCaption (MCC) file parser and encoder.
New Elements
-- this section will be filled in in due course
+- overlaycomposition: New element that allows applications to draw
+ GstVideoOverlayCompositions on a stream. The element will emit the
+ "draw" signal for each video buffer, and the application then
+ generates an overlay for that frame (or not). This is much more
+ performant than e.g. cairooverlay for many use cases, e.g. because
+ pixel format conversions can be avoided or the blitting of the
+ overlay can be delegated to downstream elements (such as
+ gloverlaycompositor). It’s particularly useful for cases where only
+ a small section of the video frame should be drawn on.
+
+- gloverlaycompositor: New OpenGL-based compositor element that
+ flattens any overlays from GstVideoOverlayCompositionMetas into the
+ video stream.
+
+- glalpha: New element that adds an alpha channel to a video stream.
+ The values of the alpha channel can either be set to a constant or
+ can be dynamically calculated via chroma keying. It is similar to
+ the existing alpha element but based on OpenGL. Calculations are
+ done in floating point so results may not be identical to the output
+ of the existing alpha element.
+
+- rtpfunnel funnels together rtp-streams into a single session. Use
+ cases include multiplexing and bundle. webrtcbin uses it to
+ implement BUNDLE support.
+
+- testsrcbin is a source element that provides an audio and/or video
+ stream and also announces them using the recently-introduced
+ GstStream API. This is useful for testing elements such as playbin3
+ or uridecodebin3 etc.
+
+- New closed caption elements: cccombiner, ccextractor, ccconverter,
+ line21decoder and cc708overlay (see above)
+
+- wpesrc: new source element acting as a Web Browser based on WebKit
+ WPE
+
+- Two new OpenCV-based elements: cameracalibrate and cameraundistort
+ who can communicate to figure out distortion correction parameters
+ for a camera and correct for the distortion.
+
+- new sctp plugin based on usrsctp with sctpenc and sctpdec elements
New element features and additions
-- this section will be filled in in due course
+- playbin3, playbin and playsink have gained a new "text-offset"
+ property to adjust the positioning of the selected subtitle stream
+ vis-a-vis the audio and video streams. This uses subtitleoverlay’s
+ new "subtitle-ts-offset" property. GstPlayer has gained matching API
+ for this, namely gst_player_get_text_video_offset().
+
+- playbin3 buffering improvements: in network playback scenarios there
+ may be multiple inputs to decodebin3, and buffering will be done
+ before decodebin3 using queue2 or downloadbuffer elements inside
+ urisourcebin. Since this is before any parsers or demuxers there may
+ not be any bitrate information available for the various streams, so
+ it was difficult to configure the buffering there smartly within
+ global constraints. This was improved now: The queue2 elements
+ inside urisourcebin will now use the new bitrate query to figure out
+ a bitrate estimate for the stream if no bitrate was provided by
+ upstream, and urisourcebin will use the bitrates of the individual
+ queues to distribute the globally-set "buffer-size" budget in bytes
+ to the various queues. urisourcebin also gained "low-watermark" and
+ "high-watermark" properties which will be proxied to the internal
+ queues, as well as a read-only "statistics" property which allows
+ querying of the minimum/maximum/average byte and time levels of the
+ queues inside the urisourcebin in question.
+
+- splitmuxsink has gained a couple of new features:
+
+ - new "async-finalize" mode: This mode is useful for muxers or
+ outputs that can take a long time to finalize a file. Instead of
+ blocking the whole upstream pipeline while the muxer is doing
+ its stuff, we can unlink it and spawn a new muxer + sink
+ combination to continue running normally. This requires us to
+ receive the muxer and sink (if needed) as factories via the new
+ "muxer-factory" and "sink-factory" properties, optionally
+ accompanied by their respective properties structures (set via
+ the new "muxer-properties" and "sink-properties" properties).
+ There are also new "muxer-added" and "sink-added" signals in
+ case custom code has to be called for them to configure them.
+
+ - "split-at-running-time" action signal: When called by the user,
+ this action signal ends the current file (and starts a new one)
+ as soon as the given running time is reached. If called multiple
+ times, running times are queued up and processed in the order
+ they were given.
+
+ - "split-after" action signal to finish outputting the current GOP
+ to the current file and then start a new file as soon as the GOP
+ is finished and a new GOP is opened (unlike the existing
+ "split-now" which immediately finishes the current file and
+ writes the current GOP into the next newly-started file).
+
+ - "reset-muxer" property: when unset, the muxer is reset using
+ flush events instead of setting its state to NULL and back. This
+ means the muxer can keep state across resets, e.g. mpegtsmux
+ will keep the continuity counter continuous across segments as
+ required by hlssink2.
+
+- qtdemux gained PIFF track encryption box support in addition to the
+ already-existing PIFF sample encryption support, and also allows
+ applications to select which encryption system to use via a
+ "drm-preferred-decryption-system-id" context in case there are
+ multiple options.
+
+- qtmux: the "start-gap-threshold" property determines now whether an
+ edit list will be created to account for small gaps or offsets at
+ the beginning of a stream in case the start timestamps of tracks
+ don’t line up perfectly. Previously the threshold was hard-coded to
+ 1% of the (video) frame duration, now it is 0 by default (so edit
+ list will be created even for small differences), but fully
+ configurable.
+
+- rtpjitterbuffer has improved end-of-stream handling
+
+- rtpmp4vpay will be prefered over rtpmp4gpay for MPEG-4 video in
+ autoplugging scenarios now
+
+- rtspsrc now allows applications to send RTSP SET_PARAMETER and
+ GET_PARAMETER requests using action signals.
+
+- rtspsrc also has a small (100ms) configurable teardown delay by
+ default to try and make sure an RTSP TEARDOWN request gets sent out
+ when the source element shuts down. This will block the downward
+ PAUSED to READY state change for a short time, but can be unset
+ where it’s a problem. Some servers only allow a limited number of
+ concurren clients, so if no proper TEARDOWN is sent clients may have
+ problems connecting to the server for a while.
+
+- souphttpsrc behaves better with low bitrate streams now. Before it
+ would increase the read block size too quickly which could lead to
+ it not reading any data from the socket for a very long time with
+ low bitrate streams that are output live downstream. This could lead
+ to servers kicking off the client.
+
+- filesink: do internal buffering to avoid performance regression with
+ small writes since we bypass libc buffering by using writev()
+
+- identity: add "eos-after" property and fix "error-after" property
+ when the element is reused
+
+- input-selector: lets context queries pass through, so that
+ e.g. upstream OpenGL elements can use contexts and displays
+ advertised by downstream elements
+
+- queue2: avoid ping-pong between 0% and 100% buffering messages if
+ upstream is pushing buffers larger than one of its limits, plus
+ performance optimisations
+
+- opusdec: new "phase-inversion" property to control phase inversion.
+ When enabled, this will slightly increase stereo quality, but
+ produces a stream that when downmixed to mono will suffer audio
+ distortions.
+
+- The x265enc HEVC encoder also exposes a "key-int-max" property to
+ configure the maximum allowed GOP size now.
+
+- decklinkvideosink has seen stability improvements for long-running
+ pipelines (potential crash due to overflow of leaked clock refcount)
+ and clock-slaving improvements when performing flushing seeks
+ (causing stalls in the output timeline), pausing and/or buffering.
+
+- srtpdec, srtpenc: add support for MKIs which allow multiple keys to
+ be used with a single SRTP stream
+
+- The srt Secure Reliable Transport plugin has integrated server and
+ client elements srt{client,server}{src,sink} into one (srtsrc and
+ srtsink), since SRT connection mode can be changed by uri
+ parameters.
+
+- h264parse and h265parse will handle SEI recovery point messages and
+ mark recovery points as keyframes as well (in addition to IDR
+ frames)
+
+- webrtcbin: "add-turn-server" action signal to pass multiple ICE
+ relays (TURN servers).
+
+- The removesilence element has received various new features and
+ properties, such as a
+ "threshold"1 property, detecting silence only after minimum silence time/buffers, a“silent”property to control bus message notifications as well as a“squash”`
+ property.
+
+- AOMedia AV1 decoder gained support for 10/12bit decoding whilst the
+ AV1 encoder supports more image formats and subsamplings now and
+ acquired support for rate control and profile related configuration.
+
+- The Fraunhofer fdkaac plugin can now be built against the 2.0.0
+ version API and has improved multichannel support
+
+- kmssink now supports unpadded 24-bit RGB and can configure mode
+ setting from video info, which enables display of multi-planar
+ formats such as I420 or NV12 with modesetting. It has also gained a
+ number of new properties: The "restore-crtc" property does what it
+ says on the tin and is enabled by default. "plane-properties" and
+ "connector-properties" can be used to pass custom properties to the
+ DRM.
+
+- waylandsink has a "fullscreen" property now.
Plugin and library moves
-- this section will be filled in in due course
+- The stereo element was moved from -bad into the existing audiofx
+ plugin in -good. If you get duplicate type registration warnings
+ when upgrading, check that you don’t have a stale gststereo plugin
+ lying about somewhere.
+
+GstVideoAggregator, compositor, and OpenGL mixer elements moved from -bad to -base
+
+GstVideoAggregator is a new base class for raw video mixers and muxers
+and is based on [GstAggregator][aggregator]. It provides defined-latency
+mixing of raw video inputs and ensures that the pipeline won’t stall
+even if one of the input streams stops producing data.
+
+As part of the move to stabilise the API there were some last-minute API
+changes and clean-ups, but those should mostly affect internal elements.
+Most notably, the "ignore-eos" pad property was renamed to
+"repeat-after-eos" and the conversion code was moved to a
+GstVideoAggregatorConvertPad subclass to avoid code duplication, make
+things less awkward for subclasses like the OpenGL-based video mixer,
+and make the API more consistent with the audio aggregator API.
+
+It is used by the compositor element, which is a replacement for
+‘videomixer’ which did not handle live inputs very well. compositor
+should behave much better in that respect and generally behave as one
+would expected in most scenarios.
+
+The compositor element has gained support for per-pad blending mode
+operators (SOURCE, OVER, ADD) which determines what operator to use for
+blending this pad over the previous ones. This can be used to implement
+crossfading.
+
+A number of OpenGL-based video mixer elements (glvideomixer, glmixerbin,
+glvideomixerelement, glstereomix, glmosaic) which are built on top of
+GstVideoAggregator have also been moved from -bad to -base now. These
+elements have been merged into the existing OpenGL plugin, so if you get
+duplicate type registration warnings when upgrading, check that you
+don’t have a stale gstopenglmixers plugin lying about somewhere.
Plugin removals
-- this section will be filled in in due course
+The following plugins have been removed from gst-plugins-bad:
+
+- The experimental daala plugin has been removed, since it’s not so
+ useful now that all effort is focused on AV1 instead, and it had to
+ be enabled explicitly with --enable-experimental anyway.
+
+- The spc plugin has been removed. It has been replaced by the gme
+ plugin.
+
+- The acmmp3dec and acmenc plugins for Windows have been removed. ACM
+ is an ancient legacy API and there was no point in keeping them
+ around for a licensed mp3 decoder now that mp3 patents have expired
+ and we have a decoder in -good. We also didn’t ship these in our
+ cerbero-built Windows packages, so it’s unlikely that they’ll be
+ missed.
Miscellaneous API additions
-- this section will be filled in in due course
+- GstBitwriter: new generic bit writer API to complement the existing
+ bit reader
+
+- gst_buffer_new_wrapped_bytes() creates a wrap buffer from a GBytes
+
+- gst_caps_set_features_simple() sets a caps feature on all the
+ structures of a GstCaps
+
+- New GST_QUERY_BITRATE query: This allows determining from downstream
+ what the expected bitrate of a stream may be which is useful in
+ queue2 for setting time based limits when upstream does not provide
+ timing information. tsdemux, qtdemux and matroskademux have basic
+ support for this query on their sink pads.
+
+- elements: there is a new “Hardware” class specifier. Elements
+ interacting with hardware devices should specify this classifier in
+ their element factory class metadata. This is useful to advertise as
+ one might need to put such elements into READY state to test if the
+ hardware is present in the system for example.
+
+- protection: Add a new definition for unspecified system protection
+
+- take functions for various mini objects that didn’t have them yet:
+ gst_query_take(), gst_message_take(), gst_tag_list_take(),
+ gst_buffer_list_take(). Unlike the various _replace() functions
+ _take() does not increase the reference count but takes ownership of
+ the mini object passed.
+
+- clear functions for various mini object types and GstObject which
+ unrefs the object or mini object (if non-NULL) and sets the variable
+ pointed to to NULL: gst_clear_structure(), gst_clear_tag_list(),
+ gst_clear_query(), gst_clear_message(), gst_clear_event(),
+ gst_clear_caps(), gst_clear_buffer_list(), gst_clear_buffer(),
+ gst_clear_mini_object(), gst_clear_object()
+
+- miniobject: new API gst_mini_object_add_parent() and
+ gst_mini_object_remove_parent()to set parent pointers on mini objects to ensure correct writability: Every container of miniobjects now needs to store itself as parent in the child object, and remove itself again later. A mini object is then only writable if there is at most one parent, that parent is writable itself, and the reference count of the mini object is 1.GstBuffer(for memories),GstBufferList(for buffers),GstSample(for caps, buffer, bufferlist), andGstVideoOverlayComposition`
+ were updated accordingly. Without this it was possible to have
+ e.g. a buffer list with a refcount of 2 used in two places at once
+ that both modify the same buffer with refcount 1 at the same time
+ wrongly thinking it is writable even though it’s really not.
+
+- poll: add API to watch for POLLPRI and stop treating POLLPRI as a
+ read. This is useful to wait for video4linux events which are
+ signalled via POLLPRI.
+
+- sample: new API to update the contents of a GstSample and make it
+ writable: gst_sample_set_buffer(), gst_sample_set_caps(),
+ gst_sample_set_segment(), gst_sample_set_info(), plus
+ gst_sample_is_writable() and gst_sample_make_writable(). This makes
+ it possible to reuse a sample object and avoid unnecessary memory
+ allocations, for example in appsink.
+
+- ClockIDs now keep a weak reference to underlying clock to avoid
+ crashes in basesink in corner cases where a clock goes away while
+ the ClockID is still in use, plus some new API
+ (gst_clock_id_get_clock(), gst_clock_id_uses_clock()) to check the
+ clock a ClockID is linked to.
+
+- The GstCheck unit test library gained a
+ fail_unless_equals_clocktime() convenience macro as well as some new
+ GstHarness API for for proposing meta APIs from the allocation
+ query: gst_harness_add_propose_allocation_meta(). ASSERT_CRITICAL()
+ checks in unit tests are now skipped if GStreamer was compiled with
+ GST_DISABLE_GLIB_CHECKS.
+
+- gst_audio_buffer_truncate() convenience function to truncate a raw
+ audio buffer
+
+
+Miscellaneous performance and memory optimisations
+
+As always there have been many performance and memory usage improvements
+across all components and modules. Some of them (such as dmabuf
+import/export) have already been mentioned elsewhere so won’t be
+repeated here.
+
+The following list is only a small snapshot of some of the more
+interesting optimisations that haven’t been mentioned in other contexts
+yet:
+
+- The GstVideoEncoder and GstVideoDecoder base classes now release the
+ STREAM_LOCK when pushing out buffers, which means (multi-threaded)
+ encoders and decoders can now receive and continue to process input
+ buffers whilst waiting for downstream elements in the pipeline to
+ process the buffer that was pushed out. This increases throughput
+ and reduces processing latency, also and especially for
+ hardware-accelerated encoder/decoder elements.
+
+- GstQueueArray has seen a few API additions
+ (gst_queue_array_peek_nth(), gst_queue_array_set_clear_func(),
+ gst_queue_array_clear()) so that it can be used in other places like
+ GstAdapter instead of a GList, which reduces allocations and
+ improves performance.
+
+- appsink now reuses the sample object in pull_sample() if possible
+
+- rtpsession only starts the RTCP thread when it’s actually needed now
+
+- udpsrc uses a buffer pool now and the GstUdpSrc object structure was
+ optimised for better cache performance
GstPlayer
-- this section will be filled in in due course
+- API was added to fine-tune the synchronisation offset between
+ subtitles and video
Miscellaneous changes
-- this section will be filled in in due course
+- As a result of moving to different FFmpeg APIs, encoder and decoder
+ elements exposed by the GStreamer FFmpeg wrapper plugin (gst-libav)
+ may have seen possibly incompatible changes to property names and/or
+ types, and not all properties exposed might be functional. We are
+ still reviewing the new properties and aim to minimise breaking
+ changes at least for the most commonly-used properties, so please
+ report any issues you run into!
OpenGL integration
-- this section will be filled in in due course
+- The OpenGL mixer elements have been moved from -bad to
+ gst-plugins-base (see above)
+
+- The Mesa GBM backend now supports headless mode
+
+- gloverlaycompositor: New OpenGL-based compositor element that
+ flattens any overlays from GstVideoOverlayCompositionMetas into the
+ video stream.
+
+- glalpha: New element that adds an alpha channel to a video stream.
+ The values of the alpha channel can either be set to a constant or
+ can be dynamically calculated via chroma keying. It is similar to
+ the existing alpha element but based on OpenGL. Calculations are
+ done in floating point so results may not be identical to the output
+ of the existing alpha element.
+
+- glupload: Implement direct dmabuf uploader, the idea being that some
+ GPUs (like the Vivante series) can actually perform the YUV->RGB
+ conversion internally, so no custom conversion shaders are needed.
+ To make use of this feature, we need an additional uploader that can
+ import DMABUF FDs and also directly pass the pixel format, relying
+ on the GPU to do the conversion.
Tracing framework and debugging improvements
-- this section will be filled in in due course
+- There is now a GDB PRETTY PRINTER FOR VARIOUS GSTREAMER TYPES: For
+ GstObject pointers the type and name is added, e.g.
+ 0x5555557e4110 [GstDecodeBin|decodebin0]. For GstMiniObject pointers
+ the object type is added, e.g. 0x7fffe001fc50 [GstBuffer]. For
+ GstClockTime and GstClockTimeDiff the time is also printed in human
+ readable form, e.g. 150116219955 [+0:02:30.116219955].
+
+- GDB EXTENSION WITH TWO CUSTOM GDB COMMANDS gst-dot AND gst-print:
+
+ - gst-dot creates dot files that a very close to what
+ GST_DEBUG_BIN_TO_DOT_FILE() produces, but object properties and
+ buffer contents such as codec-data in caps are not available.
+
+ - gst-print produces high-level information about a GStreamer
+ object. This is currently limited to pads for GstElements and
+ events for the pads. The output may look like this:
+
+ (gdb) gst-print pad.object.parent
+ GstMatroskaDemux (matroskademux0) {
+ SinkPad (sink, pull) {
+ }
+ SrcPad (video_0, push) {
+ events:
+ stream-start:
+ stream-id: 0463ccb080d00b8689bf569a435c4ff84f9ff753545318ae2328ea0763fd0bec/001:1274058367
+ caps: video/x-theora
+ width: 1920
+ height: 800
+ pixel-aspect-ratio: 1/1
+ framerate: 24/1
+ streamheader: < 0x5555557c7d30 [GstBuffer], 0x5555557c7e40 [GstBuffer], 0x7fffe00141d0 [GstBuffer] >
+ segment: time
+ rate: 1
+ tag: global
+ container-format: Matroska
+ }
+ SrcPad (audio_0, push) {
+ events:
+ stream-start:
+ stream-id: 0463ccb080d00b8689bf569a435c4ff84f9ff753545318ae2328ea0763fd0bec/002:1551204875
+ caps: audio/mpeg
+ mpegversion: 4
+ framed: true
+ stream-format: raw
+ codec_data: 0x7fffe0014500 [GstBuffer]
+ level: 2
+ base-profile: lc
+ profile: lc
+ channels: 2
+ rate: 44100
+ segment: time
+ rate: 1
+ tag: global
+ container-format: Matroska
+ tag: stream
+ audio-codec: MPEG-4 AAC audio
+ language-code: en
+ }
+ }
+
+- gst_structure_to_string() now serialises the actual value of
+ pointers when serialising GstStructures instead of claiming they’re
+ NULL. This makes debug logging in various places less confusing,
+ because it’s clear now that structure fields actually hold valid
+ objects. Such object pointer values will never be deserialised
+ however.
Tools
-- this section will be filled in in due course
+- gst-inspect-1.0 has coloured output now and will automatically use a
+ pager if the output does not fit on a page. This only works in a
+ unix environment and if the output is not piped. If you don’t like
+ the colours you can disable them by setting the
+ GST_INSPECT_NO_COLORS=1 environment variable or passing the
+ --no-colors command line option.
GStreamer RTSP server
-- this section will be filled in in due course
+- Improved backlog handling when using TCP interleaved for data
+ transport. Before there was a fixed maximum size for backlog
+ messages, which was prone to deadlocks and made it difficult to
+ control memory usage with the watch backlog. The RTSP server now
+ limits queued TCP data messages to one per stream, moving queuing of
+ the data into the pipeline and leaving the RTSP connection
+ responsive to RTSP messages in both directions, preventing all those
+ problems.
+
+- Initial ULP Forward Error Correction support in rtspclientsink and
+ for RECORD mode in the server.
+
+- API to explicitly enable retransmission requests (RTX)
+
+- Lots of multicast-related fixes
+
+- rtsp-auth: Add support for parsing .htdigest files
GStreamer VAAPI
@@ -110,34 +748,350 @@ GStreamer validate
GStreamer Python Bindings
-- this section will be filled in in due course
+- add binding for gst_pad_set_caps()
+- pygobject dependency requirement was bumped to >= 3.8
-Build and Dependencies
+- new audiotestsrc, audioplot, and mixer plugin examples, and a
+ dynamic pipeline example
-- this section will be filled in in due course
+GStreamer C# Bindings
+
+- bindings for the GstWebRTC library
+
+
+GStreamer Rust Bindings
+
+The GStreamer Rust bindings are now officially part of the GStreamer
+project and are also maintained in the GStreamer GitLab.
+
+The releases will generally not be synchronized with the releases of
+other GStreamer parts due to dependencies on other projects.
+
+Also unlike the other GStreamer libraries, the bindings will not commit
+to full API stability but instead will follow the approach that is
+generally taken by Rust projects, e.g.:
+
+1) 0.12.X will be completely API compatible with all other 0.12.Y
+ versions.
+2) 0.12.X+1 will contain bugfixes and compatible new feature additions.
+3) 0.13.0 will _not_ be backwards compatible with 0.12.X but projects
+ will be able to stay at 0.12.X without any problems as long as they
+ don’t need newer features.
+
+The current stable release is 0.12.2 and the next release series will be
+0.13, probably around March 2019.
+
+At this point the bindings cover most of GStreamer core (except for most
+notably GstAllocator and GstMemory), and most parts of the app, audio,
+base, check, editing-services, gl, net. pbutils, player, rtsp,
+rtsp-server, sdp, video and webrtc libraries.
+
+Also included is support for creating subclasses of the following types
+and writing GStreamer plugins:
-Platform-specific improvements
+- gst::Element
+- gst::Bin and gst::Pipeline
+- gst::URIHandler and gst::ChildProxy
+- gst::Pad, gst::GhostPad
+- gst_base::Aggregator and gst_base::AggregatorPad
+- gst_base::BaseSrc and gst_base::BaseSink
+- gst_base::BaseTransform
+
+Changes to 0.12.X since 0.12.0
+
+Fixed
+
+- PTP clock constructor actually creates a PTP instead of NTP clock
+
+Added
+
+- Bindings for GStreamer Editing Services
+- Bindings for GStreamer Check testing library
+- Bindings for the encoding profile API (encodebin)
+
+- VideoFrame, VideoInfo, AudioInfo, StructureRef implements Send and
+ Sync now
+- VideoFrame has a function to get the raw FFI pointer
+- From impls from the Error/Success enums to the combined enums like
+ FlowReturn
+- Bin-to-dot file functions were added to the Bin trait
+- gst_base::Adapter implements SendUnique now
+- More complete bindings for the gst_video::VideoOverlay interface,
+ especially
+ gst_video::is_video_overlay_prepare_window_handle_message()
+
+Changed
+
+- All references were updated from GitHub to freedesktop.org GitLab
+- Fix various links in the README.md
+- Link to the correct location for the documentation
+- Remove GitLab badge as that only works with gitlab.com currently
+
+Changes in git master for 0.13
+
+Fixed
+
+- gst::tag::Album is the album tag now instead of artist sortname
+
+Added
+
+- Subclassing infrastructure was moved directly into the bindings,
+ making the gst-plugin crate deprecated. This involves many API
+ changes but generally cleans up code and makes it more flexible.
+ Take a look at the gst-plugins-rs crate for various examples.
+
+- Bindings for CapsFeatures and Meta
+- Bindings for
+ ParentBufferMeta,VideoMetaandVideoOverlayCompositionMeta`
+- Bindings for VideoOverlayComposition and VideoOverlayRectangle
+- Bindings for VideoTimeCode
+
+- UniqueFlowCombiner and UniqueAdapter wrappers that make use of the
+ Rust compile-time mutability checks and expose more API in a safe
+ way, and as a side-effect implement Sync and Send now
+
+- More complete bindings for Allocation Query
+- pbutils functions for codec descriptions
+- TagList::iter() for iterating over all tags while getting a single
+ value per tag. The old ::iter_tag_list() function was renamed to
+ ::iter_generic() and still provides access to each value for a tag
+- Bus::iter() and Bus::iter_timed() iterators around the corresponding
+ ::pop*() functions
+
+- serde serialization of Value can also handle Buffer now
+
+- Extensive comments to all examples with explanations
+- Transmuxing example showing how to use typefind, multiqueue and
+ dynamic pads
+- basic-tutorial-12 was ported and added
+
+Changed
+
+- Rust 1.31 is the minimum supported Rust version now
+- Update to latest gir code generator and glib bindings
+
+- Functions returning e.g. gst::FlowReturn or other “combined” enums
+ were changed to return split enums like
+ Result<gst::FlowSuccess, gst::FlowError> to allow usage of the
+ standard Rust error handling.
+
+- MiniObject subclasses are now newtype wrappers around the underlying
+ GstRc<FooRef> wrapper. This does not change the API in any breaking
+ way for the current usages, but allows MiniObjects to also be
+ implemented in other crates and makes sure rustdoc places the
+ documentation in the right places.
+
+- BinExt extension trait was renamed to GstBinExt to prevent conflicts
+ with gtk::Bin if both are imported
+
+- Buffer::from_slice() can’t possible return None
+
+- Various clippy warnings
+
+
+GStreamer Rust Plugins
+
+Like the GStreamer Rust bindings, the Rust plugins are now officially
+part of the GStreamer project and are also maintained in the GStreamer
+GitLab.
+
+In the 0.3.x versions this contained infrastructure for writing
+GStreamer plugins in Rust, and a set of plugins.
+
+In git master that infrastructure was moved to the GLib and GStreamer
+bindings directly, together with many other improvements that were made
+possible by this, so the gst-plugins-rs repository only contains
+GStreamer elements now.
+
+Elements included are:
+
+- Tutorials plugin: identity, rgb2gray and sinesrc with extensive
+ comments
+
+- rsaudioecho, a port of the audiofx element
+
+- rsfilesrc, rsfilesink
+
+- rsflvdemux, a FLV demuxer. Not feature-equivalent with flvdemux yet
+
+- threadshare plugin: ts-appsrc, ts-proxysrc/sink, ts-queue, ts-udpsrc
+ and ts-tcpclientsrc elements that use a fixed number of threads and
+ share them between instances. For more background about these
+ elements see Sebastian’s talk “When adding more threads adds more
+ problems - Thread-sharing between elements in GStreamer” at the
+ GStreamer Conference 2017.
+
+- rshttpsrc, a HTTP source around the hyper/reqwest Rust libraries.
+ Not feature-equivalent with souphttpsrc yet.
+
+- togglerecord, an element that allows to start/stop recording at any
+ time and keeps all audio/video streams in sync.
+
+- mccparse and mccenc, parsers and encoders for the MCC closed caption
+ file format.
+
+Changes to 0.3.X since 0.3.0
+
+- All references were updated from GitHub to freedesktop.org GitLab
+- Fix various links in the README.md
+- Link to the correct location for the documentation
+
+Changes in git master for 0.4
+
+- togglerecord: Switch to parking_lot crate for mutexes/condition
+ variables for lower overhead
+- Merge threadshare plugin here
+- New closedcaption plugin with mccparse and mccenc elements
+- New identity element for the tutorials plugin
+
+- Register plugins statically in tests instead of relying on the
+ plugin loader to find the shared library in a specific place
+
+- Update to the latest API changes in the GLib and GStreamer bindings
+- Update to the latest versions of all crates
+
+
+Build and Dependencies
+
+- The MESON BUILD SYSTEM BUILD IS NOW FEATURE-COMPLETE (*) and it is
+ now the recommended build system on all platforms and also used by
+ Cerbero to build GStreamer on all platforms. The Autotools build is
+ scheduled to be removed in the next cycle. Developers who currently
+ use gst-uninstalled should move to gst-build. The build option
+ naming has been cleaned up and made consistent and there are now
+ feature options to enable/disable plugins and various other features
+ on a case-by-case basis. (*) with the exception of plugin docs which
+ will be handled differently in future
+
+- Symbol export in libraries is now controlled via explicit exports
+ using symbol visibility or export defines where supported, to ensure
+ consistency across all platforms. This also allows libraries to have
+ exports that vary based on detected platform features and configure
+ options as is the case with the GStreamer OpenGL integration library
+ for example. A few symbols that had been exported by accident in
+ earlier versions may no longer be exported. These symbols will not
+ have had declarations in any public header files then though and
+ would not have been usable.
+
+- The GStreamer FFmpeg wrapper plugin (gst-libav) now depends on
+ FFmpeg 4.x and uses the new FFmpeg 4.x API and stopped relying on
+ ancient API that was removed with the FFmpeg 4.x release. This means
+ that it is no longer possible to build this module against an older
+ system-provided FFmpeg 3.x version. Use the internal FFmpeg 4.x copy
+ instead if you build using autotools, or use gst-libav 1.14.x
+ instead which targets the FFmpeg 3.x API and _should_ work fine in
+ combination with a newer GStreamer. It’s difficult for us to support
+ both old and new FFmpeg APIs at the same time, apologies for any
+ inconvenience caused.
+
+- Hardware-accelerated Nvidia video encoder/decoder plugins nvdec and
+ nvenc can be built against CUDA Toolkit versions 9 and 10.0 now. The
+ dynlink interface has been dropped since it’s deprecated in 10.0.
+
+- The (optional) OpenCV requirement has been bumped to >= 3.0.0 and
+ the plugin can also be built against OpenCV 4.x now.
+
+- New sctp plugin based on usrsctp (for WebRTC data channels)
+
+
+Platform-specific changes and improvements
Android
-- this section will be filled in in due course
+- The way that GIO modules are named has changed due to upstream GLib
+ natively adding support for loading static GIO modules. This means
+ that any GStreamer application using gnutls for SSL/TLS on the
+ Android or iOS platforms (or any other setup using static libraries)
+ will fail to link looking for the g_io_module_gnutls_load_static()
+ function. The new function name is now
+ g_io_gnutls_load(gpointer data). data can be NULL for a static
+ library. Look at this commit for the necessary change in the
+ examples.
macOS and iOS
-- this section will be filled in in due course
+- macOS binaries should be fully relocatable now
+
+- The way that GIO modules are named has changed due to upstream GLib
+ natively adding support for loading static GIO modules. This means
+ that any GStreamer application using gnutls for SSL/TLS on the
+ Android or iOS platforms (or any other setup using static libraries)
+ will fail to link looking for the g_io_module_gnutls_load_static()
+ function. The new function name is now
+ g_io_gnutls_load(gpointer data). data can be NULL for a static
+ library. Look at this commit for the necessary change in the
+ examples.
Windows
-- this section will be filled in in due course
+- The webrtcdsp element is shipped again as part of the Windows binary
+ packages, the build system issue has been resolved.
+- ‘Inconsistent DLL linkage’ warnings when building with MSVC have
+ been fixed
-Contributors
+- Hardware-accelerated Nvidia video encoder/decoder plugins nvdec and
+ nvenc build on Windows now, also with MSVC and using Meson.
-- this section will be filled in in due course
+- The ksvideosrc camera capture plugin supports 16-bit grayscale video
+ now
+
+- The wasapisrc audio capture element implements loopback recording
+ from another output device or sink
-... and many others who have contributed bug reports, translations, sent
+- wasapisink recover from low buffer levels in shared mode and some
+ exclusive mode fixes
+
+- dshowsrc now implements the GstDeviceMonitor interface
+
+
+Contributors
+
+Aleix Conchillo Flaqué, Alessandro Decina, Alexandru Băluț, Alex Ashley,
+Alexey Chernov, Alicia Boya García, Amit Pandya, Andoni Morales
+Alastruey, Andreas Frisch, Andre McCurdy, Andy Green, Anthony Violo,
+Antoine Jacoutot, Antonio Ospite, Arun Raghavan, Aurelien Jarno,
+Aurélien Zanelli, ayaka, Bananahemic, Bastian Köcher, Branko Subasic,
+Brendan Shanks, Carlos Rafael Giani, Christoph Reiter, Corentin Noël,
+Daeseok Youn, Daniel Drake, Daniel Klamt, Dardo D Kleiner, David Ing,
+David Svensson Fors, Devarsh Thakkar, Dimitrios Katsaros, Edward Hervey,
+Emilio Pozuelo Monfort, Enrique Ocaña González, Ezequiel Garcia, Fabien
+Dessenne, Fabrizio Gennari, Florent Thiéry, Francisco Velazquez,
+Freyr666, Garima Gaur, Gary Bisson, George Kiagiadakis, Georg Lippitsch,
+Georg Ottinger, Geunsik Lim, Göran Jönsson, Guillaume Desmottes, H1Gdev,
+Haihao Xiang, Haihua Hu, Harshad Khedkar, Havard Graff, He Junyan,
+Hoonhee Lee, Hosang Lee, Hyunjun Ko, Ingo Randolf, Iñigo Huguet, James
+Stevenson, Jan Alexander Steffens, Jan Schmidt, Jerome Laheurte, Jimmy
+Ohn, Joakim Johansson, Jochen Henneberg, Johan Bjäreholt, John-Mark
+Bell, John Nikolaides, Jonathan Karlsson, Jonny Lamb, Jordan Petridis,
+Josep Torra, Joshua M. Doe, Jos van Egmond, Juan Navarro, Jun Xie,
+Junyan He, Justin Kim, Kai Kang, Kim Tae Soo, Kirill Marinushkin, Kyrylo
+Polezhaiev, Lars Petter Endresen, Linus Svensson, Louis-Francis
+Ratté-Boulianne, Luis de Bethencourt, Luz Paz, Lyon Wang, Maciej Wolny,
+Marc-André Lureau, Marc Leeman, Marcos Kintschner, Marian Mihailescu,
+Marinus Schraal, Mark Nauwelaerts, Marouen Ghodhbane, Martin Kelly,
+Matej Knopp, Mathieu Duponchelle, Matteo Valdina, Matthew Waters,
+Matthias Fend, memeka, Michael Drake, Michael Gruner, Michael Olbrich,
+Michael Tretter, Miguel Paris, Mike Wey, Mikhail Fludkov, Naveen
+Cherukuri, Nicola Murino, Nicolas Dufresne, Niels De Graef, Nirbheek
+Chauhan, Norbert Wesp, Ognyan Tonchev, Olivier Crête, Omar Akkila,
+Patricia Muscalu, Patrick Radizi, Patrik Nilsson, Paul Kocialkowski, Per
+Forlin, Peter Körner, Peter Seiderer, Petr Kulhavy, Philippe Normand,
+Philippe Renon, Philipp Zabel, Pierre Labastie, Roland Jon, Roman
+Sivriver, Rosen Penev, Russel Winder, Sam Gigliotti, Sean-Der, Sebastian
+Dröge, Seungha Yang, Sjoerd Simons, Snir Sheriber, Song Bing, Soon,
+Thean Siew, Sreerenj Balachandran, Stefan Ringel, Stephane Cerveau,
+Stian Selnes, Suhas Nayak, Takeshi Sato, Thiago Santos, Thibault
+Saunier, Thomas Bluemel, Tianhao Liu, Tim-Philipp Müller, Tomasz
+Andrzejak, Tomislav Tustonić, U. Artie Eoff, Ulf Olsson, Varunkumar
+Allagadapa, Víctor Guzmán, Víctor Manuel Jáquez Leal, Vincenzo Bono,
+Vineeth T M, Vivia Nikolaidou, Wang Fei, wangzq, Whoopie, Wim Taymans,
+Wind Yuan, Wonchul Lee, Xabier Rodriguez Calvar, Xavier Claessens,
+Haihao Xiang, Yacine Bandou, Yeongjin Jeong, Yuji Kuwabara, Zeeshan Ali,
+
+… and many others who have contributed bug reports, translations, sent
suggestions or helped testing.
@@ -165,30 +1119,41 @@ the git 1.16 branch, which is a stable branch.
1.16.0
-1.16.0 is scheduled to be released around September 2018.
+1.16.0 is scheduled to be released around January/February 2019.
Known Issues
-- The webrtcdsp element is currently not shipped as part of the
- Windows binary packages due to a build system issue.
+- possibly breaking/incompatible changes to properties of wrapped
+ FFmpeg decoders and encoders (see above).
+
+- The way that GIO modules are named has changed due to upstream GLib
+ natively adding support for loading static GIO modules. This means
+ that any GStreamer application using gnutls for SSL/TLS on the
+ Android or iOS platforms (or any other setup using static libraries)
+ will fail to link looking for the g_io_module_gnutls_load_static()
+ function. The new function name is now
+ g_io_gnutls_load(gpointer data). See Android/iOS sections above for
+ further details.
Schedule for 1.18
-Our next major feature release will be 1.16, and 1.15 will be the
-unstable development version leading up to the stable 1.16 release. The
-development of 1.15/1.16 will happen in the git master branch.
+Our next major feature release will be 1.18, and 1.17 will be the
+unstable development version leading up to the stable 1.18 release. The
+development of 1.17/1.18 will happen in the git master branch.
-The plan for the 1.16 development cycle is yet to be confirmed, but it
-is expected that feature freeze will be around August 2017 followed by
-several 1.15 pre-releases and the new 1.16 stable release in September.
+The plan for the 1.18 development cycle is yet to be confirmed, but it
+is expected that feature freeze will be around July 2019 followed by
+several 1.17 pre-releases and the new 1.18 stable release in
+August/September.
-1.16 will be backwards-compatible to the stable 1.14, 1.12, 1.10, 1.8,
-1.6, 1.4, 1.2 and 1.0 release series.
+1.18 will be backwards-compatible to the stable 1.16, 1.14, 1.12, 1.10,
+1.8, 1.6, 1.4, 1.2 and 1.0 release series.
------------------------------------------------------------------------
-_These release notes have been prepared by Tim-Philipp Müller._
+_These release notes have been prepared by Tim-Philipp Müller with_
+_contributions from Sebastian Dröge._
_License: CC BY-SA 4.0_
diff --git a/RELEASE b/RELEASE
index f5def01..0ef2c5b 100644
--- a/RELEASE
+++ b/RELEASE
@@ -1,6 +1,6 @@
-This is GStreamer gst-omx 1.15.0.1.
+This is GStreamer gst-omx 1.15.1.
-GStreamer 1.15 is the development version leading up to the next major
+GStreamer 1.15 is the development branch leading up to the next major
stable version which will be 1.16.
The 1.15 development series adds new features on top of the 1.14 series and is
@@ -11,8 +11,8 @@ Full release notes will one day be found at:
https://gstreamer.freedesktop.org/releases/1.16/
-Binaries for Android, iOS, Mac OS X and Windows will be provided shortly
-after the release.
+Binaries for Android, iOS, Mac OS X and Windows will usually be provided
+shortly after the release.
This module will not be very useful by itself and should be used in conjunction
with other GStreamer modules for a complete multimedia experience.
@@ -57,7 +57,7 @@ You can find source releases of gstreamer in the download
directory: https://gstreamer.freedesktop.org/src/gstreamer/
The git repository and details how to clone it can be found at
-http://cgit.freedesktop.org/gstreamer/gstreamer/
+https://cgit.freedesktop.org/gstreamer/gstreamer/
==== Homepage ====
@@ -65,10 +65,16 @@ The project's website is https://gstreamer.freedesktop.org/
==== Support and Bugs ====
-We use GNOME's bugzilla for bug reports and feature requests:
-http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer
+We have recently moved from GNOME Bugzilla to GitLab on freedesktop.org
+for bug reports and feature requests:
-Please submit patches via bugzilla as well.
+ https://gitlab.freedesktop.org/gstreamer
+
+Please submit patches via GitLab as well, in form of Merge Requests. See
+
+ https://gstreamer.freedesktop.org/documentation/contribute/
+
+for more details.
For help and support, please subscribe to and send questions to the
gstreamer-devel mailing list (see below for details).
@@ -77,8 +83,14 @@ There is also a #gstreamer IRC channel on the Freenode IRC network.
==== Developers ====
-GStreamer is stored in Git, hosted at git.freedesktop.org, and can be cloned
-from there (see link above).
+GStreamer source code repositories can be found on GitLab on freedesktop.org:
+
+ https://gitlab.freedesktop.org/gstreamer
+
+and can also be cloned from there and this is also where you can submit
+Merge Requests or file issues for bugs or feature requests.
Interested developers of the core library, plugins, and applications should
-subscribe to the gstreamer-devel list.
+subscribe to the gstreamer-devel list:
+
+ https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
diff --git a/configure.ac b/configure.ac
index 76a1822..3c89b59 100644
--- a/configure.ac
+++ b/configure.ac
@@ -5,7 +5,7 @@ dnl please read gstreamer/docs/random/autotools before changing this file
dnl initialize autoconf
dnl releases only do -Wall, git and prerelease does -Werror too
dnl use a three digit version number for releases, and four for git/prerelease
-AC_INIT(GStreamer OpenMAX Plug-ins, 1.15.0.1,
+AC_INIT(GStreamer OpenMAX Plug-ins, 1.15.1,
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer,
gst-omx)
@@ -45,10 +45,10 @@ AC_DEFINE_UNQUOTED(GST_API_VERSION, "$GST_API_VERSION",
[GStreamer API Version])
AG_GST_LIBTOOL_PREPARE
-AS_LIBTOOL(GST, 1500, 0, 1500)
+AS_LIBTOOL(GST, 1501, 0, 1501)
dnl *** required versions of GStreamer stuff ***
-GST_REQ=1.15.0.1
+GST_REQ=1.15.1
dnl *** autotools stuff ****
diff --git a/gst-omx.doap b/gst-omx.doap
index 6bba069..501373e 100644
--- a/gst-omx.doap
+++ b/gst-omx.doap
@@ -33,6 +33,16 @@ a basic collection of elements
<release>
<Version>
+ <revision>1.15.1</revision>
+ <branch>master</branch>
+ <name></name>
+ <created>2019-01-17</created>
+ <file-release rdf:resource="https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-1.15.1.tar.xz" />
+ </Version>
+ </release>
+
+ <release>
+ <Version>
<revision>1.14.0</revision>
<branch>master</branch>
<name></name>
diff --git a/meson.build b/meson.build
index 8ddf58f..d482cee 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
project('gst-omx', 'c',
- version : '1.15.0.1',
+ version : '1.15.1',
meson_version : '>= 0.36.0',
default_options : [ 'warning_level=1',
'buildtype=debugoptimized' ])
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-27 22:28:55 +0000