On Fri, 15 Dec 2017 12:46:10 +0100
Jorge Ramirez wrote:
> On 12/14/2017 07:54 PM, Jorge Ramirez wrote:
> > On 12/14/2017 07:48 PM, wm4 wrote:
> >> This is pretty much a requirement for any codec that handles modern
> >> codecs like h264, but it was missing. Potentially could lead to issues
> >>
On 12/21/2017 09:54 AM, wm4 wrote:
On Fri, 15 Dec 2017 12:46:10 +0100
Jorge Ramirez wrote:
On 12/14/2017 07:54 PM, Jorge Ramirez wrote:
On 12/14/2017 07:48 PM, wm4 wrote:
This is pretty much a requirement for any codec that handles modern
codecs like h264, but it was missing. Potentially cou
From: Karthick Jeyapal
The HLS specification states the following about EXT-X-TARGETDURATION
4.3.3.1. EXT-X-TARGETDURATION
The EXT-X-TARGETDURATION tag specifies the maximum Media Segment
duration. The EXTINF duration of each Media Segment in the Playlist
file, when rounded to the ne
On 20 December 2017 at 19:58, Aurelien Jacobs wrote:
> ---
> libavutil/crc.c | 20
> libavutil/crc.h | 12
> 2 files changed, 32 insertions(+)
>
> diff --git a/libavutil/crc.c b/libavutil/crc.c
> index 8e44a76ec8..cb26a09a20 100644
> --- a/libavutil/crc.c
> +++
On Sun, Dec 17, 2017 at 11:35:25PM +0100, Michael Niedermayer wrote:
> Decreases memory requirements
> Fixes: OOM
> Fixes: 4525/clusterfuzz-testcase-minimized-6400713073623040
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by
On Sun, Dec 17, 2017 at 11:35:26PM +0100, Michael Niedermayer wrote:
> Reduces memory needed
> ---
> libavcodec/jpeg2000dec.c | 3 +++
> 1 file changed, 3 insertions(+)
applied
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Republics decline into democracies a
2017-12-21 2:07 GMT+01:00 :
> The branch, master has been updated
>via 979b3a6608b30683dc1d722e0304315a44f86cf7 (commit)
> from 73341e6d38818f9723926b58715e751463771d45 (commit)
>
>
> - Log -
> commit 979b3a6608b30683d
On Sun, Dec 10, 2017 at 10:19:30PM +, Mark Thompson wrote:
> On 10/12/17 21:49, Michael Niedermayer wrote:
> > On Sun, Dec 10, 2017 at 07:56:49PM +, Mark Thompson wrote:
> >> On 10/12/17 15:20, Michael Niedermayer wrote:
> >>> Signed-off-by: Michael Niedermayer
> >>> ---
> >>> libavcodec/
From: Henrik Gramner
AVX-512 consists of a plethora of different extensions, but in order to keep
things a bit more manageable we group together the following extensions
under a single baseline cpu flag which should cover SKL-X and future CPUs:
* AVX-512 Foundation (F)
* AVX-512 Conflict Detect
---
libavutil/x86/cpu.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/libavutil/x86/cpu.c b/libavutil/x86/cpu.c
index f33088c8c7..696f47b3bf 100644
--- a/libavutil/x86/cpu.c
+++ b/libavutil/x86/cpu.c
@@ -97,6 +97,7 @@ int ff_get_cpu_flags_x86(void)
int max_
---
configure | 2 ++
libavcodec/internal.h | 4 +++-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 07fb825f91..d3187d71ed 100755
--- a/configure
+++ b/configure
@@ -1892,6 +1892,7 @@ ARCH_FEATURES="
local_aligned
simd_align_16
---
configure | 5 +
1 file changed, 5 insertions(+)
diff --git a/configure b/configure
index d09eec4155..07fb825f91 100755
--- a/configure
+++ b/configure
@@ -411,6 +411,7 @@ Optimization options (experts only):
--disable-fma3 disable FMA3 optimizations
--disable-fma4
---
tests/checkasm/checkasm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/checkasm/checkasm.c b/tests/checkasm/checkasm.c
index 45a70aa87f..ff0ca5b68d 100644
--- a/tests/checkasm/checkasm.c
+++ b/tests/checkasm/checkasm.c
@@ -204,6 +204,7 @@ static const struct {
{ "FMA3", "
I have addressed all the comments raised in the previous threads. While some
patches were okayed last time I am still sending them as part of these to give
everyone a final change to see them again and to object if they wish.
Henrik Gramner (1):
x86inc: AVX-512 support
James Darnley (6):
con
---
Changelog | 1 +
doc/APIchanges| 3 +++
libavutil/cpu.c | 6 +-
libavutil/cpu.h | 1 +
libavutil/tests/cpu.c | 1 +
libavutil/version.h | 2 +-
libavutil/x86/cpu.h | 2 ++
7 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/Changelog b/Change
---
libavutil/mem.c | 2 +-
libavutil/x86/cpu.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavutil/mem.c b/libavutil/mem.c
index 6ad409daf4..79e8b597f1 100644
--- a/libavutil/mem.c
+++ b/libavutil/mem.c
@@ -61,7 +61,7 @@ void free(void *ptr);
#include "mem_inte
2017-12-21 14:40 GMT+01:00 James Darnley :
> I have addressed all the comments raised in the previous threads.
> While some patches were okayed last time I am still sending them
> as part of these to give everyone a final change to see them again
> and to object if they wish.
Does any of the patch
2017-12-21 11:09 GMT+01:00 Karthick J :
> if (target_duration <= duration)
> -target_duration = hls_get_int_from_double(duration);
> +target_duration = lrint(duration);
If this patch gets committed, please move the function
into dashenc.c.
Carl Eugen
On 12/21/17 7:45 PM, Carl Eugen Hoyos wrote:
2017-12-21 11:09 GMT+01:00 Karthick J :
if (target_duration <= duration)
-target_duration = hls_get_int_from_double(duration);
+target_duration = lrint(duration);
If this patch gets committed, please m
From: Karthick Jeyapal
The HLS specification states the following about EXT-X-TARGETDURATION
4.3.3.1. EXT-X-TARGETDURATION
The EXT-X-TARGETDURATION tag specifies the maximum Media Segment
duration. The EXTINF duration of each Media Segment in the Playlist
file, when rounded to the ne
From: Karthick Jeyapal
dashenc no longer needs this function.
---
libavformat/hlsenc.c | 5 +
libavformat/hlsplaylist.h | 5 -
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 29fc1d4..14a9a12 100644
--- a/libavformat/h
2017-12-21 23:41 GMT+08:00 Karthick J :
> From: Karthick Jeyapal
>
> The HLS specification states the following about EXT-X-TARGETDURATION
>
> 4.3.3.1. EXT-X-TARGETDURATION
>
>The EXT-X-TARGETDURATION tag specifies the maximum Media Segment
>duration. The EXTINF duration of each Media Se
>On 12/21/17, 9:47 PM, "Steven Liu" wrote:
>
>I cannot sure if this patch can fix the problem playlist target
>duration not same.
>
>MacBook:xxx StevenLiu$ ./ffmpeg -hide_banner -i
>~/bbb_sunflower_1080p_30fps_normal.mp4 -g 150 -r 100 -x264opts
>"scenecut=-1" -f dash -min_seg_duration 100 -w
2017-12-22 0:37 GMT+08:00 Jeyapal, Karthick :
>
>
>>On 12/21/17, 9:47 PM, "Steven Liu" wrote:
>>
>>I cannot sure if this patch can fix the problem playlist target
>>duration not same.
>>
>>MacBook:xxx StevenLiu$ ./ffmpeg -hide_banner -i
>>~/bbb_sunflower_1080p_30fps_normal.mp4 -g 150 -r 100 -x264o
On 2017-12-21 15:06, Carl Eugen Hoyos wrote:
> 2017-12-21 14:40 GMT+01:00 James Darnley :
>> I have addressed all the comments raised in the previous threads.
>> While some patches were okayed last time I am still sending them
>> as part of these to give everyone a final change to see them again
>>
>On 12/21/17, 10:15 PM, "Steven Liu" wrote:
>
>2017-12-22 0:37 GMT+08:00 Jeyapal, Karthick :
>>
>>
>>>On 12/21/17, 9:47 PM, "Steven Liu" wrote:
>>>
>>>I cannot sure if this patch can fix the problem playlist target
>>>duration not same.
>>>
>>>MacBook:xxx StevenLiu$ ./ffmpeg -hide_banner -i
>>>
On Thu, Dec 21, 2017, at 4:07 AM, Carl Eugen Hoyos wrote:
> Where was this agreed upon?
>
> Carl Eugen
As a mailing list maintainer I made this decision based on the reality of the
situation and due to developer feedback in the following three threads:
[FFmpeg-devel] [PATCH] Refactor Developer
Lou Logan (2017-12-21):
> * All messages on ffmpeg-cvslog now have a reply-to header set to
> ffmpeg-devel.
Oh, good. I was actually about to suggest just that. Thank you.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
__
video_format is not used.
---
Introduced by 4b2a186ef02c1fbe7f7cae30a2bdfff72bcc75f7:
src/libavcodec/mpeg4videodec.c: In function ‘mpeg4_decode_visual_object’:
src/libavcodec/mpeg4videodec.c:1771:17: warning: unused variable ‘video_format’
[-Wunused-variable]
int video_format = get_b
Hi all,
I compile ffmpeg for android, some bugs as below:
MACRO B0
bionic/libc/kernel/uapi/asm-generic/termbits.h:142:#define B0 000
src/libavcodec/aaccoder.c:803:25: error: expected identifier or '(' before
numeric constant
int B0 = 0, B1 = 0;
atomic_int
src/liba
On Mon, 18 Dec 2017, Paul B Mahol wrote:
On 12/10/17, Marton Balint wrote:
Signed-off-by: Marton Balint
---
tests/fate/filter-video.mak| 4 ++
tests/ref/fate/filter-framerate-12bit-down | 55 +
tests/ref/fate/filter-framerate-12bit-up | 64
+++
This is just a lot of complicated and confusing code that does nothing.
Also, the functions return values were checked only sometimes. Locking
shouldn't fail anyway, so remove the return values. Barely any other
pthread lock calls check the return value (including more important code
that is more l
This removes the XP compatibility code, and switches entirely to SWR
locks, which are available starting at Windows Vista.
This removes CRITICAL_SECTION use, which allows us to add
PTHREAD_MUTEX_INITIALIZER, which will be useful later.
Windows XP is hereby not a supported build target anymore. It
Deprecated and useless.
---
fftools/ffplay.c | 27 ---
1 file changed, 27 deletions(-)
diff --git a/fftools/ffplay.c b/fftools/ffplay.c
index 10a917194d..9bfa3e6cea 100644
--- a/fftools/ffplay.c
+++ b/fftools/ffplay.c
@@ -1284,7 +1284,6 @@ static void do_exit(VideoState *i
Use static mutexes instead of requiring a lock manager. The behavior
should be roughly the same before and after this change for API users
which did not set the lock manager at all (except that a minor memory
leak disappears).
---
doc/APIchanges | 5 +++
libavcodec/avcodec.h | 8 +++-
li
It's completely absurd that libavcodec would care about libavformat
locking, but it was there because the lock manager was in libavcodec.
This is more stright forward. Changes ABI, but we don't require ABI
compatibility currently.
---
openssl, avisynth, chromaprint build untested
---
libavcodec/i
2017-12-21 18:09 GMT+08:00 Karthick J :
> From: Karthick Jeyapal
>
> The HLS specification states the following about EXT-X-TARGETDURATION
>
> 4.3.3.1. EXT-X-TARGETDURATION
>
>The EXT-X-TARGETDURATION tag specifies the maximum Media Segment
>duration. The EXTINF duration of each Media Se
2017-12-22 7:37 GMT+08:00 Steven Liu :
> 2017-12-21 18:09 GMT+08:00 Karthick J :
>> From: Karthick Jeyapal
>>
>> The HLS specification states the following about EXT-X-TARGETDURATION
>>
>> 4.3.3.1. EXT-X-TARGETDURATION
>>
>>The EXT-X-TARGETDURATION tag specifies the maximum Media Segment
>>
On 12/21/2017 7:22 PM, wm4 wrote:
> This removes the XP compatibility code, and switches entirely to SWR
> locks, which are available starting at Windows Vista.
>
> This removes CRITICAL_SECTION use, which allows us to add
> PTHREAD_MUTEX_INITIALIZER, which will be useful later.
>
> Windows XP is
On Thu, 21 Dec 2017 21:31:37 -0300
James Almer wrote:
> On 12/21/2017 7:22 PM, wm4 wrote:
> > This removes the XP compatibility code, and switches entirely to SWR
> > locks, which are available starting at Windows Vista.
> >
> > This removes CRITICAL_SECTION use, which allows us to add
> > PTHRE
On 12/21/2017 9:40 PM, wm4 wrote:
> On Thu, 21 Dec 2017 21:31:37 -0300
> James Almer wrote:
>
>> On 12/21/2017 7:22 PM, wm4 wrote:
>>> This removes the XP compatibility code, and switches entirely to SWR
>>> locks, which are available starting at Windows Vista.
>>>
>>> This removes CRITICAL_SECTI
On Thu, 21 Dec 2017 22:05:11 -0300
James Almer wrote:
> On 12/21/2017 9:40 PM, wm4 wrote:
> > On Thu, 21 Dec 2017 21:31:37 -0300
> > James Almer wrote:
> >
> >> On 12/21/2017 7:22 PM, wm4 wrote:
> >>> This removes the XP compatibility code, and switches entirely to SWR
> >>> locks, which ar
On 12/21/2017 10:49 PM, wm4 wrote:
> On Thu, 21 Dec 2017 22:05:11 -0300
> James Almer wrote:
>
>> On 12/21/2017 9:40 PM, wm4 wrote:
>>> On Thu, 21 Dec 2017 21:31:37 -0300
>>> James Almer wrote:
>>>
On 12/21/2017 7:22 PM, wm4 wrote:
> This removes the XP compatibility code, and swit
On Thu, 21 Dec 2017 22:57:42 -0300
James Almer wrote:
> On 12/21/2017 10:49 PM, wm4 wrote:
> > On Thu, 21 Dec 2017 22:05:11 -0300
> > James Almer wrote:
> >
> >> On 12/21/2017 9:40 PM, wm4 wrote:
> >>> On Thu, 21 Dec 2017 21:31:37 -0300
> >>> James Almer wrote:
> >>>
> On 12/21/2
Fixes: runtime error: left shift of negative value -180
Fixes: 4626/clusterfuzz-testcase-minimized-5647837887987712
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/hevcdsp_template.c | 2 +-
1
Fixes: runtime error: signed integer overflow: 2147483646 + 33554433 cannot be
represented in type 'int'
Fixes: 4563/clusterfuzz-testcase-minimized-5438979567517696
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niederma
On 12/22/17, 5:08 AM, "Steven Liu" wrote:
>
>2017-12-21 18:09 GMT+08:00 Karthick J :
>> From: Karthick Jeyapal
>>
>> The HLS specification states the following about EXT-X-TARGETDURATION
>> […]
>
>LGTM, I have checked from HLS Team, Set the EXT-X-TARGETDURATION by
>print(EXTINF).
Oh, I am glad w
From: Karthick Jeyapal
Currently http end of chunk is called implicitly in hlsenc_io_open().
This mean playlists http writes would have to wait upto a segment duration to
signal end of chunk causing delays.
This patch will fix that problem and improve performance.
---
libavformat/hlsenc.c | 5 +
From: Karthick Jeyapal
Right now there is no explicit way to signal end of chunk, when http_multiple
is set.
ff_http_do_new_request() function implicitly signals end of chunk. But that
could be too late for certain applications.
Hence added a new function ff_http_signal_end_of_chunk() which cou
On Fri, 22 Dec 2017 12:34:41 +0530
Karthick J wrote:
> From: Karthick Jeyapal
>
> Right now there is no explicit way to signal end of chunk, when http_multiple
> is set.
> ff_http_do_new_request() function implicitly signals end of chunk. But that
> could be too late for certain applications.
50 matches
Mail list logo
