Alessandro Ros

Hello, the main different between v0.17.17 and v0.18.0 is that the latter parses all incoming RTP/RTCP packets and re-encodes them. Anyway, please post a sample configuration and a server log...

Hello, in my opinion you have to either lower the resolution or switch to H265. It can be a bandwidth problem (try increasing readBufferCount) or even a decoder problem, since...

Hello, of course it would be good to support RTSP streams with a single track that contains a MPEG-TS stream that multiplexes multiple tracks, but... in my opinion using RTSP...

> First of all, RTSP with MPEG-TS have sense in several scenarios. For example if you want to pass the PSI tables in the stream for a DVB environment If...

Hello, please post server logs with `logLevel: debug`. It would be good to support these kind of tracks.

> I don't want that the rtsp-simple-server will internally parse/filter these tracks. That I want is to receive them untouched. The server needs to know the clock rate of that...

i'm fixing the very similar issue #832 and i took another look at this - text and application tracks are **supported by the server** indeed, the problem here is that...

Clock rate is needed to generate RTCP receiver reports, that are mandatory when reading with RTSP/UDP. There isn't a default clock rate, therefore these kind of streams can't be supported....

@wazerstar i'd really like to hard-code a default clock rate value into the server and solve this issue once for all, but without clock rate there are no RTCP reports,...

Hello, the problem of WebRTC is that it requires video re-encoding from H264 to VP8 (or alternatively, the video track must already be in VP8). This can't be done without...