• 1 Post
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle


  • I’m not sure that I would need this very much. I’m mostly interested in a sort of ephemeral surveilance system; I only really need to store, at most, a few days, and then rewrite over it all.

    This is exactly what I do. I simply cloud backup any event/object clips but only retain last 5 days. The cloud is if law enforcement needs it, or in the event of hardware failure/catastrophic house damage.

    What tweaking do you generally need to do for the camera server?

    Recording schedules change based on time of day/when we’re in/out of the house. This is all handled as automations through Home Assistant, but is set up through Surveillance Station NVR.




  • That’s quite a few cameras. I would do an audit on how many you will actually need first, because you will likely find you could get by with 5-10.

    In terms of what you’ll need - any Intel chip that supports QuickSync will likely do for the main ffmpeg processing of the image, but you will definitely want a Google Coral TPU. If you do end up needing 10-15 cameras, you may end up needing the M2 with dual TPU version of the Coral. You will also want some form of reliable storage for your clips (NAS local or NFS), as well as the ability to back up those clips/shots to the cloud somewhere.

    I’m personally running 4 cameras (3x1080 @ 15fps, 1x4k @ 25fps) through my ~7 year old Synology DS418play NAS using Surveillance Station as the first ingestion point, then restreaming from there to Frigate. Now that Surveillance Station can accept external events via webhook, I may look to swap the direction, and ingest into Frigate first, then restream out to Surveillance Station for long-term storage.

    “Why not directly use Frigate?” I hear you ask. Mostly because Frigate is pretty static. It’s all set up via YAML with no config UI currently, whereas I can tweak stuff on Surveillance Station quite easily.


  • I think that one of the most disappointing things about D4 is that it actively punishes you for wanting to try new things via high respec costs and gearing/aspect requirements. This is especially true at end game because there is no “Refund All” for paragon boards. Hence why (accurate) build guides are so important.

    Another thing that makes theorycrafting difficult yourself is that due to all skills being %age based, it’s much harder to plan out the math behind a build.

    Finally, while it’s relatively easy to try out different builds while you’re leveling, the landscape of what is viable when you hit WT3/WT4 completely changes as Glyphs start generating more of your DPS/survivability than the skills in your previous build, which dramatically changes what your build may look like. This change at end-game is great for variety (leveling builds are different to end-game builds), but due to the aforementioned way that D4 punishes you for wanting to try new things, it makes it pretty difficult in WT4+ to play anything but the “meta” builds.

    All that being said, the Dev update tomorrow mentioned that they’ll be going over Season 1 details as well as a bunch of QoL changes that are upcoming. So my fingers are crossed for at least a “Refund all” for paragon boards, if not multiple “Spec”/Armory slots.