summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.12.51.12.51.12Tim-Philipp Müller2018-03-286-91/+433
|
* Update docsTim-Philipp Müller2018-03-2868-68/+69
|
* matroskamux: Clip maximum cluster duration to the maximum possible valueSebastian Dröge2018-03-131-1/+2
| | | | | | | | | | Only up to timescale * G_MAXINT16 is possible as cluster duration, which is already higher than our default value. Using higher values would cause overflows and broken files. Based on the investigation by Nicola Murino <nicola.murino@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=792775
* matroskamux: Only mark new clusters as keyframe if they start on a keyframe ↵Sebastian Dröge2018-03-131-1/+2
| | | | | | | | or we're muxing only audio Based on a patch by Nicola Murino <nicola.murino@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=792775
* Revert "rtspsrc: Ignore medias marked as sendonly"Sebastian Dröge2018-03-131-8/+0
| | | | This reverts commit 86a56cc48c521d4fbd4c73c903a58787313458d4.
* Revert "rtspsrc: Fix up sendonly/recvonly attribute handling"Sebastian Dröge2018-03-131-4/+4
| | | | | | | | | This reverts commit 326e9549e378bcc71587ba569f73755e0abc1794. In master/1.14 this was already disabled, and the attributes are only ever looked at when a backchannel is used. This is necessary because various ONVIF cameras out there are implementing the attributes the wrong way around.
* monoscope: Forward the SEGMENT event from the chain functionSebastian Dröge2018-02-222-1/+14
| | | | | Otherwise we'll break the event order and forward the SEGMENT event before sending a CAPS event.
* splitmuxsrc: Improve not-linked handling.Jan Schmidt2018-02-162-1/+34
| | | | | Don't report not-linked unless all pads have returned not-linked.
* interleave: fix memory leak of GAP buffersPhilippe Normand2018-01-311-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=793067
* rtspsrc: Fix up sendonly/recvonly attribute handlingSebastian Dröge2018-01-221-4/+4
| | | | | | | | | | | | | | | | | | We can't handle recvonly streams, sendonly streams are perfectly fine. The direction is the one from the point of view of the SDP offerer (i.e. the RTSP server), and a recvonly stream would be one where the server expects us to send media. RFC 3264, section 5.1: If the offerer wishes to only send media on a stream to its peer, it MUST mark the stream as sendonly with the "a=sendonly" attribute. This is mixed up in the ONVIF streaming specification examples, but actual implementations and conformance tools seem to not care at all about the attributes. https://bugzilla.gnome.org/show_bug.cgi?id=792376
* aacparse: When parsing raw input, accept frames of any sizeJan Alexander Steffens (heftig)2018-01-181-0/+4
| | | | | | | | | | | | | | | | Raw AAC streams might have very small frames, e.g. 6 byte frames when encoding silence. These frames are then smaller than aacparse's default min_frame_size of 10 bytes (ADTS_MAX_SIZE). When passthrough is disabled or aacparse has to output ADTS, GstBaseParse will concatenate these short frames to the following frame before handling them to aacparse, which processes each input buffer as a single frame, producing bad output. To avoid this problem, set the min_frame_size to 1 when receiving a raw stream. https://bugzilla.gnome.org/show_bug.cgi?id=792644
* flacdec: flush flac decoder on lost sync.Mathieu Duponchelle2018-01-172-1/+10
| | | | | | | This to allow the decoder to start searching for a new frame again. https://bugzilla.gnome.org/show_bug.cgi?id=791473
* rtspsrc: also proxy multicast-iface property to RTCP udpsrcMark Nauwelaerts2018-01-171-1/+1
|
* multiudpsink: don't try to set IPV6_TCLASS on IPV4 socketsSebastian Rasmussen2018-01-171-2/+4
| | | | | | Avoids ERROR log message. https://bugzilla.gnome.org/show_bug.cgi?id=757449
* equalizer: Fix -Wincompatible-pointer-types warningMichael Catanzaro2017-12-111-1/+1
| | | | | | This is caused by the new type propagation for g_object_ref. https://bugzilla.gnome.org/show_bug.cgi?id=791494
* Release 1.12.41.12.4Sebastian Dröge2017-12-0777-160/+533
|
* Update .po filesSebastian Dröge2017-12-0742-798/+685
|
* po: Update translationsSebastian Dröge2017-12-072-651/+763
|
* Revert "flacparse: fix header rewriting being ignored"Tim-Philipp Müller2017-12-072-52/+1
| | | | | | | | | | | This caused broken metadata and also looks a bit dodgy. Revert until we can figure out a solution that works for all cases and doesn't break anything. This reverts commit adeee44b07a173b9ab4253216caba8f66dd43abb. https://bugzilla.gnome.org/show_bug.cgi?id=727802 https://bugzilla.gnome.org/show_bug.cgi?id=785558
* rtpsession: Handle zero length feedback packetsHaakon Sporsheim2017-12-021-6/+17
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=791074
* qtdemux: fix debug log for 'hvcC' codec_dataFlorian Zwoch2017-12-021-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=784749
* rganalysis: Fix left shift of signed valuesEdward Hervey2017-12-011-5/+5
| | | | | | | left shifting signed values is undefined. Instead of doing "x << offs" which is undefined, do the equivalent "x * (1 << offs)" which is well defined
* flacparse: Request at least the full header size when parsing headersSebastian Dröge2017-12-011-0/+4
| | | | | | | | | Otherwise baseparse will incrementally send us bigger buffers until the full header size is reached, which is not only pointless but also means that baseparse will reallocate and copy into a bigger buffer for every input buffers. In pull mode that's done in 64kb increments, in push mode usually in much smaller increments, causing a lot of overhead for example when parsing high-quality coverart.
* qtdemux: reset reused QtDemuxStream while parsing a new 'trak'Jun Xie2017-11-201-7/+13
| | | | | | if QtDemuxStream is reused, then we need to reset it. https://bugzilla.gnome.org/show_bug.cgi?id=788759
* splitmuxsrc: Don't return FALSE from event handling.Jan Schmidt2017-11-181-6/+4
| | | | | | | | Returning FALSE because we drop an event means that internal sources like qtdemux might throw an error and break the whole pipeline. The only time it can happen is either flushing or shutdown, and those will be handled anyway.
* souphttpsrc: Remove range header when seek to 0paul.kim2017-11-101-1/+2
| | | | | | | This fixes the previous range header is remained if seek to 0 is attempted. https://bugzilla.gnome.org/show_bug.cgi?id=779957
* tests: souphttpsrc: Update test-cert.pemJan Alexander Steffens (heftig)2017-11-091-15/+16
| | | | | | | | | | | Recent GnuTLS disregards the Common Name and only looks at the Subject Alternative Name extension. Since our test-cert has no SAN extension, validation fails. Generate a new certificate with SAN. In addition to 127.0.0.1, for good measure make it valid for localhost and ::1, too. https://bugzilla.gnome.org/show_bug.cgi?id=784005
* tests: souphttpsrc: Avoid deprecated ssl-ca-file propertyJan Alexander Steffens (heftig)2017-11-091-1/+22
| | | | | | | | | | SoupSession's ssl-ca-file property is deprecated. Use the recommended tls-database property. This is a bit more complex as it requires creating a GTlsFileDatabase object for an absolute (!) path to the CA certificates file. https://bugzilla.gnome.org/show_bug.cgi?id=784005
* tests: souphttpsrc: Avoid deprecated server ssl propertiesJan Alexander Steffens (heftig)2017-11-091-8/+13
| | | | | | | The ssl-cert-file and ssl-key-file properties are deprecated. Use the soup_server_set_ssl_cert_file function to load the files. https://bugzilla.gnome.org/show_bug.cgi?id=784005
* tests: souphttpsrc: Make ssl_cert/key_file staticJan Alexander Steffens (heftig)2017-11-091-3/+4
| | | | | | Just a bit of cleanup. https://bugzilla.gnome.org/show_bug.cgi?id=784005
* souphttpsrc: Fix seeking back to 0Edward Hervey2017-11-091-0/+6
| | | | | | | | | | | | This is a regression introduced by "03db374 - souphttpsrc: retry request on early termination from the server" The problem was that when seeking back to 0, we would not end up calling add_range_header() which in addition to adding range headers *ALSO* sets the read_position to the requested one. This would result in a wide variety of later failures, like reading again and again instead of stopping properly.
* v4l2deviceprovider: Add missing V4L2_CAP_TOUCHJan Alexander Steffens (heftig)2017-11-061-0/+5
| | | | | | | | This define was only added in Linux 4.8. This commit is for the stable branch only, since we want to avoid bumping the v4l headers in fear of regressions. https://bugzilla.gnome.org/show_bug.cgi?id=789197
* v4l2deviceprovider: Ignore touch sensing devicesJan Alexander Steffens (heftig)2017-11-061-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With GST_V4L2_USE_LIBV4L2=1, my laptop's touchpad shows up as a video source device in gst-device-monitor, but attempting to stream from it fails because the device doesn't actually support any video formats. name : Synaptics RMI4 Touch Sensor class : Video/Source caps : video/x-raw, format=(string)I420, framerate=(fraction)[ 0/1, 2147483647/1 ], width=(int)0, height=(int)0, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1; video/x-raw, format=(string)YV12, framerate=(fraction)[ 0/1, 2147483647/1 ], width=(int)0, height=(int)0, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1; video/x-raw, format=(string)BGR, framerate=(fraction)[ 0/1, 2147483647/1 ], width=(int)0, height=(int)0, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1; video/x-raw, format=(string)RGB, framerate=(fraction)[ 0/1, 2147483647/1 ], width=(int)0, height=(int)0, interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1; properties: udev-probed = true device.bus_path = /sys/devices/rmi4-00/rmi4-00.fn54/video4linux/v4l-touch0 sysfs.path = /sys/devices/rmi4-00/rmi4-00.fn54/video4linux/v4l-touch0 device.subsystem = video4linux device.product.name = "Synaptics\ RMI4\ Touch\ Sensor" device.capabilities = :capture: device.api = v4l2 device.path = /dev/v4l-touch0 v4l2.device.driver = rmi4_f54 v4l2.device.card = "Synaptics\ RMI4\ Touch\ Sensor" v4l2.device.bus_info = rmi4:rmi4-00.fn54 v4l2.device.version = 265480 (0x00040d08) v4l2.device.capabilities = 2501902337 (0x95200001) v4l2.device.device_caps = 354418689 (0x15200001) gst-launch-1.0 v4l2src device=/dev/v4l-touch0 ! ... v4l2-ctl -d /dev/v4l-touch0 --list-formats reports: ioctl: VIDIOC_ENUM_FMT Index : 0 Type : Video Capture Pixel Format: 'TD16' Name : 16-bit signed deltas Index : 1 Type : Video Capture Pixel Format: 'TD08' Name : 8-bit signed deltas Index : 2 Type : Video Capture Pixel Format: 'TU16' Name : 16-bit unsigned touch data https://bugzilla.gnome.org/show_bug.cgi?id=789197
* flvdemux: Ignore invalid H.264 codec dataNicolas Dufresne2017-10-191-0/+5
| | | | | | | | | This code basically skip over codec_data with empty payload. In this case, the codec_data variable is the size of the header for the CODEC part of Video Tag. The remaining is supposed to be the H.264 codec data, hence should not be empty. https://bugzilla.gnome.org/show_bug.cgi?id=787795
* flvdemux: Only set pixel-aspect-ratio if specifiedNicolas Dufresne2017-10-191-2/+4
| | | | | | | | If it's not specified, we should let the decoder figure it out. Apparently the code was already in place, all was to make the code conditional. https://bugzilla.gnome.org/show_bug.cgi?id=787795
* flvdemux: Don't pull passed the EOSNicolas Dufresne2017-10-191-0/+3
| | | | | | | | When a truncated FLV is provided and processed in pull mode, we may endup trying to pull passed EOS, causing a rather confusing warning as the pull offset is an integer overflow. https://bugzilla.gnome.org/show_bug.cgi?id=787795
* flvdemux: Avoid integer overflow on invalid CTSNicolas Dufresne2017-10-191-0/+6
| | | | | | | If the CTS is negative an would lead to a negtive PTS, clip the CTS so the PTS will be 0. https://bugzilla.gnome.org/show_bug.cgi?id=787795
* rtspsrc: Ignore medias marked as sendonlySebastian Dröge2017-10-191-0/+8
| | | | | We're never going to receive anything from them, so don't create pads for them. These medias are destinations where *we* could send something.
* Release 1.12.31.12.3Sebastian Dröge2017-09-1873-87/+510
|
* Update .po filesSebastian Dröge2017-09-1842-793/+672
|
* po: Update translationsSebastian Dröge2017-09-182-642/+756
|
* v4l2object: Don't leak the par valueNicolas Dufresne2017-09-131-1/+11
|
* v4l2object: Handle BT2020 for colorspace and transferIan Jamison2017-09-061-1/+5
| | | | | | | This was not fully handled in switches and ub gst_v4l2_object_get_colorspace(); https://bugzilla.gnome.org/show_bug.cgi?id=787313
* v4l2object: Fix colorimetry transfer lookup for 4K videoIan Jamison2017-09-061-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787160
* rtph265depay: fix keyunit detectionTim-Philipp Müller2017-09-051-1/+9
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787254
* rtpbin: also create session when creating the send_rtcp_src_%u padMatthew Waters2017-08-291-6/+12
| | | | | | | | If one requests the send_rtcp_src_%u pad before a recv_rtcp_sink_%u pad, the session/pad would never be created and NULL was returned. Switching the request order would work. https://bugzilla.gnome.org/show_bug.cgi?id=786718
* Automatic update of common submoduleTim-Philipp Müller2017-08-172-1/+1
| | | | From 48a5d85 to dd9d403
* wavparse: Add support for growing WAV filesEduard Sinelnikov2017-08-172-3/+31
| | | | With some fixes by me.
* vpxenc: discard frames that have been dropped by libvpxGeorge Kiagiadakis2017-08-171-1/+16
| | | | | | | | | | | | | | | | This fixes a memory leak. When dropframe-threshold has been set, libvpx may output less frames than the input ones, which causes some GstVideoCodecFrames to queue up in GstVideoEncoder's internal frame queue with no chance of ever being all released. And because the frames keep references to the input buffers, the input buffer pool keeps allocating new buffers and memory usage grows very fast. For example the following pipeline's memory usage grows at a rate of about 1GB per minute! videotestsrc ! capsfilter caps=video/x-raw,width=1920,height=1080,framerate=30/1,format=I420 ! \ vp8enc target-bitrate=1000000 end-usage=cbr dropframe-threshold=95 ! fakesink https://bugzilla.gnome.org/show_bug.cgi?id=783086
* rtpstats: fix unsigned integer comparisons.Mathieu Duponchelle2017-08-172-4/+4
| | | | | | | | | | | | | Callers of the API (rtpsource, rtpjitterbuffer) pass clock_rate as a signed integer, and the comparison "<= 0" is used against it, leading me to think the intention was to have the field be typed as gint32, not guint32. This led to situations where we could call scale_int with a MAX_UINT32 (-1) guint32 as the denom, thus raising an assertion. https://bugzilla.gnome.org/show_bug.cgi?id=785991
View Lorry Controller Status