From 9621b4b9a1f9377079f334851f2de57942daf0df Mon Sep 17 00:00:00 2001 From: Nicolas Mowen Date: Thu, 23 Feb 2023 20:23:14 -0700 Subject: [PATCH] Add tips for debugging playback issues (#5574) --- docs/docs/troubleshooting/faqs.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/docs/troubleshooting/faqs.md b/docs/docs/troubleshooting/faqs.md index 15ce9bc12..4b166b037 100644 --- a/docs/docs/troubleshooting/faqs.md +++ b/docs/docs/troubleshooting/faqs.md @@ -17,16 +17,18 @@ ffmpeg: record: preset-record-generic-audio-aac ``` +### I can't view events or recordings in the Web UI. + +Ensure your cameras send h264 encoded video, or [transcode them](/configuration/restream.md). + +You can open `chrome://media-internals/` in another tab and then try to playback, the media internals page will give information about why playback is failing. + ### My mjpeg stream or snapshots look green and crazy This almost always means that the width/height defined for your camera are not correct. Double check the resolution with VLC or another player. Also make sure you don't have the width and height values backwards. ![mismatched-resolution](/img/mismatched-resolution-min.jpg) -### I can't view events or recordings in the Web UI. - -Ensure your cameras send h264 encoded video, or [transcode them](/configuration/restream.md). - ### "[mov,mp4,m4a,3gp,3g2,mj2 @ 0x5639eeb6e140] moov atom not found" These messages in the logs are expected in certain situations. Frigate checks the integrity of the recordings before storing. Occasionally these cached files will be invalid and cleaned up automatically.