summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-05-29Release 1.14.51.14.51.14Tim-Philipp Müller6-19/+258
2019-05-09testelg: include eglext.hGuillaume Desmottes1-0/+1
Neded for the declaration of eglSaneChooseConfigBRCM().
2019-05-09testegl: move up pi specific macrosGuillaume Desmottes1-9/+9
We need to define __VCCOREVER__ and disable redundant-decls before including the egl.h from the pi.
2019-05-09Update git locations to gitlabMatthew Waters2-3/+3
2019-05-09omxvideodec: fix pool caps reference stealingGuillaume Desmottes1-1/+1
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-10-02Release 1.14.41.14.4Tim-Philipp Müller6-8/+64
2018-09-16Release 1.14.31.14.3Tim-Philipp Müller6-10/+152
2018-08-29omx: wait for flush complete and buffers being released when flushingGuillaume Desmottes1-6/+16
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-29omx: factor out should_wait_until_flushed()Guillaume Desmottes1-7/+15
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-07-20Release 1.14.21.14.2Tim-Philipp Müller6-143/+259
2018-05-17meson: fix miscellaneous meson warningsTim-Philipp Müller1-24/+12
cc.has_header*() doesn't have a 'required:' kwarg.
2018-05-17Release 1.14.11.14.1Tim-Philipp Müller6-24/+216
2018-04-18omxvideoenc/dec: fix handling of component enabling failingGuillaume Desmottes2-2/+32
- 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-06log_omx_performance: convert pointers to stringsGuillaume Desmottes1-2/+11
G_TYPE_POINTER are not serialized in logs. https://bugzilla.gnome.org/show_bug.cgi?id=794331
2018-04-02omxvideoenc: remove duplicated debug messageGuillaume Desmottes1-1/+0
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-03-28omxvideoenc: add 'roi' qp-mode on zynqultrascaleplusGuillaume Desmottes1-0/+10
New QP mode used to handle ROI metadata. https://bugzilla.gnome.org/show_bug.cgi?id=793696
2018-03-19Release 1.14.01.14.0Tim-Philipp Müller6-64/+204
2018-03-13Release 1.13.911.13.91Tim-Philipp Müller6-40/+955
2018-03-09meson: fix typo in package name defineTim-Philipp Müller1-1/+1
2018-03-05omxh265: update 422 profile namesGuillaume Desmottes2-4/+5
h265parse is gaining support for the format range extension profile (bgo#793876). Use the profile names defined in h265parse. https://bugzilla.gnome.org/show_bug.cgi?id=793928
2018-03-05omxvideoenc: Don't drop the frame on empty payloadNicolas Dufresne1-1/+3
This otherwise may lead to "No reference frame found" warning.
2018-03-05omxvideodec: Don't drop the frame on empty payloadNicolas Dufresne1-1/+3
This otherwise may lead to "No reference frame found" warning.
2018-03-05omx: Free empty buffers list in use_dynamic_buffersNicolas Dufresne1-0/+2
To indicate we are doing dynamic buffers importation, we pass a list of NULL pointers, but we forgot to free that list.
2018-03-05omxvideodec: Fix CodecState leakNicolas Dufresne1-0/+1
2018-03-03Release 1.13.901.13.90Tim-Philipp Müller6-134/+1555
2018-03-03config: dist tizonia config filesTim-Philipp Müller1-1/+1
2018-03-02Revert "omx: wait for flush complete and buffers being released when flushing"Nicolas Dufresne1-1/+1
This reverts commit 4211e4c29a262f110cb92ddf9c06b403ced233ef.
2018-02-28videoenc: don't set stride padding to 0 when copying framesGuillaume Desmottes1-20/+2
Padding can be left undefined there is no point filling it with 0. https://bugzilla.gnome.org/show_bug.cgi?id=793694
2018-02-28add support for NV12_10LE32 and NV16_10LE32 on zynqultrascaleplusGuillaume Desmottes6-15/+101
The encoder and decoder on zynqultrascaleplus support these new 10 bits format. https://bugzilla.gnome.org/show_bug.cgi?id=793694
2018-02-28omxvideoenc: factor out gst_omx_video_enc_nv12_manual_copy()Guillaume Desmottes1-58/+66
No semantic change, I'm going to re-use it to copy the NV12_10LE32 format. https://bugzilla.gnome.org/show_bug.cgi?id=793694
2018-02-28omxvideoenc: display the computed buffer size when configuring inputGuillaume Desmottes1-6/+6
https://bugzilla.gnome.org/show_bug.cgi?id=793694
2018-02-21videoenc: implement ROI on zynqultrascaleplusGuillaume Desmottes2-0/+111
Check input buffers for ROI meta and pass them to the encoder by using zynqultrascaleplus's custom OMX extension. Also add a new "default-roi-quality" in order to tell the encoder what quality level should be applied to ROI by default. https://bugzilla.gnome.org/show_bug.cgi?id=793696
2018-02-21omxvideoenc: remove GST_PARAM_MUTABLE_PLAYING from 'max-bitrate' propertyGuillaume Desmottes1-1/+1
This property isn't actually mutable in the PLAYING state. https://bugzilla.gnome.org/show_bug.cgi?id=793458
2018-02-21omxvideoenc: protect target_bitrate with the object lockGuillaume Desmottes2-1/+10
The 'target-bitrate' property can be changed while PLAYING (GST_PARAM_MUTABLE_PLAYING). Make it thread-safe to prevent concurrent accesses between the application and streaming thread. https://bugzilla.gnome.org/show_bug.cgi?id=793458
2018-02-21omxbufferpool: add PERFORMANCE DEBUG message when copying output framesGuillaume Desmottes1-0/+9
I spent quiet some time figuring out why performance of my pipeline were terrible. Turned out it was because of output frames being copied because of stride/offset mismatch. Add a PERFORMANCE DEBUG message to make it easier to spot and debug from logs. https://bugzilla.gnome.org/show_bug.cgi?id=793637
2018-02-15Back to developmentTim-Philipp Müller2-3/+3
2018-02-15Release 1.13.11.13.1Tim-Philipp Müller5-623/+116
2018-02-12omxh265enc: fix typo in "periodicty-idr" property nameGuillaume Desmottes1-1/+1
Also fix the 'nick' of the property. omxh265enc is based on the code from omxh264enc and suffers the same typo as we fixed in https://bugzilla.gnome.org/show_bug.cgi?id=784370 This element isn't part of a stable release yet so it's not an API break. https://bugzilla.gnome.org/show_bug.cgi?id=793390
2018-02-08meson: make version numbers ints and fix int/string comparisonTim-Philipp Müller1-9/+5
WARNING: Trying to compare values of different types (str, int). The result of this is undefined and will become a hard error in a future Meson release. Also remove unused libversion/soversion.
2018-01-30include all OMX extension headers if presentGuillaume Desmottes3-1/+89
The OMX specs defines 8 headers that implementations can use to define their custom extensions. We were checking and including 3 and ignoring the other ones. https://bugzilla.gnome.org/show_bug.cgi?id=792043
2018-01-30meson: simplify OMX extensions detectionGuillaume Desmottes3-38/+26
We are now always checking which files are present or not, even when using our internal copy of OMX, rather than hardcoding the ones present in it. https://bugzilla.gnome.org/show_bug.cgi?id=792043
2018-01-30Revert "meson: use include_directories() with external OMX headers path"Nicolas Dufresne3-26/+39
This reverts commit 9d37a92a615e54e8ee12f8c65bcfe386ec9de2d0.
2018-01-30omxh265enc: add some encoding propertiesGuillaume Desmottes2-0/+74
constrained-intra-prediction and loop-filter-mode. Those map standard OMX settings. https://bugzilla.gnome.org/show_bug.cgi?id=792528
2018-01-30omxh264enc: add some encoding propertiesGuillaume Desmottes2-0/+108
entropy-mode, constrained-intra-prediction and loop-filter-mode. Those map standard OMX settings. https://bugzilla.gnome.org/show_bug.cgi?id=792528
2018-01-30omxvideoenc: add zynqultrascaleplus specific propertiesGuillaume Desmottes2-1/+607
https://bugzilla.gnome.org/show_bug.cgi?id=792528
2018-01-30omxvideoenc: document unit of target-bitrate propertyGuillaume Desmottes1-1/+1
nTargetBitrate and nEncodeBitrate are defined in bits per second in the OMX spec. https://bugzilla.gnome.org/show_bug.cgi?id=792528
2018-01-30omxvideodec: add internal-entropy-buffers property on zynqultrascaleplusGuillaume Desmottes2-1/+111
Custom property to control the number of internal buffers used in the decoder to smooth out entropy decoding performance. https://bugzilla.gnome.org/show_bug.cgi?id=792528
2018-01-30meson: use include_directories() with external OMX headers pathGuillaume Desmottes3-39/+26
It seems cleaner to use the proper meson tools to include this path rather than manually tweak the build flags. This also allows us to simplify the OMX extensions detection code. We are now always checking which files are present, even when using our internal copy of OMX, rather than hardcoding the ones present in it. https://bugzilla.gnome.org/show_bug.cgi?id=792043
2018-01-30omxvideoenc: expose chroma format and bit depth in output capsGuillaume Desmottes1-0/+56
As we added in the parser (bgo#792039) expose the chroma and bit depth information in output caps. https://bugzilla.gnome.org/show_bug.cgi?id=792040
2018-01-30omxvideoenc: factor out get_output_caps()Guillaume Desmottes1-2/+13
No semantic change so far. https://bugzilla.gnome.org/show_bug.cgi?id=792040
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-18 13:27:38 +0000