> If you need to use H.264 and must achieve low latency, you’ll have to modify
> your encoder to use a very conservative GOP structure. Best to use no B
> frames at all.
>
> You can make an argument for no P frames, either. That is, I-frame-only
> video, like MJPEG, but with about 20 years of
First, please properly trim old text (from the replied-to message) when
replying to emails.
Second, you don’t need to go to random third-party sites (like ‘github’) to get
“testRTSPClient”. It is already part of the “LIVE555 Streaming Media”
software; see
http://live555.com/liveMedia/#
Thank you all for your feedback. So with Ross's suggestion I implemented a
rtsp client based on this live555 example:
https://github.com/rgaufman/live555/blob/master/testProgs/testRTSPClient.cpp.
The latency may have gone down a bit actually (looks like my client may
have been at fault for some amo
On Dec 28, 2018, at 10:31 AM, Ross Finlayson wrote:
>
> 1/ In your H.264 encoder - i.e., between the creation of a raw video frame,
> and the time that it is encoded into (one or more) H.264 NAL units.
Ross didn’t go into any detail on this point, Kevin, so I thought I’d weigh in
on it.
I th
First, you haven’t said specifically how you are using the “LIVE555 Streaming
Media” software. (Remember that the software includes a RTSP server, a RTSP
client, a RTSP proxy server, and many other things.) But from the context of
your message, I assume that you are using it as a RTSP server,
Hi all! I am not quite understanding why my code has so much latency... My
main use case is not for gaming, but I did try to play a game over the
stream and the latency is HORRIBLE. I am not quite understanding what the
cause could be...
Here are some links to my code on pastebin:
https://pastebi
