Sfoglia il codice sorgente

clarify h264 in docs

Blake Blackshear 4 anni fa
parent
commit
1e7b53dc0e
1 ha cambiato i file con 2 aggiunte e 0 eliminazioni
  1. 2 0
      docs/docs/configuration/cameras.md

+ 2 - 0
docs/docs/configuration/cameras.md

@@ -127,6 +127,8 @@ objects:
 
 Frigate can save video clips without any CPU overhead for encoding by simply copying the stream directly with FFmpeg. It leverages FFmpeg's segment functionality to maintain a cache of video for each camera. The cache files are written to disk at `/tmp/cache` and do not introduce memory overhead. When an object is being tracked, it will extend the cache to ensure it can assemble a clip when the event ends. Once the event ends, it again uses FFmpeg to assemble a clip by combining the video clips without any encoding by the CPU. Assembled clips are are saved to `/media/frigate/clips`. Clips are retained according to the retention settings defined on the config for each object type.
 
+These clips will not be playable in the web UI or in HomeAssistant's media browser unless your camera sends video as h264.
+
 :::caution
 Previous versions of frigate included `-vsync drop` in input parameters. This is not compatible with FFmpeg's segment feature and must be removed from your input parameters if you have overrides set.
 :::