Rebuilding the Frigate UI for 0.14

[blakeblackshear]

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

• Many improvements have been made to improve the usability of the mobile UI
• Live view now displays full-resolution camera streams
• Cameras with non standard aspect ratios like panoramic and portrait fit into the UI seamlessly
• Zone / mask editor has been improved to be easier to use and makes more options fully configurable in the UI
• Tune motion detection in real-time directly in the UI

[OnFreund]

This is awesome!
The designs mention that the review screen is filtered by day, which makes the "last night" uses cases a bit tricky because they technically span 2 calendar days. Is it filtered by the current date or the last 24 hours?

[NickM-27]

by default it is the last 24 hours, or a specific day can be selected on the calendar

[OnFreund]

Perfect

[blakeblackshear]

24 hours by default, then the specific day when choosing a date which would include the morning and evening of that day. It's always easy to look at last night each morning.

[nayzm]

Amazing work! Looking forward to this. 👏🏼

[nwish]

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

[nwish]

It is somehow possible to configure one object to alert in multiple zones, while another object alerts in one zone, and only detects in another?

[NickM-27]

yes, just set which objects each zone applies to. You can configure this in the UI by editing your zone and setting which objects apply to that zone

[wjbeckett]

Yep. I currently do this.

On my driveway camera, I have alerts set to person and car, but on my front yard camera, only person alerts where other labels are marked for detection.

The alerts and detections configuration are per camera.

[nwish]

I think I phrased my question improperly. In the UI, in individual zone settings, it seems like I can only enable or disable objects for the zone, but not for alerts and detections specifically, but I'd want to accomplish the following:

Person enters ZONE 1 and then crosses into ZONE 2 - alert for both
Car enters ZONE 1 and then crosses into ZONE 2 - detection for ZONE 1, alert for ZONE 2

So I guess I'm looking for a required_zones setting on a per object basis.

[NickM-27]

you would need 3 zones to accomplish this

zone 2, required for alerts and has person and car object
zone 1_person, required for alerts and has person object
zone_1_car, required for detections and has car object

[TorgeSchmidt]

Awesome stuff, really looking forward to it!
But what do you mean by

initial revenue from Frigate+ subscriptions

?
I setup an account, uploaded labeled images, but the option to change subscription from free to 50$/y is unavailable, marked „coming soon“…
I thought Frigate+ is not ready yet, is there a hidden button or something? 😜

[NickM-27]

Frigate+ has been available for about 8 months now, you just need to email [email protected] to request access

[binarybucks]

looks very promising. Will there be a version optimized for mobile devices?

[NickM-27]

the UI has been built with both desktop and mobile views in mind

[binarybucks]

I just tried the dev build and the new interface really is a vast improvement on both the desktop and mobile.
I really appreciate that some of the Frigate+ earnings are invested into this.

The switching from static to live images on motion is a very neat trick and superbly implemented. The loading times are also so fast that they might replace my existing professional NVR altogether and the new Motion Tuner and Frigate+ Score Range filter are two really helpful details.

Overtall, very well done and a big improvement in the right direction.

The only issue I found so far is that the interface elements on the mobile version are quite small and hard to hit at the moment .

[dz4news]

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.
Quick question... as you move forward with a standalone UI and as it matures, will the integration with HomeAssistant continue?

[NickM-27]

I don't speak for the project but personally I can see the integration sensors and services progressing but I think the media browser gets replaced with a link to the frigate ui in the sidebar

[hawkeye217]

Like @NickM-27, I am only a contributor to the project so I can't speak to future goals and direction. But the new UI does not provide automation features, notifications, or sensors. Home Assistant and Frigate work very well together, and there has been no discussion to change that whatsoever.

[dz4news]

Completely understandable.. I personally find myself using the Frigate Proxy more often to review events, etc and just use HA for the alerts and quick viewing of the cameras.

[OnFreund]

FWIW my vote would be against dropping the media browser - it's really useful and is an easy way to integrate with media players in HA (e.g. cast device)

[nomonkeynodeal]

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".

[NickM-27]

frigate has supported a config editor for over a year now, this config editor checks your file validity before restarting among other benefits like lint checking and auto complete. so there really is no reason to be using nano

[NickM-27]

also, the new UI does make more things configurable directly from the UI

