"Changing video frame properties on the fly is not supported by all filters." message flood

[Michael Niedermayer]

Playing any video with ffplay fills the screen with
"Changing video frame properties on the fly is not supported by all filters." messages

./ffplay ~/videos/matrixbench_mpeg2.mpg 
ffplay version N-113489-ga8321669cac Copyright (c) 2003-2024 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
  configuration: --enable-libspeex --enable-libvpx --enable-gpl --cc='ccache gcc' --enable-pthreads --enable-debug=0 --cpu=core2 --enable-libvorbis --samples=fate-suite/ --enable-libx264 --enable-libdc1394 --enable-libxvid --enable-libfreetype --enable-nonfree --enable-libmodplug --enable-libmp3lame --enable-version3 --enable-libbluray --assert-level=2 --enable-libtheora --enable-openssl --enable-libcaca --enable-libopus --enable-libcdio --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libgsm --enable-vdpau --enable-iconv --enable-libgme --enable-libwebp --enable-libpulse --enable-libass --enable-frei0r --enable-libfdk-aac --enable-libilbc --tempprefix=/home/michael/ffconftemp --enable-libxavs --enable-libx265 --enable-fontconfig --enable-libbs2b --enable-libzvbi --enable-libtwolame --enable-chromaprint --enable-libsmbclient --enable-libopenh264 --enable-libxcb --enable-libsnappy --enable-libssh --enable-libv4l2 --enable-libjack --enable-libsoxr --enable-libharfbuzz --prefix=install-tmp
  libavutil      58. 37.101 / 58. 37.101
  libavcodec     60. 38.100 / 60. 38.100
  libavformat    60. 20.100 / 60. 20.100
  libavdevice    60.  4.100 / 60.  4.100
  libavfilter     9. 17.100 /  9. 17.100
  libswscale      7.  6.100 /  7.  6.100
  libswresample   4. 13.100 /  4. 13.100
  libpostproc    57.  4.100 / 57.  4.100
[mpeg @ 0x7f0a4c000c80] start time for stream 0 is not set in estimate_timings_from_pts
Input #0, mpeg, from '/home/michael/videos/matrixbench_mpeg2.mpg':
  Duration: 00:03:07.66, start: 0.220000, bitrate: 5633 kb/s
  Stream #0:0[0x1bf]: Data: dvd_nav_packet
  Stream #0:1[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, bt470bg/bt470m/bt470m, bottom first), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
      Side data:
        cpb: bitrate max/min/avg: 11421600/0/0 buffer size: 1835008 vbv_delay: N/A
  Stream #0:2[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16p, 384 kb/s
[ffplay_buffer @ 0x7f0a186bac80] filter context - w: 720 h: 576 fmt: 0 csp: unknown range: unknown, incoming frame - w: 720 h: 576 fmt: 0 csp: bt470bg range: tv pts_time: 0.22
[ffplay_buffer @ 0x7f0a186bac80] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f0a186bac80] filter context - w: 720 h: 576 fmt: 0 csp: unknown range: unknown, incoming frame - w: 720 h: 576 fmt: 0 csp: bt470bg range: tv pts_time: 0.26
[ffplay_buffer @ 0x7f0a186bac80] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f0a186bac80] filter context - w: 720 h: 576 fmt: 0 csp: unknown range: unknown, incoming frame - w: 720 h: 576 fmt: 0 csp: bt470bg range: tv pts_time: 0.3
[ffplay_buffer @ 0x7f0a186bac80] Changing video frame properties on the fly is not supported by all filters.

[Gyan]

There are two issues here.

One is, that the message appears at all. This seems related to the late setting of colorspace and range. That needs to be addressed in fftools/*.

Second is the spamming of the log with each frame. This is easily addressed by limiting the warning to the first time each new permutation of changed params is seen. I can send a patch for this if you like.

[Michael Niedermayer]

its certainly a good idea to limit repeating the message but even one is bad if its wrong

[Niklas Haas]

Both issues should be fixed, no?

• 94422871fce3b90bebc95f5cae939fbbc4e33224 prevents log spamming
• dcc7263b0e7935b6864e43465cfeca423bdf9e77 implements metadata setting for ffplay

[Michael Niedermayer]

Replying to Niklas Haas:

Both issues should be fixed, no?

• 94422871fce3b90bebc95f5cae939fbbc4e33224 prevents log spamming
• dcc7263b0e7935b6864e43465cfeca423bdf9e77 implements metadata setting for ffplay

yes, seems fixed