0.15.0 Beta 5

[blakeblackshear]

Beta Documentation: https://deploy-preview-13787--frigate-docs.netlify.app/

Images

• ghcr.io/blakeblackshear/frigate:0.15.0-beta5
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-standard-arm64
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-tensorrt
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-tensorrt-jp4
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-tensorrt-jp5
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-rk
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-rocm
• ghcr.io/blakeblackshear/frigate:0.15.0-beta5-h8l

Changes since Beta 4

• Ability to save debug images for GenAI
• QSV ffmpeg changes for reolink compatibility
• Nested model config simplifications
• Fix for GPU stats when user has multiple Nvidia GPUs of same model
• Fix event cleanup error
• UI fixes and wording updates to simplify UI

Major Changes for 0.15.0

Breaking Changes

There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to back up your current config and database before upgrading:

1. Simply copy your current config file to a new location
2. Stop Frigate and make a copy of the frigate.db file

• Rewritten SHM system
  • The SHM system has been rewritten to be more stable. This means that a large % of shared memory (SHM) will be used by default but the total usage will not fluctuate, and Frigate will not fail from SHM overflowing. However, this also means that having the correct SHM size for your cameras, detector, and hardware is more important to having a smooth experience with Frigate. A new calculation is done on startup, so if your shm_size is too low then a warning will be printed in the log stating that it needs to be increased.
• Recording configuration changed
  • The record config has been refactored to allow for direct control of how long alerts and detections are retained. These values will be automatically populated from your current config, but you may want to adjust the values that are set after updating. See the updated docs here and ensure your updated config retains the footage you want it to.
• ffmpeg updates
  • ffmpeg has been updated to version 7. Some Intel users may need to change what hwaccel preset they are using (preset-vaapi may need to now be preset-intel-qsv-h264 or preset-intel-qsv-h265) if camera feeds are not functioning correctly after upgrading. This may need to be adjusted on a per-camera basis. If a qsv preset is not working properly, you may still need to use a preset-vaapi or revert to the previous ffmpeg version as described below.
  • The new version provides many improvements, but the old version can still be run if needed by specifying path: "5.0" in your ffmpeg: config entry. For example:

    ffmpeg:
      path: "5.0"
    

  • ffmpeg presets have been updated. It is always recommended to use ffmpeg presets rather than manual arguments.
  • ffmpeg is no longer part of $PATH. In most cases this is handled automatically.
    • go2rtc exec streams will need to add the full path for ffmpeg which in most cases will be /usr/lib/ffmpeg/7.0/bin/ffmpeg.
    • If the go2rtc config has bin: ffmpeg defined, it needs to be removed.
• The nested model config under a detector has been simplified to just model_path as a string value. This change will be handled automatically through config migration.
• Submitting to Frigate+
  • The Frigate+ view in the UI has been replaced by the new Explore view. See the notes below.

Explore

The new Explore pane in Frigate 0.15 makes it easy to explore every object tracked by Frigate. It offers a variety of filters and supports keyword and phrase-based text search, searching for similar images, and searching through descriptive text generated by AI models.

The default Explore pane shows a summary of your most recent tracked objects organized by label. Clicking the small arrow icon at the end of the list will bring you to an infinitely scrolling grid view. The grid view can also be set as the default by changing the view type from the Settings button in the top right corner of the pane.

The Explore pane also serves as the new way to submit images to Frigate+. Filters can be applied to only display tracked objects with snapshots that have not been submitted to Frigate+. The left/right arrow keys on the keyboard allow quick navigation between tracked object snapshots when looking at the Tracked Object Details pane from the grid view.

AI/ML Search

Frigate 0.15 introduces two powerful search features: Semantic Search and GenAI Search. Semantic Search can be enabled on its own, while GenAI Search works in addition to Semantic Search.

Semantic Search

Semantic Search uses a CLIP model to generate embeddings (numerical representations of images) for the thumbnails of your tracked objects, enabling searches based on text descriptions or visual similarity. This is all done locally.

