summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2014-10-28qtdemux: Update global duration on moov+moof filesqtdemuxEdward Hervey1-0/+49
Otherwise we end up stopping reading after the first fragment
2014-10-27qtdemux: don't blindly use any previous buffer timestamp for moofEdward Hervey1-2/+3
The previous PTS might actually be from quite far away, from way before the moof header. We don't want to use that blindly. Use a safety distance of 4kbytes instead Avoids using completely bogus base timestamp for fragments
2014-10-27qtdemux: forward DISCONT from upstream to the output streamsGeorge Kiagiadakis1-0/+11
This makes sense in DASH reverse playback, where the upstream dashdemux will download DASH segments in reverse order, but push their buffers forward to qtdemux and mark each segment start as DISCONT. This needs to be forwarded downstream to the parser/decoder, otherwise it won't work. https://bugzilla.gnome.org/show_bug.cgi?id=734443
2014-10-24speex: Fix segfault when resetting the codecs multiple timesAnanda2-0/+2
https://bugzilla.gnome.org/show_bug.cgi?id=738793
2014-10-24rtpjitterbuffer: make debug line less confusingWim Taymans1-2/+2
2014-10-24rtspsrc: set full stream caps on internal src TCP padsAleix Conchillo Flaqué1-0/+6
Set the complete stream caps on the TCP internal src pads. Otherwise, ptdemux will not properly detect the caps change. https://bugzilla.gnome.org/show_bug.cgi?id=737868
2014-10-24rtpmux: Don't set PROXY_CAPS flag on the src padSjoerd Simons2-1/+5
rtpmux behaves like a funnel in that it forwards whatever upstream is sending buffers. So setting proxy caps doesn't make sense as the upstream don't have to have compatible caps, thus resulting in an empty caps set as a result of a caps query. Instead set fixed caps just as funnel does. https://bugzilla.gnome.org/show_bug.cgi?id=738722
2014-10-24videobox: critical error when element properties set as max/minVineeth T M1-1/+1
left, right, top, bottom can be set from range of -2147483648 to 2147483647 when i launch the videobox element with that values, it gives a critical error (gst-check-1.0:29869): GStreamer-CRITICAL **: gst_value_set_int_range_step: assertion 'start < end' failed This happens because min cannot be equal to max. https://bugzilla.gnome.org/show_bug.cgi?id=738838
2014-10-24equalizer: Don't call iirequalizer's transform_ip in passthrough modeDavid Sansome1-3/+1
It tries to map the read-only buffer with GST_MAP_READWRITE and crashes. https://bugzilla.gnome.org/show_bug.cgi?id=737886
2014-10-14souphttpclientsink: Fix lifetime of stream headers and queued buffersNirbheek Chauhan1-4/+11
Stream headers are updated whenever ::set_caps is called, so we can't assume they'll be valid before the message body is written out. We *can* assume that for queued buffers, but SOUP_MEMORY_STATIC is still wrong for those. Also, add some debug logging for stream header interactions. https://bugzilla.gnome.org/show_bug.cgi?id=737771
2014-10-14aacparse: fix memory leak when prepending ADTS headersMatej Knopp1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=737761
2014-10-14wavenc: Send CAPS event after the pad was activatedSebastian Dröge1-3/+7
Otherwise the CAPS event will be dropped and we never configure any caps at all, leading to weird behaviour in many situations. Especially header rewriting is not going to work if a capsfilter is after wavenc. https://bugzilla.gnome.org/show_bug.cgi?id=737735
2014-10-14souphttpclientsink: Add some more useful debug loggingNirbheek Chauhan1-0/+4
2014-10-14souphttpclientsink: Free queued buffers in ::resetNirbheek Chauhan1-0/+3
::render sets a new callback for writing out new buffers only if there aren't already buffers queued for writing with a previously-scheduled callback. However, if the previously-scheduled callback is interrupted by a state change (either manually or due to an error) and there are still buffers in the queue, restarting the pipeline will result in buffers being queued forever, and no callbacks will ever be scheduled, and no buffers will be written out. https://bugzilla.gnome.org/show_bug.cgi?id=737739
2014-10-14vp8enc: finish() and drain() should return a GstFlowReturnSebastian Dröge1-2/+2
2014-10-14vp8enc/vp9enc: Protect the encoder with a mutex in all situationsSebastian Dröge2-4/+10
2014-10-14vp9enc: Allow caps renegotiationSebastian Dröge1-9/+35
https://bugzilla.gnome.org/show_bug.cgi?id=726329
2014-10-14vp8enc: Allow caps renegotiationJose Antonio Santos Cadenas1-8/+34
https://bugzilla.gnome.org/show_bug.cgi?id=726329
2014-10-14pulse: Add some documentation about threading and synchronisationArun Raghavan2-2/+29
This gives a quick introduction to how the pulsesink/pulsesrc code interacts with the pa_threaded_mainloop that we start up to communicate with the server.
2014-10-14pulsesink: Make emitting stream status messages synchronousArun Raghavan1-0/+16
The stream status messages are emitted in the PA mainloop thread, which means the mainloop lock is taken, followed by the Gst object lock (by gst_element_post_message()). In all other locations, the order of locking is reversed (this is unavoidable in a bunch of cases where the object lock is taken by GstBaseSink or GstAudioBaseSink, and then we get control to take the mainloop lock). The only way to guarantee that the defer callback for stream status messages doesn't deadlock is to either stop posting those messages, or make sure that the message emission is completed before we proceed to any point that might take the object lock before the mainloop lock (which is what we do after this patch). https://bugzilla.gnome.org/show_bug.cgi?id=736071
2014-10-10rtpsource: Rename seqnum-base to seqnum-offset in capsOlivier Crête2-7/+7
This was modified back in 1.0 in GstRtpBasePayload
2014-10-10rtpmux: clock-base and seqnum-base -> timestamp-offset and seqnum-offsetOlivier Crête3-13/+14
These were renamed in GstRTPBasePayload in 1.0
2014-10-10rtpdtmfsrc: clock-base and seqnum-base -> timestamp-offset and seqnum-offsetOlivier Crête2-16/+18
These were renamed in GstRTPBasePayload in 1.0
2014-09-24Release 1.4.3Sebastian Dröge72-103/+231
2014-09-24Update .po filesSebastian Dröge41-41/+41
2014-09-24flacparse: Only calculate with durations != -1Sebastian Dröge1-1/+1
2014-09-23check/soup: Temporarily disable G_ENABLE_DIAGNOSTICEdward Hervey1-0/+5
The SOUP_SERVER_PORT property has been deprecated in recent libsoup versions.
2014-09-23check/soup: Define minimum version requiredEdward Hervey1-0/+2
To avoid deprecation warnings
2014-09-19Release 1.4.2Sebastian Dröge72-91/+437
2014-09-19Update .po filesSebastian Dröge41-41/+41
2014-09-19po: Update translationsSebastian Dröge1-17/+16
2014-09-19rtpbin: do not leak encsink pad in error caseOgnyan Tonchev1-4/+4
https://bugzilla.gnome.org/show_bug.cgi?id=736807
2014-09-19multipartdemux: do not leak new stream eventOgnyan Tonchev1-0/+1
https://bugzilla.gnome.org/show_bug.cgi?id=736805
2014-09-19osxaudio: OSStatus is not a fourcc, so don't print it as one...Sebastian Dröge4-94/+57
2014-09-17flacparse: do not leak uid after parsing TOC eventOgnyan Tonchev1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=736739
2014-09-16v4l2allocator: O_CLOEXEC needs _GNU_SOURCEPeter Korsgaard1-0/+4
Similar to 94f3d6fc / bz 709423 On some systems (E.G. uClibc and older Glibc versions), O_CLOEXEC is only defined when _GNU_SOURCE is specified, so do so. https://bugzilla.gnome.org/show_bug.cgi?id=736670
2014-09-15capssetter: update to 1.0 transform_caps sematicsWim Taymans1-20/+18
In 1.0, we pass the complete caps to transform_caps to allow for better optimizations. Make this function actually work on non-simple caps instead of just ignoring the configured filter caps.
2014-09-13wavparse: Fix parsing of adtl chunksSebastian Dröge1-2/+10
We have to skip 12 bytes of data for the chunk, and the data size passed to the sub-chunk parsing functions should have 4 bytes less than the data size. Also when parsing the sub-chunks, check if we actually have enough data to read instead of just crashing. https://bugzilla.gnome.org/show_bug.cgi?id=736266
2014-09-11matroska-demux: Don't handle parse errors at the end of file as an errorSebastian Dröge2-10/+28
But only if they happen after the Matroska segment. https://bugzilla.gnome.org/show_bug.cgi?id=735833
2014-09-11souphttpsrc: If the server reports "Accept-Ranges: none" don't try range ↵Sebastian Dröge1-0/+11
requests
2014-09-10v4l2sink: Unref pool after usageOgnyan Tonchev1-0/+1
https://bugzilla.gnome.org/show_bug.cgi?id=736384
2014-09-09v4l2transform: Don't rank it for nowNicolas Dufresne1-1/+1
This will prevent the converter to be picked automatically in case someone implement dynamic converter selection support. I'd like this to be ranked only for known device, as it's hard to be sure a device is a converter suited for general purpose. Re-negotiation is also needed before we can rank it. https://bugzilla.gnome.org/show_bug.cgi?id=733607
2014-09-09v4l2allocator: Workaround driver that don't support REQBUFS(0)Nicolas Dufresne1-20/+14
There is still around 18 drivers not yet ported to videobuf2. These driver don't support freeing buffetrs through REQBUFS(0) hence for these the memory type probing fails. In order to gain back our previous behaviour in presence of these, we implement a workaround that assuming MMAP is supported. Note that an allocator is only created for device with STREAMING support in the device capabilities. In such case one of MMAP, USERPTR and DMABUF is required. Though DMABUF came afterward, so is not an option and in practice none of these drivers will only do USERPTR. https://bugzilla.gnome.org/show_bug.cgi?id=735660 Also-by: Hans de Goede <hdegoede@redhat.com>
2014-09-07avidemux: fix crash with certain videosTim-Philipp Müller1-1/+1
This is a regression from 1.2 caused by the port to the pad flow combiner. https://bugzilla.gnome.org/show_bug.cgi?id=736192
2014-09-04aacparse: Fix parsing issue when the buffer does not have a complete ↵Nicolas Huet1-5/+13
ADTS/LOAS frame https://bugzilla.gnome.org/show_bug.cgi?id=735520
2014-09-04souphttpsrc: Include redirection target in error messagesSebastian Dröge1-15/+18
Just giving the original URI can give the false impression that e.g. that one failed host name resolution, while actually the redirection target did.
2014-09-04videomixer: Fix synchronization if dynamically changing the FPSAndrei Sarakeev1-0/+14
https://bugzilla.gnome.org/show_bug.cgi?id=735859
2014-09-04smpte: Check if input caps are the same and create output caps from video infoRavi Kiran K N1-10/+2
This makes sure that also properties like the pixel-aspect-ratio are the same between both streams and that the output caps contain all fields necessary for complete video caps. https://bugzilla.gnome.org/show_bug.cgi?id=735804
2014-09-04qtdemux: Silence some warnings for normal file contentsJan Schmidt2-2/+4
2014-09-02vp9dec: Get input width/height from the codec instead of the input capsSebastian Dröge1-7/+4
They are reported properly by libvpx if the correct struct members are used. This also fixes handling of resolution changes without input caps changes. https://bugzilla.gnome.org/show_bug.cgi?id=719359
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-21 14:06:00 +0000