Alessandro Ros

Hello, as anticipated by @Ataman this is a hardware-related issue that happens when power is not enough for the current workload. Switch to a better power supply or alternatively decrease...

Hello, this can be probably fixed but you need to provide a network dump of traffic exchanged between the camera and the server, from the moment the server starts to...

Hello, the network dump you provided is not enough to replicate the bug since it contains exchanged data between your NVR and FFmpeg, not between your NVR and the server....

@Build2NU your issue is unrelated from this and happens under different circumstances. Instructions on how to generate network dumps are present in the issue template.

@svk23 thanks for providing the network dump, what i noticed from your stream is that IDR frames have a pic_order_cnt that is not zero, while the server assume they have....

@svk23 that's wonderful, just one thing before merging - i noticed that recordings of the network dump you provided were blank - are you able to verify whether recordings of...

Hello, the API already provides basic track informations (tracks and their codec) with the `/v2/paths/list` endpoint: ```json { "pageCount": 0, "items": [ { "name": "mypath", "tracks": [ "h264", "mpeg4-audio" ],...

Hello, i tested your configuration, but in my case everything worked as expected. This is the overall configuration, i used two different `recordPaths` for two different cameras: ```yml pathDefaults: record:...

Hello, in order to provide inter-operability between Linux and Windows, we're not using Bash and its features (like variable replacement, i.e. `${RTSP_PATH////_}`) but a simpler system that only provides `$RTSP_PATH`...

Is it normal that the NACK SSRC is random? https://github.com/pion/interceptor/blob/0ee4264763aea2c10d447866f4916982d8e2346c/pkg/nack/generator_interceptor.go#L116 I didn't saw the specification, but the receiver SSRC should be shared between reports and nacks, therefore it is random...