On Tue, Mar 1, 2022 at 8:12 AM Xiang, Haihao <
haihao.xiang-at-intel@ffmpeg.org> wrote:
> On Mon, 2022-02-21 at 13:27 +0100, Paul B Mahol wrote:
> > Signed-off-by: Paul B Mahol
> > ---
> > libavfilter/audio.c | 11 +--
> > libavfilter/framepool.c | 18 --
> > liba
On Tue, Mar 1, 2022 at 8:46 AM Michael Koch
wrote:
> > We have 0 project ideas on our gsoc 2022 page
> > well we have 2 now as i copied my two from last year
> > If you have an idea, please add it!
>
> Might it be possible to integrate LibRaw into FFmpeg?
> https://www.libraw.org/
>
> This could
This updates the locations searched for the OpenH264 headers to be
consistent with upstream
Discussed here:
https://github.com/cisco/openh264/pull/3415
Due to the change in the pkgconfig file, it is possible to compile with
either:
#include
OR
#include
but in this patch, I used the for
On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock wrote:
>
>
> This updates the locations searched for the OpenH264 headers to be
> consistent with upstream
>
> Discussed here:
> https://github.com/cisco/openh264/pull/3415
>
> Due to the change in the pkgconfig file, it is possible to compile with
> ei
In some case, the input files have different time base even though
they share the same codec and codec parameters,
while processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed chang
On 01/03/2022 10:19, Hendrik Leppkes wrote:
> On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock wrote:
>>
>>
>> This updates the locations searched for the OpenH264 headers to be
>> consistent with upstream
>>
>> Discussed here:
>> https://github.com/cisco/openh264/pull/3415
>>
>> Due to the change
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
On 24 Feb 2022, at 14:46, Nicolas George wrote:
> Thilo Borgman (12022-02-24):
>> Both LGTM.
>
> Does it?
An earlier reply would have been helpful here, i.e. before an ACK rather than
after.
> The way I remember it, this condition was for the initial assembly, as a
> temporary measure. I mig
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
Hi Gyan
Thanks for suggestion
Base on the different time_base, the connection between the streams, the pts
and dts may be not continuate, the the codec
May reporte warning. Is that ‘bug’ acceptable?
Regards,
Chuan Ye
From: ffmpeg-devel on behalf of Gyan Doshi
Date: Tuesday, March 1, 2022
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
Ye Chuan (12022-03-01):
> In some case, the input files have different time base even though
> they share the same codec and codec parameters,
> While processing the packet, it will adjust the pts/dts by its own
> time base instead of the unified one of the output stream, which may
> lead to wrong
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
> 2022年2月28日 下午10:17，Michael Niedermayer 写道：
>
> On Mon, Feb 28, 2022 at 04:19:55PM +0800, 殷时友 wrote:
>>
>>
>>> 2022年2月21日 下午11:00，Michael Niedermayer 写道：
>>>
>>> On Thu, Feb 17, 2022 at 07:11:47PM +0800, Hao Chen wrote:
The loongson_intrinsics.h file is updated from v1.0.3 version
>>>
There is some bug on my mail application , when it open the .eml file , the
space may be erase by the application, so the patch will not pass the test
online
From: ffmpeg-devel on behalf of Nicolas
George
Date: Tuesday, March 1, 2022 at 8:18 PM
To: FFmpeg development discussions and patches
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
In some case, the input files have different time base even though
they share the same codec and codec parameters,
While processing the packet, it will adjust the pts/dts by its own
time base instead of the unified one of the output stream, which may
lead to wrong pts/dts or unexpected speed change
Signed-off-by: Paul B Mahol
---
Fix possible hangs if (a)split filter is used in graph and one of outputs ends
earlier than others.
Then filter may never receive EOF from input provided by (a)split filter.
See ticket #9152 for commands how to reproduce issue.
---
libavfilter/split.c | 68 +
On Tue, 1 Mar 2022, Daniel Pocock wrote:
On 01/03/2022 10:19, Hendrik Leppkes wrote:
On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock wrote:
This updates the locations searched for the OpenH264 headers to be
consistent with upstream
Discussed here:
https://github.com/cisco/openh264/pull/3415
Hi,
There was some discussion recently about the possibility of reducing the
amount of ad-hoc file loading in filters by introducing common syntax
for loading AV_OPT_TYPE_BINARY options from files. (vf_libvmaf,
vf_frei0r, vf_libplacebo, vf_vidstabtransform, ...)
Another source of redundancy curre
On Tue, Mar 1, 2022 at 2:28 PM Niklas Haas wrote:
> Hi,
>
> There was some discussion recently about the possibility of reducing the
> amount of ad-hoc file loading in filters by introducing common syntax
> for loading AV_OPT_TYPE_BINARY options from files. (vf_libvmaf,
> vf_frei0r, vf_libplacebo
> On Feb 27, 2022, at 2:49 PM, Gyan Doshi wrote:
>
>
>
> On 2022-02-27 12:04 pm, "zhilizhao(赵志立)" wrote:
>> Ping.
>>
>>> On Dec 31, 2021, at 7:36 PM, Zhao Zhili wrote:
>>>
>>> When editlist is disabled, the workaournd method of shift dts to
>>> zero and increase the first sample duration d
On 3/1/2022 4:12 AM, Xiang, Haihao wrote:
Hi,
fate-vsynth1-mpeg2-422 is broken after this patch (commit 17a59a6).
--- ./tests/ref/vsynth/vsynth1-mpeg2-4222021-11-22 12:59:25.013517219
+0800
+++ tests/data/fate/vsynth1-mpeg2-422 2022-03-01 13:30:48.446378312 +0800
@@ -1,4 +1,4 @@
-6e1
Signed-off-by: James Almer
---
libavfilter/framepool.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/libavfilter/framepool.c b/libavfilter/framepool.c
index 5b510c9af9..cf6a1d0ea0 100644
--- a/libavfilter/framepool.c
+++ b/libavfilter/framepool.c
@@ -57
On Tue, Mar 1, 2022 at 3:23 PM James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavfilter/framepool.c | 20 ++--
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/libavfilter/framepool.c b/libavfilter/framepool.c
> index 5b510c9af9..cf6a1d0ea0 100644
>
On 3/1/2022 11:31 AM, Paul B Mahol wrote:
On Tue, Mar 1, 2022 at 3:23 PM James Almer wrote:
Signed-off-by: James Almer
---
libavfilter/framepool.c | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/libavfilter/framepool.c b/libavfilter/framepool.c
ind
On Tue, Mar 1, 2022 at 3:36 PM James Almer wrote:
> On 3/1/2022 11:31 AM, Paul B Mahol wrote:
> > On Tue, Mar 1, 2022 at 3:23 PM James Almer wrote:
> >
> >> Signed-off-by: James Almer
> >> ---
> >> libavfilter/framepool.c | 20 ++--
> >> 1 file changed, 14 insertions(+), 6 de
On 3/1/2022 11:53 AM, Paul B Mahol wrote:
On Tue, Mar 1, 2022 at 3:36 PM James Almer wrote:
On 3/1/2022 11:31 AM, Paul B Mahol wrote:
On Tue, Mar 1, 2022 at 3:23 PM James Almer wrote:
Signed-off-by: James Almer
---
libavfilter/framepool.c | 20 ++--
1 file changed,
On 01/03/2022 14:27, Martin Storsjö wrote:
> On Tue, 1 Mar 2022, Daniel Pocock wrote:
>
>>
>>
>> On 01/03/2022 10:19, Hendrik Leppkes wrote:
>>> On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock wrote:
This updates the locations searched for the OpenH264 headers to be
consistent
On Tue, Mar 01, 2022 at 08:46:42AM +0100, Michael Koch wrote:
> > We have 0 project ideas on our gsoc 2022 page
> > well we have 2 now as i copied my two from last year
> > If you have an idea, please add it!
>
> Might it be possible to integrate LibRaw into FFmpeg?
> https://www.libraw.org/
>
>
On Tue, 1 Mar 2022, Daniel Pocock wrote:
On 01/03/2022 14:27, Martin Storsjö wrote:
On Tue, 1 Mar 2022, Daniel Pocock wrote:
On 01/03/2022 10:19, Hendrik Leppkes wrote:
On Tue, Mar 1, 2022 at 9:16 AM Daniel Pocock wrote:
This updates the locations searched for the OpenH264 headers to b
On Thu, Feb 24, 2022 at 9:34 AM Vignesh Venkatasubramanian
wrote:
>
> On Tue, Feb 22, 2022 at 1:43 PM Vignesh Venkatasubramanian
> wrote:
> >
> > Add an AVIF muxer by re-using the existing the mov/mp4 muxer.
> >
> > AVIF Specifiation: https://aomediacodec.github.io/av1-avif
> >
> > Sample usage f
On 1 Mar 2022, at 9:09, Paul B Mahol wrote:
> On Tue, Mar 1, 2022 at 8:46 AM Michael Koch
> wrote:
>
>>> We have 0 project ideas on our gsoc 2022 page
>>> well we have 2 now as i copied my two from last year
>>> If you have an idea, please add it!
>>
>> Might it be possible to integrate LibRaw
Plan to push tomorrow.
On 2022-02-28 12:58 pm, Gyan Doshi wrote:
Allows user to specify a frame interval at which textfile is reloaded.
---
doc/filters.texi | 6 --
libavfilter/vf_drawtext.c | 6 +++---
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/doc/filters.t
Friendly ping for feedback on the patch below.
Thank you.
-Original Message-
From: ffmpeg-devel On Behalf Of Eric Juteau
Sent: Thursday, January 27, 2022 9:06 AM
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] libavformat/utils: Check codec whitelist
Modified the function av
On Tue, Mar 01, 2022 at 09:16:17AM +0100, Daniel Pocock wrote:
>
> This updates the locations searched for the OpenH264 headers to be
> consistent with upstream
>
> Discussed here:
> https://github.com/cisco/openh264/pull/3415
>
> Due to the change in the pkgconfig file, it is possible to compil
On Mon, Feb 28, 2022 at 02:09:15PM +0100, Tomas Härdin wrote:
> sön 2022-02-27 klockan 15:29 +0100 skrev Mark Gaiser:
> > Ping 2
> >
> > I'd really like to get this merged!
> > This kinda blocks me right now from proceeding with IPFS integration
> > in
> > Kodi, MPV and VLC. Implementations in
On Thu, Feb 17, 2022 at 08:08:08PM +0800, 殷时友 wrote:
>
>
> > 2022年2月17日 下午7:11，Hao Chen 写道：
> >
> > ffmpeg -i 5_h265_1080p_60fps_3Mbps.mkv -f rawvideo -y /dev/null -an
> > before: 94fps
> > after : 191fps
> >
> > V2: Retrigger the patchwork.ffmpeg test.
> >
> > [PATCH v2 1/5] avutil: [loongar
Hi Jonathan,
The patch looks good to me.
Clément, could you please have a look at the patch as well?
Thanks,
Sebastian
On Mon, Feb 28, 2022 at 4:15 PM Swinney, Jonathan
wrote:
> This patch adds specializations for hscale for filterSize == 4 and 8 and
> converts the existing implementation for
Ping.
> -Original Message-
> From: Wu, Jianhua
> Sent: Wednesday, February 23, 2022 4:58 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Wu, Jianhua
> Subject: [PATCH 1/6] avutil/cpu: add AVX512 Icelake flag
>
> From: Wu Jianhua
>
> Signed-off-by: Wu Jianhua
> ---
> configure
> On 23.02.2022 15:58 Andreas Unterweger wrote:
>
>
> The last encoded frame is now fetched on EOF. It was previously left in the
> encoder and caused a "1 frame left in queue" warning.
>
> Signed-off-by: Andreas Unterweger
> ---
> doc/examples/transcode_aac.c | 22 +++---
> 1
On Tue, 2022-03-01 at 10:43 -0300, James Almer wrote:
> On 3/1/2022 4:12 AM, Xiang, Haihao wrote:
> > Hi,
> >
> > fate-vsynth1-mpeg2-422 is broken after this patch (commit 17a59a6).
> >
> > --- ./tests/ref/vsynth/vsynth1-mpeg2-4222021-11-22
> > 12:59:25.013517219 +0800
> > +++ tests/data/
On 2022-03-01 11:21 pm, Gyan Doshi wrote:
Plan to push tomorrow.
Pushed as 4b72bca6ca3f982614ac2f94160c55abe3778555
Regards,
Gyan
On 2022-02-28 12:58 pm, Gyan Doshi wrote:
Allows user to specify a frame interval at which textfile is reloaded.
---
doc/filters.texi | 6 --
On Tue, 2022-03-01 at 12:03 -0300, James Almer wrote:
>
> On 3/1/2022 11:53 AM, Paul B Mahol wrote:
> > On Tue, Mar 1, 2022 at 3:36 PM James Almer wrote:
> >
> > > On 3/1/2022 11:31 AM, Paul B Mahol wrote:
> > > > On Tue, Mar 1, 2022 at 3:23 PM James Almer wrote:
> > > >
> > > > > Signed-off-b
46 matches
Mail list logo
