Alessandro Ros

Hello, WebSocket is a generic communication protocol like HTTP - in order to perform signaling, there must be a specification that describes how messages are formatted and what's their order....

@pikachu937 that signaling implementation worked with a non-standardized procedure that was more or less like this: 1. a client connects through WebSocket to the server, without sending anything other than...

Instructions on how to publish to the server with Unity, WebRTC and WHIP, and on how to read from the server with Unity, WebRTC and WHEP have been added to...

Hello, the problem of both proposed solutions (https://github.com/bluenviron/mediamtx/issues/3455#issuecomment-2216296201 and #3507) is that they prevent `runOnDemandRestart: yes` from working, which is also the correct way to address the issue, although it's...

@mrlt8 in every operating system or programming language there are two ways to start subprocesses: * in the foreground, in which the subprocess is launched directly, stays open during runtime...

> The onDemandPublisherCloseTimer becomes unnecessary once the onDemandPublisher has closed This is not true, the on-demand publisher might be in the process of restarting, as described in the background logic...

Hello, Graylog already supports ingesting MediaMTX logs through systemd. The GELF format would be an improvement since it allows to pass structured data in place of plain strings. We are...

The situation is the following: Symmetric parameters now play a role in matching codecs between senders and receivers, in particular: * H264 symmetric parameters were implemented with #1903 * VP9...

@Sean-Der this issue was a little bit too generic since it refers to "all codecs", present and future 🤣, let's just say that given all information that we have available...

Hello, it's impossible to replicate the issue or to assert what the problem is without a server log, with `logLevel` set to `debug`, that shows IPs of incoming clients and...