On Di, 2023-01-17 at 12:17 +0100, David Rosca wrote:
> v3: pic_order_cnt steps by 2
> ---
> libavcodec/vaapi_encode_h264.c | 10 --
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c
> index f15bcc6..de0951f 1
On Do, 2023-01-19 at 16:30 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang
>
> Include hstack_vaapi, vstack_vaapi and xstack_vaapi. They may accept
> input streams with different sizes. libva2 (VA-API 1.0+) is required.
>
> Example:
> $ ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i inp
---
doc/ffmpeg.texi | 2 --
1 file changed, 2 deletions(-)
diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
index 67b3294256..6b93386b49 100644
--- a/doc/ffmpeg.texi
+++ b/doc/ffmpeg.texi
@@ -1041,8 +1041,6 @@ version > 1:
@code{out= %2d st= %2d frame= %5d q= %2.1f PSNR= %6.2f f_size= %6d s_size=
Use it for logging. This makes log messages related to this output
stream more consistent.
---
fftools/ffmpeg.c | 95
fftools/ffmpeg.h | 5 +-
fftools/ffmpeg_demux.c| 10 +--
fftools/ffmpeg_mux.c | 13 ++--
fftools/ffmpeg_mux.h | 3 +
Use it for logging. This makes log messages related to this output file
more consistent.
---
fftools/ffmpeg.h | 2 +
fftools/ffmpeg_mux.c | 26 +++-
fftools/ffmpeg_mux.h | 3 +
fftools/ffmpeg_mux_init.c | 133 +++---
4 files changed, 96 i
LGTM
___
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".
Probably ok
___
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".
Probably ok
___
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".
Will push the set tomorrow if nobody has further comments.
--
Anton Khirnov
___
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.or
On 25 Jan 2023, at 17:55, Anton Khirnov wrote:
> Change return value descriptions into proper lists.
> ---
> libavcodec/avcodec.h | 81 +++-
> 1 file changed, 42 insertions(+), 39 deletions(-)
>
> diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
Quoting Marvin Scholz (2023-01-28 12:37:42)
>
>
> On 25 Jan 2023, at 17:55, Anton Khirnov wrote:
>
> > Change return value descriptions into proper lists.
> > ---
> > libavcodec/avcodec.h | 81 +++-
> > 1 file changed, 42 insertions(+), 39 deletions(-)
>
Change return value descriptions into proper lists.
---
libavcodec/avcodec.h | 79 ++--
1 file changed, 39 insertions(+), 40 deletions(-)
diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 0ac581d660..ad6377e8d8 100644
--- a/libavcodec/avcodec.h
libavutil/color_utils contains some avpriv_ symbols that map
enum AVTransferCharacteristic values to gamma-curve approximations and
to the actual transfer functions to invert them (i.e. -> linear).
There's two issues with this:
(1) avpriv is evil and should be avoided whenever possible
(2) libavut
On 27/01/2023 18:31, Paul B Mahol wrote:
On 1/27/23, Francesco Carusi wrote:
On 26/01/2023 17:37, Paul B Mahol wrote:
On 1/26/23, Francesco Carusi wrote:
On 26/01/2023 14:21, Paul B Mahol wrote:
On 1/26/23, Francesco Carusi wrote:
The drawtext reinit command is also used in the docs as an
On 28 Jan 2023, at 14:23, Anton Khirnov wrote:
> Quoting Marvin Scholz (2023-01-28 12:37:42)
>>
>>
>> On 25 Jan 2023, at 17:55, Anton Khirnov wrote:
>>
>>> Change return value descriptions into proper lists.
>>> ---
>>> libavcodec/avcodec.h | 81 +++-
>>>
On 1/28/23, Francesco Carusi wrote:
> On 27/01/2023 18:31, Paul B Mahol wrote:
>> On 1/27/23, Francesco Carusi wrote:
>>> On 26/01/2023 17:37, Paul B Mahol wrote:
On 1/26/23, Francesco Carusi wrote:
> On 26/01/2023 14:21, Paul B Mahol wrote:
>> On 1/26/23, Francesco Carusi wrote:
>
Don't use "static const" for compile time float constants, but use
defines. This fixes the following error:
src/libavfilter/vf_ssim360.c(549): error C2099: initializer is not a constant
Signed-off-by: Martin Storsjö
---
libavfilter/vf_ssim360.c | 6 +++---
1 file changed, 3 insertions(+), 3 del
On Sat, 28 Jan 2023, Martin Storsjö wrote:
Don't use "static const" for compile time float constants, but use
defines. This fixes the following error:
src/libavfilter/vf_ssim360.c(549): error C2099: initializer is not a constant
Signed-off-by: Martin Storsjö
---
libavfilter/vf_ssim360.c | 6 +
Signed-off-by: Andreas Rheinhardt
---
libavfilter/vf_ssim360.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_ssim360.c b/libavfilter/vf_ssim360.c
index a0bf73da1e..89f5100740 100644
--- a/libavfilter/vf_ssim360.c
+++ b/libavfilter/vf_ssim360.c
@@ -547,7 +547,7
The FILTER_INPUTS and FILTER_OUTPUTS macros already set
AVFilter.(inputs|outputs); Clang therefore emits a warning for
this: "initializer overrides prior initialization of this subobject
[-Winitializer-overrides]"
Signed-off-by: Andreas Rheinhardt
---
libavfilter/vf_ssim360.c | 2 --
1 file chan
This brings ff_vf_ssim360 in line with its declaration in allfilters.c;
this discrepancy is actually undefined behaviour.
Signed-off-by: Andreas Rheinhardt
---
libavfilter/vf_ssim360.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_ssim360.c b/libavfilter/vf_s
set LGTM
thanks,
--
Anton Khirnov
___
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".
On Fri, 27 Jan 2023, Marton Balint wrote:
On Fri, 27 Jan 2023, James Almer wrote:
On 1/27/2023 3:04 PM, Anton Khirnov wrote:
Quoting Marton Balint (2023-01-27 18:59:39)
On Fri, 27 Jan 2023, Anton Khirnov wrote:
I still think we should do a deprecation+replacement like we do f
Frame counters can overflow relatively easily (INT_MAX number of frames is
slightly more than 1 year for 60 fps content), so make sure we use 64 bit
values for them.
Also deprecate the old 32 bit frame_number attribute.
Signed-off-by: Marton Balint
---
doc/APIchanges | 4 +
Signed-off-by: Marton Balint
---
libavcodec/diracdec.c | 33 ++---
1 file changed, 18 insertions(+), 15 deletions(-)
diff --git a/libavcodec/diracdec.c b/libavcodec/diracdec.c
index a5cad29597..22a2925188 100644
--- a/libavcodec/diracdec.c
+++ b/libavcodec/diracdec.c
Move these fields to MPEGPicture instead and use that.
Signed-off-by: Marton Balint
---
libavcodec/mpeg12enc.c | 4 ++--
libavcodec/mpegpicture.c | 4
libavcodec/mpegpicture.h | 3 +++
libavcodec/mpegvideo_enc.c | 17 ++---
libavcodec/ratecontrol.c | 4 ++--
libavc
Their usefulness are questionable, very few decoders set them, and their type
should have been int64_t. A replacement field can be added later if a valid use
case is found.
Signed-off-by: Marton Balint
---
doc/APIchanges | 4
doc/examples/demuxing_decoding.c | 4 ++--
ff
On Fri, Jan 27, 2023 at 10:59:38AM +1100, Peter Ross wrote:
> On Sun, Jan 22, 2023 at 01:02:21AM +0100, Michael Niedermayer wrote:
> > bink supports 16x16 blocks in chroma planes thus we need to allocate enough.
> > Fixes: out of array access
> > Fixes:
> > 55026/clusterfuzz-testcase-minimized-ffm
28 matches
Mail list logo
