On Wed, Jun 7, 2023 at 8:02 PM Neal Gompa wrote:
>
> On Tue, Jun 6, 2023 at 2:43 AM Steven Liu wrote:
> >
> > Neal Gompa 于2023年5月31日周三 13:47写道：
> > >
> > > On Mon, May 15, 2023 at 10:41 PM Neal Gompa wrote:
> > > >
> > > > On Mon, May 15, 2023 at 4:32 AM Steven Liu wrote:
> > > > >
> > > > >
Attached.From eca7929274b9bfd7c5aa8a76177dafaa57ab91a5 Mon Sep 17 00:00:00 2001
From: Hendi
Date: Fri, 9 Jun 2023 01:46:30 +0200
Subject: [PATCH] avformat/mov: Add support for uuid-based senc box
In PIFF-branded mp4 files, the senc data comes in a uuid box.
Signed-off-by: Hendi
---
On Thu, Jun 08, 2023 at 11:44:38PM -0300, James Almer wrote:
> On 6/8/2023 11:32 PM, Anton Khirnov wrote:
> > Quoting Leo Izen (2023-06-08 16:26:36)
> > > Inlines some ret < 0 checks to look like:
> > > if ((ret = func()) < 0)
> > > return ret;
> > >
> > > which clarifies code
Hi David,
I think the reworking of the "-r" option is a breaking change.
I understand that output won't conform to the spec, but at least CC won't be
broken. For example libx264->a53cc option is 1 by default, so any h264 output
with CC with frame rate up-conversion will be broken.
The
Hi Artem,
On Fri, Jun 9, 2023 at 9:19 AM Artem Smorodin
wrote:
>
> When up-converting frame rate, ffmpeg duplicates frames including side data.
> This causes duplicated characters in the output. This patch removes A53 side
> data from duplicated frames.
>
> Signed-off-by: Artem Smorodin
> ---
On 09.06.2023 04:47, "zhilizhao(赵志立)" wrote:
It’s a quick fix, but I’m afraid the two tickets are caused by more deep
pitfalls.
It would be helpful if someone can provide a sample for test.
I've uploaded a sample called bear-640x360-v_frag-cenc-senc.mp4. You can
play it with
When up-converting frame rate, ffmpeg duplicates frames including side data.
This causes duplicated characters in the output. This patch removes A53 side
data from duplicated frames.
Signed-off-by: Artem Smorodin
---
fftools/ffmpeg_enc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
From: Zhao Zhili
This can happen when user set the avctx->profile field directly
instead of specify profile via option.
---
libavcodec/videotoolboxenc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index
From: Zhao Zhili
Use FF_PROFILE_UNKNOWN as auto mode.
---
libavcodec/videotoolboxenc.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c
index 26485a3dea..9f65519700 100644
---
From: Zhao Zhili
Other than save a few bytes, it also has the benefit to show the
AV_OPT_TYPE_CONST value in help, e.g.,
-profile E..V... Profile (from 0 to INT_MAX)
(default 0)
baseline66 E..V... Baseline Profile
...
---
From: Zhao Zhili
H.264 high10/high422/high44 are unlikely supported by devices.
It's there for developers to do the experiment.
H.265 main10 works on my device with AV_PIX_FMT_MEDIACODEC.
OMX_COLOR_FormatYUV420Planar16 doesn't work.
Signed-off-by: Zhao Zhili
---
libavcodec/mediacodecenc.c |
On Fri, Jun 9, 2023 at 7:57 AM Jean-Baptiste Kempf wrote:
> On Thu, 8 Jun 2023, at 19:39, Paul B Mahol wrote:
> > Attached.
>
> Missing version bumping?
>
That is done when committing.
To prevent potential need for rebase if in meantime someone changes version.
> --
> Jean-Baptiste Kempf -
Optimize the put and avg filtering for 4xH and 2xH blocks
Signed-off-by: Arnie Chang
---
checkasm: using random seed 3475799765
RVVi32:
- h264chroma.chroma_mc [OK]
checkasm: all 6 tests passed
avg_h264_chroma_mc1_8_c: 1821.5
avg_h264_chroma_mc1_8_rvv_i32: 466.5
avg_h264_chroma_mc2_8_c: 939.2
13 matches
Mail list logo
