I haven’t tried it, but Tube Archivist may fit the bill.
I haven’t tried it, but Tube Archivist may fit the bill.
The downside with ULA is that ipv4 is given preference, which is annoying on dual stack networks. I believe there is a draft RFC to change this but it will take a while for it to be approved and longer still for OSes to change their behaviour. I workaround it by using one of the unused (but not ULA) prefixes.
Pretty cool especially since it’s RISC-V. I’d have some concerns about the software and driver side of things, though (and the performance).
Ah Nvidia. Bazzite uses Wayland I believe since it uses the same gamescope session as SteamOS (unless something has changed recently). While it may be possible to get it working, I’d expect a much better time with an AMD card.
A traditional distribution may be a better bet with Nvidia for now.
There’s a bunch of other variants like PiKVM and BIiKVM as well. Even some cheap knockoffs on Aliexpress that may do the job.
Mainly because running multiple desktop machines adds up to a lot of power, even at idle. If you power them off and on as needed it’s better, but then it’s not as convenient. Of course, if you leave a single machine with multiple GPUs on 24/7 that will also eat a lot of power, but it will be less than multiple machines turned on 24/7 at least.
And the physical space taken up by multiple desktop machines starts to add up significantly, particularly if you live in an apartment or smaller house.
Vanguard is especially bad because it will not allow to run the game with Intel-VT/AMD-V enabled even if you are running bare metal as of its last update.
The Vanguard anti-cheat is incredibly invasive and something akin to malware, so that’s not surprising.
I’ve recently tried to do that using sunsine and different linux gaming distros and it was awful, the VM was working great for a few minutes and then suddenly crashes and I have to hard stop it.
Are you running this with something like libvirtd/qemu? If so, VFIO configurations can get pretty complex. Random crashes seem like MSI interrupt issues (or you’ve allocated too much RAM to the guest). Or it could be GPU reset issues that would also occur on the (Linux) host, a newer kernel and Mesa version in the guest may help.
Setting on the kernel commandline for the host to workaround MSR interrupt crashes:
kvm.ignore_msrs=1
If you’re running on a Windows host or with something like Virtualbox (assuming GPU passthrough is supported by these), YMMV but I wouldn’t expect good results.
Systems themselves are all around 5-20W, although the ones with mechanical HDDs obviously add their own idle usage.
Ledger/hledger may be an option if you’re command line inclined although more local only then self-hosted per-se.
Try jellyfin-mpv-shim. It directly uses mpv
(either a built in version or even your system mpv
) and if it doesn’t play well there, it’s likely not going to play well anywhere.
Just to add to the other comments, you probably want to use a wildcard cert so you don’t need to individually certify each subdomain (or expose them at all).
Look at mini-PCs like the Lenovo Tiny series. These can be had for very little on the used market, and don’t use much power (<10W typically, although I don’t have any mechanical HDDs in mine).
EDIT: Obviously missed that you meant just a single device for everything. SFF PCs usually have a few SATA slots, and their power usage and price on the used market isn’t too bad.
I suspect the delay would still be longer than a Youtube like implementation which may need to switch transcodes multiple times, but that’s probably unrealistic at this point anyway.
Transcoding everything to AV1 could be a solution too, since high resolutions can look quite good at low bitrates, so you could limit it to 5mbps or 10mbps for any resolution and be done with it. But I’m not sure Jellyfin supports that, and at least from the UI it doesn’t give you particularly fine grained control over resolution/bitrates. Perhaps having a secondary library of just AV1 transcodes that you handle manually (perhaps even using a software encoder) could be an option for some.
The client side is also an issue, with not that many devices supporting hardware decoding (although I’ve found it’s fast enough in software with most modern smartphones at least).
Of course. Youtube and the like “pre-transcode” it so that would be one way for Jellyfin to better solve it, at the cost of a significant amount of disk space.
Maybe Jellyfin, where I believe you can force a low bitrate for every remote client. It wouldn’t be “adjust to internet speed” but you could minimise buffering that way.
having them VPN into shit is a hurdle that none of them are going to overcome.
If you have a lot of people connecting, then that’s fair. But setting up a VPN for one or two households isn’t hard. Even easier if you use Tailscale (apparently, never tried it myself).
I hope to see Jellyfin support this too (Plex is already getting support apparently) and hopefully it will work desktop-to-desktop and not just between streaming devices and phones.
Although it’s probably not massively needed as Jellyfin can already control remote devices.
Looks like it would eat power in a 24/7 setup but might be useful as an alternative to multiple systems.
Probably where some of the attitude comes from. People are assuming that it’s paid IT people bringing their work home with them, which is a different case then a casual user trying out self-hosting without the broader background.
Although I haven’t seen this attitude myself so I suspect it’s not that common, and probably just a handful of users jumping to conclusions.