vp8 rtsp copy stream not working

[Yuri Valentini]

I am trying to send and receive a webm file (only video) through a rtsp tcp tunnel with the following command line, but the receiver part produces an empty file:

Receiver site:

C:\temp\recv>ffmpeg -v 9 -loglevel 99 -report -y -f rtsp -rtsp_flags listen -rtsp_transport tcp -i rtsp://127.0.0.1:23020/live.sdp -vcodec copy -an out.webm

Transmit site:

C:\temp>ffmpeg -v 9 -loglevel 99 -report -i small.webm -vcodec copy -an -f rtsp -rtsp_transport tcp rtsp://127.0.0.1:23020/live.sdp

The same, but with mp4 files, instead is (correctly) working.

Receiver site:

C:\temp\recv>ffmpeg -v 9 -loglevel 99 -report -y -f rtsp -rtsp_flags listen -rtsp_transport tcp -i rtsp://127.0.0.1:23020/live.sdp -vcodec copy -an out.mp4

Transmit site:

C:\temp>ffmpeg -v 9 -loglevel 99 -report -i small.mp4 -vcodec copy -an -f rtsp -rtsp_transport tcp rtsp://127.0.0.1:23020/live.sdp

ffmpeg version 2.5.2
built on Dec 30 2014 17:29:04 with gcc 4.9.2 (GCC)
zeranoe build

[Yuri Valentini]

webm receiver site

[Yuri Valentini]

webm transmitter file

[Yuri Valentini]

webm input file

[Yuri Valentini]

webm output file

[Yuri Valentini]

mp4 receiver site

[Yuri Valentini]

mp4 transmitter site

[Yuri Valentini]

mp4 input file

[Yuri Valentini]

mp4 output file

[Yuri Valentini]

Using -dump option, looks like ffmpeg is not recognizing key frames (even the initial) in vp8 stream, so the copy stream is not starting.
Using -copyinkf option, overrides this behavior and the resulting file is correct.

[Carl Eugen Hoyos]

Please reopen this ticket if you can reproduce the issue with current FFmpeg git head or if you believe that this is a regression.