#Frigate - Unresolved FFMpeg crashes

1 messages · Page 1 of 1 (latest)

gloomy hedge
#

I've been experiencing for months now very unstable streams from my frigate installation. My cameras are configured using RTSP feeds from a Lorex NVR. For the most part, they appear to work but frequently I'll receive the "frames not received" error and checking the logs shows that the ffmpeg process is crashing. I've tried a bunch of different combinations including different input_args, disabling harware acceleration per-camera, and I just cant seem to resolve this. Attached is all I can see in the frigate logs when this occurs. Any help would be greatly appreciated 🙏

image.png
gloomy hedge
#

Relevant config sections:

  hwaccel_args: preset-nvidia-h264
go2rtc:
  streams:
    Front_Porch:
      - ffmpeg:rtsp://<username>:<password>@<address>/cam/realmonitor?channel=2&subtype=0
  webrtc:
    candidates:
      - <address>:8555
      - stun:8555
cameras:
  Front_Porch:
    ui:
      order: 2
    live:
      stream_name: Front_Porch
    objects:
      track:
        - person
        - dog
        - car
        - bicycle
      filters:
        person:
          mask:
            - 220,193,352,192,352,240,220,240
            - 220,193,352,192,220,240,281,99
        car:
          mask:
            - 198,83,204,0,233,0,235,45,352,133,352,240,0,240,0,0,148,0,148,46
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/Front_Porch
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
    motion:
      mask:
        - 352,122,352,240,260,240,232,214,252,180,298,167,273,129,299,97
        - 194,71,228,98,248,72,224,36
        - 276,19,351,19,351,8,276,8```
topaz dock
#

the camera is sending bad data that the GPU is unable to handle, based on the logs

pliant sky
#

I'm getting similar problems, with the timestamps are unset error, and non-monotonous dts in output error, causing my camera connections to timeout, causing ffmpeg to crash

#

also getting EOF (end of file) errors in go2rtc

pliant sky
#

is it a reolink thing? the error usually occurs 30 minutes-2 hours after starting frigate and putting birdseye view on my tv.

#

if I don't put birdseye view on, it doesn't show any errors in the logs afaik

#

the substream is using http-flv, while the main stream uses rtsp

#

also with the main stream, it is h265, but I also thought it was interesting that I could watch it in firefox. Is it actually h265, or is my laptop doing some h265 plugin trickery

gloomy hedge