Tried using RTP protocol, results in error Unable to receive RTP payload type 96 without an SDP file describing it.Client-side command: ffmpeg -y -i udp://localhost:12345/ -c copy test.mp4.Tried streaming raw UDP w/o RTSP (still hangs, same issue).Removed the -re real-time streaming option on the server side.Removed -vcodec libx264 -strict 2 on the server side.Tried adding -vsync 0 to the server side command as an output option.In response to warnings about PTS/DTS issues on the client-side, I added the options -fflags +genpts+igndts to the client-side command.Messed with the client buffer size, by appending buffer_size and fifo_size arguments to the client-side input URL like so: rtsp://localhost:12345/live.sdp?buffer_size=10000000?fifo_size=100000.What I've tried (all of these have failed): The problem I'm describing happens regardless of which video file I try to stream. TVs_Best_Kisses_Top_50_(52_to_41)_kiss_h_nm_np2_le_goo_1: Input video file for the commands in these logs, for completeness. Gdb.txt: ffmpeg_g log for the client with SIGINT at the point where it hangs (seems like it waits for a packet forever). This works without a problem.įfmpeg-20200803-172802.log: Using ffmpeg version 3.4.8-0ubuntu0.2, server-side command run with additional arguments -report -loglevel 99 -v 9. This works without a problem.įfmpeg-20200803-172801.log: Using ffmpeg version 3.4.8-0ubuntu0.2, client-side command run with additional arguments -report -loglevel 99 -v 9. This command hangs.įfmpeg-20200803-170915.log: Using ffmpeg version N-98617-g533d603, server-side command run with additional arguments -report -loglevel 99 -v 9. I've attached log files following the bug report guidelines at for both the commands above, as well as some auxiliary logs.įfmpeg-20200803-170914.log: Using ffmpeg version N-98617-g533d603, client-side command run with additional arguments -report -loglevel 99 -v 9. Test.mp4: Invalid data found when processing input When I Ctrl-C the client, I see a file called test.mp4, but it's unplayable, which I can tell because ffprobe outputs the following: This happens regardless of the input file that I use. However, it works when I switch protocol to TCP (using -rtsp_transport tcp). When I run the same commands as above in the updated version, however, the client side hangs indefinitely. However, I have since upgraded to the most recent version because I need to use the -stream_loop functionality, which was buggy in older versions of ffmpeg. This works without a hitch on ffmpeg 3.4.8-0ubuntu0.2 (installed via apt-get), and I can open test.mp4 in a media player to view a streamed copy of the input video file. On the same machine, I run the following two commands:įfmpeg -y -rtsp_flags listen -timeout 10 -i rtsp://localhost:12345/live.sdp -c copy test.mp4 prefix=/home/trenton-windows/ffmpeg_build -pkg-config-flags=-static -extra-cflags=-I/home/trenton-windows/ffmpeg_build/include -extra-ldflags=-L/home/trenton-windows/ffmpeg_build/lib -extra-libs='-lpthread -lm' -bindir=/home/trenton-windows/bin -enable-gpl -enable-gnutls -enable-libaom -enable-libass -enable-libfdk-aac -enable-libfreetype -enable-libmp3lame -enable-libopus -enable-libvorbis -enable-libvpx -enable-libx264 -enable-libx265 -enable-nonfree -enable-debug=3 -disable-optimizations -disable-stripping OS: Ubuntu 18.04.4 LTS (reproduced on Ubuntu 20.04 LTS as well)įfmpeg version: N-98617-g533d603 (reproduced with 4.3 as well) I am currently working on some video-related experiments involving streaming H.264-encoded video using UDP. I was hoping to get some help on my streaming setup.