For instance, if Frigate detects and tracks a car, you can use similarity search to see other instances where Frigate detected and tracked that same car. You can also quickly search your tracked objects using an "image caption" approach. Searching for "red car driving on a residential street" or "person in a blue shirt walking on the sidewalk at dawn" or even "a person wearing a black t-shirt with the word 'SPORT' on it" will produce some stunning results.

Semantic Search works by running an AI model locally on your system. Small or underpowered systems like a Raspberry Pi will not run Semantic Search reliably or at all. A dedicated GPU and 16GB of RAM is recommended for best performance.

See the Semantic Search docs for system requirements, setup instructions, and usage tips.

Generative AI

GenAI Search employs generative AI models to create descriptive text for the thumbnails of your tracked objects, which are stored in the Frigate database to enhance future searches. Supported providers include Google Gemini, Ollama, and OpenAI, so you can choose whether you want to send data to the cloud or use a locally hosted provider.

See the GenAI docs for setup instructions and use case suggestions.

Improved Tools for Debugging

Review Item Details Pane

A new Review Item Details pane can be viewed by clicking / tapping on the gray chip on a review item in the Review pane. This shows more information about the review item as well as thumbnails or snapshots for individual objects (if enabled). The pane also provides links to share the review item, download it, submit images to Frigate+, view object lifecycles, and more.

Object Lifecycle Pane

The Recordings Timeline from Frigate 0.13 has been improved upon and returns to 0.15 as the Object Lifecycle, viewable in the Review Details pane as well as the new Explore page. The new pane shows the significant moments during the object's lifecycle: when it was first seen, when it entered a zone, became stationary, etc. It also provides information about the object's area and size ratio to assist in configuring Frigate to tune out false positives.

Native Notifications

Frigate now supports notifications using the WebPush protocol. This allows Frigate to deliver notifications to devices that have registered to receive notifications in the Frigate settings, delivering them in a timely and secure manner. Currently, notifications will be delivered for all review items marked as alerts. More options for native notifications will be supported in the future.

See the notifications docs.

New Object Detectors

ONNX

ONNX is an open model standard which allows for a single model format that can run on different types of GPUs. The default, tensorrt, and rocm Frigate build variants include GPU support for efficient object detection via ONNX models, simplifying configuration and support more models. There are no default included ONNX models for object detection.

AMD MiGraphX

Support has been added for AMD GPUs via ROCm and MiGraphX. Currently there is no default included model for this detector.

Hailo-8

Support has been added for the Hailo8 and Hailo-8L hardware for object detection on both arm64 and amd64 platforms.

Other UI Changes

• Rework the Storage metrics pane to be more clear how much storage each camera is using
• Camera stream info button has been added to the camera metrics page allowing easy access to see camera codec information
• Add button for downloading the full set of logs
• The timeline handlebar will now automatically scroll while viewing recordings
• Review items and exports can now be shared via your browser's sharing pane or via direct link url. A secure context is required for the browser/OS sharing pane to function
• Add the ability to rename camera groups
• Add middle mouse button support in the Review pane to open full recordings view in a new tab
• Add Nvidia GPU encode and decode stats to system metrics
• New desktop keyboard shortcuts. In addition to the numerous keyboard shortcuts available with 0.14, 0.15 adds several more. In Live view, the numeric keys (1-9) will move PTZ cameras to presets. In Review, Page Up and Page Down will scroll through review items
• Accessibility updates for users with screen readers

Other Backend Changes

• FFMPEG updated to 7.0
• OpenVINO updated to 2024.3
• Use FastAPI instead of Flask for the Frigate API
• Add service manager infrastructure
• Install onevpl tools and update drivers for Intel
• If record is disabled for a camera then that camera will not save frames to the preview during that time
• Fix stalled connections to certain onvif cameras
• Fix autotracking absolute zoom interpolation logic
• TensorRT models are no longer generated by default, the ENV var must be set

---

This discussion was created from the release 0.15.0 Beta 5.

[pyrodex]

