We should use the systems crypto policy by default. If there is no
system policy, gnutls will use the "NORMAL" policy.
Signed-off-by: Andreas Schneider
---
libavformat/tls_gnutls.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/tls_gnutls.c b/libavformat/tls_gnut
> On Tue, 2022-02-08 at 11:05 +0800, Wenbin Chen wrote:
> > Add vaSyncBuffer to VAAPI encoder. Old version API vaSyncSurface wait
> > surface to complete. When surface is used for multiple operation, it
> > waits all operations to finish. vaSyncBuffer only wait one channel to
> > finish.
> >
> > Ad
> Add async_depth to increase encoder's performance. Reuse encode_fifo as
> async buffer. Encoder puts all reordered frame to HW and then check
> fifo size. If fifo < async_depth and the top frame is not ready, it will
> return AVERROR(EAGAIN) to require more frames.
>
> 1080p transcoding (no B
On Tue, 2022-02-08 at 11:05 +0800, Wenbin Chen wrote:
> Fix: #7706. After commit 5fdcf85bbffe7451c2, vaapi encoder's performance
> decrease. The reason is that vaRenderPicture() and vaSyncBuffer() are
> called at the same time (vaRenderPicture() always followed by a
> vaSyncBuffer()). When we encod
On Tue, 2022-02-08 at 11:05 +0800, Wenbin Chen wrote:
> Add vaSyncBuffer to VAAPI encoder. Old version API vaSyncSurface wait
> surface to complete. When surface is used for multiple operation, it
> waits all operations to finish. vaSyncBuffer only wait one channel to
> finish.
>
> Add wait param
On 2/10/2022 11:16 PM, Steven Liu wrote:
2022年2月11日 上午10:10,James Almer 写道:
On 2/10/2022 11:03 PM, Steven Liu wrote:
2022年2月11日 上午10:01,James Almer 写道:
On 2/10/2022 10:43 PM, Steven Liu wrote:
2022年2月10日 下午8:27,James Almer 写道:
On 2/10/2022 9:20 AM, Steven Liu wrote:
because the sr
MSDK recognizes both yuv420p10 and yuv420p9 as MFX_FOURCC_P010, but
parameters are different. When decode yuv420p9 video, ffmpeg-qsv will use
yuv420p10le to configure surface which is different with param from
DecoderHeader and this will lead to error. Now change it use
param from decoderHeader to
> 2022年2月11日 上午10:10,James Almer 写道:
>
>
>
> On 2/10/2022 11:03 PM, Steven Liu wrote:
>>> 2022年2月11日 上午10:01,James Almer 写道:
>>>
>>> On 2/10/2022 10:43 PM, Steven Liu wrote:
> 2022年2月10日 下午8:27,James Almer 写道:
>
> On 2/10/2022 9:20 AM, Steven Liu wrote:
>> because the src,
On 2/10/2022 11:03 PM, Steven Liu wrote:
2022年2月11日 上午10:01,James Almer 写道:
On 2/10/2022 10:43 PM, Steven Liu wrote:
2022年2月10日 下午8:27,James Almer 写道:
On 2/10/2022 9:20 AM, Steven Liu wrote:
because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
set to null when the us
> 2022年2月11日 上午10:01,James Almer 写道:
>
> On 2/10/2022 10:43 PM, Steven Liu wrote:
>>> 2022年2月10日 下午8:27,James Almer 写道:
>>>
>>> On 2/10/2022 9:20 AM, Steven Liu wrote:
because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
set to null when the user calling av_hwfram
On 2/10/2022 10:43 PM, Steven Liu wrote:
2022年2月10日 下午8:27,James Almer 写道:
On 2/10/2022 9:20 AM, Steven Liu wrote:
because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
set to null when the user calling av_hwframe_transfer_data, this will
get crash if they are null.
src
> 2022年2月10日 下午8:27,James Almer 写道:
>
> On 2/10/2022 9:20 AM, Steven Liu wrote:
>> because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
>> set to null when the user calling av_hwframe_transfer_data, this will
>> get crash if they are null.
>
> src can not be NULL. The doxy d
On Sat, Feb 05, 2022 at 08:31:46PM +0800, lance.lmw...@gmail.com wrote:
> From: Limin Wang
>
> Signed-off-by: Limin Wang
> ---
> libavformat/udp.c | 32
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/libavformat/udp.c b/libavformat/udp.c
>
By the way, is there any problem with the patch itself? Not sure why it says
'Failed to apply patch'.
Did my email client break it somehow?
>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To u
Yes, I tried, but this only works if your sequence has the '-' before the
numeric elements. You can see they comment that in the thread, by saying you
have to remove the '-' from the expression.
$ ffmpeg -v debug -start_number -24 -i Comentaris_prova_%05d.png out.mkv
ffmpeg version 2020-10-17-gi
On 2/10/2022 9:20 AM, Steven Liu wrote:
because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
set to null when the user calling av_hwframe_transfer_data, this will
get crash if they are null.
src can not be NULL. The doxy doesn't allow it.
And if transfer_data_alloc() is call
because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
set to null when the user calling av_hwframe_transfer_data, this will
get crash if they are null.
Signed-off-by: Steven Liu
---
libavutil/hwcontext.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/li
> 2022年2月10日 下午8:20,Steven Liu 写道:
>
> because the src, src->hw_frames_ctx and src->hw_frames_ctx->data can be
> set to null when the user calling av_hwframe_transfer_data, this will
> get crash if they are null.
>
Reported-by: TOTE Robot
> Signed-off-by: Steven Liu
> ---
> libavutil/hwconte
Fixes: memleak
Fixes:
42341/clusterfuzz-testcase-minimized-ffmpeg_dem_MOV_fuzzer-4566632823914496
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavformat/mov.c | 2 ++
1 file changed, 2 insertions(+)
On 2022-02-08 04:33 pm, Gyan Doshi wrote:
On 2022-02-07 09:34 am, Gyan Doshi wrote:
On 2022-02-07 03:59 am, Marton Balint wrote:
On Sat, 5 Feb 2022, Gyan Doshi wrote:
bca30570d2 added a user option to set max_packet_size replacing
a hardcoded value. This had a side-effect of leaving
Untested, no testcase
Signed-off-by: Michael Niedermayer
---
libavcodec/libuavs3d.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavcodec/libuavs3d.c b/libavcodec/libuavs3d.c
index 0b5c6268a4..d8d09cacbc 100644
--- a/libavcodec/libuavs3d.c
+++ b/libavcodec/libuavs3d.c
Yes,yes,yes, moreover the graph should be rebuilt if some other parameters
change - interpolation method etc, also when a single input splitted by
zscaling to 2 different resolution streams.
So I've submitted a new patch version that fixes everything. It has a lot
of checks inside but they are abs
Andreas Rheinhardt:
> Signed-off-by: Andreas Rheinhardt
> ---
> I did not add these codecs the last time I searched for codecs
> to add the FF_CODEC_CAP_INIT_CLEANUP because I was unsure whether
> calling ff_thread_release_buffer() on a NULL frame was safe
> (it is).
>
> libavcodec/pngdec.c | 9
On 2022-02-10 03:01 pm, Sergio Acereda wrote:
Signed-off-by: Sergio Acereda
---
This patch should allow to play a image sequence in backwards direction,
without needing to apply a reverse filter.
Have you considered this: https://stackoverflow.com/a/40479257/ ?
Regards,
Gyan
_
By ffmpeg threading support implementation via frame slicing and doing
zimg_filter_graph_build that used to take 30-60% of each frame processig
only if necessary (some parameters changed)
the performance increase vs original version
in video downscale and color conversion >4x is seen
on 64 cores I
Hi!
GSoC 2022 just started the org application phase. As usual, we'll send an
application and need to gather project ideas for GSoC 2022.
There is the 2022 GSoC page in our wiki now [1], please add your project idea
before the application deadline there or send it to the ML for discussion.
App
Signed-off-by: Sergio Acereda
---
This patch should allow to play a image sequence in backwards direction,
without needing to apply a reverse filter.
$ ffmpeg -i sequence%05.png forward.mkv
$ ffmpeg -reverse 1 sequence%05.png backward.mkv
---
libavformat/img2.h| 1 +
libavformat/img2dec.c |
27 matches
Mail list logo