This can be useful in known-broken scenarios like miscompilation
by legacy compilers and similar.
---
Yeah, one could come up with more elaborate solutions, but this already
works and we have cases where it could be useful right away...
configure | 3 +++
tests/Makefile | 2 ++
2 files chan
On Wed, Oct 05, 2016 at 02:04:31PM +0200, Alexandra Hájková wrote:
> --- a/libavcodec/x86/hevc_idct.asm
> +++ b/libavcodec/x86/hevc_idct.asm
> @@ -74,34 +286,578 @@ cglobal hevc_idct_%1x%1_dc_%2, 1, 2, 1, coeff, tmp
>
> INIT_XMM sse2
> +IDCT_DC_NL 8, %1
> +IDCT_DC16, 4, %1
> +IDCT_DC
On 07/10/16 00:28, Vittorio Giovara wrote:
> Missing from 9bd6ea5695660529b2887292874a7b9e61fc301e.
>
> Signed-off-by: Vittorio Giovara
> ---
> Fixes the ppc fate tests.
> Vittorio
>
Sounds Ok.
Thanks for spotting it!
lu
___
libav-devel mailing list
On 07/10/16 00:27, Vittorio Giovara wrote:
> This makes them easier to search for.
> ---
> doc/APIchanges | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/APIchanges b/doc/APIchanges
> index 655783e..ef25a98 100644
> --- a/doc/APIchanges
> +++ b/doc/APIchanges
> @@
Missing from 9bd6ea5695660529b2887292874a7b9e61fc301e.
Signed-off-by: Vittorio Giovara
---
Fixes the ppc fate tests.
Vittorio
libswscale/input.c | 4
tests/ref/fate/filter-pixfmts-scale | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/libswscale/input.
This makes them easier to search for.
---
doc/APIchanges | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index 655783e..ef25a98 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -20,7 +20,7 @@ API changes, most recent first:
Add AVIO_SEE
On 06/10/16 14:24, Diego Biurrun wrote:
> libavdevice/bktr.c:107:12: warning: missing braces around initializer
> ---
> libavdevice/bktr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavdevice/bktr.c b/libavdevice/bktr.c
> index f76a163..563bbe5 100644
> --- a/libav
On Thu, Oct 06, 2016 at 02:10:02PM +0200, Alexandra Hájková wrote:
> This's a part of my add IDCT patch, I don't undesrtand why it's sent
> under your name.
It's an independent refactoring of existing code that I did and applied
your patch on top.
> Also I see this's already pushed without any r
On Thu, Oct 06, 2016 at 09:16:58AM +, Yogender Gupta wrote:
> From 0cd1617f9fcc3ae6dba5793db46386d06f3a910e Mon Sep 17 00:00:00 2001
> From: Yogender Gupta
> Date: Thu, 6 Oct 2016 14:44:26 +0530
> Subject: [PATCH] nvenc.c: fixed error log
>
> ---
> libavcodec/nvenc.c | 2 +-
> 1 file changed
libavdevice/bktr.c:107:12: warning: missing braces around initializer
---
libavdevice/bktr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavdevice/bktr.c b/libavdevice/bktr.c
index f76a163..563bbe5 100644
--- a/libavdevice/bktr.c
+++ b/libavdevice/bktr.c
@@ -104,7 +104,7
This's a part of my add IDCT patch, I don't undesrtand why it's sent
under your name. Also I see this's already pushed without any review.
I strongly dislike your behaviour and I don't understand why are you
doing this.
___
libav-devel mailing list
libav
>> I'd fold it in the current check for ctx->data_pix_fmt that is already
>> present.
I kept it separate to maintain consistency as it is set for HEVC
>> Currently we are setting FF_PROFILE_H264_HIGH_444 should it be changed to
>> FF_PROFILE_H264_HIGH_444_PREDICTIVE as well?
FF_PROFILE_H264_HIGH
On 06/10/16 11:16, Yogender Gupta wrote:
> Fixed error log
>
Looks fine.
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
On 06/10/16 11:10, Yogender Gupta wrote:
> +if (ctx->data_pix_fmt == AV_PIX_FMT_YUV444P) {
> +cc->profileGUID = NV_ENC_H264_PROFILE_HIGH_444_GUID;
> +avctx->profile = FF_PROFILE_H264_HIGH_444_PREDICTIVE;
> +}
I'd fold it in the current check for ctx->data_pix_fmt that is al
Fixed error log
Thanks,
Yogender
---
This email message is for the sole use of the intended recipient(s) and may
contain
confidential information. Any unauthorized review, use, disclosure or
distribution
is prohibi
This patches forces high_444 profile selection for yuv444p inputs for
nvenc_h264.
Thanks,
Yogender
---
This email message is for the sole use of the intended recipient(s) and may
contain
confidential information. A
On 2016-09-29 17:52:01 +0200, Diego Biurrun wrote:
> On Thu, Sep 29, 2016 at 02:21:17PM +0300, Martin Storsjö wrote:
> > On Tue, 20 Sep 2016, Diego Biurrun wrote:
> >
> > > This avoids SIMD-optimized functions having to sign-extend their
> > > stride argument manually to be able to do pointer arit
17 matches
Mail list logo