Thanks for all the hard work! I just upgraded and encountering a bug on the UI Tracked objects detail page. If you look at the bottom right the button is gone or something since it shows the event ID down there.

[hawkeye217]

It's actually a timestamp. I'll have a fix up for this shortly.

[hawkeye217]

Fixed in #15946

[pyrodex]

Tested and fixed. Thanks!

[hawkeye217]

Great! Thanks for checking it.

[bagobones]

Just updated.. Excited for this to go stable but also slightly more excited to start testing 0.16 features.

[hawkeye217]

Glad you're excited, but we're still a good while off from 0.16 :)

[thelovemyth]

Hope we have 0.15 stable soon <3

[hawkeye217]

Hope we have 0.15 stable soon <3

We do too! This is dependent on the community testing the betas and reporting any issues.

[ElectronicBattle]

A painless "docker compose" method for me. I didn't bother backing up my config nor my db - the config got translated to the new format without problem as far as I can tell and the db did lose some arbitrary entries (but that doesn't trouble me).

CPU burden might be a bit lower ... I will monitor.

I stopped and exited my 0.15 container and created a new docker compose with 0.15-1 which, as described, worked fine. But how/where did the new 0.15-1 get my full config from? I presume it's because 0.15 and 0.15-1 docker compose files state the same path for host:container.

[hawkeye217]

I presume it's because 0.15 and 0.15-1 docker compose files state the same path for host:container.

That's correct.

[ElectronicBattle]

I am getting a lot (many hundreds) of these errors, which I might have been getting in previous versions, but I don't recall seeing quite this message:

