So if the full structure is /home/appdata/frigate/custom-ffmpeg/bin/ffmpeg then /home/appdata/frigate/custom-ffmpeg needs to be mapped to /usr/lib/btbn-ffmpeg.I want to use ffmpeg to access my webcam. NOTE: The folder that is mapped from the host needs to be the folder that contains /bin. Restart frigate and the custom version will be used if the mapping was done correctly.Update your docker-compose or docker CLI to include '/home/appdata/frigate/custom-ffmpeg':'/usr/lib/btbn-ffmpeg':'ro' in the volume mappings.Download your ffmpeg build and uncompress to a folder on the host (let's use /home/appdata/frigate/custom-ffmpeg for this example).In this case, a docker volume mapping can be used to overwrite the included ffmpeg build with an ffmpeg build that works for your specific hardware setup. However, there exists some hardware setups which have incompatibilities with the included build. Included with Frigate is a build of ffmpeg that works for the vast majority of users. Note that if you rename objects in the labelmap, you will also need to update your objects -> track list as well. This may need to be in a custom location if network storage is used for the media folder. You can customize the location of the database in the config if necessary. If you are storing your database on a network share (SMB, NFS, etc), you may get a database is locked error message on startup. They also won't show up in the Media Browser within Home Assistant. If that database is deleted, recordings will be orphaned and will need to be cleaned up manually. within HassOS) database #Įvent and recording information is managed in a sqlite database at /media/frigate/frigate.db. This section can be used to set environment variables for those unable to modify the environment of the container (ie. NOTE: All FFmpeg logs are sent as error level. Available log levels are: debug, info, warning, error, critical
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |