[Support]: Wrong time stamp being played when reviewing event, after 16.0 upgrade (now on 16.1) #19923
Replies: 3 comments 34 replies
-
Based on your description of recording playback issues after upgrading to Frigate 16.1, there are several potential causes and solutions to investigate. For recording playback problems where the wrong time segment plays, this could be related to recording integrity or browser compatibility issues. First, ensure your cameras send h264 encoded video for proper Web UI playback(1). You can open The nginx logs you're seeing with warnings about DTS timestamps suggest potential video stream issues(2). These messages indicate problems with the video stream timing that can affect recording playback. For troubleshooting recording issues, enable debug logging for the recording system(3): logger:
logs:
frigate.record.maintainer: debug This will show how long it takes for recordings to be moved from RAM cache to disk and help identify if there are performance bottlenecks(3). Given your system specifications and the random restarts, check your system resources. The documentation notes that if CPU, RAM, disk throughput, or bus I/O is insufficient, performance issues will occur(3). Monitor your system using:
For the SQLite database, ensure it's not stored on a network share as this can cause locking issues(1). If your The random restarts combined with recording playback issues suggest potential system resource constraints or hardware acceleration problems with your NVIDIA GPU setup. Monitor GPU utilization and consider temporarily disabling hardware acceleration to isolate the issue. ** 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
I have a similar issue after upgrading to 16.1 from 16.0. My logs are clean - no errors reported both in main and go2rtc logs. The issue is with reviewing recordings. When from Review interface I click on a clip that has a start time at 7:38AM, Frigate jumps to 8:03AM time mark, despite there are events and motion on timeline between 7:38AM and 8AM. If I manually click on, let's say, 7:10AM the red marker jumps back to 8:04AM, bypassing all the recordings in between. There's a workaround to see all the recordings. If I click on a motion at 7:00AM, Frigate starts playback normally and, if I let it play, it goes through all the records without skipping anything. Moreover, I noticed that the issue seem to affect all the cameras simultaneously, i.e. I have 3 cameras and I cannot review any clip of any camera between 7:20AM and 8:00AM, unless I go back in time to 7:00AM and just let it play. This is a new behaviour introduced in version 16.1. My setup is unchanged and I didn't touch Frigate config for ~6 months. My setup is 3 different POE Reolink cameras, Frigate runs in a Docker container, Intel CPU/GPU. |
Beta Was this translation helpful? Give feedback.
-
Bump. Having the same problem. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
When clicking on a detection in the review pane to view the video, the page loads to play the segment, and the blured out thumbnail contains the event, however when the video starts playing a totally different time segment starts playing, usually at the top of the hour. I.e if the event happened at 17:30, I click on the event to review it, and what starts playing is the camera feed from 17:00.
On one clip I see an event that happened at 19:58, click on it to review, that camera feed from 20:03, starts playing. I try and scrub timeline back to 19:58 and frigate says " no recordings found for this time "
There is also an issue where frigate seems to be restarting itself randomly every couple hours.
Version
16.1
What browser(s) are you using?
Firefox 142.01 and Chromium 138
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
Docker CLI
docker-compose file or Docker CLI command
Object Detector
TensorRT
Network connection
Wired
Camera make and model
mix of hikvsion, amcrests, reolinks
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Recent changes I've done were switching some cameras to run "detect" on full camera resolution to try and get better Facial recognition and license plate detection.
Also battling an issue where frigate is randomly restarting but difficult to catch when that happens, nor capture logs when that's happening as frigate restarts.
Beta Was this translation helpful? Give feedback.
All reactions