I've attached a third attempt at this patch with all the
suggestions by Carl Eugen Hoyos and Moritz Barsnick,
including converting the UPDATE_INFO macro into a
function, and some more comments and little fixes.
Thanks.
From 2dbbfc0cea83b769b5b02eecc5ec3dabc477457b Mon Sep 17 00:00:00 2001
From:
2016-07-03 23:39 GMT+02:00 Hendrik Leppkes :
> On Tue, Jun 28, 2016 at 12:01 PM, Hendrik Leppkes wrote:
>> On Tue, Jun 28, 2016 at 11:48 AM, Hendrik Leppkes
>> wrote:
>>> Visual Studio 2015 Update 3 introduced a new SSA optimizer,
Finish providing SIMD versions for POWER8 VSX of functions in libswscale/input.c
That should allow trac ticket #5570 to be closed.
---
libswscale/ppc/input_vsx.c | 1018 +++-
1 file changed, 1014 insertions(+), 4 deletions(-)
diff --git
About 10% faster.
Signed-off-by: James Almer
---
libavcodec/x86/dcadsp.asm | 43 +++
1 file changed, 31 insertions(+), 12 deletions(-)
diff --git a/libavcodec/x86/dcadsp.asm b/libavcodec/x86/dcadsp.asm
index c5bf21a..055361a 100644
---
On Tue, Jun 28, 2016 at 12:01 PM, Hendrik Leppkes wrote:
> On Tue, Jun 28, 2016 at 11:48 AM, Hendrik Leppkes wrote:
>> Visual Studio 2015 Update 3 introduced a new SSA optimizer, however
>> it unfortunately causes miscompilations. Until it is fixed, the
On 7/3/2016 5:24 PM, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, Jul 3, 2016 at 3:45 PM, James Almer wrote:
>
>> Signed-off-by: James Almer
>> ---
>> Tested on Win64 (xmm), but not arm and aarch64 (neon).
>>
>> configure | 4
>>
Signed-off-by: Michael Niedermayer
---
libavcodec/vaapi_encode_h264.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
index db9071f..d576ede 100644
---
Hi,
On Sun, Jul 3, 2016 at 3:45 PM, James Almer wrote:
> Signed-off-by: James Almer
> ---
> Tested on Win64 (xmm), but not arm and aarch64 (neon).
>
> configure | 4
> libavcodec/aarch64/neontest.c | 10 ++
>
Signed-off-by: James Almer
---
Tested on Win64 (xmm), but not arm and aarch64 (neon).
configure | 4
libavcodec/aarch64/neontest.c | 10 ++
libavcodec/arm/neontest.c | 10 ++
libavcodec/x86/w64xmmtest.c | 10 ++
4 files
hello
about once a month (also, around OPW/GSOC time) we get people in
#ffmpeg-devel or the ml asking about contributing to ffmpeg. i think we
need to try to organize something for new contributors.
usually there is only one or two devs alive (including me) to guide
newbies. most times these
Am Sonntag, den 03.07.2016, 18:05 +0200 schrieb Moritz Barsnick:
> On Sun, Jul 03, 2016 at 17:20:41 +0200, Jens Ziller wrote:
> >
> > Am Samstag, den 02.07.2016, 17:54 +0200 schrieb Moritz Barsnick:
> > >
> > > On Sun, Jun 26, 2016 at 17:12:14 +0200, Jens Ziller wrote:
> > > >
> > > >
> > > >
On Tue, May 10, 2016 at 08:30:11PM +0200, Matthias Hunstock wrote:
> Am 10.05.2016 um 07:54 schrieb Felipe Astroza:
> > This patch add additional input options: video input connection (vinput),
> > audio input connection (ainput).
> >
> > Usage:
> > ffmpeg -f decklink -i 'Card name'@fmt
On Sun, Jul 03, 2016 at 17:20:41 +0200, Jens Ziller wrote:
> Am Samstag, den 02.07.2016, 17:54 +0200 schrieb Moritz Barsnick:
> > On Sun, Jun 26, 2016 at 17:12:14 +0200, Jens Ziller wrote:
> > >
> > > +ctx->interlaced_frame = !(interlace_type.eMode ==
> > > MMAL_InterlaceProgressive);
>
Am Samstag, den 02.07.2016, 17:54 +0200 schrieb Moritz Barsnick:
> On Sun, Jun 26, 2016 at 17:12:14 +0200, Jens Ziller wrote:
> >
> > +ctx->interlaced_frame = !(interlace_type.eMode ==
> > MMAL_InterlaceProgressive);
> What's wrong with using the "!=" operator instead?
"!=" is a
On Sat, Jul 02, 2016 at 09:07:42PM +0200, Michael Niedermayer wrote:
> On Sat, Jul 02, 2016 at 07:23:35PM +0200, Clément Bœsch wrote:
> > ---
> > libavcodec/h264_slice.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> LGTM
>
> thx
>
applied
--
Clément B.
Thanks. I've sent a new version of the patch in reply to Carl Eugen
Hoyos, and using git send-email this time, but I saw this message and
included most of the things you mentioned.
I'm still getting used to this.
Anyway, I am curious why both of you think UPDATE_INFO should not
remain a macro? It
The new HDCD filter really does nothing to show that it is working or
that HDCD control information was even detected in the stream. This
patch collects information about the decode, like which features were
used, and reports it to the user at the end.
Signed-off-by: Burt P
---
Burt P. gmail.com> writes:
> +/* For user information/stats, pulled up into HDCDContext
> + * by filter_frame() */
> +int _hdcd_detected;
No leading underscores please, same below.
[...]
> +/* update the user info/flags */
> +#define UPDATE_INFO(s,pe,tg,tf)
I believe this should
18 matches
Mail list logo