- Nov 09, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
This is similar to what we do for packets with payload
-
When the frame buffer is AYUV writing all zeros does not set it to black, in YUV colorspace 0x10 is the black level for luminance and 0x80 is the black level for chrominance. Fix setting the background to black when the out_frame format is AYUV; in all the other supported formats zeroing the data with memset is still the right thing to do. https://bugzilla.gnome.org/show_bug.cgi?id=710392
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This reverts commit f0ebc684. The fix was not complete, see discussion in https://bugzilla.gnome.org/show_bug.cgi?id=711627
-
- Nov 07, 2013
-
-
When the input buffer is empty and we need more data to determine whether or not to terminate the previous frame, the last start code location needs to be set to 4 bytes before the the current position (size of start_code is 32-bits) https://bugzilla.gnome.org/show_bug.cgi?id=711627
-
It is needed to update location properties and it was being lost on state changes, causing issues if the pipeline was to be reused
-
It only gets the sink flag set when it adds the multifilesink, that happens in null->ready and it might be too late. Set the flag explicitly on the constructor. https://bugzilla.gnome.org/show_bug.cgi?id=711086
-
Thiago Santos authored
Force filesink to null before posting video-done to make sure the file was closed. Had to do it from a separate thread to avoid calling state_change from a sync message handler. https://bugzilla.gnome.org/show_bug.cgi?id=709373
-
- Nov 04, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Nov 01, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
yadif.c:49:24: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] DECLARE_ASM_CONST (16, const xmm_reg, pb_1) = { ^ yadif.c:33:50: note: expanded from macro 'DECLARE_ASM_CONST' #define DECLARE_ASM_CONST(n,t,v) static const t __attribute__((used)) __attribute__ ((aligned (n))) v ^ yadif.c:52:24: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] DECLARE_ASM_CONST (16, const xmm_reg, pw_1) = { ^ yadif.c:33:50: note: expanded from macro 'DECLARE_ASM_CONST' #define DECLARE_ASM_CONST(n,t,v) static const t __attribute__((used)) __attribute__ ((aligned (n)))
-
-
- Oct 31, 2013
-
-
Andoni Morales Alastruey authored
In Galaxy S4 the codecs list contains some OMX.SEC.foo.sw.dec as software decoders https://bugzilla.gnome.org/show_bug.cgi?id=711214
-
- Oct 30, 2013
-
-
Andoni Morales Alastruey authored
Flushing the decoder invalidates all buffers, so it should be done after quiting the decoding loop. Otherwise we can jump into "failed_release" and stop everything https://bugzilla.gnome.org/show_bug.cgi?id=711156
- Oct 26, 2013
-
-
Alex Ashley authored
This patch fixes three memory leaks in hlsdemux, one that occurs during normal operation and two that occur during error conditions. The gst_hls_demux_get_next_fragment function calls gst_fragment_get_buffer which increments the reference count on the buffer but gst_hls_demux_get_next_fragment never calls unref on the buffer. This means that the reference count for each downloaded fragment never gets to zero and so its memory is never released. This patch adds a call to gst_buffer_unref after the flags have been updated on the buffer. There is a leak-on-error in gst_hls_demux_decrypt_fragment if it fails to download the key file. If the key fails to download, null is returned without doing an unref on the encrypted fragment. The semantics of gst_hls_demux_decrypt_fragment is that it takes ownership of the encrypted fragment and releases it before returning. There is a leak-on-error in gst_hls_src_buf_to_utf8_playlist in the unlikely event that the gst_buffer_map fails. In the "happy path" operation of gst_hls_src_buf_to_utf8_playlist the buffer gets an unref before the function returns, therefore the error condition must do the same. https://bugzilla.gnome.org/show_bug.cgi?id=710881
-
- Oct 25, 2013
- Oct 12, 2013
-
-
Olivier Crête authored
-
- Oct 10, 2013
-
-
Sebastian Dröge authored
Otherwise we will crash when handling multiple channels and miscalculate timestamps. https://bugzilla.gnome.org/show_bug.cgi?id=709734
-
Sebastian Dröge authored
-
- Oct 03, 2013
-
-
Thiago Santos authored
It will cause a deadlock and the calers for _get_next_fragment will already call _stop if required when _get_next_fragment fails. Fixes #690148
-
-
- Oct 01, 2013
-
-
- Sep 30, 2013
-
-
On some live HLS streams, gst_hls_demux_switch_playlist causes assertion failures because it tried to dereference a NULL fragment. This is because g_queue_peek_tail sometimes was returning NULL and this case was not being checked. This patch does two things: * move the g_queue_peek_tail inside the semaphore protection * check if q_queue_peek_tail returns NULL https://bugzilla.gnome.org/show_bug.cgi?id=708849
-
-
The previous code could enter an infinite loop because the adapter state could get out of sync with its mapped data state after sync was lost. The code was pretty confusing so it's been rewritten to be clearer. The easiest way to reproduce the infinite loop is to use the breakmydata element before tsdemux to trigger a resync. https://bugzilla.gnome.org/show_bug.cgi?id=708161
-
This can happen with a corrupt TS file, found with breakmydata element plugged before tsdemux. https://bugzilla.gnome.org/show_bug.cgi?id=708161
-
Sebastian Dröge authored
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-