summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-04-17opencv: facedetect: Add adaptive off-center dampingopencvReynaldo H. Verdejo Pinochet1-5/+17
This is a naive adaptive-damping implementation for out-of-center detection flickering. This modification makes it so a the damping factor is not harcoded but computed. Default is 5% of magnitude. Additionally: Add braces around multiline if statement body (for clarity)
2019-04-17opencv: facedetect: introduce fixed leaning damping factorReynaldo H. Verdejo Pinochet1-0/+4
2019-04-17opencv: facedetect: factor out right/left determination logicReynaldo H. Verdejo Pinochet1-13/+31
Additionally: Swap colors so that RED means leaning right
2019-04-17opencv: facedetect: signal gaze direction with colorReynaldo H. Verdejo Pinochet1-7/+40
THIS CHANGE IS NOT MEANT TO BE UPSTREAMED. This is just a mod.
2019-04-17opencv: facedetect: add right/left ear detectionReynaldo H. Verdejo Pinochet2-4/+78
2019-04-17opencv: facedetect: allow getting haar path from the environmentReynaldo H. Verdejo Pinochet1-12/+17
2019-02-28cccombiner: implement update_src_capsMathieu Duponchelle2-1/+20
It is necessary to implement this vmethod, as when the src pad is marked as reconfigure, the base class will reset to src caps, and the default update_src_caps simply queries the caps allowed downstream without taking into account the caps set by gst_aggregator_set_src_caps.
2019-02-28msdkdec: fix for small resolutionHaihao Xiang3-3/+3
2019-02-28msdkdec: fix for resolution changeHaihao Xiang1-3/+15
Returning MFX_ERR_INCOMPATIBLE_VIDEO_PARAM from MFXVideoDECODE_DecodeFrameAsync means the allocated mfx surface is not suitable for the current frame, we need a new mfx surface and try MFXVideoDECODE_DecodeFrameAsync again.
2019-02-28meson: don't build icles when tests are disabledTim-Philipp Müller1-1/+1
They are manual tests, so let them be controlled via the tests option not the examples option, for consistency with -good.
2019-02-27hlssink2: Add property for disabling sending of force-keyunit eventsSebastian Dröge2-1/+21
2019-02-27mpegtsmux: restore stream creation orderMathieu Duponchelle1-7/+6
In 7c767f3fcd5a7b40d205bb4d588dad6c6275c729 , stream creation was refactored to occur before potential program creation. This created issues with pipelines such as: gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640, height=640, framerate=25/1 ! \ x264enc ! hlssink2 target-duration=1 eg.: gst_buffer_copy_into: assertion 'bufsize >= offset + size' failed As this reordering was actually not needed for the purpose of allowing to specify a PCR stream, this reverts the reordering part of the initial commit.
2019-02-27msdkdec: force the alignment of width/height to 16 for vp8/vp9Haihao Xiang4-7/+46
MSDK library requires 16 alignment for vp8/vp9, otherwise a pipeline for vp8/vp9 decoding might fail. example pipeline: gst-launch-1.0 filesrc location=vp8_1280x720.webm ! matroskademux ! \ msdkvp8dec ! fakesink 0:00:00.150565444 10657 0x55c8484036d0 ERROR msdkdec gstmsdkdec.c:1056:gst_msdkdec_handle_frame:<msdkvp8dec0> DecodeFrameAsync failed (invalid video parameters)
2019-02-27msdkvpp: add RGB16 format in the sink padHaihao Xiang1-2/+2
Note: MSDK doesn't support RGB16 output, hence don't add RGB16 format in the src pad
2019-02-27msdk: set some parameters in mfxFrameData for a RGB16 frameHaihao Xiang2-0/+12
2019-02-27msdk: map MFX_FOURCC_RGB565 to VA_FOURCC_RGB565Haihao Xiang1-0/+1
2019-02-27msdk: map GST_VIDEO_FORMAT_RGB16 to VA_FOURCC_RGB565Haihao Xiang1-0/+4
2019-02-27msdk: map GST_VIDEO_FORMAT_RGB16 to MFX_FOURCC_RGB565Haihao Xiang1-0/+1
2019-02-26Release 1.15.2Tim-Philipp Müller6-102/+1241
2019-02-26Update docsTim-Philipp Müller129-142/+161
2019-02-26Update translationsTim-Philipp Müller41-313/+135
2019-02-24msdkdec: release the occupied surface for MFX_WRN_DEVICE_BUSYHaihao Xiang1-0/+6
When MFXVideoDECODE_DecodeFrameAsync () returns MFX_WRN_DEVICE_BUSY with an output surface, a new input surface is required when retrying MFXVideoDECODE_DecodeFrameAsync (). This fixes the out-of-surface issue mentioned in https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/890
2019-02-24msdk: don't destroy an image twiceHaihao Xiang1-2/+19
This gets rid of annoying message in the log, e.g. run the pipeline below: gst-launch-1.0 videotestsrc num-buffers=100 ! \ video/x-raw,format=NV12,width=352,height=288 ! msdkh264enc ! filesink \ location=test.h264 [LIBVA]:CRITICAL - DdiMedia_DestroyImage:4357: Invalid image
2019-02-24msdk: move the comment to the correct placeHaihao Xiang1-5/+6
2019-02-24srtobject: check for null local address to avoid SIGSEVAaron Boxer1-4/+5
2019-02-21ccconverter: fix typo in framerateMathieu Duponchelle1-1/+1
2019-02-21audiobuffersplit: Added max-silence-time propertyVivia Nikolaidou2-82/+117
2019-02-20mpegtsmux: allow specifying the PID of the PCR streamMathieu Duponchelle1-5/+21
The structure passed through the prog-map can now contain a PCR_<prog_id>=sink_<PID> key-value pair.
2019-02-19decklink: add Hardware tag to element metadataTim-Philipp Müller4-4/+8
2019-02-19wasapi: add Hardware tag to element metadataTim-Philipp Müller2-2/+2
2019-02-19winks: add Hardware tag to element metadataTim-Philipp Müller1-1/+1
2019-02-19androidmedia: add Hardware tag to element metadataTim-Philipp Müller3-3/+3
2019-02-19applemedia: add Hardware tag to element metadataTim-Philipp Müller4-5/+5
2019-02-19msdk: add Hardware tag to element metadataTim-Philipp Müller12-12/+12
2019-02-19nvenc, nvdec: add Hardware tag to element metadataTim-Philipp Müller3-3/+3
2019-02-19curlhttpsrc: set BUFFER_OFFSET when creating GstBufferAlex Ashley1-0/+1
To make curlhttpsrc behave more like souphttpsrc, set the BUFFER_OFFSET in its output buffers to match the segment start. This means that in a HTTP RANGE request, the BUFFER_OFFSET will match the value in the RANGE request.
2019-02-19curlhttpsrc: export same HTTP error status as souphttpsrcAlex Ashley2-4/+23
To make it closer to a drop-in replacement for souphttpsrc, expose the same gst_error_message_with_details as souphttpsrc, so that applications can received the HTTP status code and reason when an error occurs.
2019-02-19curlhttpsrc: fix various leaks and thread safety issuesAlex Ashley5-230/+303
curlhttpsrc uses a single thread running the gst_curl_http_src_curl_multi_loop() function to handle receiving data and messages from libcurl. Each instance of curlhttpsrc adds an entry into a queue in GstCurlHttpSrcMultiTaskContext and waits for the multi_loop to perform the HTTP request. Valgrind has shown up race conditions and memory leaks: 1. gst_curl_http_src_change_state() does not wait for the multi_loop to complete before going to the NULL state, which means that an instance of GstCurlHttpSrc can be released while gst_curl_http_src_curl_multi_loop() still has a reference to it. 2. if multiple elements try to be removed from the queue at once, only the last one is deleted. 3. source->caps is leaked 4. curl multi_handle is leaked 5. leak of curl_handle if URI not set 6. leak of http_headers when reusing element 7. null pointer dereference in negotiate caps 8. double-free of the default user-agent string 9. leak of multi_task_context.task This commit changes the logic so that each element has a connection status, which is used by the multi_loop to decide when to remove an element from its queue. An instance of curlhttpsrc will not enter the NULL state until its reference has been removed from the queue. When shutting down the curl multi loop, the memory allocated from the call to curl_multi_init() is now released. When gstadaptivedemux uses a URI source element, it will re-use it for multiple requests, moving it between READY and PLAYING between each request. curlhttpsrc was leaking the http_headers structure in this use case. The gst_curl_http_src_negotiate_caps() function extracts the "response-headers" field from the http_headers, but did not check that this field might be NULL. If the user-agent property is set, the global user-agent string was freed. This caused a double-free error if the user-agent is ever set a second time during the execution of the process. There are situations within curlhttpsrc where the code needs both the global multi_task_context mutex and the per-element buffer_mutex. To avoid deadlocks, it is vital that the order in which these are requested is always the same. This commit modifies the locking order to always be in the order: 1. multi_task_context.task_rec_mutex 2. buffer_mutex Fixes #876
2019-02-19tests: curlhttpsrc: add unit testsAlex Ashley3-0/+698
Based upon the souphttpsrc tests, add unit tests for the curlhttpsrc element. The souphttpsrc tests are able to use an HTTP server that is provided as part of the soup library. This does not exist in the curl library, therefore these tests provide a very simple HTTP server using the GIO library. These curlhttpsrc tests contain one new test that does not come from the souphttpsrc tests. The test_multiple_http_requests test tries to reproduce the way in which GstAdaptiveDemux makes use of URI source elements. GstAdaptiveDemux creates a bin with the httpsrc element and a queue element and sets the locked state of that bin to TRUE, so that it does not follow the state transitions of its parent. It then moves this bin to the PLAYING state to start each download and back to READY when the download completes.
2019-02-19msdkvpp: allow UYVY in DMABuf mode in the sink padHaihao Xiang1-1/+1
Tested with the pipeline below: gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \ video/x-raw\(memory:DMABuf\),format=UYVY ! msdkvpp ! video/x-raw, \ format=YUY2 ! filesink location=a.yuv
2019-02-19msdkvpp: allow UYVY in the src padHaihao Xiang1-2/+2
This make the pipeline below works: gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \ video/x-raw,format=UYVY ! filesink location=a.yuv Once https://github.com/intel/media-driver/pull/526 in the media-driver is merged, the pipeline below also works: gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \ video/x-raw\(memory:DMABuf\),format=UYVY ! filesink location=a.yuv
2019-02-19msdk: map GST_VIDEO_FORMAT_UYVY to VA_FOURCC_UYVYHaihao Xiang1-0/+4
2019-02-19msdkvpp: allow BGRx in DMABuf mode in the src padHaihao Xiang1-1/+1
Tested with the pipeline below: gst-launch-1.0 videotestsrc ! msdkvpp ! \ video/x-raw\(memory:DMABuf\),format=BGRx ! glimagesink
2019-02-18vcdsrc: Remove unusable VCD sourceBastien Nocera12-757/+3
The VCD source was ported in 2014 (commit 89eb1e9), but the necessary "cdxaparse" plugin, which is used to "Parse a .dat file (VCD) into raw mpeg1" was never ported. This means that the probable main user for the feature, totem, hasn't actually been able to play back VCDs, since 2012, when it switched to using GStreamer 1.0. Note that even if cdxaparse was finally ported, a lot of work would still be necessary before it is considered usable. Notably, it is missing disc image support [1] and some VCDs just cannot be opened for reading [2]. [1]: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/898 [2]: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/899
2019-02-15closedcaption: Use portable variadic macro syntaxNirbheek Chauhan1-0/+21
args... is not understood by MSVC: error C2010: '.': unexpected in macro parameter list
2019-02-15closedcaption: Port plugin to MSVCNirbheek Chauhan2-20/+20
pthread is not portable, so we can't use a pthread mutex use GMutex instead.
2019-02-15waylandsink: Don't create throwaway empty regionsDaniel Stone1-8/+2
Instead of creating a region, adding nothing to it, setting that as the input region and destroying the region, you can instead just pass NULL to wl_surface_set_input_region for the same effect. Fixes #702
2019-02-15webrtc: fix rtx + bundleMatthew Waters1-71/+85
If bundle was used in combination with rtx, only the bundled transport stream would have correctly configured rtx parameters. Iterate over the payloads upfront in the bundled case to ensure the correct payload mapping is set for the RTX elements.
2019-02-13dtls: Don't abort on non-fatal issuesEdward Hervey1-3/+6
OpenSSL will take care of returning valid context if there are only non-fatal issues. Don't abort in those cases and instead just print out the issues Fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/811
2019-02-13fdkaacenc: Fix draining with libfdk-aac v2.0.0Jan Alexander Steffens (heftig)1-8/+13
This release requires all buffer descriptor pointers to be valid, even when we provide zero input buffers.