#9013(ffplay:new): ffplay: Stop-and-go display / mpeg4
#9013: ffplay: Stop-and-go display / mpeg4 -----------------------------------+---------------------------------- Reporter: malaterre | Type: defect Status: new | Priority: normal Component: ffplay | Version: 4.1.4 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Summary of the bug: How to reproduce: The truncated movie should display nice and smooth using mpv: {{{ % mpv bb2_an2500_copy.mkv }}} Watch closely as snow falls, or as the scene moves up the cascade. Now try with ffplay {{{ % ffplay bb2_an2500_copy.mkv }}} The movie display with tiny stop-and-go. In particular the snow does not fall as smoothly as with mpv, same goes for cascade which display with tiny freeze. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: ffplay: Stop-and-go display / mpeg4 -----------------------------------+---------------------------------- Reporter: malaterre | Owner: Type: defect | Status: new Priority: normal | Component: ffplay Version: 4.1.4 | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+---------------------------------- Changes (by malaterre): * Attachment "bb2_an2500_copy.mkv" added. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: ffplay: Stop-and-go display / mpeg4 ------------------------------------+---------------------------------- Reporter: malaterre | Owner: Type: defect | Status: new Priority: normal | Component: ffplay Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Changes (by malaterre): * version: 4.1.4 => git-master Comment: Using instructions from: * https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu I am able to reproduce the bug using: {{{ ./ffplay -version ffplay version N-100064-g3c92268 Copyright (c) 2003-2020 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) configuration: --prefix=/home/mathieu/ffmpeg_build --pkg-config- flags=--static --extra-cflags=-I/home/mathieu/ffmpeg_build/include --extra-ldflags=-L/home/mathieu/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/home/mathieu/bin --enable-gpl --enable-gnutls --disable- libaom --enable-libass --enable-libfdk-aac --enable-libfreetype --enable- libmp3lame --enable-libopus --disable-libsvtav1 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree libavutil 56. 61.100 / 56. 61.100 libavcodec 58.113.100 / 58.113.100 libavformat 58. 64.100 / 58. 64.100 libavdevice 58. 11.103 / 58. 11.103 libavfilter 7. 91.100 / 7. 91.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc 55. 8.100 / 55. 8.100 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: ffplay: Stop-and-go display / mpeg4 ------------------------------------+---------------------------------- Reporter: malaterre | Owner: Type: defect | Status: new Priority: normal | Component: ffplay Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Comment (by Balling): That happens because by default mpv does not have interpolation at all. And of course, if you display is G-sync, without interpolation it will switch to native frame rate of 25.000 progressive. See this discussion https://github.com/mpv-player/mpv/issues/6137 -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: ffplay: Stop-and-go display / mpeg4 -------------------------------------+------------------------------------- Reporter: malaterre | Owner: Type: defect | Status: new Priority: normal | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cus): * cc: cus (added) * component: ffplay => undetermined Comment: Timestamps of the decoded frames are wrong and not reordered properly for some reason, so this is not an ffplay bug... E.g. {{{ ffprobe bb2_an2500_copy.mkv -of xml -show_frames -show_entries frame=best_effort_timestamp_time | grep best }}} {{{ <frame best_effort_timestamp_time="0.000000"> <frame best_effort_timestamp_time="0.080000"> <frame best_effort_timestamp_time="0.040000"> <frame best_effort_timestamp_time="0.160000"> <frame best_effort_timestamp_time="0.120000"> }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: ffplay: Stop-and-go display / mpeg4 ------------------------------------+----------------------------------- Reporter: malaterre | Owner: Type: defect | Status: closed Priority: normal | Component: ffplay Version: git-master | Resolution: wontfix Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Changes (by malaterre): * status: new => closed * resolution: => wontfix * component: undetermined => ffplay Comment: Replying to [comment:2 Balling]:
That happens because by default mpv does not have interpolation at all. And of course, if you display is G-sync, without interpolation it will switch to native frame rate of 25.000 progressive. Ffplay also supports G-sync, but I am not so sure how good does it work. See this discussion https://github.com/mpv-player/mpv/issues/6137
Indeed applying suggestion from: * https://github.com/mpv-player/mpv/issues/6137#issuecomment-423171571 as: {{{ $ ffmpeg -i bb2_an2500_copy.mkv -filter:v fps=fps=60 bb2_an2500_copy_60.mkv }}} does solve the symptoms, at least on my side. I'll close the issue as wontfix. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: mpeg4 pts values are not reordered when decoding -------------------------------------+------------------------------------- Reporter: malaterre | Owner: Type: defect | Status: reopened Priority: normal | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cus): * status: closed => reopened * resolution: wontfix => * component: ffplay => undetermined Comment: No, this looks like a real bug with mpeg4 pts values, so reponeded it with updated description. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: mpeg4 pts values are not reordered when decoding -------------------------------------+------------------------------------- Reporter: malaterre | Owner: Type: defect | Status: reopened Priority: normal | Component: | undetermined Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by Balling): So it should have reordered the frames 1, 3; 2, 5; 4, 7; 6, 9; ... Really? Apparently mpv does "mkv: Discarding potentially broken or useless index" while ffplay does not do it, so the file is just broken. LOL. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#9013: mpeg4 pts values are not reordered when decoding -------------------------------------+------------------------------------- Reporter: malaterre | Owner: Type: defect | Status: reopened Priority: normal | Component: | undetermined Version: git-master | Resolution: Keywords: asp mkv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * keywords: => asp mkv -- Ticket URL: <https://trac.ffmpeg.org/ticket/9013#comment:7> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg