aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/loongarch/h264dsp_lasx.c
diff options
context:
space:
mode:
authorAlexander Strasser <eclipse7@gmx.net>2024-04-09 01:36:08 +0200
committerAlexander Strasser <eclipse7@gmx.net>2024-07-14 13:31:03 +0200
commit36aee69f0d2ac2255c9a47d46bc8a26c196a40c2 (patch)
tree573324d5e862aa091c39a9984d2b49abebb67f9d /libavcodec/loongarch/h264dsp_lasx.c
parent8b3d997bede0e065f19bcaa96f99dfa9978fd181 (diff)
downloadffmpeg-36aee69f0d2ac2255c9a47d46bc8a26c196a40c2.tar.gz
libavdevice: Improve example in deprecation message for opengl and sdl
When piping ffmpeg into ffplay both programs write a status line in the terminal. That causes flickering and invisibility of one or the other status line. As compromise set ffplay log level to warning, so it doesn't show the status line. The user is usually testing ffmpeg command lines and want's a preview of the result. This way the user can see the ffmpeg output and still see errors and warnings from ffplay, should they occur. Additionally set PTS to zero in ffplay to lessen the delay until the frames are displayed. Without it delay is quite observable when e.g. live capturing with low frame rates.
Diffstat (limited to 'libavcodec/loongarch/h264dsp_lasx.c')
0 files changed, 0 insertions, 0 deletions