Alessandro Ros

Hello @eravellaSC, of course there's interest, but the problem is that currently the API is missing a strong authentication system, therefore it's meant to be used either in a closed...

replaced by #3280

Hello, from the first log you posted it seems that the server is reading correctly the MPEG-TS stream: ``` [UDP source] ready: 2 tracks (H264, MPEG-1/2 Audio) 2023/11/27 12:55:54 INF...

Closed since author didn't provide requested data. @haimlevyy your issue is unrelated from this, i've created a dedicated issue in #3490

Hello @rudyryk, i took a look at the network dumps through Wireshark, and in particular at the pcap corresponding to the "bad" sample. For the first two seconds, your camera...

Hello, regarding the memory leak when reading non-existent streams, i ran your script against MediaMTX 1.3.1 with no one publishing, but i couldn't find any trace of it. I enabled...

@Munoon enable pprof: ``` # Enable pprof-compatible endpoint to monitor performances. pprof: yes # Address of the pprof listener. pprofAddress: 127.0.0.1:9999 ``` and post here the goroutine and heap reports,...

In the pprof you posted there is no sign of any leak, there are 12 publishers (corresponding to the 12 routines that are waiting on ringbuffer.(*RingBuffer).Pull) and 150 readers (corresponding...

Hello @jsbohnert, i took a look at the dump you sent, and i can say that the difference between a stream generated with x264 and the stream generated with the...

Hello, this can be fixed but you need to attach a server log with the option `logLevel` set to `debug` in `mediamtx.yml` and then replicate the issue.