- 28 Nov, 2014 17 commits
-
-
Rong Yan authored
avcodec/ppc/h264dsp: POWER LE support for h264_idct8_add_altivec() h264_idct_dc_add_internal() h264_loop_filter_luma_altivec() write16x4() VEC_1D_DCT() weight_h264_W_altivec() biweight_h264_W_altivec() VEC_LOAD_U8_ADD_S16_STORE_U8() ALTIVEC_STORE_SUM_CLIP() add marcos GET_2PERM() dstv_load() vdst_load() dest_unligned_store() Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit 'fcae9f21': dashenc: Avoid a VLA-like construct Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit 'a9d8d35e': dashenc: Add options to make segment names configurable Conflicts: libavformat/dashenc.c Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '01eac895': rtmpproto: Only prepend @setDataFrame for onMetaData and |RtmpSampleAccess Conflicts: libavformat/rtmpproto.c See: 60fd790fMerged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '44127b15': rtmppkt: Make pkt->data reallocable Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '3c3b8003': rtmpproto: Simplify code for copying data into the output packet Conflicts: libavformat/rtmpproto.c Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '857e6667': rtmpproto: Clarify a comment Conflicts: libavformat/rtmpproto.c Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Martin Storsjö authored
This fixes the build on compilers that interpreted the earlier code as a variable length array (which we intentionally disallow). Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Bryan Huh authored
This allows one to specify templated segment names for init-segments, media-segments, and for the base-url in the case of single-file. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Currently, when streaming to an RTMP server, any time a packet of type RTMP_PT_NOTIFY is encountered, the packet is prepended with @setDataFrame before it gets sent to the server. This is incorrect; only packets for onMetaData and |RtmpSampleAccess should invoke @setDataFrame on the RTMP server. Specifically, the current bug manifests itself when trying to stream onTextData or onCuePoint invocations. This fix addresses that problem and ensures that the @setDataFrame is only prepended for onMetaData and |RtmpSampleAccess. Since data is fed to the rtmp_write function in smaller pieces (depending on the calling IO buffer size), we can't generally assume that the whole packet (or even the whole command string) is available at once, therefore we can only check the command string once the full packet has been transferred to us for sending. Based on a patch by Jeffrey Wescott. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
We try to avoid mixing av_malloc with av_realloc, since av_malloc may be implemented with functions that can't (formally) be mixed with the functions used in av_realloc. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Michael Niedermayer authored
Fixes out of array access Fixes: signal_sigsegv_35bd0f0_1182_cov_791726764_STRUCT_B_Samsung_4.bit Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Benoit Fouet authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Benoit Fouet authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Timo Rothenpieler authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 27 Nov, 2014 23 commits
-
-
Michael Niedermayer authored
* commit '19730794': opusdec: make sure all substreams have the same number of coded samples Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '96fda42a': vf_interlace: get rid of useless loads See: ca59b5b6Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit 'fbd6c97f': lavu: fix memory leaks by using a mutex instead of atomics Conflicts: libavutil/buffer.c The atomics code is left in place as a fallback for synchronization in the absence of p/w32 threads. Our ABI did not requires applications to only use threads (and matching ones) to what libavutil was build with Our code also was not affected by the leak this change fixes, though no question the atomics based implementation is not pretty at all. First and foremost the code must work, being pretty comes after that. If this causes problems, for example when libavutil is used by multiple applications each using a different kind of threading system then the default possibly has to be changed to the uglier atomics. See: cea3a63bMerged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Lukasz Marek authored
-
Lukasz Marek authored
So far ffmpeg used recommended configuration only for codec priv options. ffmpeg will use now codec defaults and then apply recommended configuration for all options. Recommended configuration possibly contains minimal set of options to filful user configuration. Signed-off-by:
Lukasz Marek <lukasz.m.luki2@gmail.com>
-
Lukasz Marek authored
ffmenc will store recommended encoder configuration if present. This will allow the user to base on local defaults and apply only explicitly set options. If recommended encoder configuration is not present, then non-default context's options are stored. Signed-off-by:
Lukasz Marek <lukasz.m.luki2@gmail.com>
-
Lukasz Marek authored
Signed-off-by:
Lukasz Marek <lukasz.m.luki2@gmail.com>
-
Michael Niedermayer authored
* commit '2443e522': lavu: add wrappers for the pthreads mutex API Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-
Vincent Bernat authored
By appending `?dscp=26` to the URL, IP packets will be classified as AF31 (assured forwarding for multimedia flows with low probability of loss). On congested network, this allows a user to assign priorities to flows. Signed-off-by:
Vincent Bernat <vincent@bernat.im>
-
Vincent Bernat authored
By appending `?dscp=26` to the URL, IP packets will be classified as AF31 (assured forwarding for multimedia flows with low probability of loss). On congested network, this allows a user to assign priorities to flows. Signed-off-by:
Vincent Bernat <vincent@bernat.im>
-
Michael Niedermayer authored
Fixes: signal_sigabrt_7ffff6ac7bb9_2683_cov_4120310995_m_ijpg.avi Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Clément Bœsch authored
-
Clément Bœsch authored
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Fixes out of array read Fixes: signal_sigsegv_35bcf26_471_cov_2806540268_CAINIT_A_SHARP_4.bit Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Stefano Sabatini authored
-
Anton Khirnov authored
Fixes invalid writes with invalid multichannel streams. CC:libav-stable@libav.org
-
Kieran Kunhya authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
wm4 authored
The buffer pool has to atomically add and remove entries from the linked list of available buffers. This was done by removing the entire list with a CAS operation, working on it, and then setting it back again (using a retry-loop in case another thread was doing the same thing). This could effectively cause memory leaks: while a thread was working on the buffer list, other threads would allocate new buffers, increasing the pool's total size. There was no real leak, but since these extra buffers were not needed, but not free'd either (except when the buffer pool was destroyed), this had the same effects as a real leak. For some reason, growth was exponential, and could easily kill the process due to OOM in real-world uses. Fix this by using a mutex to protect the list operations. The fancy way atomics remove the whole list to work on it is not needed anymore, which also avoids the situation which was causing the leak. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Anton Khirnov authored
Also add no-op fallbacks when threading is disabled. This helps keeping the code clean if Libav is compiled for targets without threading. Since we assume that no threads of any kind are used in such configurations, doing nothing is ok by definition. Based on a patch by wm4 <nfxjfg@googlemail.com>.
-
Matthew Oliver authored
Ensures that the header include order is such that winsock2.h is always included before windows.h or that windows.h does not include winsock.h. Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Rong Yan authored
libavutil/ppc/util_altivec.h : fix load_with_perm_vec() add marcos vcswapi2s() vcswapc() VEC_SPLAT16() VEC_SLD16() for POWER LE Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
* commit '675ac56b': Revert "lavf: Don't try to update files atomically with renames on windows" Conflicts: libavformat/dashenc.c libavformat/hdsenc.c libavformat/internal.h libavformat/smoothstreamingenc.c Merged-by:
Michael Niedermayer <michaelni@gmx.at>
-