The -benchmark and -benchmark_all options now show user, system, and real time,
instead of just user time.
---
fftools/ffmpeg.c | 49 +++-
1 file changed, 36 insertions(+), 13 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 4dbe72186
chmark and -benchmark_all
continue to measure the same things.
Regards,
Mark
On Thu, Apr 26, 2018 at 12:28 PM, wm4 wrote:
> On Fri, 20 Apr 2018 16:21:13 -0400
> Mark Wachsler wrote:
>
> > The -benchmark and -benchmark_all options now show user, system, and
> real time,
&
Friendly ping. Could someone please take a look? Thanks!
On Mon, Apr 23, 2018 at 2:29 PM, Mark Wachsler wrote:
> Ping.
>
> On Fri, Apr 20, 2018 at 4:21 PM, Mark Wachsler
> wrote:
>
>> The -benchmark and -benchmark_all options now show user, system, and real
>> ti
Ping.
On Fri, Apr 20, 2018 at 4:21 PM, Mark Wachsler wrote:
> The -benchmark and -benchmark_all options now show user, system, and real
> time,
> instead of just user time.
> ---
> fftools/ffmpeg.c | 50 ++--
> 1 file changed, 36
The -benchmark and -benchmark_all options now show user, system, and real time,
instead of just user time.
---
fftools/ffmpeg.c | 50 ++--
1 file changed, 36 insertions(+), 14 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 4dbe72186
I have updated my patch to also fix the references to chroma_weight in the
MBAFF case, as suggested by Mark Thompson, but without erroring out on
invalid values.
On Thu, Sep 7, 2017 at 9:42 AM, Mark Wachsler wrote:
> When parsing a monochrome file, chroma_log2_weight_denom was used with
When parsing a monochrome file, chroma_log2_weight_denom was used without
being initialized, which could lead to a bogus error message being printed, e.g.
[h264 @ 0x61a26480] chroma_log2_weight_denom 24576 is out of range
It also could led to warnings using AddressSanitizer.
---
libavcodec/h
When parsing a monochrome file, chroma_log2_weight_denom was used without
being initialized, which could lead to a bogus error message being printed, e.g.
[h264 @ 0x61a26480] chroma_log2_weight_denom 24576 is out of range
It also could result in warnings using AddressSanitizer.
---
libavcode
Memory reallocated with av_reallocp_array is supposed to be allocated
with av_realloc, not av_malloc.
---
libavcodec/h2645_parse.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/h2645_parse.c b/libavcodec/h2645_parse.c
index b0d9ff66f0..1b2534b2e6 100644
--- a/lib
