Re: [FFmpeg-user] question about fps filter
Hi, > 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 @ 0220ac5561c0] Setting 'deint' to value > 'interlaced' > [Parsed_fps_1 @ 0220ac74a500] Setting 'fps' to value '24000/1001' > [Parsed_fps_1 @ 0220ac74a500] fps=24000/1001 > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'video_size' to > value '720x480' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pix_fmt' to > value '119' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'time_base' to > value '1/1000' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'pixel_aspect' > to value '186/157' > [graph 0 input from stream 0:0 @ 0220ac749f40] Setting 'frame_rate' to > value '3/1001' > [graph 0 input from stream 0:0 @ 0220ac749f40] w:720 h:480 pixfmt:cuda > tb:1/1000 fr:3/1001 sar:186/157 This doesn't necessarily mean the fps was ignored, it just means the input has that frame rate. As you've said it looks like the argument to the fps filter was parsed correctly, the message being logged before doesn't mean anything (it wasn't later overridden to 3/1001 or anything). Is the output file 3/1001 fps? Regards, Ted Park ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] question about fps filter
Thanks for the info Moritz that is helpful to me. I'll keep looking at things and see if my issue goes away in the next couple weeks. -Andy On Tue, May 26, 2020 at 2:27 AM Moritz Barsnick wrote: > Hi Andy, > > On Mon, May 25, 2020 at 20:43:03 -0400, Andy Sheimo wrote: > > How can I check if this version contains the changes you reference? > > > ffmpeg.exe -version > > > ffmpeg version N-97877-g1e8ed181e3-ffmpeg-windows-build-helpers > Copyright (c) 2000-2020 the FFmpeg developers > > Simply speaking, by checking which git commit that version was built > from. The so-called hash of the git commit is the hexadecimal part > after the 'g' in the version: > 1e8ed181e3 > (or rather, a shortened version of the hash - but it doesn't matter > here). > > > >> 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. > > If you replace the base part of this URL with said hash, as such: > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/1e8ed181e3 > you will see the corresponding commit, and that you are using a build > which includes something committed on Fri, 22 May 2020, while Dennis's > link referenced a change made on Fri, 15 May 2020. So what you are > using includes what Dennis pointed out. > > (In reality, it may be more complicated, because git isn't guaranteed > to be linear, but this method suffices for checking how current a build > is.) > > Cheers, > Moritz > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] question about fps filter
Hi Andy, On Mon, May 25, 2020 at 20:43:03 -0400, Andy Sheimo wrote: > How can I check if this version contains the changes you reference? > > ffmpeg.exe -version > > ffmpeg version N-97877-g1e8ed181e3-ffmpeg-windows-build-helpers Copyright > > (c) 2000-2020 the FFmpeg developers Simply speaking, by checking which git commit that version was built from. The so-called hash of the git commit is the hexadecimal part after the 'g' in the version: 1e8ed181e3 (or rather, a shortened version of the hash - but it doesn't matter here). > >> 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. If you replace the base part of this URL with said hash, as such: https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/1e8ed181e3 you will see the corresponding commit, and that you are using a build which includes something committed on Fri, 22 May 2020, while Dennis's link referenced a change made on Fri, 15 May 2020. So what you are using includes what Dennis pointed out. (In reality, it may be more complicated, because git isn't guaranteed to be linear, but this method suffices for checking how current a build is.) Cheers, Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
