I think you mean an Intel CPU for transcoding. Pretty much every piece of software can use QuickSync for hwaccel. My Celeron NAS can handle 3 simultaneous Plex transcodes as well as a 5-camera Frigate setup without breaking a sweat.
To OP - if you want energy efficiency AND ML, you will want pre-baked models that can be used on an edge compute device like Google Coral.
With the removal of the Tidal API from Plexamp, I will be sorely missing my discovery recommendations. Will need to give this a shot using Last.fm scrobbling (already supported in Plex).
Welcome to the existentialist crew! It's a great and humbling place to be.
Great game made by some devs who used to work at Halfbrick (Fruit Ninja/Jetpack Joyride fame). Highly recommend playing with an actual DJ turntable for the full fantasy. Also had a recently released VR mode.
On top of all that, https://spinsha.re/
Another vote for Synology here. I previously had a DS418play for almost 8 years. Just picked up a DS423+ recently to upgrade and the process was literally as simple as removing the drives from the old NAS, chucking them in the new NAS, and booting up. All my Docker containers, all my credentials, all my licenses were all just there and working, despite being in a new shell.
Also want to call out the importance of 4-bay vs. 2-bay. With 2-bay you get 1-drive fault tolerance in RAID mode, which is nice. With 4-bay, you can still opt for 1-drive fault tolerance and with SHR you can have 4 drives active (of varying sizes) giving you much more available space and making the upgrade path of storage significantly easier.
Just reporting back that I did the work last night to change the ingestion order for my cameras. I'm now using the go2rtc component of frigate as the first ingestion point. That component is serving a restream to both Frigate and my NAS' NVR. It's working much better now, with less frame delay, and less CPU usage on the NAS.
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.
This is exactly what I do. Record at 15FPS, event detection at 5FPS (at quarter resolution too).
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.
Would love some more photos. I'm likely going to build similar specs in that case when the 50xx range release.