From: Haihao Xiang
The new modes work on new platforms and are avaialable only for oneVPL.
Signed-off-by: Haihao Xiang
---
libavfilter/vf_vpp_qsv.c | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_vpp_qsv.c b/libavfilter/vf_vpp
From: Haihao Xiang
It only works on Linux
$ ffmpeg -loglevel verbose -init_hw_device qsv=intel -f lavfi -i \
yuvtestsrc -vf "format=uyvy422,vpp_qsv=format=nv12" -f null -
Signed-off-by: Haihao Xiang
---
libavfilter/qsvvpp.c | 9 +
libavfilter/vf_vpp_qsv.c | 3 +++
2 files changed,
From: Haihao Xiang
The SDK supports UYVY from version 1.17, and VPP may support UYVY
input on Linux [1]
$ ffmpeg -loglevel verbose -init_hw_device qsv=intel -f lavfi -i \
yuvtestsrc -vf \
"format=uyvy422,hwupload=extra_hw_frames=32,vpp_qsv=format=nv12" \
-f null -
[1]
https://github.com/Intel-
On 2023-02-03 04:17 am, Marton Balint wrote:
On Thu, 2 Feb 2023, Gyan Doshi wrote:
Prior to 2d924b3a630, ffmpeg.c would exit if any packet write failed.
tee's
write_packet seemingly relied on that to enforce its abort failure
policy.
From 2d924b3a630, ffmpeg only closes that OutputStream
On Tue, 31 Jan 2023 13:17:56 +0100
Anton Khirnov wrote:
> The hardware is old and not relevant today. The decoders also have
> many special quirks and are effectively unmaintained.
> ---
> Philip confirmed on IRC that he no longer has the hardware for
> maintaining this and does not believe it is
From: Linjie Fu
Including sps/pps/slice parameters.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/vaapi_hevc.c | 52 +
1 file changed, 47 insertions(+), 5 deletions(-)
diff --git a/libavcodec/vaapi_hevc.c b/libavcodec/vaapi_hevc.c
ind
From: Linjie Fu
Allow current picture as the reference picture.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/vaapi_hevc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/libavcodec/vaapi_hevc.c b/libavcodec/vaapi_hevc.c
index 29c75e88f0..42e1b62fc3
From: Linjie Fu
According to 8.1.3 and 8.3.2.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/vaapi_hevc.c | 4
1 file changed, 4 insertions(+)
diff --git a/libavcodec/vaapi_hevc.c b/libavcodec/vaapi_hevc.c
index c10617a81a..29c75e88f0 100644
--- a/libavcodec/vaapi_hevc.
From: Linjie Fu
Screen Content Coding allows non-intra slice in an IRAP frame which can
reference the frame itself, and would mark the current decoded picture
as "used for long-term reference", no matter TwoVersionsOfCurrDecPicFlag(8.1.3),
hence some previous restricts are not suitable any more.
From: Linjie Fu
Note that Screen-Extended Main 4:4:4 and 4:4:4 10 supports
chroma_format_idc from 0, 1 or 3, hence both 420 and 444 are
supported.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/vaapi_decode.c | 4 +++-
libavcodec/vaapi_hevc.c | 14 --
libavcode
From: Linjie Fu
uint8_t is big enough and keep consistent with the definition in
cbs_h265.h.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/hevcdec.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/hevcdec.h b/libavcodec/hevcdec.h
index a7fc669b
From: Linjie Fu
According to 7.3.6.1, use_integer_mv_flag should be parsed if
motion_vector_resolution_control_idc equals to 2. If not present, it
equals to motion_vector_resolution_control_idc.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/hevcdec.c | 8
libavcodec
From: Linjie Fu
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
libavcodec/hevcdec.c | 6 ++
libavcodec/hevcdec.h | 4
2 files changed, 10 insertions(+)
diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c
index 567e8d81d4..f9a97ac7f5 100644
--- a/libavcodec/hevcdec.c
+++ b/
From: Linjie Fu
1. Add extension syntax according to 7.3.2.2.3/7.3.2.3.3 in T-REC-H.265-201911.
2. Keep using parsed PPS when bitstream overread for compatibility. For
example, the clip PS_A_VIDYO_3.bit in FATE test has incomplete extension
syntax which will be overread and un-decodable if withou
From: Linjie Fu
Described in HEVC spec A.3.7.
Signed-off-by: Linjie Fu
Signed-off-by: Fei Wang
---
update: fix accidential fail in FATE.
libavcodec/avcodec.h | 1 +
libavcodec/hevc_ps.c | 2 ++
libavcodec/profiles.c | 1 +
3 files changed, 4 insertions(+)
diff --git a/libavcodec/avcodec.h
On Thu, 2 Feb 2023, Gyan Doshi wrote:
Prior to 2d924b3a630, ffmpeg.c would exit if any packet write failed. tee's
write_packet seemingly relied on that to enforce its abort failure policy.
From 2d924b3a630, ffmpeg only closes that OutputStream and keeps on
sending packets of other streams.
Hi,
once again after the pandemic break, FFmpeg has been accepted for CLT 2023 in
Chemnitz, Germany!
This "Chemnitzer Linux Tage" will take place on 11th and 12th of March.
You can find more details on their homepage:
https://chemnitzer.linux-tage.de/2023/en/
We will man a booth with our staff
Prior to 2d924b3a630, ffmpeg.c would exit if any packet write failed. tee's
write_packet seemingly relied on that to enforce its abort failure policy.
>From 2d924b3a630, ffmpeg only closes that OutputStream and keeps on
sending packets of other streams. This breaks the abort behaviour
with the tee
Some files, likely due to faulty packetization or muxing, can have AUDs
at other positions besides the head unit of a packet. Remove these too.
---
libavcodec/h264_metadata_bsf.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/libavcodec/h264_metadata_bsf.c b/liba
On Mon, Jan 30, 2023 at 4:12 PM Marton Balint wrote:
>
> For normal mpegts it also makes sense to include SPS/PPS before IDR-s, so
> I'd say it is better if it is fixed in mpegtsenc.
>
> But it is mandatory to insert AUD NAL-s for every frame, and your patch
> breaks that, because it only inserts
ons 2023-02-01 klockan 10:42 +0100 skrev Nicolas George:
> Tomas Härdin (12023-02-01):
> > This belongs in the demuxer. In fact it appears the decoder
> > duplicates
> > code from the demuxer. Why?
>
> Because sharing code between demuxer and decoder is extremely
> annoying,
> because somebody dec
Useful, in conjuntion with option meta_period, to vary metadata during
stream.
File format is ffmetadata.
---
configure| 2 +-
doc/muxers.texi | 3 +
libavformat/flvenc.c | 133 +--
3 files changed, 107 insertions(+), 31 deletions(-)
d
Allows to re-emit global metadata. Useful for dynamic metadata.
Accepts values:
at_start or 0, for insertion only at start
at_keyframes or 1, for insertion at each video keyframe
every_packet or 2, for insertion with all video packets
---
doc/muxers.texi | 20
libavforma
Useful, in conjuntion with option meta_period, to vary metadata during
stream.
File format is ffmetadata.
---
configure| 2 +-
doc/muxers.texi | 3 +
libavformat/flvenc.c | 134 +--
3 files changed, 108 insertions(+), 31 deletions(-)
d
Allows to re-emit global metadata. Useful for dynamic metadata.
Accepts values:
at_start or 0, for insertion only at start
at_keyframes or 1, for insertion at each video keyframe
every_packet or 2, for insertion with all video packets
---
doc/muxers.texi | 20
libavforma
If the gAMA chunk is present, the gamma-transfer described by it often
matches one of our enum values (e.g. gamma = 2.2). If so, we should
populate the corresponding fields in AVCodecContext and AVFrame,
provided that some other chunk isn't already providing that info.
---
libavcodec/pngdec.c | 27
These chunks are lightweight and it's useful information to have when
running ffmpeg -i or ffprobe, for example.
---
libavcodec/pngdec.c | 103 ++-
tests/ref/fate/png-icc | 8 +--
tests/ref/fate/png-side-data | 2 +-
3 files changed, 59 insertions
We parse the fallback cHRM on decode and correctly determine that we
have BT.709 primaries, but unknown TRC. This causes us to write cICP
where we shouldn't. Primaries without transfer can be handled entirely
by cHRM, so we should only write cICP if we actually know the transfer
function.
Addition
The first patch fixes a FATE issue with cICP and iCCP.
The second patch was discussed on IRC. I got a LGTM from Kasper, but sending to
ML here and applying in a few days if there's no objections.
A few things discussed:
1) There's no need to expose the gamma table as another function as it's onl
> On Feb 2, 2023, at 16:16, Anton Khirnov wrote:
>
> Quoting Zhao Zhili (2023-02-02 08:02:03)
>> From: Zhao Zhili
>>
>> There are two group of three_Spline params. Fix the struct
>> definition and usecases inside libavcodec, libavfilter and ffprobe.
>>
>> Co-Author: Houxiang ZHU
>> Signed-o
Quoting Zhao Zhili (2023-02-02 08:02:03)
> From: Zhao Zhili
>
> There are two group of three_Spline params. Fix the struct
> definition and usecases inside libavcodec, libavfilter and ffprobe.
>
> Co-Author: Houxiang ZHU
> Signed-off-by: Zhao Zhili
> ---
> diff --git a/libavutil/hdr_dynamic_vi
The patchset lgtm. thanks.
On Thu, Feb 2, 2023 at 3:11 PM Zhao Zhili wrote:
> From: Zhao Zhili
>
> Only patch 1/6 needs to go with major version bump.
>
> Zhao Zhili (6):
> libavutil/hdr_dynamic_vivid_metadata: fix
> AVHDRVividColorToneMappingParams
> libavcodec/dynamic_hdr_vivid: fix s
32 matches
Mail list logo
