Rebuilding the Frigate UI for 0.14 #11136
Replies: 86 comments 367 replies
-
This is awesome! |
Beta Was this translation helpful? Give feedback.
-
Amazing work! Looking forward to this. 👏🏼 |
Beta Was this translation helpful? Give feedback.
-
Oh man, I can't wait to jump on that beta! I'm excited about the alerts function and scrubbing!! Outstanding work guys! Edit: When you say you plan to release the beta soon... you mean like in a few hours, right? lol |
Beta Was this translation helpful? Give feedback.
-
Awesome stuff, really looking forward to it!
? |
Beta Was this translation helpful? Give feedback.
-
looks very promising. Will there be a version optimized for mobile devices? |
Beta Was this translation helpful? Give feedback.
-
Looks very impressive and looking forward to the beta. It looks like your revenue from Frigate+ was well spent and I will gladly support you with this effort... I am one of those that completely dumped my proprietary NVR system and adopted Frigate. |
Beta Was this translation helpful? Give feedback.
-
When I saw the title I thought "oh they are finally making it possible for non-experts to configure Frigate. Maybe I will never have to type 'nano config.yml' again because I entered one wrong character and now Frigate won't start". |
Beta Was this translation helpful? Give feedback.
-
No, the answer is obviously that Frigate is difficult to configure properly and not well documented. Let me be clear that this is NOT a complaint. I'm just stating my opinion that a camera viewing GUI is low-priority compared to a configuration UI. That's it. |
Beta Was this translation helpful? Give feedback.
-
This is awesome to see, we might fully drop Blue Iris when this launches if it solves all of our needs |
Beta Was this translation helpful? Give feedback.
-
I did that nearly two years ago. |
Beta Was this translation helpful? Give feedback.
-
I have been checking in on progress/using a dev build every few weeks the past few weeks and I was always wondering/waiting for the Debug view for the camera I just started using the latest dev build and wow, you guys have done a great job! I was blind and missing the Settings page and it is really great! Nice work, especially @hawkeye217 and @NickM-27, I know you guys have been busy! |
Beta Was this translation helpful? Give feedback.
-
Great job. That looks amazing so far. Are there any configuration changes that need to be made before switching from v0.13 to 0.14 dev? |
Beta Was this translation helpful? Give feedback.
-
This looks awesome. I would like to see a password protected UI just to keep people from casually getting into the config or camera feed. |
Beta Was this translation helpful? Give feedback.
-
With the Home Assistant/MQTT Integration, will there be different events published for an "alert" as opposed to a "detection" and "motion" events? |
Beta Was this translation helpful? Give feedback.
-
Firstly thanks so much for being constantly active here and listening to your needs. I guess I will have to eat the dog shit like I promised! lol. One thing: I absolutely love that I can scroll through the timeline and see all the events from all the cameras in sync. But what I really, really need (since I don't use events) is a timeline with a playhead where I can set the playhead at a specific place on the timeline and ALL the cameras will sync up to that specific point, then I want to press Play All and see all the cameras play in sync together. Please please please please I beg you to implement this. As I explained in a previous post, I live in Europe and it's very common to live in townhouses where your doorstep is level with the sidewalk and just have a meter of distance between your front porch and the sidewalk, with people walking by the detections are moot because an urban neighborhood of townhouses will see hundreds of people walking past the door every day just to go to work etc. So as you can imagine, in situations like that when the timeline is saturated with motion events that are merely people walking past the camera, it becomes totally irrelevant and the relevancy is more about being able to quickly play all sources in sync and without stuttering. One thing I suffer with is the stuttering when the player moves from one 10s segment to another. Every time it moves from segment A to segment B to segment C and so on, I get a half-second stutter. The more you increase the playback scale, the more stuttering. It's like a buffering effect. And if you play at 16x kiss bye bye to your sanity! As you will see is incessant stuttering as the player cannot move to the next segment seamlessly. Please for the love of almighty Jesus Christ address this major issue. It's during playback/review that any NVR shines... All NVRs can record, indeed my cameras will happily let me throw all the raw footage into a simple NFS mount. But it is the reviewing itself to find the crucial moments that makes a NVR special. I know you guys focus on detections but seriously your NVR can't be touched in terms of development speed and I sincerely hope you listen to my plight and do it 🙏🏻 God bless. PS. I was just thinking I forgot to mention how exporting easily is equally as important as finding the relevant event in question. Currently I have to use dropdowns to select camera, whether it's live or a timelapse, and then use date/time fields. I wish I could quickly use a timeline to set in/out points just like I can do in a video editing app... put the start handle at the beginning of where I want to export and the finish handle at the end of my export, then select cameras with checkboxes, click "export" and job done, the visual timeline would help a lot. But for those who want to still be exact please include a button to "enter date and time". |
Beta Was this translation helpful? Give feedback.
-
Been trialling the new ui as well and like it so far however I'm totally missing birdseye now has it been removed or is it hidden somewhere? Lastly is there any way to change the grid in "live view" I have 4 cameras and to utilise all space it would make more sense to grid them 2x2 instead of just 4 in a row? Thanks |
Beta Was this translation helpful? Give feedback.
-
Loving the direction with 14 so far, pan and zoom is amazing. Quite a lot of things I miss but this isn't about that, just some quick things on the links to other cameras in the history playback. Is there a plan for 'no preview found' to be less animated? I have 3 disabled cameras and it's a bit attention pulling. And then I have this camera at 2560x1920 that seems to be causing some layout issue with the previews and they just flicker horrendously: (looks like it might be to do with .items-center class being added and removed) |
Beta Was this translation helpful? Give feedback.
-
Situation: I'm starting from Live view. I click one of the 5 cameras. I enter the big Live view for that camera. I click the History button to open the timeline. I expect that when I click the timeline the video will load to that moment in time almost instantly and start playing, but it takes ages to load with a spinning cursor, it almost feels like a VCR waiting seeking the right spot on the tape. Why so slow to load if it's local!? Curious if it might be my system... I run a 13th gen Core i5 13500 with 32GB DDR5 and a WD Purple HDD that Nick recommended. PS. doing fast playback is also not working. For example 8X... |
Beta Was this translation helpful? Give feedback.
-
Using dev-a70dd02 the UI has become weird in firefox (linux desktop). The webcam area has shrunk and an iframe like bar has appeared at the bottom after clicking a thumbnail. |
Beta Was this translation helpful? Give feedback.
-
If you are not doing any tests over WAN (vpn or cellphone network), strongly suggest to do that. You may find UI issues which dont appear on the local LAN. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
This is very exciting and I want try out 0.14 but I'm running into a config issue. Could someone take a look and see what I'm doing wrong. Thanks. Here is the error message I receive:
and here is my config
|
Beta Was this translation helpful? Give feedback.
-
Auth working, very nice. I was expecting to have to confirm a password. No problem but might surprise users because it is the normal way setting passwords |
Beta Was this translation helpful? Give feedback.
-
Can we pass basic auth credentials via URL to pre-auth when accessing a url, say from a notification? |
Beta Was this translation helpful? Give feedback.
-
I pulled down |
Beta Was this translation helpful? Give feedback.
-
I have a strange behavior that seems to have started with the last couple of dev updates. I am currently running the latest. It seems like when one of the cameras has a positive alert or detection, they all deactivate detect, record, snapshots and audio. I have not figured out exactly what causes it, but I noticed my detections have gone down significantly over the past few days and it was become everything was off. Is there a new setting I am not aware of? |
Beta Was this translation helpful? Give feedback.
-
if i set auth mode to proxy but don't actually have any upstream auth is that effectively the same as disabling auth? I ask because my frigate instance isn't publicly available and I dont want to deal with being presented a login page to access--whether thats from Frigate itself or upstream |
Beta Was this translation helpful? Give feedback.
-
just wondering for curiosity sake, i remember you all talking about 0.13 focusing on improving motion/object detection, then 0.14 being UI focused, any info your willing to share on big picture things for 0.15? |
Beta Was this translation helpful? Give feedback.
-
Is there a rough time line for when you expect to be in beta? I've been tinkering with 0.13 but would prefer to wait for 0.14 to dive all in and sunset my current dvr. |
Beta Was this translation helpful? Give feedback.
-
I may be wrong but I thought that a few builds ago we had CPU and temperature stats in the system stats page but this seems to be gone!? Can we please have this again. It helped me identify issues with my CPU decoding so I purchased a Coral for detection and want to see if it has made a difference. |
Beta Was this translation helpful? Give feedback.
-
TLDR: We have completely overhauled the UI for Frigate to focus on specific common user goals. It’s a big change and we hope you love it. This is just where we started, and the new UI isn’t entirely at feature parity with the current release yet.
Updated Documentation
Guided Demo of new UI
We plan to release the first beta soon.
Background
Frigate started as a stateless object detection pipeline for live video fees with information relayed over MQTT to be used in Home Assistant. Initially, I had no intention of building a UI for it. HomeAssistant was the UI. After a few years of releases in January 2021, a community contribution with a basic web UI was made as a part of version 0.8.0. Since then, the UI has always been treated as a basic interface to expose some of the backend information that Frigate was using to detect and track objects. As new features like clips and recordings were added the UI was updated to provide an interface to view them.
A new approach
As Frigate has become more mature, it has evolved from a real time object detection pipeline into an NVR. While it still lacks some of the customization and features from NVR solutions that have existed for longer, many users are migrating from those platforms and using Frigate as their primary NVR solution. However, Frigate’s UI was never designed around specific user goals, nor was any real thought put into the efficiency of accomplishing common tasks.
Frigate+ was created in part to help fund the future development of Frigate. While still in the early phases, the initial revenue from Frigate+ subscriptions created an opportunity to hire outside resources for revamping Frigate’s UI. After looking at various options, I decided to hire Jim Designs.
The Goals
I wanted to design the new UI around specific user goals with the intent to have a UI that allows accomplishing those goals as quickly and efficiently as possible. The following goals are where we started. I expect we will continue to find better ways of accomplishing these goals in the future as well as incorporate additional goals.
What is happening right now and/or what just happened?
The first use case centers around the need to quickly see what is happening or what just happened. Imagine you hear a sound outside, your dog barks, or the doorbell rings and you want to quickly be able to see your cameras.
The new home page for Frigate is intended to be a real time dashboard for your cameras. Recent alerts are represented by animated thumbnails in a filmstrip view above your camera feeds. Your camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras seamlessly switch to a live stream. In addition, camera groups have been added so you can quickly switch between indoor and outdoor cameras.
Selecting a camera takes you to a new live view where the scroll wheel can be used to zoom in and out.
What happened last night (or the past 24 hours)?
A common use case for security cameras is reviewing last night’s footage for any concerning activity. The first step of that process is checking to see what Frigate detected. In the current UI, this is accomplished by scrolling through your events. Because events are simply low level tracked objects, their time ranges may overlap or still be in progress. This makes it difficult to review a timeline of video without jumping around or watching the same section of video multiple times. If a person walks by with their dog and a car drives by at the same time, you will end up with 3 separate events all with overlapping time ranges. It is difficult to reason about what periods of time you have and haven’t reviewed.
In order to switch to a more timeline oriented review process, we implemented a new area of the app for reviewing video footage. When reviewing, Frigate intelligently identifies parts of your timeline for review by leveraging the underlying data about motion and tracked objects. These time periods are mutually exclusive, so once you have reviewed a portion of the timeline for a camera, it is marked as reviewed.
The other primary focus was on efficiency. We wanted users to be able to review these segments as efficiently as possible. Rather than scrolling through a timeline and trying to align a single point with an indication of activity, we implemented a scrollable grid of thumbnails alongside a timeline. Hovering (or swiping on mobile) over the thumbnails will start a preview playback for the segment inline. You can also grab the progress bar to scrub through the segment.
After watching a segment, it is marked as reviewed.
Lastly, not all segments are created equal. Video of people who enter your property are a different priority than those walking by on the sidewalk. By default, all person and car objects are considered alerts. You can refine what ends up in the alert tab by configuring required zones for your events.
Was anything missed last night?
In the current release, there isn’t a way to see motion activity on a timeline and watch video at that time. The ability to scrub video for things Frigate missed has been one of the most common feature requests.
Within the Motion tab of review, you can now scrub through the timeline for all cameras simultaneously with a timeline showing relative motion activity.
In order to avoid scrubbing over time periods already included in alerts and detections, you can scrub in motion only mode.
Other Notable Improvements
Beta Was this translation helpful? Give feedback.
All reactions