[FFmpeg-user] question about fps filter

[Andy Sheimo]

using this version created today using
https://github.com/rdp/ffmpeg-windows-build-helpers

ffmpeg.exe -version
ffmpeg version N-97877-g1e8ed181e3-ffmpeg-windows-build-helpers Copyright
(c) 2000-2020 the FFmpeg developers
built with gcc 8.3.0 (GCC)
configuration: --pkg-config=pkg-config --pkg-config-flags=--static
--extra-version=ffmpeg-windows-build-helpers --enable-version3
--disable-debug --disable-w32threads --arch=x86_64 --target-os=mingw32
--cross-prefix=/home/asheimo/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/bin/x86_64-w64-mingw32-
--enable-libcaca --enable-gray --enable-libtesseract --enable-fontconfig
--enable-gmp --enable-gnutls --enable-libass --enable-libbluray
--enable-libbs2b --enable-libflite --enable-libfreetype --enable-libfribidi
--enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug
--enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libopus --enable-libsnappy --enable-libsoxr --enable-libspeex
--enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc
--enable-libvorbis --enable-libwebp --enable-libzimg --enable-libzvbi
--enable-libmysofa --enable-libopenjpeg --enable-libopenh264
--enable-liblensfun --enable-libvmaf --enable-libsrt --enable-demuxer=dash
--enable-libxml2 --enable-opengl --enable-libdav1d --enable-cuda-llvm
--enable-libsvthevc --enable-libaom --enable-libvpx --enable-nvenc
--enable-nvdec --extra-libs=-lharfbuzz --extra-libs=-lm
--extra-libs=-lpthread --extra-cflags=-DLIBTWOLAME_STATIC
--extra-cflags=-DMODPLUG_STATIC --extra-cflags=-DCACA_STATIC --enable-amf
--enable-libmfx --enable-gpl --enable-frei0r --enable-filter=frei0r
--enable-librubberband --enable-libvidstab --enable-libx264
--enable-libx265 --enable-libxvid --enable-libxavs --enable-avresample
--extra-cflags='-mtune=generic' --extra-cflags=-O3 --enable-static
--disable-shared
--prefix=/home/asheimo/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/x86_64-w64-mingw32
libavutil      56. 46.100 / 56. 46.100
libavcodec     58. 87.100 / 58. 87.100
libavformat    58. 43.100 / 58. 43.100
libavdevice    58.  9.103 / 58.  9.103
libavfilter     7. 82.100 /  7. 82.100
libavresample   4.  0.  0 /  4.  0.  0
libswscale      5.  6.101 /  5.  6.101
libswresample   3.  6.100 /  3.  6.100
libpostproc    55.  6.100 / 55.  6.100

On Fri, May 22, 2020 at 6:24 PM Dennis Mungai <dmngaie at gmail.com> wrote:

> On Sat, 23 May 2020 at 01:07, Andy Sheimo <asheimo at gmail.com> wrote:
>
> > I am using the command line seen here but the fps filter is being
> ignored.
> >
> > ffmpeg.exe -loglevel debug -stats -hwaccel cuda -hwaccel_output_format
> cuda
> > -i "Evanescence - Anywhere but Home.mkv" -map 0:0 -filter:v
> > yadif_cuda=deint=interlaced,fps=24000/1001 -c:v h264_nvenc -b:v 2000k
> > -maxrate:v 6000k -rc:v vbr_hq -spatial-aq:v 1 -temporal-aq:v 1 -profile:v
> > high -color_primaries:v smpte170m -color_trc:v bt709 -colorspace:v
> > smpte170m -metadata:s:v title= -disposition:v default -map 0:1 -c:a:0
> eac3
> > -b:a:0 256k -metadata:s:a:0 title= -disposition:a:0 default -map 0:2
> -c:a:1
> > copy -metadata:s:a:1 title= -disposition:a:1 0 -sn -metadata:g title=
> > "Evanescence - Anywhere but Home 2.mkv"
> >
> > I found this in the debug output and am not sure why it sees what was
> > passed by the command line but then is ignored in the filter graph can
> > someone help me understand please? The complete debug output is available
> > but too big to include here.
> >
> > [Parsed_yadif_cuda_0 @ 00000220ac5561c0] Setting 'deint' to value
> > 'interlaced'
> > [Parsed_fps_1 @ 00000220ac74a500] Setting 'fps' to value '24000/1001'
> > [Parsed_fps_1 @ 00000220ac74a500] fps=24000/1001
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] Setting 'video_size'
> to
> > value '720x480'
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] Setting 'pix_fmt' to
> > value '119'
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] Setting 'time_base' to
> > value '1/1000'
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] Setting 'pixel_aspect'
> > to value '186/157'
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] Setting 'frame_rate'
> to
> > value '30000/1001'
> > [graph 0 input from stream 0:0 @ 00000220ac749f40] w:720 h:480
> pixfmt:cuda
> > tb:1/1000 fr:30000/1001 sar:186/157
> > [format @ 00000220ac74bac0] Setting 'pix_fmts' to value
> > 'yuv420p|nv12|p010le|yuv444p|p016le|yuv444p16le|bgr0|rgb0|cuda|d3d11'
> > [AVFilterGraph @ 00000220ac511d80] query_formats: 5 queried, 4 merged, 0
> > already done, 0 delayed
> > [h264_nvenc @ 00000220ac561540] Using input frames context (format cuda)
> > with h264_nvenc encoder.
> > _______________________________________________
> >
>
> What version of ffmpeg are you using?
> There have been recent updates to the NVENC encoder's implementation in
> ffmpeg that better handle frame rate, such as this commit:
>
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/b18fd2b95b2fea10f0b5381333a1b4c032f010bc
> Use the latest build and retest.
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".