[hawkeye217]

Motion/object masks, motion parameters, and new camera groups can be configured from the new UI without editing the config file, but configuring every parameter from frigate exclusively from the UI is a massive development undertaking. I suspect frigate will get there eventually.

[nomonkeynodeal]

And yet somehow a user with a significantly developed homelab and over a year of Frigate experience still makes configuration errors and has trouble understanding how Frigate works. What do you attribute that to exactly? Low IQ? Moral failing?

[nwish]

What do you attribute that to exactly? Low IQ? Moral failing?

Maybe just frustration getting the best of you. We've all been there. Always be ready to poke at the logs when things go south. It also took me a while to get used to Frigate's configuration.

[nomonkeynodeal]

What do you attribute that to exactly? Low IQ? Moral failing?

Maybe just frustration getting the best of you. We've all been there. Always be ready to poke at the logs when things go south. It also took me a while to get used to Frigate's configuration.

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.

[shinyzard123]

I have to disagree, the inability to review motion footage is a big pain point for us and I have found Frigate's documentation to be better than many other projects that I have used. It does have a learning curve but after some time spent it is pretty straightforward in my opinion

[nwish]

A configuration UI would be nice, but obviously that wasn't part of the original set of goals, and has been set back in favor of high quality and accurate object detection. Also, did you know that you can copy/paste the example "full configuration" from the docs into your own file and start removing things that you aren't changing? If you're still having trouble, maybe start over by doing that.

[adamburgoyne]

It would be nice to have an "Add camera" wizard and camera config editor in the UI to be fair but now my cameras are setup I rarely need to touch the config whereas I do quite often review footage so I'm pretty excited for this. I'd say for most people the ability to view footage is likely to be more important.

[NickM-27]

yes, that will come in some future version

[shinyzard123]

This is awesome to see, we might fully drop Blue Iris when this launches if it solves all of our needs

[nomonkeynodeal]

A configuration UI would be nice, but obviously that wasn't part of the original set of goals, and has been set back in favor of high quality and accurate object detection. Also, did you know that you can copy/paste the example "full configuration" from the docs into your own file and start removing things that you aren't changing? If you're still having trouble, maybe start over by doing that.

I did that nearly two years ago.

[xconverge]

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!

[nwish]

I just pulled the dev build today as well.. any pointers from your end so far? :)

[xconverge]

Nope, seems to be running pretty well! If I experience anything strange I would politely open an issue and follow best reporting practices to not be a headache for the active developers who are managing a pretty large userbase! Running a dev build I would take on additional responsibility if you can to look into problems or just revert back to stable if something is not to your liking 🤷

[nwish]

That’s my plan. I’ve got a list 😊

[NickM-27]

We do want feedback, will help to either fix things or give ideas for things that need to be emphasized in the beta release notes

[towerhand]

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?

[towerhand]

It looks like the config migration didn't like something in my config file because frigate won't start after changing to v14.