Timestamp 2025-01-12 13:01:14
Tag
ffmpeg.ponds.record
Message
[vost#0:0/copy @ 0x6400ce21ce40] Non-monotonic DTS; previous: 3081, current: 3081; changing to 3082. This may result in incorrect timestamps in the output file.

One of the cameras ("ponds") with which these messages are associated seems to be working OK, but another is not working OK and has always been a problem.

[ElectronicBattle]

also - trying to go back into the logs causes a webUI hang:

I tried twice; attempting to reload the page has also failed, resulting in the "aww, snap!" message on Chromium (Version 131.0.6778.204 (Official Build) for Linux Mint (64-bit)). Navigating back up from http://192.168.1.247:5000/logs to http://192.168.1.247:5000 seemed to do the trick - all OK now.

[NickM-27]

This is just an ffmpeg line, you'll want to look at the end for errors.

[ElectronicBattle]

This is just an ffmpeg line, you'll want to look at the end for errors.

OK - I'll look into it as a separate matter. Thanks.

[leccelecce]

All my streams have broken with:

Option bsf:v (A comma-separated list of bitstream filters) cannot be applied to input url rtsp://127.0.0.1:8554/hikcam8_resized -- you are trying to apply an input option to an output file or vice versa. Move this option before the file it belongs to.

Assume relates to @NickM-27 #15865

go2rtc config:

    hikcam8:
      - rtsp://hikcam8.local.lan:554/Streaming/Channels/101
    hikcam8_resized:
      - ffmpeg:hikcam8#video=h264#width=1920#height=1080#raw=-fpsmax 5#hardware=vaapi

Camera config:

    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/hikcam8
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/hikcam8_resized
          input_args: preset-rtsp-restream
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-copy
    live:
      stream_name: hikcam8

[NickM-27]

Ah right, it is only applicable to ffmpeg 7.0 not 5.0

[NickM-27]

fixed in #15956

[bmrowe]

Thanks for a new beta! I use Reolink cameras and was able to switch back to ffmpeg 7.0 (I was getting tons of ffmpeg errors in beta 4 without specifying v. 5.0). I do have to specify qsv264, else I get errors with vaapi (intel 13500), but it has been super stable so far.

[NickM-27]

Thanks, that's great to hear

[Polv89]

Can you tell me the right way to install it on proxmox?
I tried with debian 12 vm + docker but i have some issues
thanks

[NickM-27]

that is more or less the recommended way, I'd suggest creating a support discussion

[bagobones]

I don't know about RIGHT WAY, but here is what worked for me. With explanations.

VM Hardware

• Memory 8Gb or more, needs to have balloon DISABLED, when you do GPU pass through
• Machine type: q35 as it supports NEWER PCI pass through
• BIOS UEFI (to go with q35 hardware)
• Processor type: host (this will expose ALL CPU acceleration flags from the CPU, frigate uses many modern ones not in the templates)
• Controller VirtIO SCSI single
• Hard disks SCSI to go with the VirtIO SCSI controller (not to be confused with VirtIO disks which are no longer recommended) for lowest latency under current QEMU guidelines
• Network VirtIO (this should be the default anyway)

Pass through:

• iGPU pass through, PCI device, Raw device I located HD Graphics 630 on my host from the list (ROM-Bar should be checked by default)
• I have a USB Coral, I found USB device pass through made it VERY slow, so I used lsusb on the host to figure out which USB controller it was connected to and passed the WHOLE controller through as a RAW PCI device.

OS

I went with ubuntu-24.04.1 as it generally contains very modern drivers etc.. I chose the minimal install as docker and frigate will be the only things running other than adding the SSH server during install.. This results in only 4-5GB of disk use

Guest Agent

Don't forget to install the Qemu-guest-agent for shutdown and backup snapshot support https://pve.proxmox.com/wiki/Qemu-guest-agent also enable it on the VM settings in proxmox

Docker

I am not doing anything fancy with docker and ubuntu has a very current version in their repo so I just with with the ubuntu docker package docker.io
https://www.cherryservers.com/blog/install-docker-ubuntu

I then used docker compose to setup frigate, I made sure to first confirm the existence of the /dev/dri/renderD128 folder in my case in the ubuntu os and that the USB coral appeared under /dev/bus/usb

NOTES:

A PCI device can be only passed through to ONE VM at a time, you can't SHARE them unless you specifically have a very recent GPU that supports virtualization, there are more advanced proxmox guides for that.

Edit: Also a personal preference I made TWO virtual hard disks, one for the main OS and frigate install with DB and a second LARGER one for mapping /media/frigate to so that I could backup the main disk with snapshots easily without having a huge backup.. This is personal preference and requires extra steps of mounting and formatting the drive under linux.

Edit2: For further reference the host is using an Intel i7-7700T CPU @ 2.90GHz which I am using the integrated graphics for acceleration, exact device names for other iGPU and GPUs will differ.

[igiannakas]

Have been testing 0.15 for a while now and unfortunately FFmpeg v7 appears to be less resilient to camera stream / wifi latency hiccups/spikes compared to v5. For example see below. This is also repeated on pretty much all my cameras even though they all have good wifi coverage.

System is quite low utilisation wise (despite running 17 cameras). The detector spike is when rebooting due to the motion detection process generating a bunch of frames till it settles.

With v5 I seldomly get stream errors like the above.

Stats with V5 look very similar:

Using an intel pentium gold 8505 with 2 coral TPU's connected via USB3. Wifi delivered from a set of unifi access points with excellent reported coverage (cameras are connecting at their max speed). Cameras are Tapo C325WB's and C100's connected over Wifi and RTSP like so:

DownstairsLivingRoomSide:
  - rtsp://<<creds>>@192.168.1.61:554/stream1
  - ffmpeg:DownstairsLivingRoomSide#video=copy#audio=aac
DownstairsLivingRoomSide_sub:
  - rtsp://<<creds>>@192.168.1.61:554/stream2

[NickM-27]

Using an intel pentium gold 8505

https://www.intel.com/content/www/us/en/products/sku/226262/intel-pentium-gold-processor-8505-8m-cache-up-to-4-40-ghz/specifications.html

you should be using QSV not VAAPI with ffmpeg 7

[NickM-27]

The error's you're seeing has nothing to do with WiFi cameras

[igiannakas]

The error's you're seeing has nothing to do with WiFi cameras

Awesome thank you! Testing now.

[igiannakas]

Seems to have done the trick! thank you!