High!
I'm using latest ffmpeg from this mirror (https://github.com/FFmpeg)
I was building it with different options:
./configure
./configure --libdir=$dev/FFmpeg/libavcodec/
./configure --enable-shared
./configure --enable-shared --enable-pic
And after each time the whole project got recompi
From: Yan Cen
There is no need all reference frame demension is valid in libvpx.
So this change contains three part:
1. Change each judgement's loglevel from "ERROR" to "WARNING"
2. Make sure at least one of frames that this frame references has valid
dimension.
3.
All judgements fail would report "ERROR".
Signed-off-by: Xiang Haihao
Signed-off-by: Li Zhong
Signed-off-by: Yan Cen
---
libavcodec/vp9.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/libavcodec/vp9.c b/libavcodec/vp9.c
index acf3ffc..849c1a6
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost.
Signed-off-by: Yan Wang
---
libavcodec/decode.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavcodec/decode.c b/libavcodec/decode.c
index 6c31166ec2..3eda1dc42c
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost.
Signed-off-by: Yan Wang
---
libavcodec/decode.c | 6 ++
1 file changed, 6
On 5/28/2019 4:43 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 9:46 AM Yan Wang wrote:
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface
On 5/30/2019 7:39 AM, Mark Thompson wrote:
On 28/05/2019 08:46, Yan Wang wrote:
On 5/28/2019 3:16 PM, Hendrik Leppkes wrote:
On Tue, May 28, 2019 at 8:57 AM Yan Wang wrote:
When the format change, the VAAPI context cannot be destroyed.
Otherwise, the reference frame surface will lost
which is AVFrame in fact and pass them into
libva when re-creating new va_context.
Thanks.
Yan Wang
As libva allows re-create surface separately without changing the
context, this issue could be handled by only recreating hw_frames_ctx.
Could be verified by:
ffmpeg -hwaccel vaapi -hwa
On 7/8/2019 2:45 PM, Yan Wang wrote:
On 7/7/2019 9:49 PM, Fu, Linjie wrote:
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
Of Mark Thompson
Sent: Sunday, July 7, 2019 19:51
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2
All judgements fail would report "ERROR".
Signed-off-by: Xiang Haihao
Signed-off-by: Li Zhong
Signed-off-by: Yan Cen
---
libavcodec/vp9.c | 51 +++
1 file changed, 43 insertions(+), 8 deletions(-)
diff --git a/libavcodec/vp9.c b/libavcodec/
All FFMPEG gurus!
Can somebody please suggest a format of FFMPEG command to mix several audio
live
streams on Windows. Let my just make it very clear - live audio streams and
not existing
audio files. Just to put it in the context - lets say audio stream from the
microphone and
Stereo Mix.
With s
Signed-off-by: Tom Yan
---
doc/bitstream_filters.texi | 5 +
libavcodec/mpeg2_metadata_bsf.c | 30 ++
2 files changed, 35 insertions(+)
diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi
index 8a2f55cc41..7831abc120 100644
--- a/doc
Signed-off-by: Tom Yan
---
doc/bitstream_filters.texi | 6 ++
libavcodec/mpeg2_metadata_bsf.c | 27 +++
2 files changed, 33 insertions(+)
diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi
index 8a2f55cc41..7e178a6912 100644
--- a/doc
s" to be suppressed and the format tag field to be set
to WAVE_FORMAT_PCM (0x0001) for audio with sample size higher than
16 (or sample rate higher than 48000).
Signed-off-by: Tom Yan
---
libavformat/riff.h| 5 +
libavformat/riffenc.c | 4 ++--
libavformat/wavenc.c | 5 -
3 fil
s" to be suppressed and the format tag field to be set
to WAVE_FORMAT_PCM (0x0001) for audio with sample size higher than
16 (or sample rate higher than 48000).
Signed-off-by: Tom Yan
---
libavformat/riff.h| 5 +
libavformat/riffenc.c | 4 ++--
libavformat/wavenc.c | 5 -
3 fil
the top_field_first bit is only used to indicate the field order
when the picture is a frame picture (which consists of two fields)
but not when it is a field picture (which consists of one single
top or bottom field).
Signed-off-by: Tom Yan
---
libavcodec/mpegvideo_parser.c | 7 +--
1 file
RESSIVE when (processive_sequence == 0
and progressive_frame == 1), there's not really a point to check
processive_sequence at all.
On Sat, 5 Feb 2022 at 20:51, Tom Yan wrote:
>
> the top_field_first bit is only used to indicate the field order
> when the picture is a frame picture (which consist
to be 0 if progressive_frame is 0 on any picture in the
sequence).
Signed-off-by: Tom Yan
---
libavcodec/mpegvideo_parser.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/libavcodec/mpegvideo_parser.c b/libavcodec/mpegvideo_parser.c
index c5dc867d24
r.
If you insist on making it more clumsy and silly, I can resend.
On Sun, 6 Feb 2022 at 13:46, Andreas Rheinhardt
wrote:
>
> Tom Yan:
> > the top_field_first bit is only used to indicate the field order
> > when the picture is a frame picture (which consists of two fields)
&g
the top_field_first bit is only used to indicate the field order
when the picture is a frame picture (which consists of two fields)
but not when it is a field picture (which consists of one single
top or bottom field).
Signed-off-by: Tom Yan
---
libavcodec/mpegvideo_parser.c | 15
WAVEFORMAT can be used for 16-bit PCM as well.
Signed-off-by: Tom Yan
---
libavformat/riffdec.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/libavformat/riffdec.c b/libavformat/riffdec.c
index 3946ecb72f..8289438f08 100644
--- a/libavformat/riffdec.c
+++ b
21 matches
Mail list logo
