WEBVTT 00:00:00.160 --> 00:00:08.719 death to Microsoft the opensource community is ready to send you to your 00:00:05.520 --> 00:00:13.000 grave your tyrannical Reign Over PC 00:00:08.719 --> 00:00:16.880 Gamers is at an end 00:00:13.000 --> 00:00:19.119 freom is what I would say if I lived 00:00:16.880 --> 00:00:24.439 with lonus Wallace III over here in fantasy land where any of that was true 00:00:22.320 --> 00:00:29.640 so far the one month Linux gaming challenge has been as advertised a 00:00:27.160 --> 00:00:33.760 challenge and in part two Luke and I are going to be taking it to the next level 00:00:31.359 --> 00:00:38.559 by not just gaming on Linux but by recording and streaming our gameplay to 00:00:36.160 --> 00:00:42.760 viewers on Twitch now I'd be lying if I said I'm not expecting some speed bumps 00:00:41.360 --> 00:00:48.440 like this small one here to tell you about our sponsor are you running into poor quality video meetings use glass 00:00:46.399 --> 00:00:52.680 wire and instantly see what apps are wasting your bandwidth during your 00:00:49.600 --> 00:00:54.359 meeting and block them get 25% off today 00:00:52.680 --> 00:00:57.800 using offer code Linus at the link in the video description 00:01:05.000 --> 00:01:10.080 with our desktop environment set up Luke and I have a deceptively short 00:01:08.439 --> 00:01:14.759 pre-flight checklist of tasks to complete to be streaming ready we'll 00:01:12.560 --> 00:01:19.080 need comms to chat and collaborate with our fellow creators and software that's 00:01:17.159 --> 00:01:23.400 capable of capturing our gameplay audio and face cams and obviously we'll need 00:01:21.320 --> 00:01:28.159 the aformentioned audio interfaces and cameras both working we both use Elgato 00:01:26.079 --> 00:01:32.399 key lights which we've always controlled using Windows software so we'll both 00:01:30.280 --> 00:01:37.159 need to find a workaround for that and no points will be awarded for having an 00:01:34.399 --> 00:01:41.280 ugly or bad sounding stream it's got to look every bit as legit from a viewer 00:01:39.079 --> 00:01:44.960 perspective as it did on Windows immediately I started overthinking 00:01:43.040 --> 00:01:50.119 things sometimes that's the problem with knowing just enough to be dangerous I 00:01:47.520 --> 00:01:53.680 tried to apt get OBS the industry standard for desktop capture and 00:01:51.520 --> 00:01:57.840 streaming in the terminal only to discover that manaro the Linux 00:01:55.640 --> 00:02:04.200 distribution that I'm using doesn't come with apt because apt is from managing 00:02:00.360 --> 00:02:06.119 packages on Debian and related os's oops 00:02:04.200 --> 00:02:10.239 making life more difficult the message that comes up when you try to execute 00:02:07.759 --> 00:02:14.959 the command doesn't say hey you should probably be using Pac-Man you duns it 00:02:12.760 --> 00:02:19.760 tries to install some kind of dependency for apt then just quietly fails and 00:02:18.239 --> 00:02:25.000 prompts you to do the same thing again when you try to use it infinite Loop 00:02:22.319 --> 00:02:28.440 baby speaking of which I had a panic moment when I checked OBS compatibility 00:02:27.000 --> 00:02:33.560 and found out that it is actually unsupported in art by the way and its 00:02:31.400 --> 00:02:37.360 derivatives but the good news is that upon launch I was immediately relieved 00:02:35.640 --> 00:02:42.959 to find that it works exactly as expected with some exceptions for 00:02:40.200 --> 00:02:47.200 example the nank new encoder doesn't show up as an option which appears to be 00:02:45.040 --> 00:02:51.280 down to NVIDIA's poop tastic drivers on Linux side note here I always kind of 00:02:49.599 --> 00:02:55.280 assumed that the Linux Community was grousing about NVIDIA primarily for 00:02:53.319 --> 00:03:00.040 their locked down proprietary approach to things and that it had less to do 00:02:57.599 --> 00:03:05.440 with the actual quality of the product now I properly understand that it is 00:03:02.599 --> 00:03:10.159 definitely both as mentioned core product functionality from like a couple 00:03:07.560 --> 00:03:15.519 of years ago is missing the control panel looks like it's from 10 years ago 00:03:12.360 --> 00:03:18.519 and the interface is kind of confusing 00:03:15.519 --> 00:03:21.120 thankfully I was able to enable g-sync 00:03:18.519 --> 00:03:26.840 on my display but for whatever reason you allow it in order to actually turn 00:03:24.680 --> 00:03:31.959 it on which you then verify in a completely different Tab and this kind 00:03:29.599 --> 00:03:37.599 of confusion is not a deal breaker it's just obvious that the Linux software has 00:03:35.439 --> 00:03:42.360 never gotten the kind of TLC from the ux team that the Windows software does for 00:03:40.200 --> 00:03:46.040 me acquiring OBS was no problem I just got it from the package manager and it 00:03:43.760 --> 00:03:50.120 was all okay once installed though we noticed something window capture on 00:03:47.959 --> 00:03:54.120 Linux can be a little problematic we couldn't seem to get it working at all 00:03:51.920 --> 00:03:58.200 at the start I had an option for it but it didn't work and Linus didn't even 00:03:56.280 --> 00:04:02.799 have that but a few days later I tried it again for a different project and it 00:04:00.400 --> 00:04:07.799 worked just fine I checked in with lonus and his did too neither of us know what 00:04:06.079 --> 00:04:13.079 might have fixed it but that's cool I guess the bigger issue 00:04:11.280 --> 00:04:17.359 for me ended up being the software that just doesn't exist there are third party 00:04:15.599 --> 00:04:21.440 tools for example that allow key remapping keyboarding Master is 00:04:19.239 --> 00:04:27.080 evidently a popular one but if your peripherals have a manufacturer provided 00:04:23.759 --> 00:04:29.240 tool that is used to reconfigure RGB 00:04:27.080 --> 00:04:34.360 lighting or the liftoff distance of your mouse or or the sensitivity steps of 00:04:31.320 --> 00:04:36.600 your DPI button then get ready to 00:04:34.360 --> 00:04:40.960 install Windows in a virtual machine pass those devices through configure 00:04:38.919 --> 00:04:46.960 them and then hand them back over to Linux it's extremely tedious and doesn't 00:04:44.440 --> 00:04:50.840 even remotely restore full functionality for example don't expect to get a low 00:04:48.880 --> 00:04:56.639 battery warning for your grpro wireless mouse and it's even worse for my audio 00:04:53.880 --> 00:05:01.160 interface the go XLR has a handful of unique features including decent preamps 00:04:59.080 --> 00:05:05.000 reprogramming screen labels a built-in soundboard function and the infamous 00:05:03.199 --> 00:05:09.440 beep button that I am so fond of using during my live streams about the kind of 00:05:07.120 --> 00:05:13.199 that NVIDIA puts them through I'll have it in the affiliate link down 00:05:10.720 --> 00:05:18.919 below by the way the bad news about it is that as far as I can tell TC Helicon 00:05:15.800 --> 00:05:22.360 has given exactly zero thought to Linux 00:05:18.919 --> 00:05:24.280 whatsoever but wait there's the solution 00:05:22.360 --> 00:05:30.199 all I have to do is follow these simple instructions to download a random script 00:05:27.919 --> 00:05:36.759 off GitHub and run it with no indication given whatsoever for 00:05:33.080 --> 00:05:38.000 how exactly to run a script even the 00:05:36.759 --> 00:05:43.039 process of downloading it was unintuitive and I know GitHub is for 00:05:40.080 --> 00:05:47.440 developers and not for end users but it's really hard to hide behind that 00:05:45.319 --> 00:05:52.600 Shield when it took me less than 2 days to run into a situation where I had to 00:05:50.160 --> 00:05:57.800 use it I mean at that point if GitHub is only for developers then desktop Linux 00:05:55.600 --> 00:06:02.240 is only for developers you can't have it both ways unlike on LT store where you 00:06:00.319 --> 00:06:05.600 can find great merch at fair prices our Mouse mats are rated five stars with 00:06:03.919 --> 00:06:11.000 literally thousands of reviews go see what all the fuss is about at the link below anyway I found a guide on how to 00:06:08.960 --> 00:06:16.960 run a script I'm grateful for that but I'm frustrated by the condescending tone 00:06:13.880 --> 00:06:19.160 I mean my assumption that a file with a 00:06:16.960 --> 00:06:23.319 sh extension would behave as I would expect it to and launch in some kind of 00:06:21.240 --> 00:06:28.560 script running application doesn't seem that unreasonable news flash random 00:06:26.080 --> 00:06:32.520 contributor you can also change a file extension in Windows and it will attempt 00:06:30.520 --> 00:06:37.039 to launch in the default program for that file type it actually serves 00:06:34.560 --> 00:06:41.599 exactly the same fundamental purpose hinting at the contents of the file the 00:06:39.280 --> 00:06:46.560 only difference is that these hints for the user are also used as hints for the 00:06:44.400 --> 00:06:49.599 operating system it's actually a lot more convenient than digging into the 00:06:48.120 --> 00:06:54.400 properties of the file to find out what it does anyway pompus tone aside that 00:06:52.400 --> 00:06:59.560 contributor did helped me figure out my GitHub download so it turns out that 00:06:56.879 --> 00:07:06.160 rightclick save Target as gets you an H HML file insh clothing because I don't 00:07:04.160 --> 00:07:11.319 know some borderline arbitrary reason probably and in order to get it to be an 00:07:08.560 --> 00:07:16.800 actual sh file I had to copy it into a text editor Kate and then save that as a 00:07:14.120 --> 00:07:21.520 script and execute it in the terminal it spat out a bunch of errors and as I 00:07:19.440 --> 00:07:26.199 expected most of the buttons don't work but all the inputs and outputs that I 00:07:24.080 --> 00:07:32.400 had already configured in Windows did show up my faders work I even have my 00:07:29.080 --> 00:07:34.240 button until my go XLR loses power for 00:07:32.400 --> 00:07:39.120 any reason at which point I will have to pass it through to Windows reconfigure 00:07:36.160 --> 00:07:44.319 it in Windows and then pass it back over to Linux without losing power compared 00:07:41.919 --> 00:07:48.560 to that all the other stuff is minor I hope the most notable issue I had was 00:07:46.759 --> 00:07:53.759 that my audio devices were just kind of screwy in OBS my voice came across very 00:07:51.840 --> 00:07:57.360 unnaturally deep and it sounded like my mic input had been duplicated my voice 00:07:56.039 --> 00:08:01.199 just feels deep right now I don't know if I've got something lodged or what 00:07:59.680 --> 00:08:04.960 yeah chat was pretty convinced that I had set something up incorrectly and if 00:08:02.960 --> 00:08:08.120 I was a viewer of my stream I probably would have said the same thing but I've 00:08:06.319 --> 00:08:12.720 been using OBS for like six or seven years now so I had my doubts I even 00:08:10.879 --> 00:08:18.400 streamed my OBS settings panel to prove it but eventually feeling out of options 00:08:15.599 --> 00:08:23.800 I just restarted OBS and yeah that solved pretty much everything which was 00:08:21.080 --> 00:08:27.000 kind of frustrating because I've heard time and time again that you don't have 00:08:25.199 --> 00:08:32.360 to turn things off and on again to get them working in Linux but hey maybe 00:08:29.720 --> 00:08:36.159 that's just cuz I'm not really great at Linux yet maybe there's something else I 00:08:34.080 --> 00:08:39.640 could have done not sure on the good side of things though my mixer has 00:08:37.680 --> 00:08:43.680 worked flawlessly from the start though it is pretty simple as far as mixers go 00:08:42.159 --> 00:08:47.320 I didn't have to change any settings I didn't have to install anything for it I 00:08:45.480 --> 00:08:51.080 just set it as my default input device and was good to go once I got pamac 00:08:49.519 --> 00:08:56.040 figured out getting comms going was surprisingly simple pamac is a program 00:08:53.959 --> 00:09:00.120 with a graphical user interface that functions similarly to the Pac-Man 00:08:58.160 --> 00:09:04.720 package manager that you operate in the terminal at least it does once you find 00:09:02.920 --> 00:09:10.600 the hidden button in pamac to search snap flat pack and Arch user repository 00:09:07.600 --> 00:09:13.120 entries it's basically like the pop shop 00:09:10.600 --> 00:09:17.720 from popos except it didn't try to Brick my system the first time I used it the 00:09:15.800 --> 00:09:22.640 only really difficult thing was choosing the right package to install for Discord 00:09:20.079 --> 00:09:27.480 there's regular Discord and then there's Canary Discord whatever that is I chose 00:09:25.839 --> 00:09:31.120 the most official looking package and I was up and running almost immediately 00:09:29.079 --> 00:09:36.040 once I found the super convenient per application volume mixer in the bottom 00:09:33.120 --> 00:09:40.320 right corner the interface is kind of cludy like scrolling with your mouse 00:09:38.120 --> 00:09:46.240 wheel Scrolls through both the audio devices and the levels of the individual 00:09:43.680 --> 00:09:50.160 devices which is not great but other than that it works really well and my 00:09:48.279 --> 00:09:56.399 first voice call to Luke went completely without a hitch or it would have if I'd 00:09:53.600 --> 00:10:00.920 known that it was starting unfortunately I actually still have not figured out 00:09:58.399 --> 00:10:06.120 how to get desktop notifications working I found a guide but the instructions 00:10:03.680 --> 00:10:10.320 fell apart almost immediately when my Discord package didn't show up in the 00:10:08.200 --> 00:10:15.480 list where it's supposed to be for me to fix it I think that's probably a project 00:10:13.440 --> 00:10:18.800 for another day Discord was an easy install for me again it was just 00:10:17.120 --> 00:10:24.399 automatically available in package manager that being said there was 00:10:20.959 --> 00:10:26.760 certain missing features screen sharing 00:10:24.399 --> 00:10:31.560 across slack teams and Discord are kind of sketchy at best they feel less stable 00:10:29.480 --> 00:10:35.480 or they're even missing some features here and there outside of that there's 00:10:33.240 --> 00:10:39.240 even really simple stuff missing every now and then like if I download a file 00:10:37.399 --> 00:10:45.639 and slack and then try to click the open containing folder button just nothing 00:10:42.639 --> 00:10:47.240 happens and speaking of missing features 00:10:45.639 --> 00:10:51.519 I used the phone app for the Elgato control center just like Linus did I had 00:10:49.519 --> 00:10:56.440 found another solution through a script on GitHub but I thought that way would 00:10:54.920 --> 00:11:02.519 potentially be problematic in the long term so I just avoided it unfortun for 00:10:59.680 --> 00:11:06.680 my camera however Canon EOS utilities doesn't work on Linux I'd been using 00:11:04.839 --> 00:11:12.040 that software on Windows for quite a while now to get a live feed from my 00:11:08.600 --> 00:11:14.320 Canon 70D over USB to my computer it was 00:11:12.040 --> 00:11:20.680 Flawless and didn't require a capture card I do have an Avio 4K capture card 00:11:18.519 --> 00:11:24.800 which does work on Linux but I don't have the micro HDMI cable that it would 00:11:22.519 --> 00:11:29.320 need to connect to my camera I could pick one up but just for this challenge 00:11:27.440 --> 00:11:34.880 I decided to go with my old Logitech C 920 which while it doesn't remotely look 00:11:32.040 --> 00:11:39.040 as good it works just fine and when you make the window for it really small no 00:11:36.800 --> 00:11:42.760 one can really tell I think overall the easiest part for me was getting my cam 00:11:40.760 --> 00:11:46.160 link 4K up and running it was garbled when I selected one of the duplicate 00:11:44.040 --> 00:11:50.880 sources in OBS but immediately after trying the second one it cleared up and 00:11:48.320 --> 00:11:55.639 has been Picture Perfect ever since so it works but there's a much larger 00:11:53.360 --> 00:12:01.959 upfront investment in getting it working the question is just whether it feels 00:11:58.360 --> 00:12:03.440 worth it in in the end it worked if you 00:12:01.959 --> 00:12:07.440 connected to the stream after we were done about 15 minutes of troubleshooting 00:12:05.560 --> 00:12:11.360 while we were just in the thick of trying not to starve I'm sure any random 00:12:10.160 --> 00:12:18.320 viewer wouldn't have been able to tell the difference between one of my old Windows streams and this one audio was 00:12:15.959 --> 00:12:23.120 good capture was good that's where the good ends however literally everything I 00:12:21.320 --> 00:12:26.639 used past this point was a lesser experience compared to its Windows 00:12:24.680 --> 00:12:32.120 counterpart almost everything was missing at least one feature and some I 00:12:29.160 --> 00:12:37.360 i' say most notably OBS and teams were just buggy requiring restarts for simple 00:12:34.800 --> 00:12:41.120 settings to actually apply and had other various problems it definitely wasn't 00:12:39.399 --> 00:12:45.360 impossible and it was actually easier than I expected but due to various bugs 00:12:43.440 --> 00:12:50.839 missing features and incompatible software it wasn't as simple or clean as 00:12:48.760 --> 00:12:55.040 doing it on Windows that I wouldn't say that was enough for it to be a deal 00:12:52.519 --> 00:12:57.880 breaker for me the bottom line is what you're looking to get out of it if 00:12:56.440 --> 00:13:02.920 you're daily driving Linux for game streaming out of a genuine passion for 00:13:00.519 --> 00:13:08.279 learning more about it than have at it have fun but just know what you're 00:13:05.440 --> 00:13:11.160 getting into PC gaming already requires a certain amount of tinkering I mean 00:13:09.760 --> 00:13:15.560 there's a reason that more people game on consoles you know whether it's trying 00:13:13.079 --> 00:13:22.320 to track down save files in some Vista era folder or forcing an aspect ratio in 00:13:18.399 --> 00:13:24.720 an inii file but a Linux gaming PC it 00:13:22.320 --> 00:13:29.399 requires all of that crap and then another mountain of crap on top of it 00:13:27.519 --> 00:13:33.079 like when something doesn't work you can tell yourself you know well I never 00:13:31.040 --> 00:13:37.440 wanted to use that functionality or I never wanted to play that game anyway 00:13:35.279 --> 00:13:44.440 but honestly it just comes across as sour grapes it is not that easy to use 00:13:42.199 --> 00:13:50.399 the good news though is that a shocking number of experiences don't start and 00:13:46.800 --> 00:13:51.920 end with sorry you can't do this so stay 00:13:50.399 --> 00:13:55.560 tuned for part three where Luke and I are going to be trying to get as many 00:13:53.560 --> 00:13:58.720 games up and running as possible starting with twitch's top 20 and then 00:13:57.440 --> 00:14:04.519 expanding into some of our personal favorites it's going to be a really good one just 00:14:02.399 --> 00:14:07.800 like this message from our sponsor thanks to pulseway for sponsoring 00:14:05.800 --> 00:14:10.839 today's video pulseway is an all-in-one platform management tool that can help 00:14:09.320 --> 00:14:15.920 protect your business from things like fishing and ransomware how pulseway has 00:14:14.000 --> 00:14:19.680 got features like automated patching Central user and system management 00:14:17.720 --> 00:14:23.160 disaster recovery backup and stolen credential monitoring so protect your 00:14:21.320 --> 00:14:26.800 business today and try pulse wave for free at the link in the video 00:14:24.720 --> 00:14:29.720 description it's sponsors like that that are going to put him through college 00:14:28.320 --> 00:14:34.759 want to say hi to YouTube hi all right he wanted to be in the video okay off you go y if you guys are 00:14:33.240 --> 00:14:37.800 looking for another video to watch check out part one of this series so you don't 00:14:36.480 --> 00:14:43.120 miss any of the action or if you've already watched that maybe check out my I switched to Mac series from a little 00:14:41.199 --> 00:14:46.920 while back okay it was quite a while back but it was definitely interesting