Yeah, that made it @InTheWings. Still a bit of buffering (for example, if I set 1000ms it raises up to 1400ms and if I set 300ms it raises up to 700ms) but at least it skips the keyframes, which is what I wanted. Thank you!
Hm, that's a bit difficult to achieve as is just a ffmpeg output piped directly to the socket. By the way, there's always a 2000ms seconds caching, although I restart the stream 10 times, and is impossible that all 10 times I just miss a keyframe and have to wait for the next one for 2 seconds. The ...
Nice. This is a video of the process. The network caching is set to 100ms and the video keyframes are set to 1 per second. As you can see when the first picture is received, the video is paused for 1 second while buffering: https://femto.pw/8myg.mp4 By the way you can see the buffering also in the l...
This is easy. If I set the network caching to something less than the amount of keyframes, it will still "Stream buffering done" the amount of keyframes I'm sending. I'm using "tcp/ts://HOST:PORT" to receive the stream, and the stream is created using ffmpeg with mpegts output. I...