> On Jul 1, 2025, at 7:32 AM, [email protected] wrote: > > We make an RTSP server, it is fully our code. It is based on Live555. On the > other side may be VLC or ffplay or other player. Noone of them works. > Another our app (based on ffmpeg) has written an archive, this (not working) > app reads it and sends frames to a client.
I suggest that you first use our own “testRTSPClient” (see <http://live555.com/liveMedia/#testProgs >) and “openRTSP” (see <http://live555.com/openRTSP/ >) RTSP client applications - rather than VLC, ffplay, etc. - to test whether your server is working. Also, I suggest that you first try to make your server work by streaming pre-recorded media (perhaps using “testOnDemandRTSPServer” as a model), before you use it to (try to) stream from a live source. But unfortunately, because you have developed your own server code (rather than using our existing RTSP server applications, e.g., “testOnDemandRTSPServer” or “live555MediaServer”), there is only limited help that I will be able to give you on this mailing list. But note that your server code does not need to do *anything* to set (or inspect) RTP timestamps. Our code handles RTP timestamps automatically. See <http://live555.com/liveMedia/faq.html#why-are-rtp-timestamps-not-visible >; specifically: "Applications that use the LIVE555 libraries never need to concern themselves with RTP timestamps." Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
