Drathro

Why would I recommend Fileflows? It was a little more user friendly in my experience without requiring pulling in configurations from other sources. I know there are repos chalk full of Tdarr settings and configs, but for simple setups and DIY I preferred the Fileflows interface. The end result is basically the same, so pick your poison.

Isn't AMD's HEVC/265 still decent, specifically? I feel like I read that somewhere years back. 264 has always been a weak spot for them, however.

Isn't this almost the inverse argument to the android vs iPhone thing? Like the iPhone being (traditionally) more expensive for the "same technology from 5 years ago"? I don't really have a horse in this race, I'm a firm believer in use what you like and is easiest/best for you. But I do feel compelled to call this one out a bit.

I might recommend fileflows over tdarr- but either way some kind of similar solution is almost mandatory with the grab bag of arbitrary encodings you find out there.

Atomic OS's (especially Fedora based) with Nvidia are going to be a bit of a pain. Did you follow all the instructions found Here ? I personally gave up on silverblue/kinoite after I tried Bazzite. Similar bases, but the Bazzite devs paid special attention to GPU and accessory drivers/implementations that are otherwise much more painful in Fedora Atomics. You can always do a clean rebase then re-run the steps above (only the OSTree section).

Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That's going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn't break the golden rule. Until Linux gets more market share the latter isn't likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I'd also consider that a step closer in the "it just works" department.

Xbox controllers (Xbox One and newer) have been absolutely solid for me with the xone driver + xpadneo, regardless of distro. Bazzite has everything I need baked in, so it was completely plug and play. Not a very interesting answer, I know. But it still blows me away that it "just works."

Very true. But brute force checking through tons of different settings for each camera you need to configure is not fun. I couldn't seem to find any kind of "known working configs" database or anything either. Every camera seems to be different in what it expects, outputs, authenticates, etc. Once it's set up, I agree, maintaining the config is easier. Having all your cameras match in model and firmware version probably makes the whole endeavor MUCH easier.

AmCrest and Frigate together are SO good. Integrating Frigate with Home Assistant was also insanely easy for quick viewing and notifications. That initial Frigate config is a bit of a bear- but once you're past that I cannot speak more highly of it.

hunter2

Alright, where's my replacement once my current Fitbit dies? What company makes a watch that tracks steps, heart rate, sleep, spO2, notifications, is generally water resistant (light swimming) and has a battery that lasts ~5+ days? Bonus points for open firmware/hardware that doesn't require me to design my own apps/systems for each of those items. I don't even use most of what my Versa 3 can do, but I know it won't last forever and I'd at least like an idea of where to go if/when it breaks down.

Proton experimental and (at least as of yesterday) I had to opt into bleeding edge beta as well or I'd just get black screen at launch.