Or just get into CB radio. You can get a unit for like $100. No license required, and it makes road trips much more interesting, because it’s still used by a lot of truckers. Channel 17 for north/south travel, and 19 for east/west.
Or just get into CB radio. You can get a unit for like $100. No license required, and it makes road trips much more interesting, because it’s still used by a lot of truckers. Channel 17 for north/south travel, and 19 for east/west.
If you already have a Plex instance running, Prologue is an app that turns it into an audiobook host as well. Plex doesn’t natively support audiobook metadata like chapters, but Prologue simply uses Plex’s remote access to reach the files.
All you do is throw the .m4b audiobook files into a music library on Plex, sign into your Plex account on Prologue, and Prologue handles all of the metadata for the audiobooks instead of using Plex’s built-in music player.
I mention this because I had massive issues trying to get ABS to work on my setup. It simply refused to read or write any data from my NAS. After a day or two of throwing myself at it to no avail, I found Prologue and haven’t looked back. I already had Plex running for some friends and family, so setting up the music library was as easy as dropping the audiobooks into a folder.
Just out of curiosity, why bother running 4 instances of qBit for the various *arrs? Why not just use automatic torrent management, and have the different categories download to different folders? My *arrs are all using a single instance of qBit, and each service simply uses a different category with a different download path.
The benefit is that I can see my total up/down speeds, ratios, etc very easily without needing to change to an entirely different instance. I can filter by category, or see everything at the same time.
Yeah, I just wish there was a way to automatically update the port whenever it changes. It doesn’t change often since my server tends to stay on 24/7. But when it does change, it would be nice to have it automatically update.
Back before my current server, I was just messing around with it in Windows. I discovered that qBit actually stores the forwarded port in the registry, and PIA has a terminal command that can print the currently forwarded port. I tried to write a quick .bat script to automatically run when the PIA network adapter connected. The goal was to grab the port number and update the registry for qBit any time the internet went out or my server was rebooted.
And it seemed to work fine. It launched when PIA connected, and pushed the new value to the registry. But that forwarded port was also apparently being stored somewhere else as well, because just updating the registry wasn’t enough; When qBit launched it still showed the old port number, even though all of the documentation I found said it was simply a registry value. At that point I just gave up and manually updated it every time I turned my computer on.
I can’t believe this is relevant…
Lemmy has a lot of really outspoken FOSS enthusiasts. It sort of goes hand in hand with the whole “anyone can spin up their own instance” idea that Lemmy is built upon. Same reason there are so many Linux users here. But that also means you need to take any sort of “just switch to the FOSS version it’s basically the same thing” posts with a grain of salt.
Downloads definitely haven’t been removed. I use it virtually every day to watch stuff on my iPad at work.
I run both Plex and Jellyfin. Jellyfin is ready for everyone who doesn’t have to deal with the Mother-in-Law Factor. Plex has an easy setup process, and I could walk my MIL through it on my phone. In 5 minutes, her TV was connected to my server.
Jellyfin isn’t to that point yet, and likely never will be. Since there’s no centralized server for an app to phone home to, there’s no way to create a unified account creation/login experience. Jellyfin is nice as a “just for me” server. But as soon as I have to help others use it, it becomes a nightmare. Walking my MIL through setting up Jellyfin on her TV was the reason I re-installed Plex in the first place.
I had finally converted my wife away from using paid streaming apps, and dealt with all of the “Why do I have to use three different apps to access it on my three different devices? They all look different and are harder to use” complaints. By the time it got around to my MIL, I was tired of dealing with it and just reinstalled Plex so people could have a consistent experience.
I still use Jellyfin for my personal viewing because I prefer it. But saying “just ditch Plex, Jellyfin is ready now” is a little disingenuous. Jellyfin is ready for the people who want to use it. But if you’re trying to convince people to ditch their streaming apps, you’re fighting a lot of social inertia. You need to be able to provide a consistent experience across their different devices, with a decent login experience. And Jellyfin definitely isn’t there yet.
It’s because they don’t have PlexPass. I tend to forget that the restriction even exists, because I bought my lifetime pass like a decade ago.
just not so easy to setup or comparability for my shared users.
Yeah, the biggest reason I use Plex is because of the wife/mother-in-law factor. Basically, how easy is it to get the people around you to use it? If it’s more difficult to use than Netflix or Hulu, many will immediately throw up their hands in learned helplessness, claim it’s too confusing, and refuse to try any more. Plex is the only self-hosting option that actually provides an elegant user setup experience. With Plex, adding a new user is as simple as having them make an account and then sending them the server invite.
In doing so, they needed to reduce inventory, so they gave away the old laptops (sans drives) to their employees. I now own the same laptop (or a very similar one)!
Yeah, IT fleet upgrades are a great way to snag some decent hardware for dirt cheap. My Plex server is running on an old HP EliteDesk that came from a cubicle. The hardware itself is often practically new, because corporate drones rarely do anything intensive enough to actually push the hardware. Just give it a quick spray with some canned air, and pop a new drive in.
Yup. It’s a shame they don’t natively support cloud solutions like iCloud, which is what leads to workarounds like syncthing. It’s because they want to push their paid cloud option instead. But I also recognize that iCloud and their cloud hosting isn’t self-hosted, so it wouldn’t really fit here.
Yeah, you always have to account for the wife factor. Same reason I’m using Plex instead of Jellyfin for my video hosting; I’d personally prefer Jellyfin, but the wife factor (really the mother-in-law factor, but whatever…) demands that it doesn’t require a ton of config on the user’s end. If the goal is to encourage use by your family, it can’t be fiddly or difficult to set up on their end.
It’s more work to set up, but a much easier experience if you have users who can’t remotely access Overseerr. You always have to account for the “mom factor” when hosting services; Will your mom be able to learn how to use it? My mom can use Discord, but good luck getting her to learn Tailscale to access my Overseerr remotely.
I’m partial to GNOME for aesthetics and ease of use.
At that point just get a Mac. Gnome has the same “we know better than you do. If you want to do something outside of our extremely specific use cases, you’re using it wrong and should figure something else out” mentality that Apple does.
You don’t need to run it on a pi. In fact, I’d actually argue against it; A pi will be underpowered if you’re ever needing to transcode anything. Transcoding is what Plex/Jellyfin does if your watching device can’t natively play the video. Maybe you have a 4k video, but you’re playing it on a 1080p screen. That video will need to be transcoded from 4k into 1080p for the screen to be able to display it. Or maybe the file is encoded using ACC (a fairly recent encoding method) which isn’t widely supported by older devices. This often happens with things like smart TVs (which often don’t support modern encoding and need to be transcoded even if the resolution is correct.)
Basically, if you’re 100% positive that every device you’re watching it on will never need transcoding, then a pi is acceptable. But for anything else, I’d recommend a small PC instead. You can even use an old PC if you have one laying around.
Or if you want to use a new machine, maybe something like an HP Elitedesk. They’re basically what you see in every single cubicle in every single office building. They’re extremely popular in corporate settings, which means there are a ton of used/refurbished systems available for cheap, because IT destroys the drives and sends the rest to refurb when they upgrade their fleet of PCs. So for the refurb you’re basically just paying the cost of an SSD they added in (to replace the one IT pulled out), plus whatever labor is associated with dusting it out and checking the connections to make sure they all work. You can pick up a modern one for like $250 on Amazon (or your preferred electronics store).
Worth noting that the elitedesk generations are marked by a G-number, so google the model (like an EliteDesk G9, G7, etc) to see what kind of processor it has; Avoid anything with an intel 13th or 14th generation CPU, (they have major reliability issues) and check with Plex/Jellyfin’s CPU requirements list to see if it supports hardware accelerated transcoding. For Intel chips, look for QuickSync support.
For storage, I’d recommend running a NAS with however many hard drives you can afford, and one that has extra ports for future expandability. Some NAS systems support Plex and/or Jellyfin directly, but the requirements for full support are tricky and you’ll almost always have better luck just running a dedicated PC for Plex. Then for playing, one of two things will happen. Either the device is capable of directly playing the file, or it will need to be transcoded. If it’s directly playing, the plex server basically just points the player to the NAS, and the player handles the rest. If it’s transcoding, the PC will access the NAS, then stream it to the player.
As for deciding on Plex vs Jellyfin, that’s really a matter of personal preference. If you’re using Plex, I’d highly suggest a PlexPass sub/lifetime purchase; Wait until Black Friday, because they historically do a (~25% off) discount on their lifetime pass. Plex is definitely easier to set up, especially if you plan on streaming outside of your LAN.
Jellyfin currently struggles from a lack of native app support; Lots of smart TVs don’t have a native Jellyfin app, for instance. But some people have issues and complaints (many of them justified!) with Plex, so if the FOSS sounds appealing, then consider Jellyfin instead. Jellyfin is also rapidly being developed, and many people expect it to have feature parity with Plex within a few years.
And if you’re having trouble deciding, you can actually set up both (they can run in tandem on the same machine) and then see which one you prefer.
And the nice part about using a mini PC is that you can also use it for more than just Plex/Jellyfin. I have the *arr suite running on mine, alongside a Factorio server, a Palworld server, and a few other things.
Most of the episodes aired before at-home VHS was common, and TV stations weren’t in the habit of archiving their old footage for nightly broadcasts; The show was viewed as transient since it dealt with current events, and nobody expected people to want to re-watch old episodes. It’s likely that a lot of them aren’t available simply because nobody (including the tv station) has recordings.
If you already have a NAS, (since SMB was mentioned, I’m assuming there’s some sort of NAS setup going) then you may even be able to host Plex directly on the NAS. It likely won’t be powerful enough for things like video transcoding, but just audio should be fine.
It can be, yes. One of the largest complaints with Docker is that you often end up running the same dependencies a dozen times, because each of your dozen containers uses them. But the trade-off is that you can run a dozen different versions of those dependencies, because each image shipped with the specific version they needed.
Of course, the big issue with running a dozen different versions of dependencies is that it makes security a nightmare. You’re not just tracking exploits for the most recent version of what you have installed. Many images end up shipping with out-of-date dependencies, which can absolutely be a security risk under certain circumstances. In most cases the risk is mitigated by the fact that the services are isolated and don’t really interact with the rest of the computer. But it’s at least something to keep in mind.