> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Sunday, May 1, 2022 6:52 AM
> To: an...@khirnov.net; ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related
> code when MFX_VERSION < 2.0
>
> On Sun, 2022-05-01 at 03
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Sunday, May 1, 2022 6:15 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/5] avutil/hwcontext_d3d11va:
> fix the uninitialized texture bindflag
>
> On Sat, 2022-04-30 at 13:59 +
On Sun, 2022-05-01 at 03:10 +, Soft Works wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Xiang, Haihao
> > Sent: Sunday, May 1, 2022 4:16 AM
> > To: an...@khirnov.net; ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio relat
On Sat, 2022-04-30 at 13:59 +, Soft Works wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Hendrik Leppkes
> > Sent: Saturday, April 30, 2022 12:02 AM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH v2
On Sat, 2022-04-30 at 17:14 +0100, Mark Thompson wrote:
> On 28/04/2022 10:23, Haihao Xiang wrote:
> > 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 change
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Sunday, May 1, 2022 4:16 AM
> To: an...@khirnov.net; ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related
> code when MFX_VERSION < 2.0
>
> On Sat, 2022-04-30 at 16
On Sat, 2022-04-30 at 16:51 +, Soft Works wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Xiang, Haihao
> > Sent: Wednesday, April 6, 2022 5:38 AM
> > To: an...@khirnov.net; ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio
> -Original Message-
> From: ffmpeg-devel On Behalf Of Mark
> Thompson
> Sent: Saturday, April 30, 2022 11:39 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 1/3] avutils/hwcontext: add derive-
> device function which searches for existing devices in both direction
On Thu, Mar 31, 2022 at 12:49:55AM +0200, Andreas Rheinhardt wrote:
> This is possible, because every given FFCodec has to implement
> exactly one of these. Doing so decreases sizeof(FFCodec) and
> therefore decreases the size of the binary.
> Notice that in case of position-independent code the de
On 30/04/2022 21:07, softworkz wrote:
From: softworkz
The test /libavutil/tests/hwdevice checks that when deriving a device
from a source device and then deriving back to the type of the source
device, the result is matching the original source device, i.e. the
derivation mechanism doesn't crea
On Sat, Apr 30, 2022 at 12:26 PM Mark Thompson wrote:
>
> On 30/04/2022 18:53, Pierre-Anthony Lemieux wrote:
> > On Sat, Apr 30, 2022 at 10:31 AM Mark Thompson wrote:
> >>
> >> On 24/04/2022 11:14, Zane van Iperen wrote:
> >>> From: Pierre-Anthony Lemieux
> >>>
> >>> ---
> >>>libavcodec/cbs_
Michael Niedermayer:
> Fixes: Assertion failure
> Fixes:
> 46662/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_HEVC_fuzzer-4947860854013952
>
> This also results in more frames to be decoded from fate samples
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree
From: softworkz
Signed-off-by: softworkz
---
libavfilter/vf_hwmap.c| 4 ++--
libavfilter/vf_hwupload.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_hwmap.c b/libavfilter/vf_hwmap.c
index 2e03dfc1fe..b79cf6732c 100644
--- a/libavfilter/vf_hwmap.c
+++
From: softworkz
Signed-off-by: softworkz
---
doc/APIchanges | 3 +++
libavutil/version.h | 4 ++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index 1a9f0a303e..3d467bd3d6 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -14,6 +14,9 @@
From: softworkz
The test /libavutil/tests/hwdevice checks that when deriving a device
from a source device and then deriving back to the type of the source
device, the result is matching the original source device, i.e. the
derivation mechanism doesn't create a new device in this case.
Previousl
This is an updated version of: [PATCH v4 1/1] avutils/hwcontext: When
deriving a hwdevice, search for existing device in both directions
There has been an objection that the earlier patchset would change API
behavior, and that this change should be limited to ffmpeg cli.
To achieve this, the API
James Almer:
>
>
> On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
>> Soft Works:
>>> Hi,
>>>
>>> is it a known issue that the current head of the master branch has
>>> FATE errors?
>>>
>>> I get the same locally as well as on the automated GitHub build.
>>> One is this:
>>>
>>> --- ./tests/ref/v
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Saturday, April 30, 2022 9:33 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
>
>
> On 4/30/2022 4:31 PM, Felix LeClair wrote:
> >
> >
> >> On Apr 30, 2022, at 15:25, Soft Works
On 4/30/2022 4:31 PM, Felix LeClair wrote:
On Apr 30, 2022, at 15:25, Soft Works wrote:
-Original Message-
From: ffmpeg-devel On Behalf Of
Felix LeClair
Sent: Saturday, April 30, 2022 9:22 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] FATE Erro
> On Apr 30, 2022, at 15:25, Soft Works wrote:
>
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> Felix LeClair
>> Sent: Saturday, April 30, 2022 9:22 PM
>> To: FFmpeg development discussions and patches > de...@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] FATE Errors
>
On Fri, Apr 29, 2022 at 04:48:23PM +0200, Martijn van Beurden wrote:
> Op wo 6 apr. 2022 om 09:12 schreef Martijn van Beurden :
> >
> > Op di 5 apr. 2022 om 15:37 schreef Martijn van Beurden :
> > >
> > > ---
> > > libavcodec/flacdec.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
>
On 30/04/2022 18:53, Pierre-Anthony Lemieux wrote:
On Sat, Apr 30, 2022 at 10:31 AM Mark Thompson wrote:
On 24/04/2022 11:14, Zane van Iperen wrote:
From: Pierre-Anthony Lemieux
---
libavcodec/cbs_sei.h | 3 ++-
libavcodec/vaapi_encode_h264.c | 8
2 files changed,
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Felix LeClair
> Sent: Saturday, April 30, 2022 9:22 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> Both times I’ve encountered were on PopOS (think Debian/Ubunt
Both times I’ve encountered were on PopOS (think Debian/Ubuntu meets arch like
timing release)
Currently pulling to a macOS machine and seeing if it can be replicated there.
-FCLC
> On Apr 30, 2022, at 15:19, Soft Works wrote:
>
>
>
>> -Original Message-
>> From: ffmpeg-devel On
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> James Almer
> Sent: Saturday, April 30, 2022 9:10 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
>
>
> On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
> > Soft Works:
> >> Hi,
> >>
> >> is it a kno
On 30/04/2022 19:38, Andreas Rheinhardt wrote:
Mark Thompson:
On 08/02/2022 09:41, Andreas Rheinhardt wrote:
L[i] can be in the range of 0-255, see table B.5 of ITU T.81.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/cbs_jpeg.h | 2 +-
libavcodec/cbs_jpeg_syntax_templa
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Andreas Rheinhardt
> Sent: Saturday, April 30, 2022 9:07 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> Soft Works:
> > Hi,
> >
> > is it a known issue that the current head of the master branch ha
On 4/30/2022 4:06 PM, Andreas Rheinhardt wrote:
Soft Works:
Hi,
is it a known issue that the current head of the master branch has
FATE errors?
I get the same locally as well as on the automated GitHub build.
One is this:
--- ./tests/ref/vsynth/vsynth2-mpeg2-422 2022-04-30 14:23:44.3304240
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Felix LeClair
> Sent: Saturday, April 30, 2022 9:01 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> I’ve been getting the same locally, assumed an issue had alre
Soft Works:
> Hi,
>
> is it a known issue that the current head of the master branch has
> FATE errors?
>
> I get the same locally as well as on the automated GitHub build.
> One is this:
>
> --- ./tests/ref/vsynth/vsynth2-mpeg2-422 2022-04-30 14:23:44.330424058 +
> +++ tests/data/fate/vsynt
I’ve been getting the same locally, assumed an issue had already been opened.
-Fclc
> On Apr 30, 2022, at 14:54, Soft Works wrote:
>
> Hi,
>
> is it a known issue that the current head of the master branch has
> FATE errors?
>
> I get the same locally as well as on the automated GitHub buil
Hi,
is it a known issue that the current head of the master branch has
FATE errors?
I get the same locally as well as on the automated GitHub build.
One is this:
--- ./tests/ref/vsynth/vsynth2-mpeg2-422 2022-04-30 14:23:44.330424058 +
+++ tests/data/fate/vsynth2-mpeg2-422 2022-04-30 14:38:41
On 28/03/2022 02:08, James Almer wrote:
This prevents CBS from propagating zeroed AV1RawFrameHeader units in reading
scenarios.
Writing scenarios remain unaffected as the content of these units is not used
to assemble the bitstream.
Signed-off-by: James Almer
---
libavcodec/cbs_av1.c
Mark Thompson:
> On 08/02/2022 09:41, Andreas Rheinhardt wrote:
>> L[i] can be in the range of 0-255, see table B.5 of ITU T.81.
>>
>> Signed-off-by: Andreas Rheinhardt
>> ---
>> libavcodec/cbs_jpeg.h | 2 +-
>> libavcodec/cbs_jpeg_syntax_template.c | 4 ++--
>> 2 files changed
On Sat, Apr 30, 2022 at 10:31 AM Mark Thompson wrote:
>
> On 24/04/2022 11:14, Zane van Iperen wrote:
> > From: Pierre-Anthony Lemieux
> >
> > ---
> > libavcodec/cbs_sei.h | 3 ++-
> > libavcodec/vaapi_encode_h264.c | 8
> > 2 files changed, 6 insertions(+), 5 deletions(-)
On 29/03/2022 09:29, Wenbin Chen wrote:
cbs_av1_write_unit() check pbc size after parsing obu frame, and return
AVERROR(ENOSPC) if pbc is small. pbc will be reallocated and this obu
frame will be parsed again, but this may cause error because
CodedBitstreamAV1Context has already been updated, for
On 24/04/2022 11:14, Zane van Iperen wrote:
From: Pierre-Anthony Lemieux
---
libavcodec/cbs_sei.h | 3 ++-
libavcodec/vaapi_encode_h264.c | 8
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/libavcodec/cbs_sei.h b/libavcodec/cbs_sei.h
index c7a7a95be0..67c6
On 08/02/2022 09:41, Andreas Rheinhardt wrote:
L[i] can be in the range of 0-255, see table B.5 of ITU T.81.
Signed-off-by: Andreas Rheinhardt
---
libavcodec/cbs_jpeg.h | 2 +-
libavcodec/cbs_jpeg_syntax_template.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Xiang, Haihao
> Sent: Wednesday, April 6, 2022 5:38 AM
> To: an...@khirnov.net; ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related
> code when MFX_VERSION < 2.0
>
> On Tue, 2022-04-05
On 28/04/2022 10:23, Haihao Xiang wrote:
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 Win
> -Original Message-
> From: ffmpeg-devel On Behalf Of Tong
> Wu
> Sent: Friday, April 29, 2022 12:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Tong Wu
> Subject: [FFmpeg-devel] [PATCH v2 5/5] avutil/hwcontext_qsv: map
> D3D11VA frames to QSV frames
>
> Fixes:
> $ ffmpeg.exe -init_hw_dev
> -Original Message-
> From: ffmpeg-devel On Behalf Of Tong
> Wu
> Sent: Friday, April 29, 2022 12:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Tong Wu
> Subject: [FFmpeg-devel] [PATCH v2 4/5] avutil/hwcontext_qsv: map QSV
> frames to D3D11VA frames
>
> When input is a rawvideo, after ma
On 29/04/2022 08:31, Fei Wang wrote:
From: Linjie Fu
Add support for max frame size:
- max_frame_size (bytes) to indicate the max allowed size for frame.
If the frame size exceeds the limitation, encoder will to control the frame
size by adjusting QP value.
ffmpeg -hwaccel vaapi -vaapi_d
> -Original Message-
> From: ffmpeg-devel On Behalf Of Tong
> Wu
> Sent: Friday, April 29, 2022 12:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Tong Wu
> Subject: [FFmpeg-devel] [PATCH v2 3/5] avutil/hwcontext_d3d11va: add a
> format check for staging texture
>
> The texDesc.Format needs
> -Original Message-
> From: ffmpeg-devel On Behalf Of Tong
> Wu
> Sent: Friday, April 29, 2022 12:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Tong Wu
> Subject: [FFmpeg-devel] [PATCH v2 2/5] avutil/hwcontext_qsv: derive
> QSV frames to D3D11VA frames
>
> Fixes:
> $ ffmpeg.exe -y -hwacc
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> Sent: Saturday, April 30, 2022 12:02 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v2 1/5] avutil/hwcontext_d3d11va:
> fix the uninitialized texture b
> -Original Message-
> From: ffmpeg-devel On Behalf Of nil-
> admir...@mailo.com
> Sent: Friday, April 29, 2022 8:52 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v11 1/6]
> libavutil/wchar_filename.h: Add whcartoutf8, wchartoansi and
> utf8toansi
>
> > A code ch
On Sat, Apr 30, 2022 at 12:18:26AM +0200, Michael Niedermayer wrote:
> Fixes: Assertion failure
it was this
av_assert1((get_bits_count(gb) % 8) == 0);
that failed IIRC
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Rewriting code that is poorly written but fu
48 matches
Mail list logo
