WEBVTT 00:00:00.719 --> 00:00:07.759 now we've yet to actually boot this motherboard 00:00:05.520 --> 00:00:12.840 with six graphics cards this could be the thing that kills the 00:00:09.360 --> 00:00:12.840 entire project 00:00:17.520 --> 00:00:24.560 the whole system restarted when i bumped that external pci express cable my level 00:00:22.320 --> 00:00:30.080 of pissed off right now is pretty high that's not what i was expecting 00:00:30.080 --> 00:00:35.600 story blocks video offers you studio quality clips at a fraction of the cost 00:00:34.160 --> 00:00:39.840 check them out today at the link in the video description 00:00:37.440 --> 00:00:44.879 so we found a pattern vm2 and vm6 00:00:42.640 --> 00:00:49.360 are not working and honestly i'm at the point now where all i can really do is 00:00:47.600 --> 00:00:53.280 give up on two and six in their current configurations and we're gonna try 00:00:50.879 --> 00:00:56.960 swapping out the graphics cards because we finally got an error and it was 00:00:55.039 --> 00:01:01.359 something to do with the onboard audio controller for the graphics cards makes 00:00:59.039 --> 00:01:04.400 no sense never seen this before on any pascal card especially a founder's 00:01:03.440 --> 00:01:08.240 edition so here's a titan v which is a good 00:01:06.479 --> 00:01:12.320 choice because this is what we'd like to use for the final build anyway because 00:01:10.320 --> 00:01:16.240 it has single slot i o although we have to convince NVIDIA to send us six of 00:01:14.080 --> 00:01:21.360 them and they're like this is not a supported configuration for the titan v 00:01:19.360 --> 00:01:24.799 i'm like yeah yeah i know people are gonna know that 00:01:22.640 --> 00:01:28.400 anyway our quadro systems are working fine too so we're going to swap out our 00:01:26.479 --> 00:01:33.600 1070 and our titan x which conveniently are right on the top of the pile here 00:01:30.320 --> 00:01:33.600 with these two puppies 00:01:38.479 --> 00:01:44.000 i could do that a thousand times and i'd never stop dropping things and i'd never 00:01:41.680 --> 00:01:48.880 stop wearing sandals okay i think it's booted 00:01:46.000 --> 00:01:52.720 so it picked that up so that's fine and six 00:01:50.640 --> 00:01:57.439 needs a GPU as well and it picked up that one which might be 00:01:55.280 --> 00:02:01.040 fine oh sound card d9 00:01:58.560 --> 00:02:04.960 okay new update we swapped in two new graphics cards and then we did end up 00:02:03.680 --> 00:02:09.520 having to disable their audio controllers which is weird but then one 00:02:07.200 --> 00:02:14.400 of them worked so we've actually got five lit up right now so it's just the 00:02:11.599 --> 00:02:18.800 last one that's not firing up so i'm wondering if maybe it's just like my 00:02:16.640 --> 00:02:22.480 DisplayPort to HDMI cable or something no i don't think so because num lock's 00:02:20.400 --> 00:02:26.640 not working on here so we're gonna throw an rtx 2080 in here 00:02:25.280 --> 00:02:31.280 because nothing's worked yet 00:02:28.959 --> 00:02:33.599 i really doubt it's gonna fire up though no 00:02:33.840 --> 00:02:38.400 yeah it lit up all right let's try the other five no 00:02:37.120 --> 00:02:42.400 i'm not actually doing it i'm not actually doing it i want to see all of them up 00:02:41.200 --> 00:02:50.000 i know it's normal when you're installing display drivers for the screen to go blank but i'm just 00:02:46.480 --> 00:02:52.080 very on edge about this 00:02:50.000 --> 00:02:58.400 num lock's not working you have got to be kidding me 00:02:54.800 --> 00:02:58.400 yeah five didn't fire up why 00:02:58.800 --> 00:03:07.200 what is the symbolism okay well six fired up but it's in 00:03:04.640 --> 00:03:12.239 Windows recovery nonsense mode 00:03:09.519 --> 00:03:16.009 all the usb devices are there and 00:03:17.440 --> 00:03:23.840 and now it's off bastard it's trying so hard 00:03:26.959 --> 00:03:34.080 you're just capturing my sadness over here yeah thanks 00:03:34.080 --> 00:03:39.840 so after sleeping on it i thought maybe we need to get a little bit back to 00:03:38.400 --> 00:03:45.200 basics here i pulled out all the graphics cards and 00:03:43.200 --> 00:03:50.159 re-ran the utility called hw lock 00:03:47.519 --> 00:03:54.000 so something's going on with pci express that's causing some kind of nonsense in 00:03:52.080 --> 00:03:59.920 the system it was causing hw lock to crash and it was causing our vms not to load 00:03:56.959 --> 00:04:05.760 now with our new BIOS which took forever to even start posting now what we can do 00:04:02.480 --> 00:04:07.200 is start to slowly re-add hardware 00:04:05.760 --> 00:04:11.840 until we reach a problem 00:04:09.439 --> 00:04:15.760 everything's in it should be fine 00:04:13.519 --> 00:04:21.040 NVIDIA confirmed the shipment of our six titan v's for this project 00:04:19.359 --> 00:04:24.560 there seems to have been a mistake because i never had the briefing call 00:04:22.720 --> 00:04:29.440 where i you know came up with some real workloads to use them with 00:04:27.120 --> 00:04:32.479 you know like realistically they were going to support this cool project they 00:04:31.120 --> 00:04:35.759 just jumped the gun a little that's all 00:04:34.160 --> 00:04:40.080 now i do want to get in here and turn on above 4g decoding and it's weird because 00:04:38.240 --> 00:04:44.880 i've had a really hard time getting into the BIOS ever since i updated it like i 00:04:42.880 --> 00:04:50.080 just go straight from this pre-BIOS loading thing to 00:04:47.040 --> 00:04:52.160 boom unraid's firing up 00:04:50.080 --> 00:04:55.280 oh there's a ps2 port maybe i should plug into that 00:04:55.360 --> 00:05:00.240 the saga continues 00:05:00.240 --> 00:05:07.120 it's erroring out on probably pci resources allocation 00:05:05.759 --> 00:05:12.479 but instead of letting me go into the BIOS and reconfigure that it's just hard 00:05:10.479 --> 00:05:15.520 resetting you 00:05:14.160 --> 00:05:19.120 bastard it's funny i remember sending ASUS a 00:05:17.199 --> 00:05:24.080 memo about this board saying this is the best behaved dual socket board i've yet 00:05:21.199 --> 00:05:28.720 seen to issue a retraction 00:05:26.400 --> 00:05:33.600 i mean it's not garbage it's like really cool fancy stuff but like 00:05:31.680 --> 00:05:39.160 i need it to work come on 00:05:35.759 --> 00:05:39.160 just output 00:05:44.000 --> 00:05:51.280 new plan we pull out all the gpus again 00:05:48.160 --> 00:05:54.960 and we reconfigure the pci 4g decoding 00:05:51.280 --> 00:05:57.280 thing with only the onboard connected 00:05:54.960 --> 00:06:01.360 go just go 00:05:59.520 --> 00:06:04.639 instead of showing me this whole bar and showing me all the postcodes it just 00:06:02.880 --> 00:06:10.430 shows me the first one it's not working correctly 00:06:15.039 --> 00:06:17.600 turned off 00:06:18.080 --> 00:06:24.160 come on 00:06:24.160 --> 00:06:28.880 yes okay 00:06:27.199 --> 00:06:33.280 so we are on the latest BIOS 00:06:31.199 --> 00:06:38.400 let's just go through here and see what all we need to change 00:06:34.720 --> 00:06:40.400 disable the serial port CPU storage nope 00:06:38.400 --> 00:06:43.759 on board lan disabled 00:06:41.520 --> 00:06:48.720 ASUS engine booster above 4g decoding on 00:06:46.160 --> 00:06:53.680 okay see i don't know what aspm does we don't need any of these operons 00:06:50.720 --> 00:06:57.039 never extract csm i mean maybe if we just start 00:06:55.039 --> 00:07:00.240 disabling devices that'll help 00:06:58.960 --> 00:07:04.080 this is it everything's reconfigured which means we 00:07:02.240 --> 00:07:08.639 need to plug these SATA devices into the other controller 00:07:07.280 --> 00:07:13.840 now we are going to add graphics cards 00:07:12.000 --> 00:07:17.440 let's just throw them all in i mean why not yellow it again that worked out so 00:07:15.520 --> 00:07:21.280 well for us last time guys how many times do you live 00:07:22.080 --> 00:07:30.120 i don't make everything hard i mean just ask the audience i'm sure tons of them 00:07:26.400 --> 00:07:30.120 are flaccid right now 00:07:30.240 --> 00:07:37.120 okay so we're back to square i don't know what square this is but 00:07:34.800 --> 00:07:42.639 we're back to actually being able to boot on raid see 00:07:40.080 --> 00:07:46.880 a display off of the onboard vga and we have all six graphics cards installed in 00:07:45.199 --> 00:07:51.280 the system what square is that 00:07:48.880 --> 00:07:54.240 hip square you know like it's hip to be i'm gonna go get my laptop 00:07:53.360 --> 00:08:00.000 so here's what we're gonna do we're gonna edit 00:07:57.759 --> 00:08:04.000 all of our vms to 00:08:01.360 --> 00:08:07.919 not have oh well they're gone so that's convenient okay they don't have their 00:08:06.080 --> 00:08:11.440 usb controllers because those aren't plugged in 00:08:09.199 --> 00:08:14.720 so can we start them which one's this four let's start number 00:08:13.440 --> 00:08:20.879 four i expect this to turn on 00:08:18.080 --> 00:08:23.520 i'm using the power of positive speech oh 00:08:22.000 --> 00:08:29.199 crap domain id3 is tainted this is not a good 00:08:27.039 --> 00:08:33.279 indicator right now because if it's the graphics cards that are our problem we 00:08:31.360 --> 00:08:36.800 are a lot further away from this project working than i hoped 00:08:35.039 --> 00:08:41.919 okay so it fired up but i don't see anything here yet which is also 00:08:40.399 --> 00:08:47.200 not a good indicator because remember four worked before 00:08:45.200 --> 00:08:51.830 maybe turning my mom's around again yeah we can try that 00:08:52.560 --> 00:08:57.040 i don't think so though oh boy 00:08:56.160 --> 00:09:02.480 okay good work david uh okay 00:08:59.680 --> 00:09:07.440 starting numero 6 internal error yeah once again it is 00:09:04.399 --> 00:09:08.640 flipping out about the audio crap that's 00:09:07.440 --> 00:09:12.399 bad what the hell 00:09:10.720 --> 00:09:15.360 okay i'm really screwing this up right now 00:09:13.839 --> 00:09:19.360 okay let's try two just prefer the lulls 00:09:17.920 --> 00:09:23.920 device eight f zero zero whatever the crap what do you 00:09:21.120 --> 00:09:29.279 mean af whatever what what is this okay did it change the is that the GPU 00:09:26.720 --> 00:09:33.279 it changed my GPU ids oh crap so ah man which one it okay 00:09:31.920 --> 00:09:36.560 forget it we're just going to create a new one however much memory it doesn't 00:09:35.279 --> 00:09:42.000 matter right now let's just get it working primary disk location manual 00:09:39.519 --> 00:09:44.080 graphics card titan v create 00:09:42.959 --> 00:09:49.760 all right let's see if that worked oh maybe actually yes 00:09:47.920 --> 00:09:53.600 so there it is keyboard and mouse obviously aren't working right now 00:09:51.120 --> 00:09:58.160 because i don't have my usb controller plugged in but 00:09:54.800 --> 00:09:59.440 okay well let's keep going then i guess 00:09:58.160 --> 00:10:04.959 uh oh dang it well 00:10:02.720 --> 00:10:08.800 two's not up unless it is when i turn the monitor 00:10:06.959 --> 00:10:13.680 back on new plan 00:10:10.880 --> 00:10:17.640 we're gonna try two and six as the only things plugged into the system 00:10:19.600 --> 00:10:27.200 okay i got 00:10:24.399 --> 00:10:34.320 ls toppo to run so the difference between our new ls toppo run and the old 00:10:29.839 --> 00:10:36.640 one is now i have all six gpus installed 00:10:34.320 --> 00:10:40.800 in the system so what that allows us to do 00:10:38.000 --> 00:10:45.440 if this image viewing program wasn't completely worthless 00:10:42.720 --> 00:10:48.959 sure good enough what this allows us to do is figure out 00:10:47.279 --> 00:10:56.160 which gpus are the problem so we can see here 00:10:52.399 --> 00:10:57.040 six is our titan x and two is our titan 00:10:56.160 --> 00:11:04.640 v so then if we go into system devices 00:11:00.399 --> 00:11:06.399 this tells us that 1d81 00:11:04.640 --> 00:11:12.079 right here and then our titan x 00:11:08.480 --> 00:11:13.120 those are our problem gpus okay 00:11:12.079 --> 00:11:18.560 so this confirms a few things number one is it confirms 00:11:16.480 --> 00:11:22.800 that my map of the pci express slots is probably right because slot two and slot 00:11:21.120 --> 00:11:26.160 three which is where those are one of them should be CPU two i believe that's 00:11:24.480 --> 00:11:30.000 slot two and one of them should be CPU one i believe that's slot three and 00:11:28.320 --> 00:11:32.720 actually i checked that that's right so it confirms that 00:11:31.680 --> 00:11:37.920 and it confirms why i think 00:11:35.360 --> 00:11:43.920 four was fine and six is bad both of them are the only subordinate 00:11:40.800 --> 00:11:45.600 devices on a plx bridge 00:11:43.920 --> 00:11:50.959 and those are the ones i'm having issues with so 00:11:48.000 --> 00:11:55.519 it is my belief that either the solution is UEFI tuning so i've drafted an email 00:11:53.600 --> 00:11:58.720 to ASUS explaining that these are my problems 00:11:56.640 --> 00:12:04.240 or a new UEFI i remember how i started that sentence 00:12:00.880 --> 00:12:05.760 my brain is very tired um we're i'm 00:12:04.240 --> 00:12:10.519 gonna send them an email hopefully it'll be coherent in the meantime though 00:12:10.880 --> 00:12:18.160 now what i haven't been having problems with 00:12:14.560 --> 00:12:21.600 is my u.2 to pci express 00:12:18.160 --> 00:12:21.600 x4 adapters 00:12:22.720 --> 00:12:29.600 like this really is just for testing i intend to populate these 00:12:27.920 --> 00:12:34.480 two now graphics card can draw up to 75 00:12:32.560 --> 00:12:39.519 watts through the pci express slot itself so obviously 00:12:36.800 --> 00:12:44.399 this SATA to power adapter thing like look at these pin or wires on this thing 00:12:41.839 --> 00:12:48.880 but we are not going to be loading this thing anyway i just want to see them 00:12:45.760 --> 00:12:50.720 work i don't need to run doom for 24 00:12:48.880 --> 00:12:56.079 hours straight or anything like that all right so 00:12:53.360 --> 00:13:01.040 here goes one and here goes 00:12:58.720 --> 00:13:01.040 two 00:13:01.839 --> 00:13:06.959 so bad so i'm going to put this 00:13:05.200 --> 00:13:11.040 here so we're only getting four lanes but 00:13:08.639 --> 00:13:14.000 that's four lanes PCIe gen three like that's not bad 00:13:12.480 --> 00:13:17.120 does anyone else have really mixed feelings when they 00:13:15.600 --> 00:13:21.440 you know finally reached the end of a problem like where part of them is relieved and 00:13:20.000 --> 00:13:26.959 happy and the other part of them is just like pissed off that it took so long 00:13:24.399 --> 00:13:30.240 if the cringing was real last time 00:13:28.480 --> 00:13:35.780 now it's reached a level of hyper realism that we thought only possible 00:13:32.240 --> 00:13:37.519 with rtx okay so i need this 00:13:37.519 --> 00:13:40.639 to reach in through here 00:13:40.880 --> 00:13:47.760 ah yeah 00:13:46.079 --> 00:13:52.480 this seems fine so step number one is finding out if my 00:13:49.920 --> 00:13:55.519 gpus are even working in those slots i mean 00:13:53.680 --> 00:13:59.360 theoretically there's no real difference between this 00:13:57.120 --> 00:14:02.720 and this they're just pci express over a cable but you never know 00:14:01.519 --> 00:14:06.560 titan v boom there it is and one b zero zero 00:14:05.040 --> 00:14:10.720 this one's the same so that's our titan x so they're there 00:14:08.720 --> 00:14:13.920 so let's try starting it started right away 00:14:12.399 --> 00:14:17.680 i don't know if we have a display output though 00:14:15.519 --> 00:14:21.920 well would you look at that not only is it working but what's really 00:14:20.399 --> 00:14:27.440 odd is it's running in the correct resolution let's see if it survives a reboot here 00:14:25.360 --> 00:14:32.560 need i remind you guys that this is the GPU that is plugged into an extension 00:14:30.480 --> 00:14:36.480 plugged into a daughter board is vertical in the case and completely 00:14:34.720 --> 00:14:41.680 unsupported by anything like if this works it's a small christmas miracle 00:14:39.839 --> 00:14:47.040 hey are you working or what 00:14:44.320 --> 00:14:47.040 same behavior 00:14:48.079 --> 00:14:54.399 let's try the titan v let's see what happens oh oh oh oh oh 00:14:53.360 --> 00:14:57.760 okay yay obtain it's going fast at least wow 00:14:56.399 --> 00:15:04.560 it's going really fast now it slowed down and of course it's 100 complete and 00:15:01.839 --> 00:15:08.720 yet here we are progress bars man how are they this broken 00:15:06.959 --> 00:15:12.120 i'm gonna see if i can reboot that other one in the meantime 00:15:12.959 --> 00:15:22.000 so i ran ls topo again and let's have a look at what our topology is now so 00:15:19.360 --> 00:15:26.639 here's those two devices we're still having issues why 00:15:24.079 --> 00:15:30.399 why those two specifically we're actually moving backwards we're losing 00:15:28.720 --> 00:15:35.440 vms now four no longer boots i'm gonna try uh 00:15:32.880 --> 00:15:38.880 three and one as well one's up five's up 00:15:37.519 --> 00:15:43.279 three's up i don't know if they're gonna stay up 00:15:40.639 --> 00:15:47.680 five three and one let's try stopping them 00:15:45.040 --> 00:15:51.279 and then we'll try rebooting them that's the real test 00:15:48.959 --> 00:15:58.240 and none of them have a signal 00:15:58.240 --> 00:16:05.600 okay then okay 00:16:03.040 --> 00:16:10.480 i had really hoped these adapters were going to be the solution 00:16:07.279 --> 00:16:12.800 we are going to put our gpus 00:16:10.480 --> 00:16:16.399 in this thing like there's nothing 00:16:14.320 --> 00:16:21.040 that would lead me to believe that this will be better than using those NVMe 00:16:18.959 --> 00:16:25.440 adapters blah all right maybe we can shove this 00:16:23.199 --> 00:16:29.839 over to get that HDMI cable in there yep there we go okay so that's in let's go 00:16:27.839 --> 00:16:33.199 ahead and throw our expansion card doodad 00:16:30.880 --> 00:16:38.399 back in here oh ballsack which slot was i think it's the bottom one that i use 00:16:35.040 --> 00:16:38.399 okay ah 00:16:38.480 --> 00:16:45.199 why is this keyboard powered up oh these cards have power even though 00:16:42.560 --> 00:16:50.759 they don't have a data signal did that just shut down and reboot 00:16:47.040 --> 00:16:50.759 sounds good okay 00:16:50.959 --> 00:16:55.759 that's the pain train it's leaving the station 00:16:56.480 --> 00:17:03.199 so the configuration's a complete cluster at this point the two that i'm 00:17:00.639 --> 00:17:07.439 really worried about are the titan x in vm number two and the titan v and 00:17:05.839 --> 00:17:11.199 number six so why don't we do those first all right so they're both up but 00:17:09.839 --> 00:17:15.199 let's find out if they're going to stay up this has a blinking cursor so that'll 00:17:13.039 --> 00:17:19.199 tell us if this freezes mind you if it behaves like before it'll probably just 00:17:17.600 --> 00:17:23.360 go away did that just go away 00:17:20.959 --> 00:17:26.160 oh whoa whoa whoa whoa whoa whoa whoa whoa 00:17:24.720 --> 00:17:32.640 this one's up i'm gonna shut it down and reboot it 00:17:29.679 --> 00:17:36.960 is it doing a graceful shutdown okay so this is still working i can tell 00:17:34.640 --> 00:17:40.320 because the system clock is still right this one finished its update while i 00:17:39.039 --> 00:17:45.200 wasn't looking we're gonna rerun our command here 00:17:43.280 --> 00:17:48.799 did we just crash oh yeah that bm's gone 00:17:49.120 --> 00:17:56.480 we're not going hail mary anymore we're not going for glory so 00:17:53.840 --> 00:17:59.679 we're gonna go back to basics and we're just gonna start with one then we're 00:17:58.160 --> 00:18:04.640 gonna put in two and three and four we're gonna see where we crap 00:18:03.120 --> 00:18:09.360 out and see if we can find a pattern here so after sleeping on it i thought 00:18:07.600 --> 00:18:14.799 maybe we need to get a little bit back to basics here now what we can do is 00:18:11.679 --> 00:18:16.160 start to slowly re-add hardware 00:18:14.799 --> 00:18:22.000 until we reach a problem the is that 00:18:20.240 --> 00:18:25.280 this is honestly starting to feel a little bit like a journal that i'm 00:18:23.280 --> 00:18:28.720 keeping on a on a desert island where i'm the only survivor or some garbage 00:18:27.520 --> 00:18:36.400 like that like so while the camera was off last night we 00:18:32.960 --> 00:18:38.480 went back to unraid 6.5.3 00:18:36.400 --> 00:18:42.160 just in case the newer Linux kernel with all the spectre and meltdown nonsense 00:18:40.400 --> 00:18:46.720 that's going on was was causing some problems that was a suggestion from the 00:18:43.919 --> 00:18:50.799 unraid guys and i went down to one card and it was working 00:18:48.080 --> 00:18:53.919 then i added a second card and boom already flaky behavior 00:18:52.720 --> 00:18:59.919 i don't even i don't even know if that was one of the slots i was having trouble with before so this is this is 00:18:57.280 --> 00:19:05.679 like a big problem and now that i had all the mapping information i was 00:19:02.080 --> 00:19:08.160 definitely assigning gpus to the correct 00:19:05.679 --> 00:19:12.799 CPU course so we weren't having to cross between the cpus in order to get to the 00:19:10.480 --> 00:19:18.480 pci express lanes so that got me thinking 00:19:15.280 --> 00:19:21.679 what if the problem is hardware now ivan 00:19:18.480 --> 00:19:23.120 is a competent pc technician 00:19:21.679 --> 00:19:28.480 but he doesn't have experience with lga 3647 00:19:26.640 --> 00:19:34.160 and it occurred to me that he was the one who installed my 00:19:30.880 --> 00:19:36.240 cpus so that got me thinking 00:19:34.160 --> 00:19:39.840 what if we just have a bent pin in the socket 00:19:37.679 --> 00:19:39.840 so 00:19:42.320 --> 00:19:48.559 it was a little piece of debris in the socket but 00:19:46.720 --> 00:19:53.280 it seems to be clear now all right so there's one 00:19:50.640 --> 00:19:56.559 now let's try the other one no obvious issues 00:19:54.799 --> 00:20:01.840 i should put them in the opposite sockets just to see if like 00:19:58.960 --> 00:20:07.400 maybe i start having problems with like different slots or something 00:20:04.240 --> 00:20:07.400 you know 00:20:08.000 --> 00:20:12.799 well so much for that theory i mean you never 00:20:11.280 --> 00:20:18.720 know when you know reseeding can just 00:20:16.080 --> 00:20:23.520 magically solve something though so still 00:20:20.240 --> 00:20:25.679 i'm not very hopeful but you never know 00:20:23.520 --> 00:20:29.919 so this is interesting we just got a kernel panic again 00:20:28.720 --> 00:20:36.159 this time it's CPU one 00:20:31.840 --> 00:20:37.600 processor id one it is still possible 00:20:36.159 --> 00:20:42.159 that one of my you know ten thousand dollar cpus is 00:20:39.280 --> 00:20:45.760 defective but i'm really leaning towards like motherboard 00:20:44.000 --> 00:20:49.679 BIOS optimizations that are 00:20:47.600 --> 00:20:54.720 wonky at this point we're not getting away from these hard resets 00:20:52.240 --> 00:21:00.000 so my idea just now was do a fresh install to that vm and see if we can 00:20:57.039 --> 00:21:04.880 avoid whatever devices it's trying to install drivers for 00:21:02.799 --> 00:21:07.360 so that all is behaving completely normally 00:21:07.600 --> 00:21:11.039 wouldn't that be a weird thing 00:21:11.919 --> 00:21:17.520 if it spazzed out over the copied vdisks but then 00:21:15.679 --> 00:21:22.320 getting ready i don't know about you computer but i've 00:21:19.120 --> 00:21:23.679 been ready for a while here 00:21:22.320 --> 00:21:26.000 hey uh 00:21:28.840 --> 00:21:33.120 what what's going on 00:21:33.440 --> 00:21:35.760 hi 00:21:40.159 --> 00:21:44.159 we have a Windows desktop 00:21:44.159 --> 00:21:50.400 on machine number two 00:21:47.919 --> 00:21:55.280 how did this happen so this is how it's going to be for now 00:21:53.600 --> 00:21:59.200 we finally got machine 2 00:21:56.880 --> 00:22:03.200 working we think but Windows updates 00:22:01.440 --> 00:22:07.679 are not having any of it storyblocks video gets you studio 00:22:05.200 --> 00:22:11.520 quality video clips at a fraction of the cost you can download all the stock 00:22:09.840 --> 00:22:16.880 video that your heart desires from their member library including hd and 00:22:14.400 --> 00:22:22.000 4k footage after effects templates motion backgrounds and more we actually 00:22:19.280 --> 00:22:25.919 use it quite a bit here on our tech wiki channel plus you can get exclusive 00:22:23.919 --> 00:22:29.520 discounts on millions of additional marketplace clips you'll save 40 on the 00:22:28.080 --> 00:22:35.520 purchase compared to non-members and what's really cool is the original artist will take a commission on each 00:22:33.120 --> 00:22:39.200 sale all the content is royalty free so you can use it even for commercial use 00:22:37.440 --> 00:22:42.559 to your heart's content and for personal projects like youtube videos for example 00:22:41.039 --> 00:22:46.159 and new clips are added regularly so there's always something new to check 00:22:44.320 --> 00:22:51.440 out so check it out today at the link below so thanks for watching guys 00:22:49.440 --> 00:22:54.559 if you disliked this video then quite frankly you and i are in the same boat 00:22:52.960 --> 00:22:57.919 because i did not have a good time over the last few days working on this and 00:22:56.240 --> 00:23:01.440 i'm not looking forward to continuing to work on it but if you liked it hit like 00:23:00.159 --> 00:23:04.559 get subscribed and maybe consider checking out where to buy the stuff we featured at the link in the video 00:23:03.520 --> 00:23:09.039 description but i wouldn't recommend buying it yet because we haven't quite determined if any of this works also 00:23:07.760 --> 00:23:14.799 down there is our merch store which has cool shirts like this one and our community forum which you should 00:23:11.679 --> 00:23:14.799 definitely join