Hello, and thanks for the help.
- We see these types of messages all the time in our platform (which
is implemented using live555 on the server.) A different media player
we've tried seems to play the stream without these "glitches".
- I see the same messages using my own RTSP/RTP stack written
> I`m implementing low-latency h264 rtsp source. Based on this code
> http://stackoverflow.com/questions/13863673/how-to-write-a-live555-framedsource-to-allow-me-to-stream-h-264-live
>
Oh please! Only second-rate programmers use 'stackoverflow.com'.
The proper web site for documentation on the
Hello.
I`m implementing low-latency h264 rtsp source. Based on this code
http://stackoverflow.com/questions/13863673/how-to-write-a-live555-framedsource-to-allow-me-to-stream-h-264-live
I wrote subclass of FramedSource and able to watch this stream in my client
app. But even if I put 1 frame per se
> Ok, that clears it up a bit. And as PassiveServerMediaSubsession would
> multicast it would do it all the time, regardless of
> if anyone actually receives the stream, right? Not all of the backend cameras
> are interesting all the time though, so this also
> requires some consideration as netw
