neolink icon indicating copy to clipboard operation
neolink copied to clipboard

Trackmix Wifi video running slow, timestamp gradually further off

Open Legendhidde opened this issue 1 month ago • 1 comments

Describe the bug Using the Reolink Trackmix WiFi and streaming the main 4K stream video is delayed. At first it doesn't seem too bad, a few seconds here and there. But after minutes it will start to slow, the timestamp on the video will be multiple minutes behind. This causes Frigate to add wrong video files and show me the wrong video for detections.

This does not happen when accessing the RTSP stream of the camera directly, but that has the result of making the video stutter every 2-3 seconds. This is the only plugin that fixes that.

This also seems to happen with other h265 Reolink camera's, such as my Duo Floodlight, but this one doesnt stutter when accessing the main stream.

I have tried basically everything so far, restreams in Scrypted, frigate, Neolink, trying it in VLC, any configuration option I could find. I have exhausted every troubleshooting step I could find online regarding Reolink, Frigate, Scrypted or Neolink. The one thing I haven't yet tried is restreaming Neolink as RTSP with Scrypted and feeding those restreams into Frigate, which sounds crazy and not sure if it would even work as VLC also shows a massive delay in the rtsp stream from Neolink.

To Reproduce Steps to reproduce the behavior. Example:

  1. Create this configuration file:
bind = "0.0.0.0"

[[cameras]]
name = "VoordeurGarage"
username = "admin"
password = "XXX"
uid = "XXX"
address = "192.168.1.XX:9000"
channel_id = 0
stream = "mainStream"
push_notifications = false

[[cameras]]
name = "VoordeurGarageZoom"
username = "admin"
password = "XXX"
uid = "XXX"
address = "192.168.1.XX:9000"
channel_id = 1
stream = "mainStream"
push_notifications = false

[[cameras]]
name = "AchterdeurGarage"
username = "admin"
password = "XXX"
uid = "XXX"
address = "192.168.1.XX:9000"
stream = "mainStream"
push_notifications = false
  1. Launch Neolink: I run Neolink in Docker on my Synology DS920+ with Intel J4125. Nothing special configured, except I bound port 8556 to 8554 because Frigate is already using that.
  2. Add the camera in Frigate using this config:
   cam1:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/h264Preview_01_sub
          input_args: preset-rtsp-generic
          roles:
            - detect
        - path: rtsp://192.168.1.XX:8556/VoordeurGarage/mainStream
          input_args: preset-rtsp-restream-low-latency
          roles:
            - record
            - audio
    detect:
      width: 896 # <---- update for your camera's resolution
      height: 512 # <---- update for your camera's resolution
      fps: 5
    onvif:
      host: 192.168.1.XX
      port: 8000
      user: admin
      password: XXX

Versions NVR software: Frigate 0.16 in Docker Neolink software: 0.6.3-rc3 Reolink camera model and firmware: Reolink Trackmix Wifi v3.0.0.4255_2411271222 and Reolink Duo Floodlight Wifi v3.0.0.4428_2412183476

Legendhidde avatar Oct 20 '25 14:10 Legendhidde

Sincere apologies for saying I have exhausted every topic, Github isn't too friendly for trying to find already solved issues.

I just discovered this, which sounds very familiar: https://github.com/QuantumEntangledAndy/neolink/issues/233

Set the buffer size to 500 for my camera's using buffer_duration = 500

Can you see any problems with this in the long or short term? So far it seems like my recordings are pretty spot on and smooth again.

Forgot to mention that I also tried the preset-rtsp-restream-low-latency which improved but didn't solve the issue.

Another strange thing I noticed is that when I fixed it, I was running 0.6.2. I tried to update to 0.6.3-rc3 like I had in the post and the problem started happening again. Deleted the container and started 0.6.2 again and no issues.

Legendhidde avatar Oct 20 '25 15:10 Legendhidde