YouTube got traction before Google bought it and before Google bought it they tried to make Google videos and failed, what peertube lacks is contributors
And discoverability, it still has ways to go on the social networking integration. I still don't know how to go from watching a peertube video on a peertube instance to liking/boosting it on another fediverse service, even if I wanted to.
That said, I have been following Peertube for a couple of years, and the progress has been incredible. It makes sense to create a solid foundation for video playback first, and a lot of people seem to not understand the extent of the innovation Peertube has made in that regard. Social media tools obviously come second after providing a solid service, and I have no idea it will develop in great ways in the coming years. :)
I’ve nibbled at trying to use Linux on my home computer for years and years, but games didn’t have a good track-record in Wine so I never went over.
I recently heard differently, and tried PopOS, and I’ve mostly been able to get all the games I wanted to play to play, mostly using Steam’s own emulation using Proton, and a few using Lutris.
The only two that gave me trouble were Starfield–it had a bug with Nvidia cards and I had to wait for a Linux driver to be updated with a driver fix. (And honestly after playing Starfield, it wouldn’t have mattered if it never played.) And Crusader Kings III…but only if I had it playing natively on Linux, as it’s supposed to be able to. It kept constantly crashing if I clicked on a character portrait. When I switched to playing it on Proton (so emulating Windows) it’s been rock solid.
I’ve played No Man’s Sky, Cyberpunk 2077, Rimworld, Control, Alan Wake II, Baldur’s Gate 3, and Valheim all successfully. (And Starfield and Crusader Kings III after some troubleshooting.) Those are modern enough that I don’t feel any more disadvantaged gaming on Linux than I did on Windows (accounting for my last-gen hardware and such.)
www.protondb.com is worth a look. It shows the state of games using Proton and people list their tweaks to make games work. You can filter it to only show Nvidia GPU’s on PopOS as an example too. To find tweaks more applicable to your system.
I’ve been playing Cyberpunk 2077 on Linux just fine as well, and Forza Horizon 4 (though the Xbox account setup was a rigmarole). Only thing I had to do was use bluetoothctl to set up my Xbox Series X/S controller, as it uses Bluetooth to connect and it doesn’t work with KDE’s Bluetooth setting GUI.
How about a used Thinkpad? Like the X280. 12.5". Touch. Depending on your region you can get a pretty good deal if you are OK with some scratches or other faults
First off, I want to make it clear that the distro doesn’t really matter. Different distros are just what it comes pre-packed with by default.
TLDR:
For something easy to use: Linux Mint
For something that has pre-installed audio software (but maybe not the ones you want): Ubuntu Studio
If you want to build your system from scratch: Debian (or Arch if you want the latest and greatest software, and don’t mind the occasional update breaking your system around once a year or so, and needing to spend an hour fixing it)
Regardless of which distro you get, use JACK or PipeWire for your sound server. PulseAudio (on its own) has too much latency.
More details:
I first tried Ubuntu Studio. It comes with a lot of software related to audio production. But I found it to be insanely slow, and it didn’t even come with Reaper anyway.
I tried OpenSUSE because I liked that it had the option to manually deselect the software you don’t want (and I was too much of a beginner to know how to pick my packages from the ground-up). It worked well.
Eventually I moved to Debian. I didn’t want any of the extra fluff and found it was pretty easy to choose everything myself. One thing that’s important is that you don’t want to use PulseAudio. Either use JACK (which I think needs to be used in conjunction with PulseAudio actually) or use PipeWire, which is what I use.
For any Windows software, use Bottles to emulate them on Linux. I actually ended up needing to go back to windows because of one audio software: Wwise. There was no way of running it in Linux. A VM probably would’ve worked, but that would’ve been a massive hassle for how I’d need to use it.
I didn’t get to spend too too much time doing pro audio on linux because as soon as I realized Wwise will not work, I didn’t spend much more time in Reaper after that. But it was good, especially with an audio interface (if you’re buying an audio interface, check to see how well it works with linux. Apparently some may have issues)
By the way, the whole point of Debian is that it has older software, and in exchange you’re almost guaranteed to have a system that doesn’t break. But for some professional software you’ll want the newest version. I recommend using Flatpak for that stuff instead of Apt (like for Reaper)
When installing Debian, when it asks “Allow login as root?” be sure to select “no”. This one step is why some people don’t recommend Debian, saying it complicates the install process. But if you get that right, then you’re all good. Or I think sometimes it will instead ask you to create and type in a root password, in which case you should leave it blank and click next. You only want to make a password for your user, not for the root.
As an aside, distro doesn’t matter but should make sure realtime is set up properly for the optimal latency. That usually requires the linux-rt kernel. The default one isn’t quite as bad as it used to be, but linux-rt will be able to guarantee low latency processing without dropouts. Also worth tuning/hardcoding latencies in JACK or PipeWire if the audio delay is too big out of the box.
Other than the way you installed the packages there’s nothing intrinsically arch on that wiki. I recommend you read the page and see if it helps before assuming it doesn’t because you’re using a different distro, arch wiki is great even if you don’t use arch.
Ah, sorry, your reply was 8 min after I sent the link which seemed awfully short to test the different approaches listed there, I assumed you hadn’t read it and just discarded for being a different distro. Sorry I couldn’t be more helpful.
Luthis, you’re doing God’s work here. You are learning by experimentation and then, importantly, documenting and sharing what you’ve learned. There is absolutely zero wrong and only good to be had in either of those and in combining them, you’re doing service to our entire community.
<span style="color:#323232;"> --filter, -f=filter
</span><span style="color:#323232;"> Filter what containers are going to be stopped. Multiple filters can be given with multiple uses of the --filter flag. Filters with the same key work
</span><span style="color:#323232;"> inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.
</span>
<span style="color:#323232;">Usage: docker stop [OPTIONS] CONTAINER [CONTAINER...]
</span><span style="color:#323232;">
</span><span style="color:#323232;">Options:
</span><span style="color:#323232;"> -s, --signal string Signal to send to the container
</span><span style="color:#323232;"> -t, --time int Seconds to wait before killing the container
</span>
One rule of thumb I discovered when doing research about a year ago is that AMD chips are generally way better than Intel chips when it comes to power consumption.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.