frigate  | 2024-04-28 23:36:56.823125673  *************************************************************
frigate  | 2024-04-28 23:36:56.823128853  *************************************************************
frigate  | 2024-04-28 23:36:56.823132973  ***    Your config file is not valid!                     ***
frigate  | 2024-04-28 23:36:56.823134845  ***    Please check the docs at                           ***
frigate  | 2024-04-28 23:36:56.823136042  ***    https://docs.frigate.video/configuration/index     ***
frigate  | 2024-04-28 23:36:56.823158596  *************************************************************
frigate  | 2024-04-28 23:36:56.823159823  *************************************************************
frigate  | 2024-04-28 23:36:56.823161296  ***    Config Validation Errors                           ***
frigate  | 2024-04-28 23:36:56.823162428  *************************************************************
frigate  | 2024-04-28 23:36:56.823163394  invalid literal for int() with base 10: '0.121'
frigate  | 2024-04-28 23:36:56.823889708  Traceback (most recent call last):
frigate  | 2024-04-28 23:36:56.823891717    File "/opt/frigate/frigate/app.py", line 603, in start
frigate  | 2024-04-28 23:36:56.823892859      self.init_config()
frigate  | 2024-04-28 23:36:56.823894053    File "/opt/frigate/frigate/app.py", line 136, in init_config
frigate  | 2024-04-28 23:36:56.823895194      self.config = user_config.runtime_config(self.plus_api)
frigate  | 2024-04-28 23:36:56.823896361    File "/opt/frigate/frigate/config.py", line 1456, in runtime_config
frigate  | 2024-04-28 23:36:56.823897421      camera_config.objects.filters[object] = RuntimeFilterConfig(
frigate  | 2024-04-28 23:36:56.823898522    File "/opt/frigate/frigate/config.py", line 484, in __init__
frigate  | 2024-04-28 23:36:56.823899563      mask = get_relative_coordinates(config.get("mask"), frame_shape)
frigate  | 2024-04-28 23:36:56.823900716    File "/opt/frigate/frigate/util/config.py", line 160, in get_relative_coordinates
frigate  | 2024-04-28 23:36:56.823901616      [
frigate  | 2024-04-28 23:36:56.823902717    File "/opt/frigate/frigate/util/config.py", line 161, in <listcomp>
frigate  | 2024-04-28 23:36:56.823903869      f"{round(int(points[i]) / frame_shape[1], 3)},{round(int(points[i + 1]) / frame_shape[0], 3)}"
frigate  | 2024-04-28 23:36:56.823906012  ValueError: invalid literal for int() with base 10: '0.121'
frigate  | 2024-04-28 23:36:56.823906908  
frigate  | 2024-04-28 23:36:56.823907991  *************************************************************
frigate  | 2024-04-28 23:36:56.823927703  ***    End Config Validation Errors                       ***
frigate  | 2024-04-28 23:36:56.823928905  *************************************************************

[NickM-27]

Do you have a decimal as one of your points? Otherwise I may have just missed something when working on the conversion to relative coordinates

[towerhand]

I don't see anything, but I'll send you my config via a discord DM just in case.

[NickM-27]

Perfect

[niqu1982]

This same problem. If anybody resolve this problem please describe how. My ovinf config https://pastebin.com/dmSkGepa

2024-05-11 19:02:07.549507734 invalid literal for int() with base 10: '0.0'
2024-05-11 19:02:07.549912934 Traceback (most recent call last):
2024-05-11 19:02:07.549914580 File "/opt/frigate/frigate/app.py", line 604, in start
2024-05-11 19:02:07.549915494 self.init_config()
2024-05-11 19:02:07.549916408 File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-05-11 19:02:07.549917240 self.config = user_config.runtime_config(self.plus_api)
2024-05-11 19:02:07.549918129 File "/opt/frigate/frigate/config.py", line 1466, in runtime_config
2024-05-11 19:02:07.549918974 camera_config.objects.filters[object] = RuntimeFilterConfig(
2024-05-11 19:02:07.549919826 File "/opt/frigate/frigate/config.py", line 484, in init
2024-05-11 19:02:07.549920648 mask = get_relative_coordinates(config.get("mask"), frame_shape)
2024-05-11 19:02:07.549921544 File "/opt/frigate/frigate/util/config.py", line 162, in get_relative_coordinates
2024-05-11 19:02:07.549922241 [
2024-05-11 19:02:07.549923095 File "/opt/frigate/frigate/util/config.py", line 163, in
2024-05-11 19:02:07.549924326 f"{round(int(points[i]) / frame_shape[1], 3)},{round(int(points[i + 1]) / frame_shape[0], 3)}"
2024-05-11 19:02:07.549925190 ValueError: invalid literal for int() with base 10: '0.0'

[RichE85]

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.

[hawkeye217]

There's already a feature request. See #1074

[wjbeckett]

With the Home Assistant/MQTT Integration, will there be different events published for an "alert" as opposed to a "detection" and "motion" events?

[NickM-27]

Naturally the messages are not 1:1

[wjbeckett]

alright, trying to play around with Notifications in HA for alerts as opposed to events.
I have the text of an alert being sent based on the alert and the object that was detected, I just can't get the thumbnail or clip of the alert. It If I try to use the after ID, it tells me the object (whether it's a thumbnail or clip) doesn't exist.

Have you implemented notifications based on the alerts part of the /reviews endpoint at all?

[NickM-27]

you can not use a review ID for the event clips / snapshots. As part of the payload there is a list of detections which is the list of relevant event IDs, those can be used. Otherwise, you can use some of the new preview.gif or preview.mp4 endpoints though this will require a slight addition to the integration

[wjbeckett]

Ooh the new preview gif and MP4 files would be nice!
I assume I need to wait for the HA Integration to be updated to utilise those?

[NickM-27]

home assistant integrations are not compiled, you only need to add a few lines to make it work blakeblackshear/frigate-hass-integration#664

[Majestic7979]

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".

[NickM-27]

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.

this already exists in the recordings viewer page like it is shown in the demo

the motion viewer also supports a play button that will just play back previews of all cameras at the same time

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

as part of the new UI we have switched to a new HLS player (hls.js from video.js) so it is possible that this change will fix what you are describing. I used to have buffering when setting the playback speed to 8x or higher but with the new player I do not

[NickM-27]

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".

exporting using handles on the timeline is already implemented as well

Screen.Recording.2024-04-29.at.6.42.41.AM.mov

[NickM-27]

@Majestic7979 also one other thing to note, there is a new "loitering time" field that is added to zones. So maybe you will find that you want to use "events" (reviews) now, because you can make it an alert if a person loiters but a detection if the person just walks by. That way you get more information on the timeline of when an object was detected

[Majestic7979]

Thanks, I'm very eager to explore and see how it all works with my own footage. And I hope the development goes well :) How do I subscribe to support? Because I don't necessarily need the AI detections/models I don't subscribe to Frigate+, it would be nice to have a basic tier where I just make monthly payments to basically thank you guys for your development and customer service. It would be nice to be able to decide how much I can contribute rather than having a fixed price, that way I could vary based on an ongoing budget. While I'd like to pay for the work, some months would be less, some more, I'd rather give something rather than nothing on those months when budget is tigther.

Edit: just saw you addressing the other issues. OMG you guys are freaking amazing!!!!!!!!!!!!!!!!!!!!

[detroitgoose]

@Majestic7979 I've been super impressed with frigate+ detection. Even the base model is leaps and bounds more confident that the yolo model. A huge benefit is that you are given 12 "trainings" that allow you to tweak your model to your specific environment, and at the same time upgrade to newly released base models.

You also don't need to keep your subscription active (although it needs to be active to train new models / upgrade to new base models.) Even after you deactivate your subscription, you can still use the superior + models!

All that said, I'm really desperately waiting for improvements to the training process, but it still works ok. My issue is mostly with the difficultly in going back over images you've already trained and tweaking them. It's very clumsy at the moment, but I it'll get better.

Just giving a recommendation as someone who was very weary of "if it's worth it," and sharing personal camera images that could eventually be used in the base model. I've gotten over it. It's been pretty incredible. (the "free" models are trained on images that are far different than what a security camera sees. By crowd sourcing actual camera images, it's made a far more accurate model.)

[szaman-89]

In frigate's home assistant addon 0.14 beta1 there's 404 Page not found view after entering ui interface:

[szaman-89]

Thanks, still learning in 0.14 version.

[hawkeye217]

The release notes and guided demo of the new UI have all the exciting details!

[szaman-89]

Definietly will check new docs and others.

[DrSpaldo]

I got the same thing with the proxy addon as well.

[jmtatsch]

Guided demo is really insightful. I learned a lot.

[banthungprong]

Thanks for the quick demo. Very nice!

[banthungprong]

Reolink Cameras:
Recommended settings (FLV-Stream) do not work for E1 Pro and other cameras.
https://support.reolink.com/hc/en-us/articles/28256840140441-Introduction-to-FLV-Stream/

This article introduces the FLV stream on Reolink devices.
Applies to: All Reolink NVRs and cameras except add-on cameras in the NVR kits, all battery-powered cameras, cameras with hardware version IPC_3816, E1, E1 Pro, Lumus.

[jokakilla]

I just want to say thanks for all the effort. I'm just testing the 0.14 beta. Maybe I just missed some hint or am just blind but is the timelapse feature on the export gone?

[blakeblackshear]

It's not in the UI, but the API is still available. Most users were using that feature to create videos to manually review each day. One of the main focuses of the new UI was to ensure that isn't necessary. The only remaining use cases we are aware of are for very long periods of time. Having frigate do long exports on high resolution recordings on the server is a really inefficient way to accomplish that.

Can I ask what you were using that feature for?

[jokakilla]

Understood. It's not that crucial to me but was handy sometimes.
From time to time animals stray around for an hour or two on my cameras. No one will watch a two hour video of that but having a timelapse video was nice.

[pyrodex]

I have one camera that is a LARGE format, DS-2CD2387G2P-LSU/SL, and in 0.13 I could only view it live on Frigate UI by toggling to JSMPEG but that option is gone in B1. Is this going to be the way forward and if so what should I do so I can view live in this camera? I don't have the UI forced in the config to make all LIVE jsmpeg and frankly that is a crutch but not sure how to fix this for JUST this camera and not impact others working with MSE/WEBRTC.

Is there plans to use Cookies or something to keep web UI preferences stuck? I am not using the AUTH module yet since I have it behind Authelia but didn't know if those settings were going to be stored for users via the DB or via cookies.

Also in .13 the links to GH or Docs opened a new tab, can that be restored in .14?

Thanks!

[NickM-27]

What do you mean by large format? It's not clear to me what you mean or why mse / WebRTC wouldn't work.

Also the option you're using to set live mode can be set at the camera level

[pyrodex]

What do you mean by large format? It's not clear to me what you mean or why mse / WebRTC wouldn't work.

Also the option you're using to set live mode can be set at the camera level

The camera is 5120x1440.

I tried in the camera itself using this but it threw an error in the saving of the configurations so it wasn't part of the schema.

camera:
  Playroom: # Kiddo's room
    ui:
      order: 10
      live_mode: jsmpeg

How can I set just this camera to jsmpeg? I am viewing the UI in Safari on MAC but when I try it with Chrome it works. I also tried Firefox on MAC and it shows the Outline where the video would be but it's a grey square.

[NickM-27]

Okay turns out I have the exact camera you have, it works perfectly for me in the new UI. I'd suggest using the sub stream for live view not the main stream as that's a lot of data and the sub stream works great for me.

[NickM-27]

The main stream is h265 that's why it's not working for you in other browsers

[pyrodex]

The main stream is h265 that's why it's not working for you in other browsers

That worked. I wish I could force Safari to be Chrome on the frigate website but that is another issue.

[Mincka]

I don't find how to filter by zone in this version when I review events. I don't want to use alerts for that.
I just want to be able to select a zone and an object type and see all the matching events. Is it possible?

[Mincka]

What's the purpose of the "Motion only" toggle in Review page / Motion tab?

Some of the cameras get a yellow border (while the toggle is red), but I don't see any difference between ones with yellow borders and the others. I mean, there's no event, or detection (at least, not that I can see) in any of them.

Also, not sure if it's a bug, but the ticks in the timeline disappear when this toggle is on.

[hawkeye217]

This view is called "Motion review". From the release notes:

In Frigate 0.13, 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 the Review section, 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 also scrub in motion only mode.

In motion-only mode, the timeline collapses and the tick marks are not relevant. Move the handlebar and you'll notice the time change inconsistently.

[blakeblackshear]

I mean, there's no event, or detection (at least, not that I can see) in any of them

If Frigate is working perfectly and has zero false negatives, this is exactly what you would expect. The point of this mode is to look for things that Frigate's object detection missed.

[Mincka]

Ok, thank you for the explanations. I found the toggle confusing, but if I've understood properly it means "Show only motion events without object detections".

[blakeblackshear]

That's exactly what it does. It shows only periods of time when there aren't object detections.

[rajil]

Is there any way to delete events?

[NickM-27]

Right click (or long tap on mobile) then delete

[Mincka]

Hard to discover. Maybe it would be great to have access to the delete button while looking at an event.
If buttons at the top right are not related to this specific event, maybe directly in the toolbar of the event.

[hawkeye217]

The icons at the top change when you right click/long tap review items. You can select multiple and one of the buttons is "delete".

[Mincka]

Would it be possible to add buttons to jump to the next or previous event in the toolbar of the player?

On mobile, while we play an event, we cannot see the thumbnails of the other events, we only see the timeline.
In that case, having |< >| buttons would be nice to skip directly to the adjacent events.

[NickM-27]

On mobile just use the events toggle to see a list of events instead of the timeline

[Mincka]

What do you mean? I meant when an event is playing, I'd like to skip to the previous or next one.

[NickM-27]

right so tap the flag, choose events, and then you have a list of events that you can jump between easily

[Mincka]

Oh ok, never thought it would be hidden behind that icon, thanks. It comes right with my next proposal.

[Mincka]

It could be nice to have the date visible on the timeline, especially when scrolling before midnight of the current date.
I'm thinking to a sticky date label at the top of the timeline, each time the day changes.

[OnFreund]

I know I already mentioned this aboce, but looking at some of the feedback points by others, I think many of them stem from the disconnect between the various screens. When I click on a review activity, I get to the recordings screen at the right point in time, but I've lose any connection to the activity. I can't export it, delete it, see any info about it (other than its duration in the timeline, which is hidden by the playhead), or navigate to other activities. And If I click "back", the activity is hidden by default.
Same goes for the Frigate+ screen - I'd like to get from an activity to the Frigate+ snapshots for it, and get from a snapshot to the relevant recording.
I love each one of the new screens in isolation, but they could really gain from a tighter integration. It will make back navigation harder to get right, but the benefits should really outweigh this.

[NickM-27]

This is intentional, the frigate+ screen is meant for submitting to frigate+ not for reviewing your cameras. It is designed for that goal alone.

Personally, I find the new review flow has much more connection to the activity. I can see the event on all of the relevant cameras at the same time and easily switch between them as well as seeing the timeline and how long that activity lasted. I can understand wanting a review item to be there still in case it is decided that it needs to be exported or something but in general I think some users will just need time to get used to the new UI more.

[OnFreund]

I understand the motivation, but I think there's a bit of overfitting to the maintainers' experience here (I say this with utmost respect - I love what you guys are doing).
Let's tackle all of these:

1. Connection from activity to F+: I see an activity which is a result of a false positive, and then I have to go to a separate screen and look for it. This also increases my mental load and the stack I need to unwind.
2. The opposite direction: the recording can really help me understand what's going on in the snapshot. Yes, I know the model only has access to the snapshot, but my resolution and contrast have different limits than the model's, and the recording can help me.
3. Connection from the recording to the activity: I think this one is pretty clear - there are a lot of questions here stemming directly from that disconnection.

[NickM-27]

Thanks for the feedback, I think it is expected as a paradigm shift that users will take time to get used to the new flow. But I don't think just because a certain way is familiar means it is better necessarily. We will continue to take in feedback and see how things progress.

[OnFreund]

Thanks. Just to be clear - this isn't about the paradigm shift, which I love. My feedback is geared towards what I think would make the new paradigm better, regardless of the past.

[Mincka]

Maybe a stupid request but I think it would be useful to just show the name of the camera at the top.

Also, it would be nice to implement SPA navigation for review, not only live.
This exists -> http://10.0.0.84:5000/#Garden
This does not exists -> http://10.0.0.84:5000/#Frigate_Buanderie

[NickM-27]

Genuinely trying to understand why, do you not know which camera is which? Most cameras also support adding the name to the camera itself, I personally have never felt that I needed a reminder of the name of the camera I am looking at.

Also the navigation is more complicated because you usually want to look at a specific point in time for a given camera.

[Mincka]

That's because I thought it would help for the navigation context and it was unclear what the buttons on the right were associated to.
I think it would help to "link" the buttons with the camera to understand that you'll export the content of THIS camera, show "ITS" events.

In other cases, imagine you use Frigate to monitor cameras for different floors of a building, or multiple lifts, you'd be happy to see clearly the name of the camera (since it's also not available in the URL, cf. my other thread).

[NickM-27]

I would expect in those cases the cameras have the names as an overlay on the recordings themselves, and I think in general that would be the recommendation since the majority of cameras support that

[Mincka]

Ok, that's your opinion but I still feel like a regression from an accessibility point of view.
I don't use the name overlay in my camera because the name was shown in the interface before.
I don't add it because it's useless in the recording and interfere with the detection (or you need to mask it so you lose detection area).

[Mincka]

Maybe an unpopular opinion, but as much as I find the timeline nice looking, I think the default view for the navigation for desktop and mobile should be the events.

It's closer to the 0.13 experience that allows quickly browsing the events while you're reviewing the content of a specific camera.

On mobile, the timeline as the default navigation while playing an event feels like a big waste of space, that's hard to browse, while the events are more useful (in my mind). In the Reolink mobile app, the thumbnails are shown with the timeline below, best of both worlds.

To me, timeline feels more like a tool to compensate for people having a lacking object detection. Scrobbling is fun and feels like a little timelapse, but you miss too much frames during the actual events to use it like this. Clicking on yellow bars is useless 99% of the time. At least if motion boxes could be shown on the recording, it would useful to understand what you need to look at for suspicious activity.

0.14 has a strong focus on events with alerts and detections, that's why it would be best to keep the events as default navigation for the history.

[NickM-27]

we have gotten feedback from early testers that the timeline is quite useful even with object detection, especially when following an object that is moving between cameras because you can scrub and see where they went to and if any suspicious activity occurred. The idea is that you would use the main review screen, see something that needs to be investigated further and open that closer view to investigate what the object did.

In any case thanks for the feedback, we will continue to take in feedback and see how things progress.

[Mincka]

What you're saying may make sense on desktop but not on mobile where other cameras are not shown during scrobbling.

On desktop, the best would be to see the thumbnails of the events along (or in) the timeline.

[blakeblackshear]

Having been using the new UI for a couple months now, I very rarely even go to this view at all to see the full resolution recordings. The overwhelming majority of the time, I get what I need on the review page.

[Mincka]

I guess the review page would be perfect if it had the old zone filter.
We need the zone filter on this page and on the history page of the cameras.

[tensor5g]

I don't know if this has been mentioned yet, but I noticed in the new UI that the camera live feeds are slightly cropped. Is there any way to turn this off? One of my widescreen cameras is getting probably 25%+ cut off. If I screw with the css in dev tools I can see the whole feed.

EDIT: Seems like this is only present on live view, history view shows the whole frame

[NickM-27]

Is this on the all cameras page or a camera group page?

[tensor5g]

all camera page shows full frame. Selecting the specific camera gives the crop.

[NickM-27]

CC @hawkeye217

[hawkeye217]

Can you open a separate support request discussion? It'd be helpful to see your config.

[hawkeye217]

I put up a PR (#11545) that's been merged into dev that may solve your issue.

[pyrodex]

Once again sorry if this was asked and/or answered before but Github makes it impossible to go straight to a search discussion post...

For labels from Frigate+ there seems to be a disconnect from the UI and the configuration file in displaying when it comes to the Mask and Zone editor. Here is my configuration for the Driveway:

cameras:
  Driveway: # Driveway
    live:
      stream_name: driveway
    snapshots:
      required_zones:
        - Front_Yard
    ui:
      order: 1
    birdseye:
      order: 1
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/driveway
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/driveway_sub
          roles:
            - detect
    detect:
      width: 1920
      height: 1080
      enabled: true
      fps: 10
    objects:
      track:
        - person
        - car
        - face
        - package
        - amazon
        - fedex
        - ups
        - license_plate
        - dog
    motion:
      mask:
        - 0.703,0.095,0.704,0.022,0.969,0.03,0.97,0.09
        - 0.741,0,1,0,1,0.276,0.739,0.146,0.503,0.115,0.186,0.134,0,0.254,0,0.171,0,0
    zones:
      Front_Yard:
        coordinates:
          1,1,0.942,0.338,0.862,0.214,0.649,0.143,0.393,0.128,0.309,0.142,0.23,0.139,0,0.352,0,1
        objects:
          - person
          - car
          - face
          - package
          - amazon
          - fedex
          - ups
          - license_plate
          - dog
        inertia: 3
      Street:
        coordinates:
          0.181,0.132,0.358,0.105,0.596,0.099,0.753,0.13,0.904,0.206,1,0.28,1,0,0.276,0,0,0,0,0.283,0.095,0.21
        inertia: 3
        objects: person
    review:
      alerts:
        required_zones: Front_Yard
      detections:
        required_zones: Street

But in the Mask and Zone editor for that Front_Yard zone you can see it doesn't show all the tracked objects per the configuration:

Are they just hidden for now or no plans to expose those?

[blakeblackshear]

Those are the only primary labels that result in events in your list. Fedex, UPS, Amazon, license plate and face are all secondary labels. You won't see the others listed there for the same reason you didn't get face events in 0.13.