double-take VS core

# Learn more at https://github.com/jakowenko/double-take/#configuration

I looked at Double Take (UI that lets you do the training of your face recondition easily) and found CompreFace as one of models they support. It looks like what I need but there is a catch... no OpenVino (intel CPUs AI accelerator) support. I really like my low power NVR setup and would like keep it that way. Running AI on CPU without acceleration is both power inefficient and much slower. I have a spare low end GPU but if dump it in the system the current AI acceleration brakes... (I know I can prob fix it but that is a rabbit hole I would prefer to avoid).

CompreFace can be used "in addition" via Double-Take but that is additional detection based on frigate object events.

Not OP, but I _love_ talking about this stuff, so you're stuck with me. :D

I'm a big fan of this project:

https://frigate.video/

It's open source, and you can hook it up to a Coral (or some other things, I think) to get crazy-fast classifications. But CPU is fine for only a few cameras.

Once you get something like that setup, it's just a matter of finding cameras that support RTSP. You get them setup however you like (but preferably wired, with PoE), point Frigate at the RTSP stream, and that's it. Now you've got home security footage that never leaves your house. You can set up a VPN to watch the feeds from elsewhere. Frigate supports MQTT as well, so you can hook it into Home Assistant to get notifications, and even pipe person events into something like Double Take to get face detection:

https://github.com/jakowenko/double-take

have you checked out double take?

I purchased this device off eBay the week of July 4th, and willingly paid scalper prices with the idea that I'd spend much of that week learning Frigate, double-take, and DeepStack; turns out, I had the ML-powered facial recognition, alerts and Home Assistant automations up and running in an hour.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }

The tooling is not entirely open or freely available.

If you, for e.g., want to debug you have to use MS tooling.[0] You also can't use VSCodium because only the MS built/distributed version of VSCode contains the necessary proprietary binary blobs necessary to debug C# (which also means you're forced to using the aggressive telemetry and other data collection built into the non-open source distribution of VSCode).

They've also taken steps to lock down the LSP support for C#, which once again requires that you use a MS sanctioned code editor to write C#. [1]

I really enjoy writing C# and think dotnet is a great platform to develop for, but the barriers preventing me from building more projects on it is that I don't want to be forced to use VSCode or Visual Studio.

[0] https://github.com/dotnet/core/issues/505

Microsoft does not adapt their new products to operating systems (https://github.com/dotnet/core/issues/7556) which have reached End-of-Support status. Therefore, the game's system requirements have changed:

Thanks to .Net core