Renamed to headers, will apply right now!
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Signed-off-by: Paul B Mahol
---
configure |1 +
libavcodec/Makefile |1 +
libavcodec/allcodecs.c |1 +
libavcodec/bink2.c | 481 +
libavcodec/bink2f.h | 1236
libavcodec/bink2g.h | 1481 +
> -Original Message-
> From: Xiang, Haihao
> Sent: Wednesday, June 1, 2022 7:16 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: softwo...@hotmail.com
> Subject: Re: [FFmpeg-devel] [PATCH 6/6] avcodec/qsvdec: Implement SEI
> parsing for QSV decoders
>
> On Thu, 2022-05-26 at 08:08 +, softwor
Paul B Mahol:
> Renamed to headers, will apply right now!
In this case you will likely either add these headers to SKIPHEADERS or
add the necessary headers to them to make them standalone.
- Andreas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Wed, Jun 1, 2022 at 10:57 AM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Paul B Mahol:
> > Renamed to headers, will apply right now!
>
> In this case you will likely either add these headers to SKIPHEADERS or
> add the necessary headers to them to make them standalone.
>
>
Why
Paul B Mahol:
> On Wed, Jun 1, 2022 at 10:57 AM Andreas Rheinhardt <
> andreas.rheinha...@outlook.com> wrote:
>
>> Paul B Mahol:
>>> Renamed to headers, will apply right now!
>>
>> In this case you will likely either add these headers to SKIPHEADERS or
>> add the necessary headers to them to make
From: softworkz
Signed-off-by: softworkz
---
libavcodec/hevcdec.c | 117 +--
libavcodec/hevcdec.h | 9
2 files changed, 67 insertions(+), 59 deletions(-)
diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c
index f782ea6394..9e9bb48202 100644
Missing SEI information has always been a major drawback when using the QSV
decoders. I used to think that there's no chance to get at the data without
explicit implementation from the MSDK side (or doing something weird like
parsing in parallel). It turned out that there's a hardly known api metho
From: softworkz
Signed-off-by: softworkz
---
libavcodec/h264_slice.c | 98 +
libavcodec/h264dec.h| 2 +
2 files changed, 52 insertions(+), 48 deletions(-)
diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
index d56722a5c2..f2a4c1c657 10
From: softworkz
Signed-off-by: softworkz
Signed-off-by: Anton Khirnov
---
doc/APIchanges | 4 +++
libavutil/frame.c | 67 +++--
libavutil/frame.h | 32 ++
libavutil/version.h | 2 +-
4 files changed, 78 insertions(+), 27 de
From: softworkz
Signed-off-by: softworkz
---
libavcodec/qsvdec.c | 234
1 file changed, 234 insertions(+)
diff --git a/libavcodec/qsvdec.c b/libavcodec/qsvdec.c
index 5fc5bed4c8..3fc5dc3f20 100644
--- a/libavcodec/qsvdec.c
+++ b/libavcodec/qsvdec.c
From: softworkz
Signed-off-by: softworkz
---
libavfilter/qsvvpp.c | 6 ++
libavfilter/vf_overlay_qsv.c | 19 +++
2 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/libavfilter/qsvvpp.c b/libavfilter/qsvvpp.c
index 954f882637..f4bf628073 100644
--- a/lib
From: softworkz
Signed-off-by: softworkz
---
libavcodec/mpeg12.h| 28
libavcodec/mpeg12dec.c | 40 +---
2 files changed, 33 insertions(+), 35 deletions(-)
diff --git a/libavcodec/mpeg12.h b/libavcodec/mpeg12.h
index e0406b32d
Quoting Vardan Margaryan (2022-05-23 18:06:16)
> Y, U, V data is loaded at the end of the current iteration for the next
> iteration.
> It results in memory access past the frame data on the last iteration
> (that data is never used after the loading).
>
> So load data at the start of the iterat
Quoting Andreas Rheinhardt (2022-06-01 11:03:28)
> "make checkheaders" does the latter. It is not part of the standard fate
Any reason it isn't?
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/
Quoting Paul B Mahol (2022-05-31 13:32:36)
> +const FFCodec ff_qoi_decoder = {
> +.p.name = "qoi",
> +.p.long_name= NULL_IF_CONFIG_SMALL("QOI (Quite OK Image format)
> image"),
> +.p.type = AVMEDIA_TYPE_VIDEO,
> +.p.id = AV_CODEC_ID_QOI,
> +.p.capa
Quoting Tomas Härdin (2022-05-31 11:58:39)
>
>
> From fedd7f9ae2c691a25c37be935d7547be61d46017 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Tomas=20H=C3=A4rdin?=
> Date: Fri, 20 May 2022 11:38:25 +0200
> Subject: [PATCH 1/8] libavcodec/jpeg2000_parser: Speed up long skips
>
> ---
> libavcodec/jp
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 46723972dc..274fc89203 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -546,6 +546,7 @@ Operating systems / CPU architectures
Alpha Falk Hueffner
MIPS
On Wed, Jun 1, 2022 at 11:51 AM Anton Khirnov wrote:
> Quoting Paul B Mahol (2022-05-31 13:32:36)
> > +const FFCodec ff_qoi_decoder = {
> > +.p.name = "qoi",
> > +.p.long_name= NULL_IF_CONFIG_SMALL("QOI (Quite OK Image format)
> image"),
> > +.p.type = AVMEDIA_TYPE
Quoting John Cox (2022-05-27 15:51:17)
> Hwaccel doesn't use any of the block strength, pcm, slice address, etc.
> arrays which can be >100k each for 4k video. Patch to avoid initial
> allocation and zeroing at the start of every frame. On a Pi4 the memsets
> can use 10% CPU on 4k 60Hz decode, this
Quoting Michael Niedermayer (2022-05-30 21:09:10)
> alpha-linux-gnu-gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010 with qemu-alpha
> version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.39)
> trigger a FPE on the DBL_MAX * 9 operation
>
> Iam not 100% sure why, but if i mess with mfp-trap-mode the compi
Signed-off-by: Paul B Mahol
---
configure |1 +
libavcodec/Makefile |1 +
libavcodec/allcodecs.c |1 +
libavcodec/bink2.c | 381 ++
libavcodec/bink2.h | 135
libavcodec/bink2f.h | 1240
libavcodec/bink2g.
Dawid Kozinski:
> - Added xeve encoder wrapper
> - Added xevd dencoder wrapper
> - Added documentation for xeve and xevd wrappers
> - Added parser for EVC format
> - Changes in project configuration file and libavcodec Makefile
>
> Signed-off-by: Dawid Kozinski
> ---
> configure
> 在 2022年6月1日，18:21，Shiyou Yin 写道：
>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 46723972dc..274fc89203 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -546,6 +546,7 @@ Operating systems / CPU architectures
>
> Alpha
ons 2022-06-01 klockan 11:59 +0200 skrev Anton Khirnov:
> Quoting Tomas Härdin (2022-05-31 11:58:39)
> >
> >
> > From fedd7f9ae2c691a25c37be935d7547be61d46017 Mon Sep 17 00:00:00
> > 2001
> > From: =?UTF-8?q?Tomas=20H=C3=A4rdin?=
> > Date: Fri, 20 May 2022 11:38:25 +0200
> > Subject: [PATCH 1/8]
Quoting Tomas Härdin (2022-06-01 14:34:57)
> ons 2022-06-01 klockan 11:59 +0200 skrev Anton Khirnov:
> > Quoting Tomas Härdin (2022-05-31 11:58:39)
> > >
> > >
> > > From fedd7f9ae2c691a25c37be935d7547be61d46017 Mon Sep 17 00:00:00
> > > 2001
> > > From: =?UTF-8?q?Tomas=20H=C3=A4rdin?=
> > > Dat
On 5/25/2022 2:15 PM, James Almer wrote:
Normally, both the source and dest frame would have only the old API fields
set, only the new API fields set, or both set. But in some cases, like when
calling av_frame_ref() using a non reference counted source frame where only
the old channel layout API
I'm working on a new patchset for this and non-strict mode. Slice
threading requires openjpeg >= 2.2.0 while configure only demands
2.1.0.
/Tomas
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To
From: Xu Guangxin
For range extension, the luma/chroma offset is larger than 8 bits, we
need fill the 16 bits version.
Signed-off-by: Xu Guangxin
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/vaapi_hevc.c | 53 -
1 file changed, 37 in
On Tue, May 31, 2022 at 7:17 PM Ronald S. Bultje wrote:
> Hi,
>
> On Thu, May 19, 2022 at 4:42 PM Mohammad Izadi <
> izadi-at-google@ffmpeg.org> wrote:
>
> > ffmpeg support YCOCG (YCOCG=YCGCO). However, vf_colorspace is only
> support
> > YCGCO as input. Added YCOCG to the inputs.
> > ---
> >
On Wed, 2022-05-25 at 21:13 +0800, Wenbin Chen wrote:
> From: Yue Heng
>
> To do more accurate QP control, add min/max QP control on I/P/B frame
> separately to qsv encoder. qmax and qmin still work but newly-added
> options have higher priority.
>
> Signed-off-by: Yue Heng
> Signed-off-by: Wen
On Tue, May 31, 2022 at 11:58:39AM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c | 11 +++
> 1 file changed, 11 insertions(+)
> 634546fb5a0eb281eea87ad7471c503f5bc9e8ab
> 0001-libavcodec-jpeg2000_parser-Speed-up-long-skips.patch
> From fedd7f9ae2c691a25c37be935d7547be61d46017 Mon
On Wed, Jun 01, 2022 at 06:21:19PM +0200, Michael Niedermayer wrote:
> On Tue, May 31, 2022 at 11:58:39AM +0200, Tomas Härdin wrote:
> >
>
> > jpeg2000_parser.c | 11 +++
> > 1 file changed, 11 insertions(+)
> > 634546fb5a0eb281eea87ad7471c503f5bc9e8ab
> > 0001-libavcodec-jpeg2000_pa
On Fri, 2022-05-06 at 13:49 +0800, Wenbin Chen wrote:
> Use the mfxEncoderCtrl parameter to enable ROI. Get side data
> "AVRegionOfInterest"
> from filter "addroi" and use it to configure "mfxExtEncoderROI" which is
> the MediaSDK's ROI configuration.
>
> Signed-off-by: Wenbin Chen
> ---
> libav
On Tue, May 31, 2022 at 12:01:35PM +0200, Tomas Härdin wrote:
>
> jpeg2000.c |7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
> 05721f386bc015c4402f70bdb14dd6a8931a4429
> 0008-libavcodec-jpeg2000-Call-av_codec_is_encoder-only-on.patch
> From 1485b06278f38dcda5ff83f17e0a3446949
On Tue, May 31, 2022 at 12:00:26PM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c |6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
> b0a91cd73f5b4887a9d87518bc16ed6e1f104a39
> 0005-libavcodec-jpeg2000_parser-Rearrange-ifs.patch
> From 68add7a3abb85d84e484ae58b1661d7bbf66c04d
On Tue, May 31, 2022 at 12:01:12PM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c |8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
> a16f2b29057a6e89ef7a03529fb4c66ecc704094
> 0007-libavcodec-jpeg2000_parser-Localize-m-bytes_read.patch
> From 7b5e442033f0691bddbe2c2a0292f4a
On Tue, May 31, 2022 at 12:00:05PM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c | 26 +++---
> 1 file changed, 19 insertions(+), 7 deletions(-)
> 7661a5b239a94ccba349c916a390d957479a9771
> 0004-libavcodec-jpeg2000_parser-LUTify-info_marker.patch
> From d84f106d1eac7a3
On Tue, May 31, 2022 at 11:59:42AM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c |3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
> c4714ab68e0049d0ee84e5c7f89582c5426c10ad
> 0003-libavcodec-jpeg2000_parser-next_state-is-just-a-temp.patch
> From 682701613a9b816aac9e75848216e3c7e
On Tue, May 31, 2022 at 11:59:15AM +0200, Tomas Härdin wrote:
>
> jpeg2000_parser.c | 23 ++-
> 1 file changed, 10 insertions(+), 13 deletions(-)
> 54fa89b694ebf1b0fb5adf18a5f53a2aabcbc9c9
> 0002-libavcodec-jpeg2000_parser-Simplify-fix-reset_contex.patch
> From 4bf4593c0d
On Wed, Jun 01, 2022 at 12:38:05PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2022-05-30 21:09:10)
> > alpha-linux-gnu-gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010 with
> > qemu-alpha version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.39)
> > trigger a FPE on the DBL_MAX * 9 operation
On Wed, 2022-06-01 at 09:06 +, softworkz wrote:
> From: softworkz
>
> Signed-off-by: softworkz
> ---
> libavcodec/qsvdec.c | 234
> 1 file changed, 234 insertions(+)
>
> diff --git a/libavcodec/qsvdec.c b/libavcodec/qsvdec.c
> index 5fc5bed4c8..
On Sun, Apr 24, 2022 at 11:35 AM Vignesh Venkatasubramanian
wrote:
>
> Update the still AVIF parser to only read the primary item. With this
> patch, AVIF still images with exif/icc/alpha channel will no longer
> fail to parse.
>
> For example, this patch enables parsing of files in:
> https://git
> -Original Message-
> From: Xiang, Haihao
> Sent: Wednesday, June 1, 2022 7:20 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: haihao.xiang-at-intel@ffmpeg.org; softwo...@hotmail.com
> Subject: Re: [FFmpeg-devel] [PATCH v2 6/6] avcodec/qsvdec: Implement SEI
> parsing for QSV decoders
>
> O
On Wed, May 18, 2022 at 2:56 PM Vignesh Venkatasubramanian
wrote:
>
> AVIF specification allows for alpha channel as an auxillary item (in
auxiliary
> case of still images) or as an auxillary track (in case of animated
> images). Add support for both of these. The AVIF muxer will take
> exactly
Missing SEI information has always been a major drawback when using the QSV
decoders. I used to think that there's no chance to get at the data without
explicit implementation from the MSDK side (or doing something weird like
parsing in parallel). It turned out that there's a hardly known api metho
From: softworkz
Signed-off-by: softworkz
---
libavcodec/hevcdec.c | 117 +--
libavcodec/hevcdec.h | 9
2 files changed, 67 insertions(+), 59 deletions(-)
diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c
index f782ea6394..9e9bb48202 100644
From: softworkz
Signed-off-by: softworkz
---
libavcodec/h264_slice.c | 98 +
libavcodec/h264dec.h| 2 +
2 files changed, 52 insertions(+), 48 deletions(-)
diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
index d56722a5c2..f2a4c1c657 10
From: softworkz
Signed-off-by: softworkz
Signed-off-by: Anton Khirnov
---
doc/APIchanges | 4 +++
libavutil/frame.c | 67 +++--
libavutil/frame.h | 32 ++
libavutil/version.h | 2 +-
4 files changed, 78 insertions(+), 27 de
From: softworkz
Signed-off-by: softworkz
---
libavfilter/qsvvpp.c | 6 ++
libavfilter/vf_overlay_qsv.c | 19 +++
2 files changed, 21 insertions(+), 4 deletions(-)
diff --git a/libavfilter/qsvvpp.c b/libavfilter/qsvvpp.c
index 954f882637..f4bf628073 100644
--- a/lib
From: softworkz
Signed-off-by: softworkz
---
libavcodec/qsvdec.c | 234
1 file changed, 234 insertions(+)
diff --git a/libavcodec/qsvdec.c b/libavcodec/qsvdec.c
index 5fc5bed4c8..e854f363ec 100644
--- a/libavcodec/qsvdec.c
+++ b/libavcodec/qsvdec.c
From: softworkz
Signed-off-by: softworkz
---
libavcodec/mpeg12.h| 28
libavcodec/mpeg12dec.c | 40 +---
2 files changed, 33 insertions(+), 35 deletions(-)
diff --git a/libavcodec/mpeg12.h b/libavcodec/mpeg12.h
index e0406b32d
On Wed, Jun 1, 2022 at 10:52 AM James Zern wrote:
>
> On Wed, May 18, 2022 at 2:56 PM Vignesh Venkatasubramanian
> wrote:
> >
> > AVIF specification allows for alpha channel as an auxillary item (in
>
> auxiliary
>
Done.
> > case of still images) or as an auxillary track (in case of animated
>
AVIF specification allows for alpha channel as an auxiliary item (in
case of still images) or as an auxiliary track (in case of animated
images). Add support for both of these. The AVIF muxer will take
exactly two streams (when alpha is present) as input (first one being
the YUV planes and the sec
Hi,
On Tue, May 31, 2022 at 10:26 AM Ronald S. Bultje
wrote:
> On Sat, May 28, 2022 at 9:30 AM Leo Izen wrote:
>
>> This commit moves some of the functionality from avfilter/colorspace
>> into avutil/csp and exposes it as a public API so it can be used by
>> libavcodec and/or libavformat. It al
Hi,
On Tue, May 31, 2022 at 9:21 AM Ronald S. Bultje wrote:
> If the block is at the end of the allocated buffer and there is no
> padding, this will over-read, which may cause crashes. Reported by
> Firefox.
> ---
> libavcodec/x86/vp9mc.asm | 5 +
> 1 file changed, 5 insertions(+)
>
> diff
On Thu, 26 May 2022 at 09:09, ffmpegagent wrote:
> But that doesn't help. Those bugs exist and I'm sharing my workarounds,
> which are empirically determined by testing a range of files. If someone is
> interested, I can provide private access to a repository where we have been
> testing this. Al
printf %s with a NULL pointer is undefined behavior. Not returning
a NULL pointer makes for a nicer function for API users, including
in FFmpeg, since then you don't have to check it, instead you can
just print it. 32/44 uses in FFmpeg did not check for NULL.
This also matches behavior with avco
From: Kieran Kunhya
Sent: Wednesday, June 1, 2022 9:16 PM
To: FFmpeg development discussions and patches
Cc: softworkz
Subject: Re: [FFmpeg-devel] [PATCH 0/6] Implement SEI parsing for QSV decoders
On Thu, 26 May 2022 at 09:09, ffmpegagent
mailto:ffmpegag...@gmail.com>> wrote:
But that doesn
On Wed, Jun 1, 2022 at 11:52 AM xyesbee wrote:
>
> Why can it not accept it as one but two distinct streams? Why the extra
> hurdle of alphaextract? YUVA pixel format exists though.
Yes, while the YUVA pixel formats exist, AVIF specification requires
alpha channel to be a separate track (i.e.) w
>
> Captions aren’t exactly “frame accurate” anyway as each frame has just a
> very small piece
>
> of information and only when a certain sequence is complete, it leads to
> some new letters
>
> or line being ready for display.
>
In many use-cases, you want them to be frame-accurate. Final rendit
---
libswscale/input.c | 1 +
libswscale/utils.c | 1 +
libswscale/version.h | 2 +-
tests/ref/fate/filter-pixdesc-nv16 | 1 +
tests/ref/fate/filter-pixfmts-copy | 1 +
tests/ref/fate/filter-pixfmts-crop | 1 +
tests
On Wed, Jun 1, 2022 at 10:30 AM James Zern wrote:
>
> On Sun, Apr 24, 2022 at 11:35 AM Vignesh Venkatasubramanian
> wrote:
> >
> > Update the still AVIF parser to only read the primary item. With this
> > patch, AVIF still images with exif/icc/alpha channel will no longer
> > fail to parse.
> >
>
From: Kieran Kunhya
Sent: Wednesday, June 1, 2022 10:26 PM
To: Soft Works
Cc: Kieran Kunhya ; FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH 0/6] Implement SEI parsing for QSV decoders
Captions aren’t exactly “frame accurate” anyway as each frame has just a ver
From: Zane van Iperen
* Addresses review comments
Co-authored-by: Pierre-Anthony Lemieux
Signed-off-by: Zane van Iperen
---
libavutil/Makefile | 2 +
libavutil/uuid.c | 141 +++
libavutil/uuid.h | 147 +
From: Pierre-Anthony Lemieux
---
libavutil/Makefile | 1 +
libavutil/tests/.gitignore | 1 +
libavutil/tests/uuid.c | 141 +
tests/fate/libavutil.mak | 5 ++
4 files changed, 148 insertions(+)
create mode 100644 libavutil/tests/uuid.c
dif
From: Pierre-Anthony Lemieux
---
libavformat/mov.c| 25 +
libavformat/movenc.c | 9 +
2 files changed, 18 insertions(+), 16 deletions(-)
diff --git a/libavformat/mov.c b/libavformat/mov.c
index d7be593a86..f8248ab65b 100644
--- a/libavformat/mov.c
+++ b/liba
From: Pierre-Anthony Lemieux
---
libavformat/smoothstreamingenc.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libavformat/smoothstreamingenc.c b/libavformat/smoothstreamingenc.c
index 1713dd9009..ade6d5723b 100644
--- a/libavformat/smoothstreamingenc.c
+++ b/libavf
From: Pierre-Anthony Lemieux
---
libavformat/imf.h | 18 -
libavformat/imf_cpl.c | 60 +++--
libavformat/imfdec.c| 34 +++
libavformat/tests/imf.c | 18 ++---
4 files changed, 52 insertions(+), 78 deletions(-
From: Pierre-Anthony Lemieux
---
libavfilter/vf_showinfo.c | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
index 12d39310ef..6efcafce28 100644
--- a/libavfilter/vf_showinfo.c
+++ b/libavfilter/vf_showin
Changes in v8:
- Use avutil/csp for both encoding and decoding
- Handle the non-XYB case with an attached ICC Profile on decoding
- clean up some code and segment it out to static functions
Leo Izen (2):
avcodec/libjxldec: properly tag output colorspace
avcodec/libjxlenc: properly read input c
Whether an ICC profile is present or not, the decoder
should now properly tag the colorspace of pixel data
received by the decoder.
---
libavcodec/libjxldec.c | 142 ++---
1 file changed, 133 insertions(+), 9 deletions(-)
diff --git a/libavcodec/libjxldec.c b/l
Whether an ICC profile is present or not, the libjxl
encoder wrapper should now properly read colorspace tags
and forward them to libjxl appropriately, rather than just
assume sRGB as before. It will also print warnings when
colorimetric assumptions are made about the input data.
---
libavcodec/li
From: Haihao Xiang
The oneAPI Video Processing Library (oneVPL) is a single interface for
encode, decode and video processing[1][2]. oneVPL is a successor to Intel(R)
Media
SDK, but removed obsolete features. Intel(R) Media SDK lifetime comes to an
end now, new features for new Intel Gen platfor
From: Haihao Xiang
Intel's oneVPL is a successor to MediaSDK, but removed some obsolete
features of MediaSDK[1], some early versions of oneVPL still use libmfx
as library name[2]. However some of obsolete features, including OPAQUE
memory, multi-frame encode, user plugins and LA_EXT rate control
From: Haihao Xiang
The data structures for VP9 in mfxvp9.h is wrapped by
MFX_VERSION_NEXT, which means those data structures have never been used
in a public release. Actually MFX_CODEC_VP9 and other VP9 stuffs is
added in mfxstructures.h. In addition, mfxdefs.h is included in
mfxvp9.h, so we may
From: Haihao Xiang
The following Cflags has been added to libmfx.pc, so mfx/ prefix is no
longer needed when including mfx headers in FFmpeg.
Cflags: -I${includedir} -I${includedir}/mfx
Some old versions of libmfx have the following Cflags in libmfx.pc
Cflags: -I${includedir}
We may add -
From: Haihao Xiang
User plugin isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL Support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libavco
From: Haihao Xiang
Audio isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libavcodec/qs
From: Haihao Xiang
MFX_RATECONTROL_LA_EXT isn't supported for MFX_VERSION >= 2.0[1][2].
This is in preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
-
From: Haihao Xiang
OPAQUE memory isn't supported for MFX_VERSION >= 2.0[1][2]. This is in
preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
libav
From: Haihao Xiang
In oneVPL, MFXLoad() and MFXCreateSession() are required to create a
workable mfx session[1]
Add config filters for D3D9/D3D11 session (galinart)
The default device is changed to d3d11va for oneVPL when both d3d11va
and dxva2 are enabled on Microsoft Windows
This is in prepa
From: Haihao Xiang
This allows user to build FFmpeg against Intel oneVPL. oneVPL 2.6
is the required minimum version when building Intel oneVPL code.
It will fail to run configure script if both libmfx and libvpl are
enabled.
It is recommended to use oneVPL for new work, even for currently avai
From: Haihao Xiang
Multi-frame encode isn't supported for MFX_VERSION >= 2.0[1][2]. This is
in preparation for oneVPL support
[1]
https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html#msdk-full-name-feature-removals
[2] https://github.com/oneapi-src/oneVPL
---
> On Fri, 2022-05-06 at 13:49 +0800, Wenbin Chen wrote:
> > Use the mfxEncoderCtrl parameter to enable ROI. Get side data
> > "AVRegionOfInterest"
> > from filter "addroi" and use it to configure "mfxExtEncoderROI" which is
> > the MediaSDK's ROI configuration.
> >
> > Signed-off-by: Wenbin Chen
>
From: Wenbin Chen
Use the mfxEncoderCtrl parameter to enable ROI. Get side data
"AVRegionOfInterest"
and use it to configure "mfxExtEncoderROI" which is the MediaSDK's ROI
configuration.
Signed-off-by: Wenbin Chen
---
libavcodec/qsv_internal.h | 4 ++
libavcodec/qsvenc.c | 86
86 matches
Mail list logo
