[Beta2] Frigate clips occasionally do not "autoplay" -- unexpected client/server interaction? #1637
Comments
dermotduffy
changed the title
|
Can you try and get the nginx logs from inside the frigate container when this happens? They should be at |
|
On load (no autoplay, ignore /api/stats from various HA instances): On manual play click: |
|
I haven't been able to reproduce this. Does this happen for the same clip consistently? |
|
Yes -- once a clip behaves this way, it seems to reliably & repeatedly behave this way. I see it on multiple cameras. |
|
Do you have any errors in the browser console? What browser are you using? |
|
Nothing on the console. Tested:
|
|
I am wondering of there is something wrong with the first segment referenced in the m3u8 playlist. Can you curl that endpoint for the failing event and post the contents? |
|
Verified on Safari |
|
Assuming you mean on the index, here is a curl of a "bad" clip |
|
I can manually fetch the segments referenced: |
|
Hmm. This is interesting, two segments captured from a good clip and bad clip from the same camera (Note: I have no idea what this command should output, I'm stabbing in the dark here): |
|
I am guessing this is related: kaltura/nginx-vod-module#675 What is the i-frame interval on your camera? |
|
Do you see the same behavior for this event in Frigate's Events UI? |
|
Sorry, I don't know that. The cameras I have seen this behavior on so far are WYZE with the "official" RTSP firmware, I don't think they have a means to configure i-frame interval. |
|
It plays fine on the Frigate Event UI (but that does not autoplay anyway, for any clips, AFAICT). |
|
The workaround described in that other bug works! Adding this to the server section of I do not understand the implications of enabling this more generally, do you? This implies there may be timing implications. |
|
Fantastic! Thanks for testing. I actually think this will help some other issues that have been hard to track down. I believe it tries to force 10s segments, but not all cameras have consistent enough key frame intervals. I will add it in and do some testing on my end in the morning. If I don't run into anything, I will add it in and put up the next RC. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
With Frigate 0.9.0 beta2, and the matching HA integration pre-release 2.0.0, occasionally a clip/event will not autoplay in the browser. When the video element loads, manually clicking the play icon will correctly play the video. I have observed this behavior:
I am confident this is new behavior from Frigate 0.9.0 onwards, and as the URLs are resolving to correctly formed Frigate URLs and the video elements have the attribute autoplay enabled -- I am not convinced this is a "client-side" issue even though it has all the appearance of one. This happens across multiple browsers and OSes.
This makes media browsing more painful.
Version of frigate
0.9.0-3340952
Config file
Include your full config file wrapped in triple back ticks.
Frigate container logs
Nothing logged of interest.
Query logs
Logs from my reverse proxy (Apache) on the requests being made from HomeAssistant to Frigate:
On video element load (where I would expect autoplay):
... when play is manually clicked:
Frigate stats
{"back_yard":{"camera_fps":4.1,"capture_pid":285,"detection_fps":1.0,"pid":247,"process_fps":4.1,"skipped_fps":0.0},"detection_fps":7.1,"detectors":{"coral":{"detection_start":0.0,"inference_speed":9.53,"pid":227}},"front_door":{"camera_fps":4.0,"capture_pid":290,"detection_fps":0.0,"pid":249,"process_fps":4.0,"skipped_fps":0.0},"garage":{"camera_fps":4.1,"capture_pid":275,"detection_fps":0.0,"pid":244,"process_fps":4.1,"skipped_fps":0.0},"kitchen":{"camera_fps":0.1,"capture_pid":259,"detection_fps":0.1,"pid":238,"process_fps":0.1,"skipped_fps":0.0},"landing":{"camera_fps":4.0,"capture_pid":281,"detection_fps":0.0,"pid":246,"process_fps":4.0,"skipped_fps":0.0},"living_room":{"camera_fps":4.0,"capture_pid":266,"detection_fps":0.0,"pid":241,"process_fps":4.0,"skipped_fps":0.0},"master_bedroom":{"camera_fps":4.1,"capture_pid":270,"detection_fps":0.0,"pid":243,"process_fps":4.1,"skipped_fps":0.0},"office":{"camera_fps":0.1,"capture_pid":261,"detection_fps":0.0,"pid":239,"process_fps":0.1,"skipped_fps":0.0},"service":{"storage":{"/dev/shm":{"free":234.4,"mount_type":"tmpfs","total":268.4,"used":34.1},"/media/frigate/clips":{"free":15628.6,"mount_type":"ext4","total":244529.7,"used":216408.2},"/media/frigate/recordings":{"free":15628.6,"mount_type":"ext4","total":244529.7,"used":216408.2},"/tmp/cache":{"free":1999.7,"mount_type":"tmpfs","total":2000.0,"used":0.3}},"uptime":2177,"version":"0.9.0-3340952"},"sitting_room":{"camera_fps":4.1,"capture_pid":251,"detection_fps":6.0,"pid":235,"process_fps":4.1,"skipped_fps":0.0}}Screenshots
If applicable, add screenshots to help explain your problem.
Maybe ~75% of clicked clips will autoplay, 25% will act like this (no autoplay, but work fine when play is manually clicked).
Computer Hardware
The text was updated successfully, but these errors were encountered: