From e68f80b44a8e609e254ce11cdf0bc91b9ddfdbd8 Mon Sep 17 00:00:00 2001 From: Matthew Parlane Date: Tue, 19 Jul 2022 13:33:30 +1200 Subject: [PATCH] Use relative path without .. for rtmp documentation to fix #3481 ../faq was used in rtmp.md which leads to the wrong URL when the current URL ends in a slash due to 301 redirect of netlify --- docs/docs/configuration/rtmp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/rtmp.md b/docs/docs/configuration/rtmp.md index 76f6f81a7..5c6b3b5a0 100644 --- a/docs/docs/configuration/rtmp.md +++ b/docs/docs/configuration/rtmp.md @@ -5,4 +5,4 @@ title: RTMP Frigate can re-stream your video feed as a RTMP feed for other applications such as Home Assistant to utilize it at `rtmp:///live/`. Port 1935 must be open. This allows you to use a video feed for detection in frigate and Home Assistant live view at the same time without having to make two separate connections to the camera. The video feed is copied from the original video feed directly to avoid re-encoding. This feed does not include any annotation by Frigate. -Some video feeds are not compatible with RTMP. If you are experiencing issues, check to make sure your camera feed is h264 with AAC audio. If your camera doesn't support a compatible format for RTMP, you can use the ffmpeg args to re-encode it on the fly at the expense of increased CPU utilization. Some more information about it can be found [here](../faqs#audio-in-recordings). +Some video feeds are not compatible with RTMP. If you are experiencing issues, check to make sure your camera feed is h264 with AAC audio. If your camera doesn't support a compatible format for RTMP, you can use the ffmpeg args to re-encode it on the fly at the expense of increased CPU utilization. Some more information about it can be found [here](/faqs#audio-in-recordings).