[FFmpeg-devel] [PATCH 2/2] lavfi/atempo: Avoid false triggering an assertion failure

From: Pavel Koshevoy Steps to reproduce: 1. revert 4240e5b047379b29c33dd3f4438bc4e610527b83 2. ./ffmpeg -f lavfi -i sine=d=1 -af aselect=e=0,atempo=0.5 -y atempo.wav --- libavfilter/af_atempo.c | 5 + 1 file changed, 5 insertions(+) diff --git a/libavfilter/af_atempo.c

[FFmpeg-devel] [PATCH 1/2] Revert "lavfi/atempo: avoid false triggering an assertion failure"

From: Pavel Koshevoy This reverts commit 4240e5b047379b29c33dd3f4438bc4e610527b83. --- libavfilter/af_atempo.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index 944df1dd32..9eee8a63a8 100644 ---

[FFmpeg-devel] [PATCH] avfilter/af_atempo: fix drift calculation, ticket #6157

From: Pavel Koshevoy --- libavfilter/af_atempo.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index a487882..eb62656 100644 --- a/libavfilter/af_atempo.c +++ b/libavfilter/af_atempo.c @@ -697,11

[FFmpeg-devel] [PATCH] lavc/vda_h264_dec.c Fix NULL pointer dereference

From: Pavel Koshevoy ps.sps_list entries may be NULL, so check before dereferencing --- libavcodec/vda_h264_dec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/vda_h264_dec.c b/libavcodec/vda_h264_dec.c index 92839e2..972bd6b 100644 ---

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video resolution (v5)

From: Pavel Koshevoy CUVID on GeForce GT 730 and GeForce GTX 1060 does not report any when decoding 8K h264 packets. However, it does return an error during cuvidCreateDecoder call if the indicated video resolution is not supported. Given that stream resolution is

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters (v4)

From: Pavel Koshevoy Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are supported. Unfortunately CUVID silently drops packets for video of unsupported resolution. However, it will error-out at

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

From: Pavel Koshevoy Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are supported. Unfortunately CUVID silently drops packets for video of unsupported resolution. However, it will error-out at

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle video parameters

From: Pavel Koshevoy Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are supported. Given that stream resolution and pixel format are typically known as a result of probing it is better to use this info

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video parameters

From: Pavel Koshevoy Evidently CUVID doesn't support decoding 422 or 444 chroma formats, and only a limited set of resolutions per codec are supported. Given that stream resolution and pixel format are typically known as a result of probing it is better to use this info

[FFmpeg-devel] [PATCH] lavc/cuvid: fail early if GPU can't handle given video resolution

From: Pavel Koshevoy NVDEC (CUVID) does not support unlimited video resolutions, so if the resolution of the source is known it can be used during avcodec_open2 call to fail early, rather than failing later during avcodec_send_packet call. This problem surfaced when trying

[FFmpeg-devel] [PATCH] Add fate test for ticket 6024, truncated decoding mode (v2)

From: Pavel Koshevoy --- tests/fate/video.mak| 3 +++ tests/ref/fate/mpeg2-ticket6024 | 27 +++ 2 files changed, 30 insertions(+) create mode 100644 tests/ref/fate/mpeg2-ticket6024 diff --git a/tests/fate/video.mak

[FFmpeg-devel] [PATCH] lavfi/atempo: Avoid false triggering an assertion failure

From: Pavel Koshevoy Steps to reproduce: ./ffmpeg_g -f s16be -i /dev/null -af atempo=0.5 -y /tmp/atempo.wav --- libavfilter/af_atempo.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavfilter/af_atempo.c b/libavfilter/af_atempo.c index

[FFmpeg-devel] [PATCH] Add fate test for ticket 6024, truncated decoding mode

From: Pavel Koshevoy --- tests/fate/video.mak| 3 +++ tests/ref/fate/mpeg2-ticket6024 | 27 +++ 2 files changed, 30 insertions(+) create mode 100644 tests/ref/fate/mpeg2-ticket6024 diff --git a/tests/fate/video.mak

[FFmpeg-devel] [PATCH] lavc: Fix ticket 6024, truncated mode decoding

From: Pavel Koshevoy The assumption that avcodec_send_packet makes regarding decoders consuming the entire packet is not true if the codec supports truncated decoding mode and the truncated flag is turned on. Steps to reproduce: ./ffmpeg_g -flags truncated \ -i

[FFmpeg-devel] [PATCH] lavc: Fix ticket 6024 (v2)

From: Pavel Koshevoy --- libavcodec/utils.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/utils.c b/libavcodec/utils.c index 44ecc09..be50459 100644 --- a/libavcodec/utils.c +++ b/libavcodec/utils.c @@ -2788,7 +2788,7 @@ static int

[FFmpeg-devel] [PATCH] lavc: Fix ticket 6024

From: Pavel Koshevoy --- libavcodec/utils.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/libavcodec/utils.c b/libavcodec/utils.c index 44ecc09..2ad96e4 100644 --- a/libavcodec/utils.c +++ b/libavcodec/utils.c @@ -2788,8 +2788,6 @@ static int do_decode(AVCodecContext

[FFmpeg-devel] [PATCH] Restore compatibility with powerpc-apple-darwin9-gcc-4.2.1

From: Pavel Koshevoy ... and attempt to preserve compatibility with clang that was introduced in 311a953c76081fca99b872629d248f9d69ebc0c3 (untested) --- libavcodec/ppc/asm.S | 8 +++- libavcodec/ppc/fft_altivec.S | 26 +++--- 2 files