- Dec 18, 2012
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
-
-
comparison is always true due to limited range of data type
-
- Dec 17, 2012
-
-
Tim-Philipp Müller authored
The codec data blob we get from matroskademux with the SSA/ASS init section is supposed to be valid UTF-8. If it's not, just continue with the bits that are valid UTF-8 instead of erroring out. We don't actually parse the init section yet anyway.. https://bugzilla.gnome.org/show_bug.cgi?id=607630
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Don't loop forever if an USB audio device gets disconnected while in use. Post an error message instead. This is not enough yet though, we still need to make the base class and/or the ring buffer bail out. https://bugzilla.gnome.org/show_bug.cgi?id=690197
-
Tim-Philipp Müller authored
-
- Dec 14, 2012
-
-
Wim Taymans authored
Block the pad before the resample and convertor elements to give them a chance to negotiate new caps with the newly switched vis plugin. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=679976
-
- Dec 10, 2012
-
-
-
Sebastian Dröge authored
Otherwise we just pass through the timestamps directly and don't need to waste additional memory for them. Fixes bug #689814.
-
Sebastian Rasmussen authored
https://bugzilla.gnome.org/show_bug.cgi?id=689873 Conflicts: gst-libs/gst/rtsp/gstrtspmessage.c
-
- Nov 28, 2012
-
-
Tim-Philipp Müller authored
When the input buffers for a stream don't have a duration set, timestamp_end might still be GST_CLOCK_TIME_NONE. When advancing EOSed streams via GAP events (with other streams not yet EOS), we would then use the invalid timestamp_end to calculate the duration of the gap. This in turn would make baseaudiosink abort, because it would try to allocate memory for a trizillion samples. So if buffers don't have a duration set, assume a duration of one second for stream catch-up purposes, just so we can still continue to catch up in those cases. And make sure that timestamp_end is valid before doing calculations with it. http://bugzilla.gnome.org/show_bug.cgi?id=678530
-
Tim-Philipp Müller authored
Log locking/unlocking with TRACE debug level.
-
- Nov 21, 2012
-
-
Tim-Philipp Müller authored
It was causing perl warnings in gtk-doc code.
-
Tim-Philipp Müller authored
It takes ownership of the buffer.
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Nov 20, 2012
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
And only return the proportion. The earliest time already can be retrieved from get_max_decode_time() and by renaming we allow this to be more extensible in the future.
-
-
Add a getter for the QoS proportion and earliest_time to help subclasses do better estimations based on the proportion. API: gst_video_decoder_get_qos_info() https://bugzilla.gnome.org/show_bug.cgi?id=687991
-
- Nov 15, 2012
-
-
- Nov 13, 2012
-
-
Sebastian Dröge authored
Revert "vorbisdec: Fix GType name conflict if tremor and libvorbis decoder are used in the same process" This reverts commit 858392f8. A similar, cleaner fix was already in place.
-
Sebastian Dröge authored
-
- Nov 12, 2012
-
-
Tim-Philipp Müller authored
Make AAC LOAS typefinding a bit more reliable; don't report a LIKELY probability already after just two sync points, but scan for a few more consecutive frames and determine probability based on how many we found. Fixes mis-detection of wavpack file. https://bugzilla.gnome.org/show_bug.cgi?id=687674
-
Tim-Philipp Müller authored
The blocksize includes part of the header, just not the sync marker and the four size bytes.
-
Tim-Philipp Müller authored
Check for second block sync and return different probabilities depending on what we found (trumping the AAC loas typefinder's LIKELY probability after finding a second frame sync in this particular case). https://bugzilla.gnome.org/show_bug.cgi?id=687674
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Previously we could've chosen another format with the same depth even if the input format was possible. Also make sure to chose according to the order in the caps.
-
Sebastian Dröge authored
-
Rasmus Rohde authored
Enhance current code to prefer an exact match on sample depth if possible. Also ignore GST_AUDIO_FORMAT_FLAG_UNPACK when checking equality on the flags.
-
- Nov 07, 2012
-
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
We can't blend stuff on top of video formats that unpack into ARGB64 or AYUV64 yet, so don't advertise them in our template caps.
-
Tim-Philipp Müller authored
We only allocate 8 bits per component for our temp buffers, which causes invalid memory accesses if we try to unpack formats that unpack into a format with 16 bits per component such as e.g. v210. We don't support blending onto those yet, so just bail out.
-