summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-04-05docs: make GstRTCPSync enum show up in rtpbin docsHEADmasterTim-Philipp Müller3-7/+8
https://bugzilla.gnome.org/show_bug.cgi?id=747358
2015-04-05docs: add RTPJitterBufferMode enum to rtpbin docsTim-Philipp Müller1-0/+1
https://bugzilla.gnome.org/show_bug.cgi?id=747358
2015-04-04multifilesink: close files before posting messageThiago Santos1-6/+6
Makes sure the files were properly flushed and closed before the message reaches the application
2015-04-04tests: multifile: increment tests to check for multifile messagesThiago Santos1-7/+69
Also verify that the multifilesink file messages are being correctly posted to the bus
2015-04-04tests: multifile: handle FIXME for proper checking when test finishedThiago Santos1-2/+13
Use a GstBus and wait for EOS to finish the tests instead of relying on sleeping
2015-04-04multifilesink: post file message on EOSThiago Santos1-0/+37
When multifilesink is operating in any mode other than one file per buffer, the last file created won't have a file message posted as multifilesink doesn't handle the EOS event. This patch fixes it by using the last position to post a file message when EOS is received. This should ensure at least the time related data and the filename are posted to the application or other elements https://bugzilla.gnome.org/show_bug.cgi?id=747000
2015-04-03Automatic update of common submoduleTim-Philipp Müller2-23/+3
From bc76a8b to c8fb372
2015-04-03qtdemux: Guard against 64-bit overflowJan Schmidt1-3/+12
For large-file atoms, guard against overflow in the size field, which could make us jump backward in the file and cause infinite loops.
2015-04-03isomp4: Make non-seekable downstream an error in normal modeJan Schmidt3-26/+53
When not in fast-start or fragmented mode, we need to be able to rewrite the size of the mdat atom, or else the output just won't be playable - the mdat placeholder with size == 0 will cover the rest of the file, including any moov atom we write out. https://bugzilla.gnome.org/show_bug.cgi?id=708808
2015-04-02rtph263pay/-depay: add framesize SDP attributeSebastian Rasmussen3-6/+109
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=726416
2015-04-02rtpjpegpay/-depay: Remove incorrectly introduced framesize SDP attributeSebastian Rasmussen2-21/+4
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=726415
2015-04-02v4l2src: device sequence/offset correction in case of renegotiationPeter Seiderer2-2/+11
The v4l2 device restarts the sequence counter in case of streamoff/streamon, the GST offset values are supposed to increment strictly monotonic, so adjust the sequence counter/offset values in case of caps renegotiation. https://bugzilla.gnome.org/show_bug.cgi?id=745441
2015-04-02v4l2src: add frame loss detectionPeter Seiderer1-7/+23
In case of v4l2 driver filled offset/sequence values add frame loss detection (and write a warning message). Move offset meta data setting and frame loss checking after the timestamp adjustment code to get proper timestamps for the warning message. https://bugzilla.gnome.org/show_bug.cgi?id=745441
2015-04-02v4l2: use v4l2 capture device sequence counterPeter Seiderer2-2/+9
Use the v4l2 capture device sequence counter for setting the GstBuffer offset/offset_end values. https://bugzilla.gnome.org/show_bug.cgi?id=745441
2015-04-02v4l2: Ask the driver about its requirements for min_buffers before ↵Tobias Modschiedler2-22/+36
initiating buffer pool. If propose_allocation() had not been called yet, it was possible that the driver was not asked at all. In buffer pool: Consider minimum number of buffers requested by driver when setting config. https://bugzilla.gnome.org/show_bug.cgi?id=746834
2015-04-01rtpvp8depay: Parse width/height/profile from keyframesOlivier Crête2-12/+91
This makes it possible to mux the result into a container such as matroska. https://bugzilla.gnome.org/show_bug.cgi?id=747208
2015-04-01vp8enc: Expose VP8 width/height limitations in the caps templateOlivier Crête1-1/+4
The VP8 format specification (RFC 6386 section 18.1) specifies that the maximum size is 16383x16383.
2015-03-31flv: When passing seek event upstream, hold a ref.Jan Schmidt1-1/+4
In case upstream can't handle the seek, make sure we keep a ref on the event to attempt to handle it ourselves.
2015-03-30matroska: fix GValue leaks when parsing tagsGuillaume Desmottes1-15/+11
gst_tag_list_add_value() doesn't consume the GValue we pass to it so there is no point copying it. https://bugzilla.gnome.org/show_bug.cgi?id=746810
2015-03-29qtdemux: resurrect some flow return handlingMark Nauwelaerts1-4/+15
https://bugzilla.gnome.org/show_bug.cgi?id=744572
2015-03-29flvdemux: resurrect some flow return handlingMark Nauwelaerts1-2/+7
https://bugzilla.gnome.org/show_bug.cgi?id=744572
2015-03-29matroskademux: resurrect some flow return handlingMark Nauwelaerts1-2/+6
https://bugzilla.gnome.org/show_bug.cgi?id=744572
2015-03-28matroska: store stream tags and push as updatedThiago Santos4-25/+24
New tags can be found on different parts of the file, so this patch keeps the stream taglists around for the life cycle of the pad and adds those new tags as found. Then a new tag is found, the pad's is marked with a tags changed flag, making the element push a new tag event on the next check. Before this, we were sending only the newly found tags, as the element was losing its taglist when pushing the event.
2015-03-28matroskademux: send global tags incrementallyRamiro Polla1-3/+4
Instead of sending only new tags once they are found, merge the taglist and send them incrementally.
2015-03-28matroskaparse: send global tagsRamiro Polla3-0/+30
Global tags are already being read in matroskaparse, but they are not currently being sent. This patch makes global tags get sent incrementally whenever new ones are found. https://bugzilla.gnome.org/show_bug.cgi?id=746242
2015-03-28quarktv: fix "planes" property range, a value of 0 is not allowedVineeth T M1-1/+1
When planes property is set to 0, the pipeline executes in an infinite loop and never exits. Since planes must never be 0, set the minimum value in the property description to 1. https://bugzilla.gnome.org/show_bug.cgi?id=743906
2015-03-26wavparse: Fix up comments regarding DTSDavid Schleef1-3/+7
2015-03-26rtspsrc: Fix segment in TCP modeNicolas Dufresne2-24/+15
It is expected that buffers are time-stamped with running time. Set a segment accordingly. In this case we pick 0,-1 as this is what udpsrc would do. Depayloaders will update the segment to reflect the playback position. https://bugzilla.gnome.org/show_bug.cgi?id=635701
2015-03-26wavparse: be more strict about typefinding DTSDavid Schleef1-1/+1
Code now matches comments.
2015-03-25rtspsrc: Remove useless functionNicolas Dufresne1-11/+4
This function didn't do anything special, let's not use a function for that.
2015-03-25rtpjitter: Account for rtx_retry in overflow checkNicolas Dufresne1-1/+1
As rtx_retry is part of the substraction, we need to take it into account, otherwise we may endup with a big value.
2015-03-24osxvideosink: check for deprecated constants prior to OSX 10.10Julien Isorce1-0/+6
cocoawindow.m:339:5: error: 'NSOpenGLPFAWindow' is deprecated: first deprecated in OS X 10.9 cocoawindow.m:576:7: error: 'NSOpenGLPFAFullScreen' is deprecated: first deprecated in OS X 10.6 cocoawindow.m:605:24: error: 'setFullScreen' is deprecated: first deprecated in OS X 10.7
2015-03-24rtspsrc: Fix seeking queryNicolas Dufresne1-3/+2
The segment start/stop in the query is meant to represent the seekable portion of the stream. It does not match the segment start/stop. Instead export 0 to duration.
2015-03-24flvdemux: Only set caps once if they don't changeSebastian Dröge1-20/+38
Previously we were setting new caps with the same content for every H264 or AAC codec_data we found in the stream, spamming everything and causing renegotiations.
2015-03-24flvdemux: Don't create AAC/H264 caps without codec_dataSebastian Dröge1-41/+74
Instead delay creating the caps until we read the codec_data from the stream, or fail if we get normal data before the codec_data. AAC raw caps and H264 avc caps always need codec_data, setting caps on the pad without them is going to make negotiation fail most of the time. Even if we later set new caps with the codec_data, that's usually going to be too late. https://bugzilla.gnome.org/show_bug.cgi?id=746682
2015-03-24flvdemux: Fix indentionSebastian Dröge1-8/+12
2015-03-23osxaudio: Fix string format warning on 32-bitIlya Konstantinov1-1/+1
UInt32 (Darwin, not C99's uint32_t) is 'unsigned long' on 32-bit platforms.
2015-03-21rtpsession: Fix another instance of sticky event misordering warningsSebastian Dröge1-0/+12
Make sure that the sync_src pad has caps before the segment event. Otherwise we might get a segment event before caps from the receive RTCP pad, and then later when receiving RTCP packets will set caps. This will results in a sticky event misordering warning This fixes warnings in the rtpaux unit test but also in the rtpaux and rtx examples in tests/examples/rtp https://bugzilla.gnome.org/show_bug.cgi?id=746445
2015-03-21rtpsession: Also start the RTCP send thread when receiving RTP or RTCPSebastian Dröge1-1/+17
Before we only started it when either: - there is no send RTP stream or - we received an RTP packet for sending This could mean that if the send RTP pads are connected but never receive any RTP data, and the same session is also used for receiving RTP/RTCP, we would never start the RTCP thread and would never send RTCP for the receiving part of the session. This can be reproduced with a pipeline like: gst-launch-1.0 rtpbin name=rtpbin \ udpsrc port=5000 ! "application/x-rtp, media=video, clock-rate=90000, encoding-name=H264" ! rtpbin.recv_rtp_sink_0 \ udpsrc port=5001 ! rtpbin.recv_rtcp_sink_0 \ rtpbin.send_rtcp_src_0 ! fakesink name=rtcp_fakesink silent=false async=false sync=false \ rtpbin.recv_rtp_src_0_2553225531_96 ! decodebin ! xvimagesink \ fakesrc ! valve drop=true ! rtpbin.send_rtp_sink_0 \ rtpbin.send_rtp_src_0 ! fakesink name=rtp_fakesink silent=false async=false sync=false -v Before this change the rtcp_fakesink would never send RTCP for the receiving part of the session (i.e. no receiver reports!), after the change it does. And before and after this change it would send RTCP for the receiving part of the session if the sender part was omitted (the last two lines).
2015-03-19rtprtxsend: Add support for buffer listsSebastian Dröge1-9/+41
2015-03-19rtprtxqueue: Implement support for buffer listsSebastian Dröge1-5/+51
2015-03-18rtspsrc: Improve trace readabilityNicolas Dufresne1-5/+32
Change the command number into strings.
2015-03-16flvdemux: Don't repeatedly warn after no_more_pads (v2)Jan Alexander Steffens (heftig)2-6/+26
This can get rather spammy for such a high log level. Only warn once per stream. https://bugzilla.gnome.org/show_bug.cgi?id=746274
2015-03-16flvdemux: Introduce constant for no-more-pads thresholdJan Alexander Steffens (heftig)1-2/+5
https://bugzilla.gnome.org/show_bug.cgi?id=746274
2015-03-16flvdemux: Fix warning to contain 'video'Jan Alexander Steffens (heftig)1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=746274
2015-03-15matroskademux: for dts only stream set pts=dts for intra only formatsNicola Murino2-2/+18
https://bugzilla.gnome.org/show_bug.cgi?id=745192
2015-03-14matroskademux: fix sending of tagsRamiro Polla2-32/+35
* Fix critical when new tags are found after segment event has already been sent. * Send global tags before stream tags. * Split sending of tags out of gst_matroska_demux_send_event() into its own function. https://bugzilla.gnome.org/show_bug.cgi?id=745973
2015-03-14rtspsrc: properly escape percent sign in documentationRamiro Polla1-1/+1
2015-03-14rtpdtmfmux: properly escape percent sign in documentationRamiro Polla1-2/+2
2015-03-13v4l2src: delay renegotiation until it is likely buffers were reclaimedThiago Santos2-21/+55
Allow renegotiation to happen when buffers have returned after an allocation query. As the allocation query is serialized, all buffers from the pool should have returned and we can stop it to create a new one for the new format https://bugzilla.gnome.org/show_bug.cgi?id=682770
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-14 13:24:01 +0000