It supports ICL platform.
H2H (HDR to HDR): P010 -> RGB10
H2S (HDR to SDR): P010 -> RGB8
libva commit for HDR10
https://github.com/intel/libva/commit/cf11abe5e1b9c93ee75cf974076957162c1605b9
Signed-off-by: Zachary Zhou
---
configure | 2 +
doc/filters.texi |
Signed-off-by: Michael Niedermayer
---
tools/target_dec_fate.list | 61 ++
1 file changed, 61 insertions(+)
diff --git a/tools/target_dec_fate.list b/tools/target_dec_fate.list
index e0509aaa64..f6b56261bb 100644
--- a/tools/target_dec_fate.list
+++ b/tools/ta
Signed-off-by: Michael Niedermayer
---
tools/target_dec_fate.sh | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/target_dec_fate.sh b/tools/target_dec_fate.sh
index 1fdfdcaaea..5e683676d1 100755
--- a/tools/target_dec_fate.sh
+++ b/tools/target_dec_fate.sh
@@ -43
On Fri, Dec 28, 2018 at 18:51:55 -0500, Helmut K. C. Tessarek wrote:
> Either the latest x265 broke something or a change in ffmpeg's
> configure messed things up.
x265 messed it up, with a commit created 15 days ago:
http://ffmpeg.org/pipermail/ffmpeg-user/2018-December/042609.html
> What I don'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> You'd need to post your whole config.log (pastebin) likely.
>
> However, this list is for development of FFmpeg itself, and this
> question should be on the user mailing list, or #ffmpeg on
> FreeNode, where you'll likely get better answers.
I'd
On Mon, Sep 10, 2018 at 02:22:06AM +0200, Michael Niedermayer wrote:
> Script to download and test ossfuzz testcases
> This also includes a list of such testcases.
> I intend to subsequently fill this list with the cases we have fixed in the
> past
>
> Signed-off-by: Michael Niedermayer
> ---
>
Hi All,
I recently had a problem building ffmpeg for AArch64 where lld linker
complained about text relocations in readonly segment. The following
patch fixes the linker complains by referring to a local label instead
of function name.
This is similar in nature as the following previous commits:
On Fri, Dec 28, 2018 at 22:22:53 +0100, Michael Niedermayer wrote:
> - * Reinitializes the V4L2m2mContext when the driver cant continue processing
> + * Reinitializes the V4L2m2mContext when the driver cannot continue
> processing
> * with the any of the current V4L2Contexts (ie, changes in out
On Fri, Dec 28, 2018, at 12:35 PM, Lou Logan wrote:
>
> OK, of course. Same for patch 2/6. No need to submit patches for simple typos.
...also 1/6.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Fri, Dec 28, 2018, at 12:22 PM, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/qsvenc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c
> index 70772dc0e2..56a3756357 100644
> --- a/libavcod
Signed-off-by: Michael Niedermayer
---
libavformat/libopenmpt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/libopenmpt.c b/libavformat/libopenmpt.c
index 0fff702a36..a334270847 100644
--- a/libavformat/libopenmpt.c
+++ b/libavformat/libopenmpt.c
@@ -259,7 +259,
Signed-off-by: Michael Niedermayer
---
libavcodec/v4l2_m2m.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/v4l2_m2m.h b/libavcodec/v4l2_m2m.h
index 452bf0d9bc..0d4671beb1 100644
--- a/libavcodec/v4l2_m2m.h
+++ b/libavcodec/v4l2_m2m.h
@@ -104,7 +104,7 @@ int ff
Signed-off-by: Michael Niedermayer
---
libavcodec/mjpegbdec.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/libavcodec/mjpegbdec.c b/libavcodec/mjpegbdec.c
index 8583fcb4f9..37d7bb8228 100644
--- a/libavcodec/mjpegbdec.c
+++ b/libavcodec/mjpegbdec.c
@@ -87,9
Signed-off-by: Michael Niedermayer
---
libavcodec/qsvenc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c
index 70772dc0e2..56a3756357 100644
--- a/libavcodec/qsvenc.c
+++ b/libavcodec/qsvenc.c
@@ -1346,7 +1346,7 @@ int ff_qsv_encode(
Signed-off-by: Michael Niedermayer
---
libavcodec/mjpegbdec.c | 24 +---
1 file changed, 9 insertions(+), 15 deletions(-)
diff --git a/libavcodec/mjpegbdec.c b/libavcodec/mjpegbdec.c
index a858707d54..8583fcb4f9 100644
--- a/libavcodec/mjpegbdec.c
+++ b/libavcodec/mjpegbdec.c
Fixes: Timeout
Fixes:
11502/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
Before: Executed
clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
in 11294 ms
After : Executed
clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5
problem occurs in slice quant estimation and slice encoding.
if slice quant >= MAX_STORED_Q we dont use pre-calculated quant matrices but
generate new:
qmat = ctx->custom_q;
qmat_chroma = ctx->custom_q;
for (i = 0; i < 64; i++) {
qmat[i] = ctx->quant_mat[i] * quant;
qmat
On Fri, Dec 28, 2018 at 08:26:58PM +0100, Michael Niedermayer wrote:
> Fixes: Timeout
> Fixes:
> 11502/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
> Before: Executed
> clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
> in 11294 ms
This function is useful in more cases than just imgutils
Signed-off-by: Michael Niedermayer
---
doc/APIchanges | 3 +++
libavutil/imgutils.c | 8 ++--
libavutil/imgutils.h | 10 ++
3 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
Fixes: Timeout
Fixes:
11502/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
Before: Executed
clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5664893810769920
in 11294 ms
After : Executed
clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WCMV_fuzzer-5
Hello, I have got this warning in StaxRip: "encoder : Lavc58.35.100 flac
[dca @ 023cd4738e40] 10 XLL channels is not implemented. Update your FFmpeg
version to the newest one from Git. If the problem still occurs, it means that
your file has a feature which has not been implemented.
[dca @ 00
Thanks Derek, I will repost my question on the users list as well as in IRC
The pastebin is here though
https://pastebin.com/Vq8GFaui
On 12/28/2018 8:30 AM, Derek Buitenhuis wrote:
On 28/12/2018 16:21, Larry Apolonio wrote:
[...]
You'd need to post your whole config.log (pastebin) likely.
On 28/12/2018 17:04, Alex Mogurenko wrote:
> problem occurs in slice quant estimation and slice encoding.
>
> if slice quant >= MAX_STORED_Q we dont use pre-calculated quant matrices
> but generate new:
>
> qmat = ctx->custom_q;
>
> qmat_chroma = ctx->custom_q;
>
> for (i = 0; i
problem occurs in slice quant estimation and slice encoding.
if slice quant >= MAX_STORED_Q we dont use pre-calculated quant matrices
but generate new:
qmat = ctx->custom_q;
qmat_chroma = ctx->custom_q;
for (i = 0; i < 64; i++) {
qmat[i] = ctx->quant_mat[i] * quant;
On Wed, Dec 26, 2018 at 10:16:47PM +0100, Marton Balint wrote:
>
>
> On Wed, 26 Dec 2018, Paul B Mahol wrote:
>
> >On 12/26/18, Michael Niedermayer wrote:
> >>On Wed, Dec 26, 2018 at 04:32:17PM +0100, Paul B Mahol wrote:
> >>>On 12/25/18, Michael Niedermayer wrote:
> Fixes: Timeout
>
On 27/12/2018 19:28, Alex Mogurenko wrote:
> ---
> libavcodec/proresenc_kostya.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
Can you give a little more detail about what's changed and why,
in the commit message?
It looks like custom_chroma_q is zero initialized and never set to
On 28/12/2018 15:39, Toby Steele wrote:
> I was wondering whether there are plans to support AES-CBCS mode encryption
> as well? This is needed to support CENC-compatible encrypted HLS content
> using the fragmented MP4 container format, and so would be a very useful
> addition.
I'm not aware of a
On Sun, Dec 23, 2018 at 04:05:12PM +0100, Michael Niedermayer wrote:
> On Wed, Dec 19, 2018 at 10:35:25AM +0100, Jerome Martinez wrote:
> > On 19/12/2018 02:40, Michael Niedermayer wrote:
> > >Signed-off-by: Michael Niedermayer
> > >---
> > > libavcodec/ffv1enc.c | 10 +++---
> > > l
On 28/12/2018 16:21, Larry Apolonio wrote:
> [...]
You'd need to post your whole config.log (pastebin) likely.
However, this list is for development of FFmpeg itself, and this
question should be on the user mailing list, or #ffmpeg on FreeNode,
where you'll likely get better answers.
Cheers,
- D
On 12/28/2018 3:09 AM, Moritz Barsnick wrote:
On Thu, Dec 27, 2018 at 22:38:24 -0800, Larry Apolonio wrote:
ERROR: x265 not found using pkg-config
[...]
pkg-config --exists --print-errors x265
Package x265 was not found in the pkg-config search path.
Perhaps you should add the directory contai
On 24/12/2018 19:55, Derek Buitenhuis wrote:
> This breaks totally valid files that get caught in its heuristic.
>
> This, according to the commit message, is my own doing, having asked
> Michael to implement this check and providing a sample that was
> "wrong". I am now atoning for my sins, and r
On 28/12/2018 10:10, Guo, Yejun wrote:
> This patch just enables the path from ffmpeg to libx264,
> the more encoders can be added later.
>
> Signed-off-by: Guo, Yejun
> ---
> libavcodec/libx264.c | 39 +++
> 1 file changed, 39 insertions(+)
Seems OK.
- Dere
On 28/12/2018 10:09, Guo, Yejun wrote:
> The encoders such as libx264 support different QPs offset for different MBs,
> it makes possible for ROI-based encoding. It makes sense to add support
> within ffmpeg to generate/accept ROI infos and pass into encoders.
>
> Typical usage: After AVFrame is d
Hi There,
Looking at current MP4 encryption support, using the 'ffmpeg -h muxer=mp4'
command, I can see that only AES-CTR mode is supported.
I was wondering whether there are plans to support AES-CBCS mode encryption
as well? This is needed to support CENC-compatible encrypted HLS content
On 12/24/18, Derek Buitenhuis wrote:
> On 24/12/2018 17:47, David Bryant wrote:
>> I want to do that, but am swamped at work right now, so it will probably
>> be a few months before I can get to that.
>>
>> In the meantime, I think this patch would be a safe stopgap (and prevent
>> the Kodi crash)
On Thu, Dec 27, 2018 at 22:38:24 -0800, Larry Apolonio wrote:
> ERROR: x265 not found using pkg-config
[...]
> pkg-config --exists --print-errors x265
> Package x265 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `x265.pc'
> to the PKG_CONFIG_PATH env
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Moritz Barsnick
> Sent: Thursday, December 27, 2018 8:47 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH V2] avfilter: Add tonemap vaapi filter
>
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of
> Michael Niedermayer
> Sent: Thursday, December 27, 2018 9:06 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] [PATCH V2] avfilter: Add tonemap vaapi filter
>
38 matches
Mail list logo