docs: Update callouts for new docsify version (#2211)
This commit is contained in:
@@ -126,13 +126,14 @@ This could be for any number of reasons. Chromecast devices can be quite picky
|
||||
on network, DNS and certificate issues, as well as audio and video codecs. Check
|
||||
your Home Assistant log as there may be more information in there.
|
||||
|
||||
!> In particular, for Frigate to support casting of clips, the default ffmpeg
|
||||
settings for Frigate must be modified, i.e. Frigate does not encode clips in a
|
||||
Chromecast compatible format out of the box (specifically: audio must be enabled
|
||||
in the AAC codec, whether your camera supports audio or not). See the [Frigate
|
||||
Home Assistant
|
||||
documentation](https://docs.frigate.video/integrations/home-assistant) or [this
|
||||
issue](https://github.com/blakeblackshear/frigate/issues/3175) for more.
|
||||
> [!TIP]
|
||||
> For Frigate to support casting of clips, the default ffmpeg settings for
|
||||
> Frigate must be modified, i.e. Frigate does not encode clips in a Chromecast
|
||||
> compatible format out of the box (specifically: audio must be enabled in the AAC
|
||||
> codec, whether your camera supports audio or not). See the [Frigate Home
|
||||
> Assistant documentation](https://docs.frigate.video/integrations/home-assistant)
|
||||
> or [this issue](https://github.com/blakeblackshear/frigate/issues/3175) for
|
||||
> more.
|
||||
|
||||
### Custom element does not exist
|
||||
|
||||
|
||||
Reference in New Issue
Block a user