#Is frigate API broken? video files uploaded have very wrong times when playing
31 messages · Page 1 of 1 (latest)
this is a problem with the timestamps that the camera is sending. Is this an export or where is this video being downloaded and played from
this is an export using a script, being send to telegram and played from there.
the timestamps in the video itself are correct, so the camera knows todays date, and has the time correct as well.
its a Annke camera.
I am not talking about the timestamp overlay
video data has internal timestamps PTS (presentation timestamp) and DTS (decoding timestamp)
if these are incorrect then the video will not have correct length and many other issues
would be good to see your script
the input_text.telegram_video_link2 entity, when changed, will use a send video on telegram command.
okay, it is still using the frigate api. I'd be curious if this continued happening after a frigate restart
Yes, i have this issue already for a while now. And with my messing around, home assistant and the complete system get restarted often.
I went back 3 weeks ago and same issue.
I will test a frigate addon restart and then send the video when started, later today. Quite occupied with the kid atm 😄
yeah that would be helpful to see
Anything to maybe tweak in settings of annke?
make sure it is syncing with a valid time server and has access or is pointed at a local time server like the router.
It is. Timestamp is also on the second accurate
so nothing else to do?
I don't have any recommendations without seeing the config of the camera or an example of the individual recording segment files
(not the clip.mp4)
what do you then mean with the recorded segment?
go2rtc config:
- rtsp://admin:xxx@192.168.1.218:554/Streaming/Channels/101#backchannel=0
- rtsp://admin:xxx@192.168.1.218:554/Streaming/Channels/102#backchannel=0
- isapi://admin:xxx@192.168.1.218:80/
- ffmpeg:garage-door#audio=aac```
individual cam config:
ffmpeg:
inputs:
- path: rtsp://192.168.1.184:8554/garage-door
input_args: preset-rtsp-restream
roles:
- record
# - path: rtsp://admin:xxx@192.168.1.218:554/Streaming/Channels/102/
# roles:
- detect
motion:
threshold: 67
mask:
- 2160,964,2160,555,2096,572,1840,838,1190,964
- 1250,470,1039,443,1076,0,1203,0
- 0,964,0,666,321,964
- 1383,964,974,964,966,657,1295,662
- 584,0,0,426,0,0
- 2160,0,2160,410,1164,0
contour_area: 10
improve_contrast: 'true'
zones:
bamboo_hedge:
coordinates: 1089,392,890,366,1003,47,1091,66
car_parking_spot:
coordinates: 354,939,148,852,256,681,437,517,941,582,775,943
door_in_garden:
coordinates: 1157,784,1446,765,1414,585,1180,583
door_on_parkspot:
coordinates: 1099,964,664,964,799,643,901,380,1095,418
objects:
track:
- person
- cat
- dog
- car
filters:
car:
mask:
- 1200,0,1200,536,550,536,551,0
detect:
width: 2160
height: 964
enabled: true
record:
enabled: true
# Optional: Number of minutes to wait between cleanup runs (default: shown below)
# This can be used to reduce the frequency of deleting recording segments from disk if you want to minimize i/o
expire_interval: 60
retain:
days: 30
mode: all
events:
pre_capture: 5
post_capture: 10
retain:
default: 60
mode: motion
objects:
car: 3
snapshots:
enabled: true
retain:
# Required: Default retention days (default: shown below)
default: 60```
One of the individual files in /media/frigate/recordings
I will dm you one tommorow, 🙂 thanks for the assistance!
send.
downgrading go2rtc to 1.9.2 solved this