WEBVTT Kind: captions Language: en 00:00:00.520 --> 00:00:02.230 align:start position:0% let's<00:00:00.719> get<00:00:00.919> right<00:00:01.040> to<00:00:01.160> the<00:00:01.400> point<00:00:01.839> at<00:00:01.959> the<00:00:02.080> end 00:00:02.230 --> 00:00:02.240 align:start position:0% let's get right to the point at the end 00:00:02.240 --> 00:00:05.230 align:start position:0% let's get right to the point at the end of<00:00:02.439> 2024<00:00:03.439> I<00:00:03.600> had<00:00:03.760> the<00:00:03.879> urge<00:00:04.200> to<00:00:04.359> move<00:00:04.640> my<00:00:04.799> steam 00:00:05.230 --> 00:00:05.240 align:start position:0% of 2024 I had the urge to move my steam 00:00:05.240 --> 00:00:07.150 align:start position:0% of 2024 I had the urge to move my steam Library<00:00:05.680> into<00:00:05.879> the<00:00:06.040> living<00:00:06.319> room<00:00:06.799> after<00:00:07.000> an 00:00:07.150 --> 00:00:07.160 align:start position:0% Library into the living room after an 00:00:07.160 --> 00:00:09.230 align:start position:0% Library into the living room after an unsuccessful<00:00:07.759> Andro<00:00:08.320> feeble<00:00:08.760> attempt<00:00:09.080> at 00:00:09.230 --> 00:00:09.240 align:start position:0% unsuccessful Andro feeble attempt at 00:00:09.240 --> 00:00:12.110 align:start position:0% unsuccessful Andro feeble attempt at using<00:00:09.519> a<00:00:09.719> Mac<00:00:10.040> Mini<00:00:10.400> as<00:00:10.480> a<00:00:10.679> companion<00:00:11.120> to<00:00:11.280> my<00:00:11.480> PC 00:00:12.110 --> 00:00:12.120 align:start position:0% using a Mac Mini as a companion to my PC 00:00:12.120 --> 00:00:14.549 align:start position:0% using a Mac Mini as a companion to my PC I<00:00:12.320> finally<00:00:12.759> caved<00:00:13.160> in<00:00:13.400> and<00:00:13.639> decided<00:00:14.040> to<00:00:14.200> move 00:00:14.549 --> 00:00:14.559 align:start position:0% I finally caved in and decided to move 00:00:14.559 --> 00:00:16.910 align:start position:0% I finally caved in and decided to move back<00:00:14.799> into<00:00:15.000> an<00:00:15.200> ITX<00:00:15.799> case<00:00:16.400> giving<00:00:16.600> me<00:00:16.760> the 00:00:16.910 --> 00:00:16.920 align:start position:0% back into an ITX case giving me the 00:00:16.920 --> 00:00:18.790 align:start position:0% back into an ITX case giving me the power<00:00:17.199> I<00:00:17.359> sought<00:00:17.800> while<00:00:18.000> better<00:00:18.279> matching<00:00:18.640> the 00:00:18.790 --> 00:00:18.800 align:start position:0% power I sought while better matching the 00:00:18.800 --> 00:00:21.269 align:start position:0% power I sought while better matching the rest<00:00:19.039> of<00:00:19.160> the<00:00:19.320> living<00:00:19.600> room<00:00:20.279> Aesthetics 00:00:21.269 --> 00:00:21.279 align:start position:0% rest of the living room Aesthetics 00:00:21.279 --> 00:00:23.070 align:start position:0% rest of the living room Aesthetics that's<00:00:21.480> all<00:00:21.680> fine<00:00:21.960> and<00:00:22.240> dandy<00:00:22.760> but<00:00:22.920> the 00:00:23.070 --> 00:00:23.080 align:start position:0% that's all fine and dandy but the 00:00:23.080 --> 00:00:25.150 align:start position:0% that's all fine and dandy but the experience<00:00:23.560> wasn't<00:00:24.039> complete<00:00:24.680> living<00:00:24.960> room 00:00:25.150 --> 00:00:25.160 align:start position:0% experience wasn't complete living room 00:00:25.160 --> 00:00:27.390 align:start position:0% experience wasn't complete living room gaming<00:00:25.480> requires<00:00:25.840> a<00:00:26.000> certain<00:00:26.400> level<00:00:26.640> of<00:00:26.800> late 00:00:27.390 --> 00:00:27.400 align:start position:0% gaming requires a certain level of late 00:00:27.400 --> 00:00:29.669 align:start position:0% gaming requires a certain level of late backness<00:00:28.400> in<00:00:28.640> particular<00:00:29.119> I<00:00:29.240> wanted<00:00:29.519> to<00:00:29.599> be 00:00:29.669 --> 00:00:29.679 align:start position:0% backness in particular I wanted to be 00:00:29.679 --> 00:00:31.509 align:start position:0% backness in particular I wanted to be able<00:00:29.840> to<00:00:30.080> pick<00:00:30.199> up<00:00:30.320> a<00:00:30.439> controller<00:00:31.000> pledge<00:00:31.359> my 00:00:31.509 --> 00:00:31.519 align:start position:0% able to pick up a controller pledge my 00:00:31.519 --> 00:00:32.830 align:start position:0% able to pick up a controller pledge my allegiance<00:00:31.960> to<00:00:32.119> whatever<00:00:32.439> corporate 00:00:32.830 --> 00:00:32.840 align:start position:0% allegiance to whatever corporate 00:00:32.840 --> 00:00:34.990 align:start position:0% allegiance to whatever corporate overlord's<00:00:33.399> gam<00:00:33.640> pad<00:00:33.840> I<00:00:34.000> chose<00:00:34.399> and<00:00:34.559> watch<00:00:34.800> the 00:00:34.990 --> 00:00:35.000 align:start position:0% overlord's gam pad I chose and watch the 00:00:35.000 --> 00:00:38.030 align:start position:0% overlord's gam pad I chose and watch the small<00:00:35.360> but<00:00:35.559> powerful<00:00:36.000> box<00:00:36.320> boot<00:00:36.680> up<00:00:37.320> my<00:00:37.480> AV 00:00:38.030 --> 00:00:38.040 align:start position:0% small but powerful box boot up my AV 00:00:38.040 --> 00:00:39.910 align:start position:0% small but powerful box boot up my AV receiver<00:00:38.239> and<00:00:38.480> TV<00:00:38.760> to<00:00:38.960> react<00:00:39.239> to<00:00:39.399> it<00:00:39.600> Windows 00:00:39.910 --> 00:00:39.920 align:start position:0% receiver and TV to react to it Windows 00:00:39.920 --> 00:00:41.990 align:start position:0% receiver and TV to react to it Windows 11<00:00:40.200> to<00:00:40.360> welcome<00:00:40.640> me<00:00:40.800> with<00:00:40.920> Oden<00:00:41.280> arms<00:00:41.680> and<00:00:41.840> my 00:00:41.990 --> 00:00:42.000 align:start position:0% 11 to welcome me with Oden arms and my 00:00:42.000 --> 00:00:43.470 align:start position:0% 11 to welcome me with Oden arms and my steam<00:00:42.320> library<00:00:42.680> to<00:00:42.800> launch<00:00:43.120> into<00:00:43.320> the 00:00:43.470 --> 00:00:43.480 align:start position:0% steam library to launch into the 00:00:43.480 --> 00:00:45.389 align:start position:0% steam library to launch into the familiar<00:00:43.879> big<00:00:44.120> screen<00:00:44.440> UI<00:00:44.840> I've<00:00:45.039> gotten<00:00:45.239> to 00:00:45.389 --> 00:00:45.399 align:start position:0% familiar big screen UI I've gotten to 00:00:45.399 --> 00:00:47.790 align:start position:0% familiar big screen UI I've gotten to know<00:00:45.719> and<00:00:45.960> laugh<00:00:46.160> on<00:00:46.320> my<00:00:46.440> steam<00:00:46.840> day<00:00:47.440> did<00:00:47.600> I 00:00:47.790 --> 00:00:47.800 align:start position:0% know and laugh on my steam day did I 00:00:47.800 --> 00:00:50.549 align:start position:0% know and laugh on my steam day did I succeed<00:00:48.440> to<00:00:48.640> my<00:00:48.760> own<00:00:48.960> disbelief<00:00:49.559> yes<00:00:49.840> and<00:00:50.280> even 00:00:50.549 --> 00:00:50.559 align:start position:0% succeed to my own disbelief yes and even 00:00:50.559 --> 00:01:01.950 align:start position:0% succeed to my own disbelief yes and even better<00:00:51.000> than<00:00:51.160> I<00:00:51.280> had<00:00:51.480> anticipated 00:01:01.950 --> 00:01:01.960 align:start position:0% 00:01:01.960 --> 00:01:03.430 align:start position:0% before<00:01:02.239> we<00:01:02.440> get<00:01:02.640> there<00:01:02.960> just<00:01:03.120> for<00:01:03.280> your 00:01:03.430 --> 00:01:03.440 align:start position:0% before we get there just for your 00:01:03.440 --> 00:01:05.109 align:start position:0% before we get there just for your convenience<00:01:03.960> sake<00:01:04.280> this<00:01:04.400> video<00:01:04.640> is<00:01:04.720> split<00:01:05.000> up 00:01:05.109 --> 00:01:05.119 align:start position:0% convenience sake this video is split up 00:01:05.119 --> 00:01:07.310 align:start position:0% convenience sake this video is split up into<00:01:05.400> three<00:01:05.640> main<00:01:06.040> chapters<00:01:06.640> each<00:01:06.920> covering 00:01:07.310 --> 00:01:07.320 align:start position:0% into three main chapters each covering 00:01:07.320 --> 00:01:09.870 align:start position:0% into three main chapters each covering one<00:01:07.640> part<00:01:07.880> of<00:01:08.119> this<00:01:08.320> endeavor<00:01:09.280> first<00:01:09.560> is<00:01:09.720> the 00:01:09.870 --> 00:01:09.880 align:start position:0% one part of this endeavor first is the 00:01:09.880 --> 00:01:11.830 align:start position:0% one part of this endeavor first is the power<00:01:10.159> on<00:01:10.479> sequence<00:01:11.119> then<00:01:11.360> how<00:01:11.520> to<00:01:11.680> get 00:01:11.830 --> 00:01:11.840 align:start position:0% power on sequence then how to get 00:01:11.840 --> 00:01:13.789 align:start position:0% power on sequence then how to get Windows<00:01:12.200> 11<00:01:12.560> to<00:01:12.680> launch<00:01:13.080> straight<00:01:13.400> into<00:01:13.640> the 00:01:13.789 --> 00:01:13.799 align:start position:0% Windows 11 to launch straight into the 00:01:13.799 --> 00:01:15.950 align:start position:0% Windows 11 to launch straight into the desktop<00:01:14.479> without<00:01:14.720> having<00:01:14.920> to<00:01:15.080> log<00:01:15.280> in<00:01:15.600> before 00:01:15.950 --> 00:01:15.960 align:start position:0% desktop without having to log in before 00:01:15.960 --> 00:01:17.950 align:start position:0% desktop without having to log in before figuring<00:01:16.280> out<00:01:16.560> how<00:01:16.680> to<00:01:16.840> get<00:01:16.960> the<00:01:17.119> PC<00:01:17.439> to<00:01:17.600> send 00:01:17.950 --> 00:01:17.960 align:start position:0% figuring out how to get the PC to send 00:01:17.960 --> 00:01:21.350 align:start position:0% figuring out how to get the PC to send HDMI<00:01:18.640> CC<00:01:19.400> signals<00:01:20.040> so<00:01:20.240> the<00:01:20.400> connected<00:01:20.759> AV 00:01:21.350 --> 00:01:21.360 align:start position:0% HDMI CC signals so the connected AV 00:01:21.360 --> 00:01:23.550 align:start position:0% HDMI CC signals so the connected AV receiver<00:01:21.720> and<00:01:21.920> Friends<00:01:22.640> realize<00:01:23.200> it's<00:01:23.400> time 00:01:23.550 --> 00:01:23.560 align:start position:0% receiver and Friends realize it's time 00:01:23.560 --> 00:01:25.870 align:start position:0% receiver and Friends realize it's time for<00:01:23.799> Action<00:01:24.479> feel<00:01:24.720> free<00:01:24.920> to<00:01:25.079> jump<00:01:25.320> to<00:01:25.479> the<00:01:25.640> one 00:01:25.870 --> 00:01:25.880 align:start position:0% for Action feel free to jump to the one 00:01:25.880 --> 00:01:28.390 align:start position:0% for Action feel free to jump to the one that<00:01:26.079> interests<00:01:26.600> you<00:01:26.920> most<00:01:27.320> oh<00:01:27.640> and<00:01:27.920> one<00:01:28.119> more 00:01:28.390 --> 00:01:28.400 align:start position:0% that interests you most oh and one more 00:01:28.400 --> 00:01:30.870 align:start position:0% that interests you most oh and one more thing<00:01:28.799> I<00:01:28.880> am<00:01:29.079> limiting<00:01:29.520> my<00:01:29.920> entire<00:01:30.280> project<00:01:30.640> to 00:01:30.870 --> 00:01:30.880 align:start position:0% thing I am limiting my entire project to 00:01:30.880 --> 00:01:33.830 align:start position:0% thing I am limiting my entire project to Windows<00:01:31.320> 11<00:01:31.880> and<00:01:32.200> regular<00:01:32.720> steam<00:01:33.280> but<00:01:33.680> there 00:01:33.830 --> 00:01:33.840 align:start position:0% Windows 11 and regular steam but there 00:01:33.840 --> 00:01:35.590 align:start position:0% Windows 11 and regular steam but there are<00:01:34.159> alternatives<00:01:34.840> out<00:01:35.040> there<00:01:35.200> that<00:01:35.399> might 00:01:35.590 --> 00:01:35.600 align:start position:0% are alternatives out there that might 00:01:35.600 --> 00:01:37.310 align:start position:0% are alternatives out there that might make<00:01:35.880> more<00:01:36.159> sense<00:01:36.520> depending<00:01:36.880> on<00:01:37.040> your 00:01:37.310 --> 00:01:37.320 align:start position:0% make more sense depending on your 00:01:37.320 --> 00:01:39.789 align:start position:0% make more sense depending on your hardware<00:01:37.799> and<00:01:38.079> needs<00:01:38.920> for<00:01:39.200> example<00:01:39.640> I 00:01:39.789 --> 00:01:39.799 align:start position:0% hardware and needs for example I 00:01:39.799 --> 00:01:41.950 align:start position:0% hardware and needs for example I recently<00:01:40.200> installed<00:01:40.680> basite<00:01:41.200> on<00:01:41.320> my<00:01:41.479> Legion 00:01:41.950 --> 00:01:41.960 align:start position:0% recently installed basite on my Legion 00:01:41.960 --> 00:01:43.910 align:start position:0% recently installed basite on my Legion go<00:01:42.200> and<00:01:42.360> I've<00:01:42.520> been<00:01:42.759> very<00:01:43.040> happy<00:01:43.360> with<00:01:43.520> it 00:01:43.910 --> 00:01:43.920 align:start position:0% go and I've been very happy with it 00:01:43.920 --> 00:01:45.749 align:start position:0% go and I've been very happy with it basite<00:01:44.360> is<00:01:44.520> basically<00:01:44.880> Steam<00:01:45.200> OS<00:01:45.560> that<00:01:45.680> you 00:01:45.749 --> 00:01:45.759 align:start position:0% basite is basically Steam OS that you 00:01:45.759 --> 00:01:47.870 align:start position:0% basite is basically Steam OS that you can<00:01:45.880> install<00:01:46.240> on<00:01:46.439> other<00:01:46.799> Hardware<00:01:47.439> currently 00:01:47.870 --> 00:01:47.880 align:start position:0% can install on other Hardware currently 00:01:47.880 --> 00:01:49.310 align:start position:0% can install on other Hardware currently there<00:01:48.000> are<00:01:48.159> a<00:01:48.240> number<00:01:48.479> of<00:01:48.600> handhelds<00:01:49.079> and 00:01:49.310 --> 00:01:49.320 align:start position:0% there are a number of handhelds and 00:01:49.320 --> 00:01:51.510 align:start position:0% there are a number of handhelds and laptops<00:01:49.759> supported<00:01:50.280> as<00:01:50.399> well<00:01:50.560> as<00:01:50.759> desktops 00:01:51.510 --> 00:01:51.520 align:start position:0% laptops supported as well as desktops 00:01:51.520 --> 00:01:54.069 align:start position:0% laptops supported as well as desktops and<00:01:51.680> home<00:01:52.000> theater<00:01:52.360> PCS<00:01:53.119> to<00:01:53.280> a<00:01:53.399> certain<00:01:53.680> degree 00:01:54.069 --> 00:01:54.079 align:start position:0% and home theater PCS to a certain degree 00:01:54.079 --> 00:01:55.950 align:start position:0% and home theater PCS to a certain degree bazide<00:01:54.560> is<00:01:54.680> built<00:01:54.920> for<00:01:55.079> the<00:01:55.240> experience<00:01:55.759> I'm 00:01:55.950 --> 00:01:55.960 align:start position:0% bazide is built for the experience I'm 00:01:55.960 --> 00:01:57.910 align:start position:0% bazide is built for the experience I'm trying<00:01:56.200> to<00:01:56.399> achieve<00:01:57.000> however<00:01:57.360> at<00:01:57.520> this<00:01:57.719> point 00:01:57.910 --> 00:01:57.920 align:start position:0% trying to achieve however at this point 00:01:57.920 --> 00:02:00.830 align:start position:0% trying to achieve however at this point in<00:01:58.159> time<00:01:58.520> Nvidia<00:01:58.920> gpus<00:01:59.360> are<00:01:59.560> not<00:02:00.119> supported 00:02:00.830 --> 00:02:00.840 align:start position:0% in time Nvidia gpus are not supported 00:02:00.840 --> 00:02:02.630 align:start position:0% in time Nvidia gpus are not supported well<00:02:01.200> technically<00:02:01.640> it<00:02:01.799> does<00:02:02.039> work<00:02:02.320> but<00:02:02.439> not 00:02:02.630 --> 00:02:02.640 align:start position:0% well technically it does work but not 00:02:02.640 --> 00:02:04.310 align:start position:0% well technically it does work but not without<00:02:02.920> sacrificing<00:02:03.399> a<00:02:03.520> large<00:02:03.799> chunk<00:02:04.119> of 00:02:04.310 --> 00:02:04.320 align:start position:0% without sacrificing a large chunk of 00:02:04.320 --> 00:02:06.950 align:start position:0% without sacrificing a large chunk of performance<00:02:05.200> or<00:02:05.399> so<00:02:05.640> I've<00:02:05.880> read<00:02:06.439> my<00:02:06.600> goal<00:02:06.799> was 00:02:06.950 --> 00:02:06.960 align:start position:0% performance or so I've read my goal was 00:02:06.960 --> 00:02:08.710 align:start position:0% performance or so I've read my goal was to<00:02:07.079> get<00:02:07.240> the<00:02:07.399> best<00:02:07.680> performance<00:02:08.280> out<00:02:08.399> of<00:02:08.560> my 00:02:08.710 --> 00:02:08.720 align:start position:0% to get the best performance out of my 00:02:08.720 --> 00:02:10.949 align:start position:0% to get the best performance out of my machine<00:02:09.160> so<00:02:09.319> I<00:02:09.440> didn't<00:02:09.640> give<00:02:09.840> this<00:02:09.959> a<00:02:10.160> try<00:02:10.560> but 00:02:10.949 --> 00:02:10.959 align:start position:0% machine so I didn't give this a try but 00:02:10.959 --> 00:02:12.670 align:start position:0% machine so I didn't give this a try but I<00:02:11.039> still<00:02:11.280> wanted<00:02:11.560> to<00:02:11.720> mention<00:02:12.000> it<00:02:12.239> as<00:02:12.360> it's<00:02:12.520> a 00:02:12.670 --> 00:02:12.680 align:start position:0% I still wanted to mention it as it's a 00:02:12.680 --> 00:02:14.589 align:start position:0% I still wanted to mention it as it's a great<00:02:13.000> project<00:02:13.280> to<00:02:13.440> keep<00:02:13.599> an<00:02:13.760> eye<00:02:13.959> on<00:02:14.440> all 00:02:14.589 --> 00:02:14.599 align:start position:0% great project to keep an eye on all 00:02:14.599 --> 00:02:16.270 align:start position:0% great project to keep an eye on all right<00:02:14.879> time<00:02:15.040> to<00:02:15.160> start<00:02:15.400> into<00:02:15.640> chronological 00:02:16.270 --> 00:02:16.280 align:start position:0% right time to start into chronological 00:02:16.280 --> 00:02:20.430 align:start position:0% right time to start into chronological order<00:02:16.720> as<00:02:16.879> in<00:02:17.160> the<00:02:17.360> power<00:02:17.640> on 00:02:20.430 --> 00:02:20.440 align:start position:0% 00:02:20.440 --> 00:02:22.990 align:start position:0% sequence<00:02:21.440> the<00:02:21.599> idea<00:02:21.879> is<00:02:22.040> as<00:02:22.200> follows<00:02:22.720> I<00:02:22.800> want 00:02:22.990 --> 00:02:23.000 align:start position:0% sequence the idea is as follows I want 00:02:23.000 --> 00:02:25.030 align:start position:0% sequence the idea is as follows I want the<00:02:23.160> PC<00:02:23.480> to<00:02:23.599> turn<00:02:23.959> on<00:02:24.200> when<00:02:24.319> I<00:02:24.440> turn<00:02:24.640> on<00:02:24.840> the 00:02:25.030 --> 00:02:25.040 align:start position:0% the PC to turn on when I turn on the 00:02:25.040 --> 00:02:27.509 align:start position:0% the PC to turn on when I turn on the controller<00:02:26.040> both<00:02:26.239> the<00:02:26.400> series<00:02:26.760> X<00:02:27.160> and<00:02:27.360> the 00:02:27.509 --> 00:02:27.519 align:start position:0% controller both the series X and the 00:02:27.519 --> 00:02:29.869 align:start position:0% controller both the series X and the ps5s<00:02:28.120> Dual<00:02:28.440> sense<00:02:28.760> controllers<00:02:29.319> are<00:02:29.519> comp 00:02:29.869 --> 00:02:29.879 align:start position:0% ps5s Dual sense controllers are comp 00:02:29.879 --> 00:02:31.630 align:start position:0% ps5s Dual sense controllers are comp comp<00:02:30.000> able<00:02:30.280> with<00:02:30.440> Windows<00:02:30.920> these<00:02:31.160> days<00:02:31.400> and 00:02:31.630 --> 00:02:31.640 align:start position:0% comp able with Windows these days and 00:02:31.640 --> 00:02:33.869 align:start position:0% comp able with Windows these days and can<00:02:31.840> easily<00:02:32.160> be<00:02:32.319> paired<00:02:32.680> by<00:02:32.800> a<00:02:32.920> Bluetooth<00:02:33.519> but 00:02:33.869 --> 00:02:33.879 align:start position:0% can easily be paired by a Bluetooth but 00:02:33.879 --> 00:02:36.430 align:start position:0% can easily be paired by a Bluetooth but that's<00:02:34.080> where<00:02:34.239> the<00:02:34.440> problem<00:02:34.879> lies<00:02:35.440> Bluetooth 00:02:36.430 --> 00:02:36.440 align:start position:0% that's where the problem lies Bluetooth 00:02:36.440 --> 00:02:38.509 align:start position:0% that's where the problem lies Bluetooth from<00:02:36.640> what<00:02:36.760> I<00:02:37.200> understand<00:02:37.480> windows<00:02:37.920> or<00:02:38.040> the<00:02:38.200> PC 00:02:38.509 --> 00:02:38.519 align:start position:0% from what I understand windows or the PC 00:02:38.519 --> 00:02:40.030 align:start position:0% from what I understand windows or the PC to<00:02:38.640> be<00:02:38.760> more<00:02:38.959> precise<00:02:39.360> won't<00:02:39.640> keep<00:02:39.840> these 00:02:40.030 --> 00:02:40.040 align:start position:0% to be more precise won't keep these 00:02:40.040 --> 00:02:42.270 align:start position:0% to be more precise won't keep these connections<00:02:40.560> up<00:02:40.800> or<00:02:41.000> active<00:02:41.319> after<00:02:41.599> shutdown 00:02:42.270 --> 00:02:42.280 align:start position:0% connections up or active after shutdown 00:02:42.280 --> 00:02:44.509 align:start position:0% connections up or active after shutdown which<00:02:42.400> is<00:02:42.800> kind<00:02:42.920> of<00:02:43.120> obvious<00:02:43.599> but<00:02:43.879> still 00:02:44.509 --> 00:02:44.519 align:start position:0% which is kind of obvious but still 00:02:44.519 --> 00:02:46.630 align:start position:0% which is kind of obvious but still meaning<00:02:45.000> it<00:02:45.200> can't<00:02:45.480> react<00:02:45.920> to<00:02:46.159> it<00:02:46.440> from 00:02:46.630 --> 00:02:46.640 align:start position:0% meaning it can't react to it from 00:02:46.640 --> 00:02:48.750 align:start position:0% meaning it can't react to it from neither<00:02:47.040> Hardware<00:02:47.440> nor<00:02:47.640> software<00:02:48.159> standpoint 00:02:48.750 --> 00:02:48.760 align:start position:0% neither Hardware nor software standpoint 00:02:48.760 --> 00:02:50.229 align:start position:0% neither Hardware nor software standpoint therefore<00:02:49.080> the<00:02:49.239> devices<00:02:49.599> are<00:02:49.760> essentially 00:02:50.229 --> 00:02:50.239 align:start position:0% therefore the devices are essentially 00:02:50.239 --> 00:02:52.670 align:start position:0% therefore the devices are essentially left<00:02:50.599> in<00:02:50.760> the<00:02:50.959> dark<00:02:51.720> what<00:02:51.840> about<00:02:52.080> the<00:02:52.280> Sleep 00:02:52.670 --> 00:02:52.680 align:start position:0% left in the dark what about the Sleep 00:02:52.680 --> 00:02:54.910 align:start position:0% left in the dark what about the Sleep State<00:02:53.200> then<00:02:53.879> well<00:02:54.200> that<00:02:54.360> doesn't<00:02:54.560> seem<00:02:54.760> to 00:02:54.910 --> 00:02:54.920 align:start position:0% State then well that doesn't seem to 00:02:54.920 --> 00:02:56.710 align:start position:0% State then well that doesn't seem to work<00:02:55.159> either<00:02:55.480> or<00:02:55.720> I<00:02:55.840> could<00:02:56.040> for<00:02:56.239> the<00:02:56.360> love<00:02:56.519> of 00:02:56.710 --> 00:02:56.720 align:start position:0% work either or I could for the love of 00:02:56.720 --> 00:02:59.270 align:start position:0% work either or I could for the love of God<00:02:57.040> not<00:02:57.280> figure<00:02:57.599> out<00:02:57.959> how<00:02:58.599> I<00:02:58.680> believe<00:02:58.959> this<00:02:59.080> is 00:02:59.270 --> 00:02:59.280 align:start position:0% God not figure out how I believe this is 00:02:59.280 --> 00:03:01.110 align:start position:0% God not figure out how I believe this is because<00:02:59.480> of<00:02:59.640> how<00:02:59.879> how<00:03:00.040> Windows<00:03:00.360> 11<00:03:00.879> power 00:03:01.110 --> 00:03:01.120 align:start position:0% because of how how Windows 11 power 00:03:01.120 --> 00:03:03.070 align:start position:0% because of how how Windows 11 power manages<00:03:01.599> Bluetooth<00:03:02.239> there<00:03:02.519> actually<00:03:02.720> used<00:03:02.959> to 00:03:03.070 --> 00:03:03.080 align:start position:0% manages Bluetooth there actually used to 00:03:03.080 --> 00:03:04.869 align:start position:0% manages Bluetooth there actually used to be<00:03:03.200> a<00:03:03.280> setting<00:03:03.640> called<00:03:03.959> allow<00:03:04.319> this<00:03:04.519> device<00:03:04.760> to 00:03:04.869 --> 00:03:04.879 align:start position:0% be a setting called allow this device to 00:03:04.879 --> 00:03:06.430 align:start position:0% be a setting called allow this device to wake<00:03:05.159> the<00:03:05.319> computer<00:03:05.840> under<00:03:06.080> the<00:03:06.239> power 00:03:06.430 --> 00:03:06.440 align:start position:0% wake the computer under the power 00:03:06.440 --> 00:03:08.509 align:start position:0% wake the computer under the power management<00:03:06.879> tab<00:03:07.080> in<00:03:07.280> device<00:03:07.519> manager<00:03:08.280> but<00:03:08.400> it 00:03:08.509 --> 00:03:08.519 align:start position:0% management tab in device manager but it 00:03:08.519 --> 00:03:10.390 align:start position:0% management tab in device manager but it has<00:03:08.680> since<00:03:08.920> been<00:03:09.120> removed<00:03:09.560> four<00:03:09.879> Bluetooth 00:03:10.390 --> 00:03:10.400 align:start position:0% has since been removed four Bluetooth 00:03:10.400 --> 00:03:12.509 align:start position:0% has since been removed four Bluetooth devices<00:03:10.760> onto<00:03:11.040> the<00:03:11.200> premise<00:03:11.560> that<00:03:11.720> modern<00:03:12.120> PCS 00:03:12.509 --> 00:03:12.519 align:start position:0% devices onto the premise that modern PCS 00:03:12.519 --> 00:03:14.670 align:start position:0% devices onto the premise that modern PCS are<00:03:12.760> smart<00:03:13.159> enough<00:03:13.400> to<00:03:13.560> figure<00:03:13.840> this<00:03:14.000> out<00:03:14.280> by 00:03:14.670 --> 00:03:14.680 align:start position:0% are smart enough to figure this out by 00:03:14.680 --> 00:03:16.830 align:start position:0% are smart enough to figure this out by themselves<00:03:15.560> this<00:03:15.720> might<00:03:15.959> actually<00:03:16.200> be<00:03:16.440> true 00:03:16.830 --> 00:03:16.840 align:start position:0% themselves this might actually be true 00:03:16.840 --> 00:03:19.070 align:start position:0% themselves this might actually be true and<00:03:17.200> if<00:03:17.400> PCS<00:03:17.840> resemble<00:03:18.280> their<00:03:18.440> owners<00:03:18.920> just 00:03:19.070 --> 00:03:19.080 align:start position:0% and if PCS resemble their owners just 00:03:19.080 --> 00:03:20.710 align:start position:0% and if PCS resemble their owners just like<00:03:19.239> docs<00:03:19.599> do<00:03:19.920> then<00:03:20.080> it<00:03:20.200> would<00:03:20.440> actually 00:03:20.710 --> 00:03:20.720 align:start position:0% like docs do then it would actually 00:03:20.720 --> 00:03:22.789 align:start position:0% like docs do then it would actually explain<00:03:21.120> why<00:03:21.319> mine<00:03:21.560> is<00:03:21.720> so 00:03:22.789 --> 00:03:22.799 align:start position:0% explain why mine is so 00:03:22.799 --> 00:03:25.270 align:start position:0% explain why mine is so stupid<00:03:23.799> if<00:03:23.920> you're<00:03:24.120> curious<00:03:24.480> in<00:03:24.680> command<00:03:25.080> line 00:03:25.270 --> 00:03:25.280 align:start position:0% stupid if you're curious in command line 00:03:25.280 --> 00:03:27.750 align:start position:0% stupid if you're curious in command line you<00:03:25.360> can<00:03:25.519> type<00:03:25.720> in<00:03:26.000> power<00:03:26.280> CFG<00:03:27.000> then<00:03:27.319> Dash 00:03:27.750 --> 00:03:27.760 align:start position:0% you can type in power CFG then Dash 00:03:27.760 --> 00:03:29.789 align:start position:0% you can type in power CFG then Dash device<00:03:28.159> query<00:03:28.640> and<00:03:28.799> then<00:03:29.040> wake<00:03:29.360> on<00:03:29.480> the<00:03:29.599> line 00:03:29.789 --> 00:03:29.799 align:start position:0% device query and then wake on the line 00:03:29.799 --> 00:03:31.350 align:start position:0% device query and then wake on the line and<00:03:29.920> armed<00:03:30.319> which<00:03:30.400> will<00:03:30.560> give<00:03:30.680> you<00:03:30.799> a<00:03:30.959> list<00:03:31.159> of 00:03:31.350 --> 00:03:31.360 align:start position:0% and armed which will give you a list of 00:03:31.360 --> 00:03:33.390 align:start position:0% and armed which will give you a list of peripherals<00:03:31.959> that<00:03:32.159> have<00:03:32.439> that<00:03:32.720> power<00:03:33.120> none<00:03:33.319> of 00:03:33.390 --> 00:03:33.400 align:start position:0% peripherals that have that power none of 00:03:33.400 --> 00:03:35.149 align:start position:0% peripherals that have that power none of the<00:03:33.519> Bluetooth<00:03:33.920> devices<00:03:34.319> I<00:03:34.480> tried<00:03:34.799> work 00:03:35.149 --> 00:03:35.159 align:start position:0% the Bluetooth devices I tried work 00:03:35.159 --> 00:03:37.350 align:start position:0% the Bluetooth devices I tried work though<00:03:35.439> including<00:03:35.879> keyboards<00:03:36.799> so<00:03:37.000> how<00:03:37.120> are<00:03:37.239> we 00:03:37.350 --> 00:03:37.360 align:start position:0% though including keyboards so how are we 00:03:37.360 --> 00:03:39.229 align:start position:0% though including keyboards so how are we going<00:03:37.519> to<00:03:37.760> trigger<00:03:38.000> the<00:03:38.120> PC<00:03:38.439> via<00:03:38.680> Bluetooth 00:03:39.229 --> 00:03:39.239 align:start position:0% going to trigger the PC via Bluetooth 00:03:39.239 --> 00:03:41.390 align:start position:0% going to trigger the PC via Bluetooth then<00:03:39.720> well<00:03:40.120> we<00:03:40.239> don't<00:03:40.640> we're<00:03:40.840> going<00:03:40.959> to<00:03:41.080> use<00:03:41.239> a 00:03:41.390 --> 00:03:41.400 align:start position:0% then well we don't we're going to use a 00:03:41.400 --> 00:03:44.110 align:start position:0% then well we don't we're going to use a 2.4<00:03:41.920> GHz<00:03:42.280> dongle<00:03:42.680> instead<00:03:43.439> there<00:03:43.560> are<00:03:43.720> a<00:03:43.840> few 00:03:44.110 --> 00:03:44.120 align:start position:0% 2.4 GHz dongle instead there are a few 00:03:44.120 --> 00:03:46.470 align:start position:0% 2.4 GHz dongle instead there are a few options<00:03:44.480> for<00:03:44.760> this<00:03:45.040> all<00:03:45.200> of<00:03:45.319> it<00:03:45.519> involve<00:03:46.000> money 00:03:46.470 --> 00:03:46.480 align:start position:0% options for this all of it involve money 00:03:46.480 --> 00:03:47.789 align:start position:0% options for this all of it involve money unless<00:03:46.720> you<00:03:46.840> have<00:03:47.000> one<00:03:47.159> of<00:03:47.280> the<00:03:47.480> now 00:03:47.789 --> 00:03:47.799 align:start position:0% unless you have one of the now 00:03:47.799 --> 00:03:50.110 align:start position:0% unless you have one of the now discontinued<00:03:48.760> official<00:03:49.200> Xbox<00:03:49.680> wireless 00:03:50.110 --> 00:03:50.120 align:start position:0% discontinued official Xbox wireless 00:03:50.120 --> 00:03:52.470 align:start position:0% discontinued official Xbox wireless controller<00:03:50.599> adapters<00:03:51.040> for<00:03:51.280> Windows<00:03:52.120> and<00:03:52.319> of 00:03:52.470 --> 00:03:52.480 align:start position:0% controller adapters for Windows and of 00:03:52.480 --> 00:03:54.910 align:start position:0% controller adapters for Windows and of course<00:03:52.799> a<00:03:53.000> compatible<00:03:53.480> Xbox<00:03:53.959> controller<00:03:54.799> this 00:03:54.910 --> 00:03:54.920 align:start position:0% course a compatible Xbox controller this 00:03:54.920 --> 00:03:56.990 align:start position:0% course a compatible Xbox controller this was<00:03:55.040> released<00:03:55.400> during<00:03:55.640> the<00:03:55.799> Xbox<00:03:56.280> One<00:03:56.599> era 00:03:56.990 --> 00:03:57.000 align:start position:0% was released during the Xbox One era 00:03:57.000 --> 00:03:58.229 align:start position:0% was released during the Xbox One era before<00:03:57.200> the<00:03:57.360> controller<00:03:57.760> switched<00:03:58.120> to 00:03:58.229 --> 00:03:58.239 align:start position:0% before the controller switched to 00:03:58.239 --> 00:03:59.789 align:start position:0% before the controller switched to Bluetooth<00:03:58.879> I<00:03:59.040> unfortunately<00:03:59.439> couldn't<00:03:59.599> get 00:03:59.789 --> 00:03:59.799 align:start position:0% Bluetooth I unfortunately couldn't get 00:03:59.799 --> 00:04:01.470 align:start position:0% Bluetooth I unfortunately couldn't get get<00:03:59.879> a<00:03:59.920> hold<00:04:00.079> of<00:04:00.200> one<00:04:00.319> in<00:04:00.519> time<00:04:00.799> but<00:04:01.159> there<00:04:01.280> are 00:04:01.470 --> 00:04:01.480 align:start position:0% get a hold of one in time but there are 00:04:01.480 --> 00:04:03.630 align:start position:0% get a hold of one in time but there are several<00:04:01.799> listings<00:04:02.200> on<00:04:02.400> eBay<00:04:03.000> alternatively 00:04:03.630 --> 00:04:03.640 align:start position:0% several listings on eBay alternatively 00:04:03.640 --> 00:04:05.750 align:start position:0% several listings on eBay alternatively you<00:04:03.720> can<00:04:03.920> get<00:04:04.040> a<00:04:04.239> third-party<00:04:04.959> one<00:04:05.280> but<00:04:05.560> be 00:04:05.750 --> 00:04:05.760 align:start position:0% you can get a third-party one but be 00:04:05.760 --> 00:04:07.750 align:start position:0% you can get a third-party one but be careful<00:04:06.200> as<00:04:06.319> I've<00:04:06.519> read<00:04:06.760> reports<00:04:07.239> from<00:04:07.480> other 00:04:07.750 --> 00:04:07.760 align:start position:0% careful as I've read reports from other 00:04:07.760 --> 00:04:09.470 align:start position:0% careful as I've read reports from other users<00:04:08.079> that<00:04:08.519> sometimes<00:04:09.000> it's<00:04:09.159> just<00:04:09.319> a 00:04:09.470 --> 00:04:09.480 align:start position:0% users that sometimes it's just a 00:04:09.480 --> 00:04:11.910 align:start position:0% users that sometimes it's just a Bluetooth<00:04:09.920> dongle<00:04:10.239> in<00:04:10.480> Disguise<00:04:11.480> not<00:04:11.760> this 00:04:11.910 --> 00:04:11.920 align:start position:0% Bluetooth dongle in Disguise not this 00:04:11.920 --> 00:04:13.309 align:start position:0% Bluetooth dongle in Disguise not this one<00:04:12.200> though<00:04:12.400> this<00:04:12.560> one<00:04:12.720> from<00:04:12.840> a<00:04:12.959> company 00:04:13.309 --> 00:04:13.319 align:start position:0% one though this one from a company 00:04:13.319 --> 00:04:15.949 align:start position:0% one though this one from a company called<00:04:13.879> ax<00:04:14.439> Fe<00:04:14.879> or<00:04:15.200> however<00:04:15.360> you<00:04:15.519> pronounce 00:04:15.949 --> 00:04:15.959 align:start position:0% called ax Fe or however you pronounce 00:04:15.959 --> 00:04:17.590 align:start position:0% called ax Fe or however you pronounce that<00:04:16.160> name<00:04:16.479> which<00:04:16.600> I<00:04:16.720> found<00:04:16.919> on<00:04:17.160> Amazon 00:04:17.590 --> 00:04:17.600 align:start position:0% that name which I found on Amazon 00:04:17.600 --> 00:04:19.590 align:start position:0% that name which I found on Amazon immediately<00:04:18.000> got<00:04:18.239> recognized<00:04:18.840> as<00:04:18.959> an<00:04:19.160> Xbox 00:04:19.590 --> 00:04:19.600 align:start position:0% immediately got recognized as an Xbox 00:04:19.600 --> 00:04:21.550 align:start position:0% immediately got recognized as an Xbox controller<00:04:20.040> adapter<00:04:20.400> and<00:04:20.600> device<00:04:20.919> manager 00:04:21.550 --> 00:04:21.560 align:start position:0% controller adapter and device manager 00:04:21.560 --> 00:04:22.909 align:start position:0% controller adapter and device manager and<00:04:21.720> after<00:04:21.919> double-checking<00:04:22.479> its<00:04:22.639> wake 00:04:22.909 --> 00:04:22.919 align:start position:0% and after double-checking its wake 00:04:22.919 --> 00:04:25.189 align:start position:0% and after double-checking its wake privileges<00:04:23.520> and<00:04:23.800> giving<00:04:24.000> it<00:04:24.120> a<00:04:24.280> try<00:04:24.840> I<00:04:24.960> can 00:04:25.189 --> 00:04:25.199 align:start position:0% privileges and giving it a try I can 00:04:25.199 --> 00:04:26.950 align:start position:0% privileges and giving it a try I can confirm<00:04:25.960> it 00:04:26.950 --> 00:04:26.960 align:start position:0% confirm it 00:04:26.960 --> 00:04:29.710 align:start position:0% confirm it works<00:04:27.960> by<00:04:28.080> the<00:04:28.199> way<00:04:28.360> if<00:04:28.479> you<00:04:28.639> didn't<00:04:28.880> know<00:04:29.199> Xbox 00:04:29.710 --> 00:04:29.720 align:start position:0% works by the way if you didn't know Xbox 00:04:29.720 --> 00:04:31.310 align:start position:0% works by the way if you didn't know Xbox controllers<00:04:30.080> can<00:04:30.360> actually<00:04:30.560> be<00:04:30.759> paired<00:04:31.080> with 00:04:31.310 --> 00:04:31.320 align:start position:0% controllers can actually be paired with 00:04:31.320 --> 00:04:33.469 align:start position:0% controllers can actually be paired with two<00:04:31.600> devices<00:04:32.080> at<00:04:32.199> the<00:04:32.360> same<00:04:32.680> time<00:04:33.080> in<00:04:33.199> order<00:04:33.400> to 00:04:33.469 --> 00:04:33.479 align:start position:0% two devices at the same time in order to 00:04:33.479 --> 00:04:35.110 align:start position:0% two devices at the same time in order to switch<00:04:33.759> to<00:04:33.880> the<00:04:34.000> second<00:04:34.280> profile<00:04:34.639> just<00:04:34.840> double 00:04:35.110 --> 00:04:35.120 align:start position:0% switch to the second profile just double 00:04:35.120 --> 00:04:36.590 align:start position:0% switch to the second profile just double click<00:04:35.280> on<00:04:35.400> the<00:04:35.520> pairing<00:04:35.840> button<00:04:36.320> and<00:04:36.400> then 00:04:36.590 --> 00:04:36.600 align:start position:0% click on the pairing button and then 00:04:36.600 --> 00:04:39.029 align:start position:0% click on the pairing button and then hold<00:04:36.919> to<00:04:37.120> pair<00:04:37.400> with<00:04:37.560> the<00:04:37.720> second<00:04:38.080> device<00:04:38.960> you 00:04:39.029 --> 00:04:39.039 align:start position:0% hold to pair with the second device you 00:04:39.039 --> 00:04:40.950 align:start position:0% hold to pair with the second device you can<00:04:39.240> then<00:04:39.440> just<00:04:39.639> switch<00:04:40.000> back<00:04:40.120> and<00:04:40.320> forth<00:04:40.720> by 00:04:40.950 --> 00:04:40.960 align:start position:0% can then just switch back and forth by 00:04:40.960 --> 00:04:42.870 align:start position:0% can then just switch back and forth by double<00:04:41.280> tapping<00:04:41.919> this<00:04:42.039> way<00:04:42.199> you<00:04:42.320> can<00:04:42.479> have<00:04:42.600> it 00:04:42.870 --> 00:04:42.880 align:start position:0% double tapping this way you can have it 00:04:42.880 --> 00:04:45.029 align:start position:0% double tapping this way you can have it remain<00:04:43.160> connected<00:04:43.600> to<00:04:43.759> your<00:04:43.960> Xbox<00:04:44.639> and<00:04:44.800> your 00:04:45.029 --> 00:04:45.039 align:start position:0% remain connected to your Xbox and your 00:04:45.039 --> 00:04:47.550 align:start position:0% remain connected to your Xbox and your DIY<00:04:45.800> Xbox<00:04:46.639> if<00:04:46.720> you<00:04:46.840> don't<00:04:47.039> own<00:04:47.320> one<00:04:47.440> of 00:04:47.550 --> 00:04:47.560 align:start position:0% DIY Xbox if you don't own one of 00:04:47.560 --> 00:04:49.430 align:start position:0% DIY Xbox if you don't own one of Microsoft's<00:04:48.120> Best<00:04:48.280> Hardware<00:04:48.680> Designs<00:04:49.120> ever 00:04:49.430 --> 00:04:49.440 align:start position:0% Microsoft's Best Hardware Designs ever 00:04:49.440 --> 00:04:51.070 align:start position:0% Microsoft's Best Hardware Designs ever there's<00:04:49.759> also<00:04:50.039> the<00:04:50.240> option<00:04:50.520> of<00:04:50.680> buying<00:04:50.919> an 00:04:51.070 --> 00:04:51.080 align:start position:0% there's also the option of buying an 00:04:51.080 --> 00:04:53.189 align:start position:0% there's also the option of buying an entirely<00:04:51.600> different<00:04:51.919> controller<00:04:52.759> one<00:04:53.039> that 00:04:53.189 --> 00:04:53.199 align:start position:0% entirely different controller one that 00:04:53.199 --> 00:04:56.189 align:start position:0% entirely different controller one that ships<00:04:53.720> with<00:04:54.039> a<00:04:54.199> 2.4<00:04:54.720> GHz<00:04:55.080> dongle<00:04:55.639> for<00:04:55.800> example 00:04:56.189 --> 00:04:56.199 align:start position:0% ships with a 2.4 GHz dongle for example 00:04:56.199 --> 00:04:59.029 align:start position:0% ships with a 2.4 GHz dongle for example the<00:04:56.360> Razer<00:04:56.759> Wolverine<00:04:57.360> V3<00:04:58.120> Pro<00:04:58.560> or<00:04:58.680> a<00:04:58.840> much 00:04:59.029 --> 00:04:59.039 align:start position:0% the Razer Wolverine V3 Pro or a much 00:04:59.039 --> 00:05:00.629 align:start position:0% the Razer Wolverine V3 Pro or a much cheaper<00:04:59.320> alter<00:04:59.680> alternative<00:05:00.199> such<00:05:00.360> as<00:05:00.520> the 00:05:00.629 --> 00:05:00.639 align:start position:0% cheaper alter alternative such as the 00:05:00.639 --> 00:05:04.310 align:start position:0% cheaper alter alternative such as the 8bit<00:05:01.199> 2<00:05:01.600> ultimate<00:05:02.120> 2.4g<00:05:03.120> controller<00:05:04.000> I<00:05:04.120> can't 00:05:04.310 --> 00:05:04.320 align:start position:0% 8bit 2 ultimate 2.4g controller I can't 00:05:04.320 --> 00:05:06.390 align:start position:0% 8bit 2 ultimate 2.4g controller I can't speak<00:05:04.520> for<00:05:04.680> the<00:05:04.759> 8bit<00:05:05.280> 2<00:05:05.600> but<00:05:05.759> the<00:05:05.880> Wolverine 00:05:06.390 --> 00:05:06.400 align:start position:0% speak for the 8bit 2 but the Wolverine 00:05:06.400 --> 00:05:08.390 align:start position:0% speak for the 8bit 2 but the Wolverine worked<00:05:06.840> just<00:05:07.080> as<00:05:07.280> well<00:05:07.600> with<00:05:07.800> it<00:05:07.960> showing<00:05:08.280> up 00:05:08.390 --> 00:05:08.400 align:start position:0% worked just as well with it showing up 00:05:08.400 --> 00:05:09.909 align:start position:0% worked just as well with it showing up in<00:05:08.560> the<00:05:08.680> power<00:05:08.960> config<00:05:09.400> just<00:05:09.600> like<00:05:09.759> the 00:05:09.909 --> 00:05:09.919 align:start position:0% in the power config just like the 00:05:09.919 --> 00:05:12.230 align:start position:0% in the power config just like the adapter<00:05:10.800> of<00:05:10.919> course<00:05:11.160> if<00:05:11.280> you<00:05:11.560> have<00:05:11.680> a<00:05:11.840> keyboard 00:05:12.230 --> 00:05:12.240 align:start position:0% adapter of course if you have a keyboard 00:05:12.240 --> 00:05:14.270 align:start position:0% adapter of course if you have a keyboard or<00:05:12.360> a<00:05:12.479> mouse<00:05:12.759> that<00:05:12.880> also<00:05:13.080> uses<00:05:13.320> a<00:05:13.440> 2.4<00:05:13.919> GHz 00:05:14.270 --> 00:05:14.280 align:start position:0% or a mouse that also uses a 2.4 GHz 00:05:14.280 --> 00:05:16.230 align:start position:0% or a mouse that also uses a 2.4 GHz connection<00:05:14.720> you<00:05:14.840> don't<00:05:15.120> need<00:05:15.440> any<00:05:15.720> of<00:05:15.919> this 00:05:16.230 --> 00:05:16.240 align:start position:0% connection you don't need any of this 00:05:16.240 --> 00:05:17.710 align:start position:0% connection you don't need any of this but<00:05:16.400> my<00:05:16.560> goal<00:05:16.759> was<00:05:16.880> to<00:05:17.080> have<00:05:17.360> just<00:05:17.520> a 00:05:17.710 --> 00:05:17.720 align:start position:0% but my goal was to have just a 00:05:17.720 --> 00:05:19.550 align:start position:0% but my goal was to have just a controller<00:05:18.120> in<00:05:18.199> the<00:05:18.319> living<00:05:18.560> room<00:05:19.199> just<00:05:19.400> like 00:05:19.550 --> 00:05:19.560 align:start position:0% controller in the living room just like 00:05:19.560 --> 00:05:22.510 align:start position:0% controller in the living room just like with<00:05:19.680> the<00:05:19.800> PS5<00:05:20.360> and<00:05:20.479> the<00:05:20.639> Xbox<00:05:21.080> series<00:05:21.520> X 00:05:22.510 --> 00:05:22.520 align:start position:0% with the PS5 and the Xbox series X 00:05:22.520 --> 00:05:25.110 align:start position:0% with the PS5 and the Xbox series X before<00:05:22.759> I<00:05:22.880> wrap<00:05:23.199> this<00:05:23.360> chapter<00:05:23.840> Ops<00:05:24.520> one<00:05:24.800> last 00:05:25.110 --> 00:05:25.120 align:start position:0% before I wrap this chapter Ops one last 00:05:25.120 --> 00:05:27.390 align:start position:0% before I wrap this chapter Ops one last way<00:05:25.360> and<00:05:25.680> that<00:05:25.759> is<00:05:25.880> using<00:05:26.160> a<00:05:26.360> smart<00:05:26.720> plug<00:05:27.319> if 00:05:27.390 --> 00:05:27.400 align:start position:0% way and that is using a smart plug if 00:05:27.400 --> 00:05:29.710 align:start position:0% way and that is using a smart plug if you<00:05:27.520> got<00:05:27.759> smart<00:05:28.160> or<00:05:28.479> dumb<00:05:28.800> home<00:05:29.039> appliances 00:05:29.710 --> 00:05:29.720 align:start position:0% you got smart or dumb home appliances 00:05:29.720 --> 00:05:31.350 align:start position:0% you got smart or dumb home appliances you<00:05:29.800> might<00:05:29.960> be<00:05:30.160> familiar<00:05:30.639> with<00:05:30.840> these<00:05:31.120> or 00:05:31.350 --> 00:05:31.360 align:start position:0% you might be familiar with these or 00:05:31.360 --> 00:05:33.110 align:start position:0% you might be familiar with these or similar<00:05:31.800> plugs<00:05:32.240> they<00:05:32.400> essentially<00:05:32.800> allow<00:05:33.039> you 00:05:33.110 --> 00:05:33.120 align:start position:0% similar plugs they essentially allow you 00:05:33.120 --> 00:05:35.230 align:start position:0% similar plugs they essentially allow you to<00:05:33.280> control<00:05:33.639> devices<00:05:34.080> by<00:05:34.280> giving<00:05:34.560> or<00:05:34.800> cutting 00:05:35.230 --> 00:05:35.240 align:start position:0% to control devices by giving or cutting 00:05:35.240 --> 00:05:38.189 align:start position:0% to control devices by giving or cutting power<00:05:35.560> to<00:05:35.840> them<00:05:36.360> if<00:05:36.440> I<00:05:36.560> set<00:05:36.840> AC<00:05:37.319> back<00:05:37.560> to<00:05:37.880> always 00:05:38.189 --> 00:05:38.199 align:start position:0% power to them if I set AC back to always 00:05:38.199 --> 00:05:40.629 align:start position:0% power to them if I set AC back to always on<00:05:38.479> in<00:05:38.639> my<00:05:38.840> BIOS<00:05:39.280> the<00:05:39.520> PC<00:05:39.800> will<00:05:40.000> power<00:05:40.240> on<00:05:40.479> when 00:05:40.629 --> 00:05:40.639 align:start position:0% on in my BIOS the PC will power on when 00:05:40.639 --> 00:05:43.029 align:start position:0% on in my BIOS the PC will power on when the<00:05:40.800> plug<00:05:41.080> is<00:05:41.360> activated<00:05:42.000> thus<00:05:42.280> also<00:05:42.639> remotely 00:05:43.029 --> 00:05:43.039 align:start position:0% the plug is activated thus also remotely 00:05:43.039 --> 00:05:45.749 align:start position:0% the plug is activated thus also remotely turning<00:05:43.360> on<00:05:43.600> my<00:05:43.800> PC<00:05:44.479> it's<00:05:44.639> not<00:05:44.800> as<00:05:45.080> elegant<00:05:45.600> as 00:05:45.749 --> 00:05:45.759 align:start position:0% turning on my PC it's not as elegant as 00:05:45.759 --> 00:05:47.550 align:start position:0% turning on my PC it's not as elegant as the<00:05:45.919> controller<00:05:46.440> by<00:05:46.600> itself<00:05:47.120> but<00:05:47.240> it<00:05:47.400> might 00:05:47.550 --> 00:05:47.560 align:start position:0% the controller by itself but it might 00:05:47.560 --> 00:05:49.270 align:start position:0% the controller by itself but it might still<00:05:47.759> be<00:05:47.880> a<00:05:48.039> solution<00:05:48.440> for<00:05:48.720> some<00:05:49.080> and 00:05:49.270 --> 00:05:49.280 align:start position:0% still be a solution for some and 00:05:49.280 --> 00:05:51.350 align:start position:0% still be a solution for some and probably<00:05:49.560> more<00:05:49.759> energy<00:05:50.160> efficient<00:05:50.720> as<00:05:50.919> the<00:05:51.080> PC 00:05:51.350 --> 00:05:51.360 align:start position:0% probably more energy efficient as the PC 00:05:51.360 --> 00:05:53.469 align:start position:0% probably more energy efficient as the PC is<00:05:51.479> taken<00:05:51.720> from<00:05:51.880> the<00:05:52.039> grid<00:05:52.360> entirely<00:05:53.280> by<00:05:53.400> the 00:05:53.469 --> 00:05:53.479 align:start position:0% is taken from the grid entirely by the 00:05:53.479 --> 00:05:55.029 align:start position:0% is taken from the grid entirely by the way<00:05:53.720> I<00:05:53.880> made<00:05:54.039> a<00:05:54.160> whole<00:05:54.360> video<00:05:54.600> about<00:05:54.800> power 00:05:55.029 --> 00:05:55.039 align:start position:0% way I made a whole video about power 00:05:55.039 --> 00:05:56.469 align:start position:0% way I made a whole video about power consumption<00:05:55.600> and<00:05:55.840> how<00:05:56.000> you<00:05:56.160> could 00:05:56.469 --> 00:05:56.479 align:start position:0% consumption and how you could 00:05:56.479 --> 00:05:58.430 align:start position:0% consumption and how you could potentially<00:05:56.880> save<00:05:57.160> some<00:05:57.360> money<00:05:57.600> with<00:05:57.800> these<00:05:58.319> I 00:05:58.430 --> 00:05:58.440 align:start position:0% potentially save some money with these I 00:05:58.440 --> 00:05:59.710 align:start position:0% potentially save some money with these I have<00:05:58.520> to<00:05:58.639> warn<00:05:58.800> you<00:05:58.960> though<00:05:59.080> it's<00:05:59.199> about<00:05:59.360> 2<00:05:59.639> 2/ 00:05:59.710 --> 00:05:59.720 align:start position:0% have to warn you though it's about 2 2/ 00:05:59.720 --> 00:06:02.029 align:start position:0% have to warn you though it's about 2 2/ third<00:05:59.960> too<00:06:00.160> long<00:06:00.639> lastly<00:06:01.160> there's<00:06:01.440> also<00:06:01.759> wake 00:06:02.029 --> 00:06:02.039 align:start position:0% third too long lastly there's also wake 00:06:02.039 --> 00:06:04.350 align:start position:0% third too long lastly there's also wake on<00:06:02.400> land<00:06:02.880> which<00:06:03.039> will<00:06:03.240> trigger<00:06:03.560> the<00:06:03.720> PC<00:06:04.120> if<00:06:04.240> a 00:06:04.350 --> 00:06:04.360 align:start position:0% on land which will trigger the PC if a 00:06:04.360 --> 00:06:06.350 align:start position:0% on land which will trigger the PC if a signal<00:06:04.680> is<00:06:04.800> sent<00:06:05.039> to<00:06:05.199> it<00:06:05.360> via<00:06:05.600> the<00:06:05.720> network 00:06:06.350 --> 00:06:06.360 align:start position:0% signal is sent to it via the network 00:06:06.360 --> 00:06:08.029 align:start position:0% signal is sent to it via the network however<00:06:06.560> the<00:06:06.680> controller<00:06:07.120> method<00:06:07.400> is<00:06:07.680> exactly 00:06:08.029 --> 00:06:08.039 align:start position:0% however the controller method is exactly 00:06:08.039 --> 00:06:10.029 align:start position:0% however the controller method is exactly what<00:06:08.160> I<00:06:08.280> wanted<00:06:08.800> so<00:06:08.960> I<00:06:09.080> didn't<00:06:09.319> look<00:06:09.479> into<00:06:09.800> this 00:06:10.029 --> 00:06:10.039 align:start position:0% what I wanted so I didn't look into this 00:06:10.039 --> 00:06:11.909 align:start position:0% what I wanted so I didn't look into this any<00:06:10.280> further<00:06:10.960> all<00:06:11.120> right<00:06:11.400> that<00:06:11.479> should<00:06:11.680> cover 00:06:11.909 --> 00:06:11.919 align:start position:0% any further all right that should cover 00:06:11.919 --> 00:06:13.870 align:start position:0% any further all right that should cover the<00:06:12.039> power<00:06:12.319> sequence<00:06:12.960> time<00:06:13.160> to<00:06:13.319> move<00:06:13.520> on<00:06:13.680> to 00:06:13.870 --> 00:06:13.880 align:start position:0% the power sequence time to move on to 00:06:13.880 --> 00:06:16.990 align:start position:0% the power sequence time to move on to Windows 00:06:16.990 --> 00:06:17.000 align:start position:0% 00:06:17.000 --> 00:06:19.029 align:start position:0% Shenanigans<00:06:18.000> the<00:06:18.160> goal<00:06:18.319> in<00:06:18.479> this<00:06:18.680> chapter<00:06:18.960> is 00:06:19.029 --> 00:06:19.039 align:start position:0% Shenanigans the goal in this chapter is 00:06:19.039 --> 00:06:21.070 align:start position:0% Shenanigans the goal in this chapter is to<00:06:19.199> get<00:06:19.360> Windows<00:06:19.720> to<00:06:19.919> remove<00:06:20.360> any<00:06:20.599> password 00:06:21.070 --> 00:06:21.080 align:start position:0% to get Windows to remove any password 00:06:21.080 --> 00:06:23.029 align:start position:0% to get Windows to remove any password requirements<00:06:21.720> after<00:06:22.039> boot<00:06:22.319> or<00:06:22.520> waking<00:06:22.840> up 00:06:23.029 --> 00:06:23.039 align:start position:0% requirements after boot or waking up 00:06:23.039 --> 00:06:25.189 align:start position:0% requirements after boot or waking up from<00:06:23.319> sleep<00:06:23.800> so<00:06:24.000> the<00:06:24.160> system<00:06:24.479> can<00:06:24.639> go<00:06:24.880> straight 00:06:25.189 --> 00:06:25.199 align:start position:0% from sleep so the system can go straight 00:06:25.199 --> 00:06:26.950 align:start position:0% from sleep so the system can go straight into<00:06:25.400> the<00:06:25.560> desktop<00:06:26.160> where<00:06:26.319> steam's<00:06:26.720> Big 00:06:26.950 --> 00:06:26.960 align:start position:0% into the desktop where steam's Big 00:06:26.960 --> 00:06:28.830 align:start position:0% into the desktop where steam's Big Picture<00:06:27.240> Mode<00:06:27.479> is<00:06:27.639> waiting<00:06:28.080> I<00:06:28.280> also<00:06:28.440> have<00:06:28.599> one 00:06:28.830 --> 00:06:28.840 align:start position:0% Picture Mode is waiting I also have one 00:06:28.840 --> 00:06:31.029 align:start position:0% Picture Mode is waiting I also have one other<00:06:29.160> windows<00:06:29.639> related<00:06:30.080> controller<00:06:30.599> tweak<00:06:30.919> I 00:06:31.029 --> 00:06:31.039 align:start position:0% other windows related controller tweak I 00:06:31.039 --> 00:06:32.909 align:start position:0% other windows related controller tweak I would<00:06:31.199> suggest<00:06:31.639> but<00:06:32.080> I'll<00:06:32.280> get<00:06:32.400> to<00:06:32.560> that<00:06:32.680> in<00:06:32.759> a 00:06:32.909 --> 00:06:32.919 align:start position:0% would suggest but I'll get to that in a 00:06:32.919 --> 00:06:35.309 align:start position:0% would suggest but I'll get to that in a minute<00:06:33.720> I'd<00:06:34.000> strongly<00:06:34.240> advise<00:06:34.639> against<00:06:35.039> doing 00:06:35.309 --> 00:06:35.319 align:start position:0% minute I'd strongly advise against doing 00:06:35.319 --> 00:06:37.629 align:start position:0% minute I'd strongly advise against doing this<00:06:35.440> on<00:06:35.560> a<00:06:35.720> work<00:06:36.000> or<00:06:36.280> school<00:06:36.639> computer<00:06:37.120> or<00:06:37.280> any 00:06:37.629 --> 00:06:37.639 align:start position:0% this on a work or school computer or any 00:06:37.639 --> 00:06:39.870 align:start position:0% this on a work or school computer or any system<00:06:37.960> that<00:06:38.160> has<00:06:38.400> access<00:06:38.680> to<00:06:38.880> sensitive<00:06:39.400> data 00:06:39.870 --> 00:06:39.880 align:start position:0% system that has access to sensitive data 00:06:39.880 --> 00:06:41.390 align:start position:0% system that has access to sensitive data and<00:06:40.120> is<00:06:40.280> in<00:06:40.440> an<00:06:40.639> environment<00:06:41.199> where 00:06:41.390 --> 00:06:41.400 align:start position:0% and is in an environment where 00:06:41.400 --> 00:06:43.510 align:start position:0% and is in an environment where unauthorized<00:06:42.199> Personnel<00:06:42.680> may<00:06:42.880> have<00:06:43.199> access 00:06:43.510 --> 00:06:43.520 align:start position:0% unauthorized Personnel may have access 00:06:43.520 --> 00:06:45.950 align:start position:0% unauthorized Personnel may have access to<00:06:43.720> it<00:06:44.199> in<00:06:44.319> order<00:06:44.520> to<00:06:44.680> remove<00:06:45.039> any<00:06:45.319> barriers<00:06:45.800> of 00:06:45.950 --> 00:06:45.960 align:start position:0% to it in order to remove any barriers of 00:06:45.960 --> 00:06:48.309 align:start position:0% to it in order to remove any barriers of the<00:06:46.160> Wake<00:06:46.560> we<00:06:46.759> have<00:06:46.919> to<00:06:47.080> disable<00:06:47.520> any<00:06:47.880> pin<00:06:48.160> or 00:06:48.309 --> 00:06:48.319 align:start position:0% the Wake we have to disable any pin or 00:06:48.319 --> 00:06:50.150 align:start position:0% the Wake we have to disable any pin or other<00:06:48.840> Security<00:06:49.280> checks<00:06:49.680> which<00:06:49.840> you<00:06:49.919> can<00:06:50.039> do 00:06:50.150 --> 00:06:50.160 align:start position:0% other Security checks which you can do 00:06:50.160 --> 00:06:52.790 align:start position:0% other Security checks which you can do into<00:06:50.440> signin<00:06:50.880> options<00:06:51.360> within<00:06:51.759> settings<00:06:52.599> but 00:06:52.790 --> 00:06:52.800 align:start position:0% into signin options within settings but 00:06:52.800 --> 00:06:54.710 align:start position:0% into signin options within settings but doing<00:06:53.039> this<00:06:53.280> just<00:06:53.560> for<00:06:53.720> the<00:06:53.880> Sleep<00:06:54.199> scenario 00:06:54.710 --> 00:06:54.720 align:start position:0% doing this just for the Sleep scenario 00:06:54.720 --> 00:06:56.749 align:start position:0% doing this just for the Sleep scenario might<00:06:54.880> not<00:06:55.080> be<00:06:55.319> enough<00:06:55.960> sometimes<00:06:56.199> the<00:06:56.360> PC 00:06:56.749 --> 00:06:56.759 align:start position:0% might not be enough sometimes the PC 00:06:56.759 --> 00:06:58.830 align:start position:0% might not be enough sometimes the PC will<00:06:56.960> restart<00:06:57.400> or<00:06:57.560> shut<00:06:57.879> down<00:06:58.160> completely 00:06:58.830 --> 00:06:58.840 align:start position:0% will restart or shut down completely 00:06:58.840 --> 00:07:00.830 align:start position:0% will restart or shut down completely because<00:06:59.039> of<00:06:59.199> love<00:06:59.759> Windows<00:07:00.120> updates<00:07:00.599> or 00:07:00.830 --> 00:07:00.840 align:start position:0% because of love Windows updates or 00:07:00.840 --> 00:07:03.670 align:start position:0% because of love Windows updates or because<00:07:01.120> it<00:07:01.680> crashed<00:07:02.680> in<00:07:02.840> those<00:07:03.080> situations 00:07:03.670 --> 00:07:03.680 align:start position:0% because it crashed in those situations 00:07:03.680 --> 00:07:05.430 align:start position:0% because it crashed in those situations you<00:07:03.840> might<00:07:04.080> dread<00:07:04.520> at<00:07:04.680> the<00:07:04.840> thought<00:07:05.039> of<00:07:05.240> having 00:07:05.430 --> 00:07:05.440 align:start position:0% you might dread at the thought of having 00:07:05.440 --> 00:07:07.710 align:start position:0% you might dread at the thought of having to<00:07:05.599> reach<00:07:05.840> for<00:07:06.080> the<00:07:06.280> keyboard<00:07:06.960> I<00:07:07.120> know<00:07:07.319> I<00:07:07.479> would 00:07:07.710 --> 00:07:07.720 align:start position:0% to reach for the keyboard I know I would 00:07:07.720 --> 00:07:09.790 align:start position:0% to reach for the keyboard I know I would have<00:07:07.960> which<00:07:08.080> is<00:07:08.360> why<00:07:08.599> I<00:07:08.680> want<00:07:08.960> to<00:07:09.160> disable<00:07:09.639> the 00:07:09.790 --> 00:07:09.800 align:start position:0% have which is why I want to disable the 00:07:09.800 --> 00:07:12.230 align:start position:0% have which is why I want to disable the login<00:07:10.160> after<00:07:10.479> a<00:07:10.680> boot<00:07:11.080> as<00:07:11.240> well<00:07:11.759> for<00:07:11.960> this<00:07:12.120> you 00:07:12.230 --> 00:07:12.240 align:start position:0% login after a boot as well for this you 00:07:12.240 --> 00:07:13.749 align:start position:0% login after a boot as well for this you have<00:07:12.360> to<00:07:12.520> make<00:07:12.680> sure<00:07:12.919> that<00:07:13.039> you're<00:07:13.240> logged<00:07:13.560> in 00:07:13.749 --> 00:07:13.759 align:start position:0% have to make sure that you're logged in 00:07:13.759 --> 00:07:15.790 align:start position:0% have to make sure that you're logged in using<00:07:14.039> a<00:07:14.240> local<00:07:14.639> account<00:07:15.080> which<00:07:15.199> you<00:07:15.319> can<00:07:15.560> see 00:07:15.790 --> 00:07:15.800 align:start position:0% using a local account which you can see 00:07:15.800 --> 00:07:17.510 align:start position:0% using a local account which you can see in<00:07:15.879> the<00:07:16.039> settings<00:07:16.440> page<00:07:16.680> on<00:07:16.800> the<00:07:17.000> top<00:07:17.280> left 00:07:17.510 --> 00:07:17.520 align:start position:0% in the settings page on the top left 00:07:17.520 --> 00:07:19.629 align:start position:0% in the settings page on the top left corner<00:07:18.240> if<00:07:18.400> not<00:07:18.680> just<00:07:18.840> click<00:07:19.039> on<00:07:19.120> it<00:07:19.240> and<00:07:19.440> sign 00:07:19.629 --> 00:07:19.639 align:start position:0% corner if not just click on it and sign 00:07:19.639 --> 00:07:21.430 align:start position:0% corner if not just click on it and sign out<00:07:19.800> of<00:07:19.919> your<00:07:20.080> Microsoft<00:07:20.639> account<00:07:21.039> mind<00:07:21.240> you 00:07:21.430 --> 00:07:21.440 align:start position:0% out of your Microsoft account mind you 00:07:21.440 --> 00:07:22.830 align:start position:0% out of your Microsoft account mind you depending<00:07:21.759> on<00:07:21.919> your<00:07:22.039> needs<00:07:22.440> this<00:07:22.599> might 00:07:22.830 --> 00:07:22.840 align:start position:0% depending on your needs this might 00:07:22.840 --> 00:07:24.830 align:start position:0% depending on your needs this might affect<00:07:23.120> other<00:07:23.440> attributes<00:07:23.919> or<00:07:24.120> software<00:07:24.599> so 00:07:24.830 --> 00:07:24.840 align:start position:0% affect other attributes or software so 00:07:24.840 --> 00:07:27.589 align:start position:0% affect other attributes or software so make<00:07:25.000> sure<00:07:25.280> you<00:07:25.560> don't<00:07:26.160> need<00:07:26.479> this<00:07:27.160> next<00:07:27.400> up 00:07:27.589 --> 00:07:27.599 align:start position:0% make sure you don't need this next up 00:07:27.599 --> 00:07:30.510 align:start position:0% make sure you don't need this next up open<00:07:27.840> the<00:07:28.000> start<00:07:28.280> menu<00:07:28.560> and<00:07:28.840> type<00:07:29.080> in<00:07:29.520> Rec<00:07:29.879> edit 00:07:30.510 --> 00:07:30.520 align:start position:0% open the start menu and type in Rec edit 00:07:30.520 --> 00:07:32.070 align:start position:0% open the start menu and type in Rec edit right<00:07:30.759> click<00:07:30.919> and<00:07:31.080> select<00:07:31.440> run<00:07:31.720> as 00:07:32.070 --> 00:07:32.080 align:start position:0% right click and select run as 00:07:32.080 --> 00:07:34.469 align:start position:0% right click and select run as administrator<00:07:33.080> then<00:07:33.240> navigate<00:07:33.680> to<00:07:33.879> H<00:07:34.240> key 00:07:34.469 --> 00:07:34.479 align:start position:0% administrator then navigate to H key 00:07:34.479 --> 00:07:37.990 align:start position:0% administrator then navigate to H key local<00:07:34.840> machine<00:07:35.759> software<00:07:36.680> Microsoft<00:07:37.639> Windows 00:07:37.990 --> 00:07:38.000 align:start position:0% local machine software Microsoft Windows 00:07:38.000 --> 00:07:41.670 align:start position:0% local machine software Microsoft Windows NT<00:07:38.919> current<00:07:39.319> version<00:07:40.120> wi<00:07:40.440> logon<00:07:41.199> in<00:07:41.440> there<00:07:41.599> you 00:07:41.670 --> 00:07:41.680 align:start position:0% NT current version wi logon in there you 00:07:41.680 --> 00:07:44.390 align:start position:0% NT current version wi logon in there you need<00:07:41.800> to<00:07:41.960> find<00:07:42.440> three<00:07:42.879> values<00:07:43.479> first<00:07:43.919> default 00:07:44.390 --> 00:07:44.400 align:start position:0% need to find three values first default 00:07:44.400 --> 00:07:46.710 align:start position:0% need to find three values first default username<00:07:45.000> and<00:07:45.199> default<00:07:45.800> password<00:07:46.520> if<00:07:46.639> you 00:07:46.710 --> 00:07:46.720 align:start position:0% username and default password if you 00:07:46.720 --> 00:07:48.950 align:start position:0% username and default password if you don't<00:07:46.879> see<00:07:47.159> these<00:07:47.440> you'll<00:07:47.639> have<00:07:47.759> to<00:07:48.039> add<00:07:48.319> them 00:07:48.950 --> 00:07:48.960 align:start position:0% don't see these you'll have to add them 00:07:48.960 --> 00:07:50.790 align:start position:0% don't see these you'll have to add them simply<00:07:49.400> right<00:07:49.639> click<00:07:49.840> somewhere<00:07:50.240> empty<00:07:50.599> and 00:07:50.790 --> 00:07:50.800 align:start position:0% simply right click somewhere empty and 00:07:50.800 --> 00:07:52.869 align:start position:0% simply right click somewhere empty and select<00:07:51.120> new<00:07:51.360> string<00:07:51.800> value<00:07:52.319> and<00:07:52.520> name<00:07:52.720> it 00:07:52.869 --> 00:07:52.879 align:start position:0% select new string value and name it 00:07:52.879 --> 00:07:54.790 align:start position:0% select new string value and name it either<00:07:53.159> default<00:07:53.599> username<00:07:54.039> or<00:07:54.240> default 00:07:54.790 --> 00:07:54.800 align:start position:0% either default username or default 00:07:54.800 --> 00:07:56.909 align:start position:0% either default username or default password<00:07:55.560> for<00:07:55.759> both<00:07:55.919> of<00:07:56.080> these<00:07:56.360> type<00:07:56.599> in<00:07:56.720> your 00:07:56.909 --> 00:07:56.919 align:start position:0% password for both of these type in your 00:07:56.919 --> 00:07:59.149 align:start position:0% password for both of these type in your respective<00:07:57.479> local<00:07:57.840> Windows<00:07:58.280> credentials<00:07:59.039> it 00:07:59.149 --> 00:07:59.159 align:start position:0% respective local Windows credentials it 00:07:59.159 --> 00:08:01.070 align:start position:0% respective local Windows credentials it may<00:07:59.520> feel<00:07:59.639> a<00:07:59.720> bit<00:07:59.919> weird<00:08:00.280> to<00:08:00.400> see<00:08:00.680> certain 00:08:01.070 --> 00:08:01.080 align:start position:0% may feel a bit weird to see certain 00:08:01.080 --> 00:08:03.149 align:start position:0% may feel a bit weird to see certain values<00:08:01.599> clearly<00:08:01.960> readable<00:08:02.560> so<00:08:02.759> again<00:08:02.960> don't 00:08:03.149 --> 00:08:03.159 align:start position:0% values clearly readable so again don't 00:08:03.159 --> 00:08:04.749 align:start position:0% values clearly readable so again don't do<00:08:03.319> this<00:08:03.440> on<00:08:03.560> a<00:08:03.680> machine<00:08:04.039> someone<00:08:04.400> may<00:08:04.520> have 00:08:04.749 --> 00:08:04.759 align:start position:0% do this on a machine someone may have 00:08:04.759 --> 00:08:08.149 align:start position:0% do this on a machine someone may have access<00:08:05.039> to<00:08:05.560> and<00:08:05.759> also<00:08:06.440> don't<00:08:06.759> reuse<00:08:07.240> passwords 00:08:08.149 --> 00:08:08.159 align:start position:0% access to and also don't reuse passwords 00:08:08.159 --> 00:08:10.550 align:start position:0% access to and also don't reuse passwords the<00:08:08.319> last<00:08:08.560> value<00:08:08.840> to<00:08:08.960> check<00:08:09.280> is<00:08:09.560> auto<00:08:10.000> admin 00:08:10.550 --> 00:08:10.560 align:start position:0% the last value to check is auto admin 00:08:10.560 --> 00:08:12.950 align:start position:0% the last value to check is auto admin log<00:08:10.879> on<00:08:11.319> I<00:08:11.440> already<00:08:11.840> had<00:08:12.159> this<00:08:12.440> but<00:08:12.599> just<00:08:12.800> in 00:08:12.950 --> 00:08:12.960 align:start position:0% log on I already had this but just in 00:08:12.960 --> 00:08:14.790 align:start position:0% log on I already had this but just in case<00:08:13.159> you<00:08:13.240> can<00:08:13.400> add<00:08:13.599> it<00:08:13.720> as<00:08:13.840> a<00:08:13.960> new<00:08:14.159> string<00:08:14.599> as 00:08:14.790 --> 00:08:14.800 align:start position:0% case you can add it as a new string as 00:08:14.800 --> 00:08:17.710 align:start position:0% case you can add it as a new string as well<00:08:15.159> and<00:08:15.479> set<00:08:15.639> it<00:08:15.759> to<00:08:16.000> one<00:08:16.639> restart<00:08:17.039> your<00:08:17.240> PC 00:08:17.710 --> 00:08:17.720 align:start position:0% well and set it to one restart your PC 00:08:17.720 --> 00:08:19.589 align:start position:0% well and set it to one restart your PC and<00:08:18.039> congratulations<00:08:18.840> you<00:08:19.039> now<00:08:19.240> left<00:08:19.440> your 00:08:19.589 --> 00:08:19.599 align:start position:0% and congratulations you now left your 00:08:19.599 --> 00:08:21.790 align:start position:0% and congratulations you now left your doors<00:08:19.960> wide<00:08:20.240> open<00:08:20.680> but<00:08:20.919> you<00:08:21.080> also<00:08:21.280> got<00:08:21.479> closer 00:08:21.790 --> 00:08:21.800 align:start position:0% doors wide open but you also got closer 00:08:21.800 --> 00:08:23.909 align:start position:0% doors wide open but you also got closer to<00:08:21.919> becoming<00:08:22.199> a<00:08:22.319> true<00:08:22.599> couch<00:08:22.960> potato<00:08:23.479> and<00:08:23.720> that 00:08:23.909 --> 00:08:23.919 align:start position:0% to becoming a true couch potato and that 00:08:23.919 --> 00:08:26.430 align:start position:0% to becoming a true couch potato and that is<00:08:24.000> arguably<00:08:24.599> much<00:08:24.840> more<00:08:25.159> important<00:08:26.159> during 00:08:26.430 --> 00:08:26.440 align:start position:0% is arguably much more important during 00:08:26.440 --> 00:08:28.430 align:start position:0% is arguably much more important during my<00:08:26.599> search<00:08:26.919> for<00:08:27.080> a<00:08:27.240> solution<00:08:27.639> to<00:08:27.879> this<00:08:28.080> I<00:08:28.199> also 00:08:28.430 --> 00:08:28.440 align:start position:0% my search for a solution to this I also 00:08:28.440 --> 00:08:30.350 align:start position:0% my search for a solution to this I also came<00:08:28.639> across<00:08:29.000> one<00:08:29.520> redit<00:08:29.759> post<00:08:30.039> where 00:08:30.350 --> 00:08:30.360 align:start position:0% came across one redit post where 00:08:30.360 --> 00:08:32.310 align:start position:0% came across one redit post where additionally<00:08:30.879> to<00:08:31.080> the<00:08:31.240> login<00:08:31.960> someone 00:08:32.310 --> 00:08:32.320 align:start position:0% additionally to the login someone 00:08:32.320 --> 00:08:34.110 align:start position:0% additionally to the login someone managed<00:08:32.640> to<00:08:32.800> replace<00:08:33.159> the<00:08:33.320> entire<00:08:33.719> Windows 00:08:34.110 --> 00:08:34.120 align:start position:0% managed to replace the entire Windows 00:08:34.120 --> 00:08:36.550 align:start position:0% managed to replace the entire Windows shell<00:08:34.519> with<00:08:34.680> steam<00:08:35.200> itself<00:08:36.120> meaning<00:08:36.440> you 00:08:36.550 --> 00:08:36.560 align:start position:0% shell with steam itself meaning you 00:08:36.560 --> 00:08:38.509 align:start position:0% shell with steam itself meaning you won't<00:08:36.800> see<00:08:37.000> the<00:08:37.120> Windows<00:08:37.599> desktop<00:08:38.039> in<00:08:38.279> those 00:08:38.509 --> 00:08:38.519 align:start position:0% won't see the Windows desktop in those 00:08:38.519 --> 00:08:40.269 align:start position:0% won't see the Windows desktop in those dreaded<00:08:38.919> few<00:08:39.200> seconds<00:08:39.599> before<00:08:39.839> steam 00:08:40.269 --> 00:08:40.279 align:start position:0% dreaded few seconds before steam 00:08:40.279 --> 00:08:42.430 align:start position:0% dreaded few seconds before steam launches<00:08:41.279> however<00:08:41.479> reading<00:08:41.800> up<00:08:41.959> on<00:08:42.120> this<00:08:42.320> it 00:08:42.430 --> 00:08:42.440 align:start position:0% launches however reading up on this it 00:08:42.440 --> 00:08:44.269 align:start position:0% launches however reading up on this it seems<00:08:42.640> to<00:08:42.760> be<00:08:42.919> tied<00:08:43.159> to<00:08:43.360> certain<00:08:43.839> risks 00:08:44.269 --> 00:08:44.279 align:start position:0% seems to be tied to certain risks 00:08:44.279 --> 00:08:46.470 align:start position:0% seems to be tied to certain risks especially<00:08:44.680> when<00:08:44.880> trying<00:08:45.120> to<00:08:45.279> get<00:08:45.519> it<00:08:45.920> back 00:08:46.470 --> 00:08:46.480 align:start position:0% especially when trying to get it back 00:08:46.480 --> 00:08:48.190 align:start position:0% especially when trying to get it back but<00:08:46.640> since<00:08:46.880> I<00:08:47.000> am<00:08:47.160> most<00:08:47.360> of<00:08:47.480> the<00:08:47.640> time<00:08:47.839> waking 00:08:48.190 --> 00:08:48.200 align:start position:0% but since I am most of the time waking 00:08:48.200 --> 00:08:50.310 align:start position:0% but since I am most of the time waking the<00:08:48.399> PC<00:08:48.720> from<00:08:49.040> sleep<00:08:49.480> I<00:08:49.600> won't<00:08:49.880> have<00:08:50.080> this 00:08:50.310 --> 00:08:50.320 align:start position:0% the PC from sleep I won't have this 00:08:50.320 --> 00:08:53.550 align:start position:0% the PC from sleep I won't have this issue<00:08:50.760> anyway<00:08:51.279> so<00:08:51.560> I<00:08:51.720> left<00:08:51.959> it<00:08:52.200> as<00:08:52.480> is<00:08:53.120> lastly 00:08:53.550 --> 00:08:53.560 align:start position:0% issue anyway so I left it as is lastly 00:08:53.560 --> 00:08:55.550 align:start position:0% issue anyway so I left it as is lastly let's<00:08:53.720> set<00:08:53.880> up<00:08:54.000> steam<00:08:54.320> to<00:08:54.440> launch<00:08:54.720> on<00:08:55.000> Startup 00:08:55.550 --> 00:08:55.560 align:start position:0% let's set up steam to launch on Startup 00:08:55.560 --> 00:08:57.190 align:start position:0% let's set up steam to launch on Startup if<00:08:55.680> you<00:08:55.839> haven't<00:08:56.120> done<00:08:56.279> so<00:08:56.519> already<00:08:57.000> which<00:08:57.120> you 00:08:57.190 --> 00:08:57.200 align:start position:0% if you haven't done so already which you 00:08:57.200 --> 00:08:58.710 align:start position:0% if you haven't done so already which you can<00:08:57.360> do<00:08:57.519> by<00:08:57.680> going<00:08:57.880> into<00:08:58.079> the<00:08:58.200> settings<00:08:58.519> and 00:08:58.710 --> 00:08:58.720 align:start position:0% can do by going into the settings and 00:08:58.720 --> 00:09:01.310 align:start position:0% can do by going into the settings and enable<00:08:59.440> run<00:08:59.640> Steam<00:08:59.959> when<00:09:00.160> my<00:09:00.360> computer<00:09:00.839> starts 00:09:01.310 --> 00:09:01.320 align:start position:0% enable run Steam when my computer starts 00:09:01.320 --> 00:09:03.110 align:start position:0% enable run Steam when my computer starts as<00:09:01.440> well<00:09:01.560> as<00:09:01.680> start<00:09:02.040> steam<00:09:02.320> in<00:09:02.560> Big<00:09:02.800> Picture 00:09:03.110 --> 00:09:03.120 align:start position:0% as well as start steam in Big Picture 00:09:03.120 --> 00:09:05.230 align:start position:0% as well as start steam in Big Picture Mode<00:09:03.839> that's<00:09:04.079> pretty<00:09:04.279> much<00:09:04.480> it<00:09:04.720> there<00:09:04.800> is<00:09:05.000> one 00:09:05.230 --> 00:09:05.240 align:start position:0% Mode that's pretty much it there is one 00:09:05.240 --> 00:09:06.910 align:start position:0% Mode that's pretty much it there is one last<00:09:05.440> Windows<00:09:05.800> related<00:09:06.120> tweak<00:09:06.399> you<00:09:06.519> may<00:09:06.720> want 00:09:06.910 --> 00:09:06.920 align:start position:0% last Windows related tweak you may want 00:09:06.920 --> 00:09:08.949 align:start position:0% last Windows related tweak you may want to<00:09:07.079> undertake<00:09:07.760> though<00:09:08.240> if<00:09:08.360> you<00:09:08.480> connect<00:09:08.800> your 00:09:08.949 --> 00:09:08.959 align:start position:0% to undertake though if you connect your 00:09:08.959 --> 00:09:10.949 align:start position:0% to undertake though if you connect your Xbox<00:09:09.360> controller<00:09:09.720> for<00:09:09.880> the<00:09:10.040> first<00:09:10.519> time<00:09:10.760> to 00:09:10.949 --> 00:09:10.959 align:start position:0% Xbox controller for the first time to 00:09:10.959 --> 00:09:12.110 align:start position:0% Xbox controller for the first time to Windows<00:09:11.279> you<00:09:11.360> will<00:09:11.519> notice<00:09:11.800> that<00:09:11.959> when 00:09:12.110 --> 00:09:12.120 align:start position:0% Windows you will notice that when 00:09:12.120 --> 00:09:14.509 align:start position:0% Windows you will notice that when hitting<00:09:12.399> the<00:09:12.720> crest<00:09:13.200> you<00:09:13.279> will<00:09:13.480> get<00:09:13.640> the<00:09:13.880> Xbox 00:09:14.509 --> 00:09:14.519 align:start position:0% hitting the crest you will get the Xbox 00:09:14.519 --> 00:09:16.350 align:start position:0% hitting the crest you will get the Xbox game<00:09:14.800> bar<00:09:15.079> overlay<00:09:15.640> which<00:09:15.880> incidentally 00:09:16.350 --> 00:09:16.360 align:start position:0% game bar overlay which incidentally 00:09:16.360 --> 00:09:18.310 align:start position:0% game bar overlay which incidentally conflicts<00:09:16.800> with<00:09:16.920> the<00:09:17.040> one<00:09:17.279> from<00:09:17.560> Steam<00:09:18.200> in 00:09:18.310 --> 00:09:18.320 align:start position:0% conflicts with the one from Steam in 00:09:18.320 --> 00:09:20.069 align:start position:0% conflicts with the one from Steam in order<00:09:18.519> to<00:09:18.680> disable<00:09:19.120> this<00:09:19.360> simply<00:09:19.640> go<00:09:19.800> to<00:09:19.920> the 00:09:20.069 --> 00:09:20.079 align:start position:0% order to disable this simply go to the 00:09:20.079 --> 00:09:22.269 align:start position:0% order to disable this simply go to the settings<00:09:20.600> select<00:09:21.040> gaming<00:09:21.399> and<00:09:21.680> uncheck<00:09:22.120> the 00:09:22.269 --> 00:09:22.279 align:start position:0% settings select gaming and uncheck the 00:09:22.279 --> 00:09:24.990 align:start position:0% settings select gaming and uncheck the game<00:09:22.519> bar<00:09:22.839> option<00:09:23.680> so<00:09:23.959> to<00:09:24.120> summarize<00:09:24.720> if<00:09:24.839> the 00:09:24.990 --> 00:09:25.000 align:start position:0% game bar option so to summarize if the 00:09:25.000 --> 00:09:26.990 align:start position:0% game bar option so to summarize if the PC<00:09:25.240> now<00:09:25.399> boots<00:09:25.720> up<00:09:25.880> or<00:09:26.000> wakes<00:09:26.279> from<00:09:26.480> sleep<00:09:26.880> it 00:09:26.990 --> 00:09:27.000 align:start position:0% PC now boots up or wakes from sleep it 00:09:27.000 --> 00:09:28.670 align:start position:0% PC now boots up or wakes from sleep it will<00:09:27.240> then<00:09:27.480> automatically<00:09:28.040> log<00:09:28.240> in<00:09:28.519> and 00:09:28.670 --> 00:09:28.680 align:start position:0% will then automatically log in and 00:09:28.680 --> 00:09:31.190 align:start position:0% will then automatically log in and launch<00:09:29.000> Steam<00:09:29.399> in<00:09:29.839> picture<00:09:30.120> mode<00:09:30.839> that<00:09:30.959> brings 00:09:31.190 --> 00:09:31.200 align:start position:0% launch Steam in picture mode that brings 00:09:31.200 --> 00:09:33.350 align:start position:0% launch Steam in picture mode that brings us<00:09:31.360> to<00:09:31.480> the<00:09:31.680> final<00:09:32.040> chapter<00:09:32.560> the<00:09:32.800> fascinating 00:09:33.350 --> 00:09:33.360 align:start position:0% us to the final chapter the fascinating 00:09:33.360 --> 00:09:37.310 align:start position:0% us to the final chapter the fascinating world<00:09:33.640> of<00:09:33.880> HDMI 00:09:37.310 --> 00:09:37.320 align:start position:0% 00:09:37.320 --> 00:09:40.230 align:start position:0% CC<00:09:38.320> if<00:09:38.399> you<00:09:38.519> didn't<00:09:38.760> know<00:09:39.079> CC<00:09:39.680> stands<00:09:39.959> for 00:09:40.230 --> 00:09:40.240 align:start position:0% CC if you didn't know CC stands for 00:09:40.240 --> 00:09:42.590 align:start position:0% CC if you didn't know CC stands for Consumer<00:09:40.800> Electronics<00:09:41.480> control<00:09:42.079> and<00:09:42.240> is<00:09:42.399> a 00:09:42.590 --> 00:09:42.600 align:start position:0% Consumer Electronics control and is a 00:09:42.600 --> 00:09:44.750 align:start position:0% Consumer Electronics control and is a standard<00:09:43.000> that<00:09:43.160> allows<00:09:43.519> HDMI<00:09:44.160> devices<00:09:44.560> to 00:09:44.750 --> 00:09:44.760 align:start position:0% standard that allows HDMI devices to 00:09:44.760 --> 00:09:46.790 align:start position:0% standard that allows HDMI devices to talk<00:09:44.959> to<00:09:45.120> each<00:09:45.240> other<00:09:45.680> and<00:09:46.040> control<00:09:46.640> each 00:09:46.790 --> 00:09:46.800 align:start position:0% talk to each other and control each 00:09:46.800 --> 00:09:50.069 align:start position:0% talk to each other and control each other<00:09:47.800> I<00:09:47.920> believe<00:09:48.200> most<00:09:48.480> modern<00:09:48.920> TVs<00:09:49.480> AV 00:09:50.069 --> 00:09:50.079 align:start position:0% other I believe most modern TVs AV 00:09:50.079 --> 00:09:52.269 align:start position:0% other I believe most modern TVs AV receivers<00:09:50.440> as<00:09:50.560> well<00:09:50.720> as<00:09:50.920> gaming<00:09:51.320> consoles<00:09:51.920> all 00:09:52.269 --> 00:09:52.279 align:start position:0% receivers as well as gaming consoles all 00:09:52.279 --> 00:09:54.389 align:start position:0% receivers as well as gaming consoles all have<00:09:52.600> this<00:09:53.040> for<00:09:53.360> example<00:09:53.720> if<00:09:53.800> I<00:09:53.880> turn<00:09:54.079> on<00:09:54.240> my 00:09:54.389 --> 00:09:54.399 align:start position:0% have this for example if I turn on my 00:09:54.399 --> 00:09:57.069 align:start position:0% have this for example if I turn on my PS5<00:09:55.120> it<00:09:55.240> will<00:09:55.480> also<00:09:55.720> turn<00:09:55.920> on<00:09:56.079> the<00:09:56.240> AV<00:09:56.800> receiver 00:09:57.069 --> 00:09:57.079 align:start position:0% PS5 it will also turn on the AV receiver 00:09:57.079 --> 00:09:59.430 align:start position:0% PS5 it will also turn on the AV receiver and<00:09:57.399> the<00:09:57.560> TV<00:09:58.120> select<00:09:58.440> the<00:09:58.600> appropriate<00:09:59.040> h<00:09:59.360> H 00:09:59.430 --> 00:09:59.440 align:start position:0% and the TV select the appropriate h H 00:09:59.440 --> 00:10:02.670 align:start position:0% and the TV select the appropriate h H GMI<00:09:59.760> ports<00:10:00.200> and<00:10:00.360> it's<00:10:00.680> game<00:10:01.000> time<00:10:01.680> but<00:10:01.839> for<00:10:02.079> PCs 00:10:02.670 --> 00:10:02.680 align:start position:0% GMI ports and it's game time but for PCs 00:10:02.680 --> 00:10:04.870 align:start position:0% GMI ports and it's game time but for PCs this<00:10:02.920> unfortunately<00:10:03.560> doesn't<00:10:04.120> work<00:10:04.560> because 00:10:04.870 --> 00:10:04.880 align:start position:0% this unfortunately doesn't work because 00:10:04.880 --> 00:10:06.870 align:start position:0% this unfortunately doesn't work because as<00:10:05.000> far<00:10:05.160> as<00:10:05.279> I<00:10:05.440> could<00:10:05.600> figure<00:10:05.880> out<00:10:06.160> no<00:10:06.360> GPU<00:10:06.760> on 00:10:06.870 --> 00:10:06.880 align:start position:0% as far as I could figure out no GPU on 00:10:06.880 --> 00:10:09.230 align:start position:0% as far as I could figure out no GPU on the<00:10:07.000> market<00:10:07.360> neither<00:10:07.640> from<00:10:07.920> Nvidia<00:10:08.519> AMD<00:10:09.000> nor 00:10:09.230 --> 00:10:09.240 align:start position:0% the market neither from Nvidia AMD nor 00:10:09.240 --> 00:10:12.430 align:start position:0% the market neither from Nvidia AMD nor Intel<00:10:09.680> come<00:10:09.920> with<00:10:10.120> HDMI<00:10:10.760> C<00:10:11.680> so<00:10:12.000> how<00:10:12.120> do<00:10:12.279> we 00:10:12.430 --> 00:10:12.440 align:start position:0% Intel come with HDMI C so how do we 00:10:12.440 --> 00:10:14.710 align:start position:0% Intel come with HDMI C so how do we circumvent<00:10:13.200> this<00:10:13.760> well<00:10:14.040> with<00:10:14.160> the<00:10:14.360> help<00:10:14.560> of 00:10:14.710 --> 00:10:14.720 align:start position:0% circumvent this well with the help of 00:10:14.720 --> 00:10:17.910 align:start position:0% circumvent this well with the help of one<00:10:14.839> of<00:10:15.040> these<00:10:15.480> this<00:10:15.600> is<00:10:15.720> an<00:10:15.920> HDMI<00:10:16.640> CC<00:10:17.440> adapter 00:10:17.910 --> 00:10:17.920 align:start position:0% one of these this is an HDMI CC adapter 00:10:17.920 --> 00:10:20.470 align:start position:0% one of these this is an HDMI CC adapter from<00:10:18.120> a<00:10:18.279> company<00:10:18.640> called<00:10:19.000> pulse<00:10:19.440> 8<00:10:20.320> it 00:10:20.470 --> 00:10:20.480 align:start position:0% from a company called pulse 8 it 00:10:20.480 --> 00:10:22.230 align:start position:0% from a company called pulse 8 it basically<00:10:20.839> takes<00:10:21.079> the<00:10:21.200> HDMI<00:10:21.720> signal<00:10:22.040> from 00:10:22.230 --> 00:10:22.240 align:start position:0% basically takes the HDMI signal from 00:10:22.240 --> 00:10:24.430 align:start position:0% basically takes the HDMI signal from your<00:10:22.480> PC<00:10:23.000> garnishes<00:10:23.560> it<00:10:23.680> with<00:10:23.880> commands<00:10:24.320> that 00:10:24.430 --> 00:10:24.440 align:start position:0% your PC garnishes it with commands that 00:10:24.440 --> 00:10:26.430 align:start position:0% your PC garnishes it with commands that you<00:10:24.560> can<00:10:24.760> Define<00:10:25.240> and<00:10:25.360> then<00:10:25.519> sends<00:10:25.800> it<00:10:25.920> to<00:10:26.040> the 00:10:26.430 --> 00:10:26.440 align:start position:0% you can Define and then sends it to the 00:10:26.440 --> 00:10:28.829 align:start position:0% you can Define and then sends it to the receiver<00:10:26.720> or<00:10:26.920> other<00:10:27.279> connected<00:10:27.760> devices<00:10:28.680> the 00:10:28.829 --> 00:10:28.839 align:start position:0% receiver or other connected devices the 00:10:28.839 --> 00:10:31.069 align:start position:0% receiver or other connected devices the adapter<00:10:29.160> is<00:10:29.399> powered<00:10:29.680> by<00:10:29.920> USB<00:10:30.519> and<00:10:30.760> simply 00:10:31.069 --> 00:10:31.079 align:start position:0% adapter is powered by USB and simply 00:10:31.079 --> 00:10:33.150 align:start position:0% adapter is powered by USB and simply plugs<00:10:31.480> into<00:10:31.680> the<00:10:31.839> back<00:10:32.040> of<00:10:32.160> your<00:10:32.399> PC<00:10:32.920> while 00:10:33.150 --> 00:10:33.160 align:start position:0% plugs into the back of your PC while 00:10:33.160 --> 00:10:34.990 align:start position:0% plugs into the back of your PC while passing<00:10:33.440> through<00:10:33.640> the<00:10:33.800> HDMI<00:10:34.320> signal<00:10:34.760> it's<00:10:34.880> a 00:10:34.990 --> 00:10:35.000 align:start position:0% passing through the HDMI signal it's a 00:10:35.000 --> 00:10:36.750 align:start position:0% passing through the HDMI signal it's a little<00:10:35.240> ugly<00:10:35.560> dangling<00:10:36.000> around<00:10:36.320> there<00:10:36.600> but 00:10:36.750 --> 00:10:36.760 align:start position:0% little ugly dangling around there but 00:10:36.760 --> 00:10:39.730 align:start position:0% little ugly dangling around there but not<00:10:36.959> as<00:10:37.120> ugly<00:10:37.440> as<00:10:37.600> the<00:10:37.760> USB<00:10:38.360> mini<00:10:38.839> Port<00:10:39.120> it 00:10:39.730 --> 00:10:39.740 align:start position:0% not as ugly as the USB mini Port it 00:10:39.740 --> 00:10:45.350 align:start position:0% not as ugly as the USB mini Port it [Music] 00:10:45.350 --> 00:10:45.360 align:start position:0% [Music] 00:10:45.360 --> 00:10:48.230 align:start position:0% [Music] uses<00:10:46.360> Jokes<00:10:46.760> Aside<00:10:47.160> this<00:10:47.279> is<00:10:47.480> perfectly<00:10:47.959> fine 00:10:48.230 --> 00:10:48.240 align:start position:0% uses Jokes Aside this is perfectly fine 00:10:48.240 --> 00:10:50.190 align:start position:0% uses Jokes Aside this is perfectly fine as<00:10:48.360> I<00:10:48.519> doubt<00:10:48.760> anyone<00:10:49.040> will<00:10:49.240> pluck<00:10:49.519> and<00:10:49.720> unplug 00:10:50.190 --> 00:10:50.200 align:start position:0% as I doubt anyone will pluck and unplug 00:10:50.200 --> 00:10:52.230 align:start position:0% as I doubt anyone will pluck and unplug this<00:10:50.399> frequently<00:10:50.959> and<00:10:51.160> behind<00:10:51.399> the<00:10:51.560> PC<00:10:51.959> nobody 00:10:52.230 --> 00:10:52.240 align:start position:0% this frequently and behind the PC nobody 00:10:52.240 --> 00:10:54.110 align:start position:0% this frequently and behind the PC nobody will<00:10:52.360> ever<00:10:52.560> know<00:10:52.760> that<00:10:52.880> we're<00:10:53.040> using<00:10:53.440> a<00:10:53.639> USB 00:10:54.110 --> 00:10:54.120 align:start position:0% will ever know that we're using a USB 00:10:54.120 --> 00:10:55.310 align:start position:0% will ever know that we're using a USB mini<00:10:54.480> in 00:10:55.310 --> 00:10:55.320 align:start position:0% mini in 00:10:55.320 --> 00:10:57.829 align:start position:0% mini in 2025<00:10:56.320> it's<00:10:56.480> not<00:10:56.639> the<00:10:56.800> only<00:10:57.079> limiting<00:10:57.519> part<00:10:57.720> of 00:10:57.829 --> 00:10:57.839 align:start position:0% 2025 it's not the only limiting part of 00:10:57.839 --> 00:11:00.150 align:start position:0% 2025 it's not the only limiting part of this<00:10:58.079> adapter<00:10:58.519> though<00:10:58.720> it<00:10:58.800> only<00:10:59.279> reports<00:10:59.600> 4K 00:11:00.150 --> 00:11:00.160 align:start position:0% this adapter though it only reports 4K 00:11:00.160 --> 00:11:02.949 align:start position:0% this adapter though it only reports 4K signals<00:11:00.639> up<00:11:00.800> to<00:11:01.000> 60<00:11:01.360> HZ<00:11:02.000> meaning<00:11:02.360> High<00:11:02.560> refresh 00:11:02.949 --> 00:11:02.959 align:start position:0% signals up to 60 HZ meaning High refresh 00:11:02.959 --> 00:11:04.670 align:start position:0% signals up to 60 HZ meaning High refresh rate<00:11:03.200> gaming<00:11:03.560> which<00:11:03.680> is<00:11:03.839> one<00:11:03.959> of<00:11:04.079> the<00:11:04.320> benefits 00:11:04.670 --> 00:11:04.680 align:start position:0% rate gaming which is one of the benefits 00:11:04.680 --> 00:11:07.350 align:start position:0% rate gaming which is one of the benefits of<00:11:04.800> a<00:11:04.920> high-powered<00:11:05.480> PC<00:11:06.200> is<00:11:06.480> out<00:11:06.680> of<00:11:06.880> question 00:11:07.350 --> 00:11:07.360 align:start position:0% of a high-powered PC is out of question 00:11:07.360 --> 00:11:09.550 align:start position:0% of a high-powered PC is out of question here<00:11:08.079> but<00:11:08.240> let's<00:11:08.440> get<00:11:08.600> back<00:11:08.720> to<00:11:08.839> the<00:11:09.040> setup 00:11:09.550 --> 00:11:09.560 align:start position:0% here but let's get back to the setup 00:11:09.560 --> 00:11:11.350 align:start position:0% here but let's get back to the setup after<00:11:09.800> it's<00:11:09.920> been<00:11:10.120> plugged<00:11:10.480> in<00:11:10.720> it's<00:11:10.959> time<00:11:11.120> to 00:11:11.350 --> 00:11:11.360 align:start position:0% after it's been plugged in it's time to 00:11:11.360 --> 00:11:13.269 align:start position:0% after it's been plugged in it's time to download<00:11:11.760> the<00:11:11.959> necessary<00:11:12.519> drivers<00:11:13.000> and 00:11:13.269 --> 00:11:13.279 align:start position:0% download the necessary drivers and 00:11:13.279 --> 00:11:15.470 align:start position:0% download the necessary drivers and libraries<00:11:13.880> which<00:11:14.079> puls<00:11:14.360> 8<00:11:14.639> neatly<00:11:15.000> provides 00:11:15.470 --> 00:11:15.480 align:start position:0% libraries which puls 8 neatly provides 00:11:15.480 --> 00:11:17.190 align:start position:0% libraries which puls 8 neatly provides as<00:11:15.560> a<00:11:15.720> convenient<00:11:16.200> Windows<00:11:16.560> installer<00:11:17.000> on 00:11:17.190 --> 00:11:17.200 align:start position:0% as a convenient Windows installer on 00:11:17.200 --> 00:11:19.150 align:start position:0% as a convenient Windows installer on GitHub<00:11:17.880> once<00:11:18.120> installed<00:11:18.560> you<00:11:18.680> can<00:11:18.800> navigate 00:11:19.150 --> 00:11:19.160 align:start position:0% GitHub once installed you can navigate 00:11:19.160 --> 00:11:21.590 align:start position:0% GitHub once installed you can navigate to<00:11:19.320> the<00:11:19.519> program<00:11:19.880> files<00:11:20.240> and<00:11:20.399> launch<00:11:20.720> the<00:11:20.920> CC 00:11:21.590 --> 00:11:21.600 align:start position:0% to the program files and launch the CC 00:11:21.600 --> 00:11:23.470 align:start position:0% to the program files and launch the CC client<00:11:22.440> this<00:11:22.560> will<00:11:22.720> open<00:11:22.959> the<00:11:23.079> windows 00:11:23.470 --> 00:11:23.480 align:start position:0% client this will open the windows 00:11:23.480 --> 00:11:25.110 align:start position:0% client this will open the windows command<00:11:23.880> line<00:11:24.200> which<00:11:24.399> depending<00:11:24.720> on<00:11:24.880> your 00:11:25.110 --> 00:11:25.120 align:start position:0% command line which depending on your 00:11:25.120 --> 00:11:27.069 align:start position:0% command line which depending on your prior<00:11:25.519> experiences<00:11:26.160> with<00:11:26.279> the<00:11:26.360> Matrix<00:11:26.920> might 00:11:27.069 --> 00:11:27.079 align:start position:0% prior experiences with the Matrix might 00:11:27.079 --> 00:11:29.470 align:start position:0% prior experiences with the Matrix might feel<00:11:27.279> a<00:11:27.399> bit<00:11:27.639> daunting<00:11:28.120> at<00:11:28.320> first<00:11:28.760> but<00:11:28.959> feel 00:11:29.470 --> 00:11:29.480 align:start position:0% feel a bit daunting at first but feel 00:11:29.480 --> 00:11:31.350 align:start position:0% feel a bit daunting at first but feel not<00:11:29.680> for<00:11:29.839> our<00:11:30.040> use<00:11:30.399> case<00:11:30.560> it'll<00:11:30.760> luckily<00:11:31.120> not 00:11:31.350 --> 00:11:31.360 align:start position:0% not for our use case it'll luckily not 00:11:31.360 --> 00:11:33.350 align:start position:0% not for our use case it'll luckily not get<00:11:31.560> too<00:11:31.880> complicated<00:11:32.880> as<00:11:32.959> you<00:11:33.040> can<00:11:33.160> see 00:11:33.350 --> 00:11:33.360 align:start position:0% get too complicated as you can see 00:11:33.360 --> 00:11:34.990 align:start position:0% get too complicated as you can see there's<00:11:33.519> a<00:11:33.680> lot<00:11:33.959> going<00:11:34.160> on<00:11:34.440> here<00:11:34.680> which<00:11:34.800> is 00:11:34.990 --> 00:11:35.000 align:start position:0% there's a lot going on here which is 00:11:35.000 --> 00:11:36.670 align:start position:0% there's a lot going on here which is super<00:11:35.360> fascinating<00:11:35.920> and<00:11:36.079> proves<00:11:36.399> that<00:11:36.560> the 00:11:36.670 --> 00:11:36.680 align:start position:0% super fascinating and proves that the 00:11:36.680 --> 00:11:39.389 align:start position:0% super fascinating and proves that the dongle<00:11:37.279> is<00:11:37.560> working<00:11:38.320> what<00:11:38.480> we<00:11:38.600> see<00:11:38.839> is<00:11:39.040> all<00:11:39.240> the 00:11:39.389 --> 00:11:39.399 align:start position:0% dongle is working what we see is all the 00:11:39.399 --> 00:11:41.030 align:start position:0% dongle is working what we see is all the communication<00:11:40.160> happening<00:11:40.519> between<00:11:40.839> the 00:11:41.030 --> 00:11:41.040 align:start position:0% communication happening between the 00:11:41.040 --> 00:11:43.590 align:start position:0% communication happening between the different<00:11:41.399> HDMI<00:11:42.120> devices<00:11:42.880> for<00:11:43.079> example<00:11:43.440> if<00:11:43.519> I 00:11:43.590 --> 00:11:43.600 align:start position:0% different HDMI devices for example if I 00:11:43.600 --> 00:11:45.710 align:start position:0% different HDMI devices for example if I turn<00:11:43.800> up<00:11:43.959> the<00:11:44.160> volume<00:11:44.560> using<00:11:44.880> my<00:11:45.040> Apple<00:11:45.399> TV 00:11:45.710 --> 00:11:45.720 align:start position:0% turn up the volume using my Apple TV 00:11:45.720 --> 00:11:47.670 align:start position:0% turn up the volume using my Apple TV remote<00:11:46.120> I<00:11:46.200> can<00:11:46.360> see<00:11:46.560> it<00:11:46.720> happening<00:11:47.120> in<00:11:47.320> real 00:11:47.670 --> 00:11:47.680 align:start position:0% remote I can see it happening in real 00:11:47.680 --> 00:11:50.350 align:start position:0% remote I can see it happening in real time<00:11:48.040> which<00:11:48.160> is<00:11:48.480> super<00:11:48.839> cool<00:11:49.680> there<00:11:49.800> are<00:11:50.040> also 00:11:50.350 --> 00:11:50.360 align:start position:0% time which is super cool there are also 00:11:50.360 --> 00:11:52.350 align:start position:0% time which is super cool there are also two<00:11:50.680> command<00:11:51.079> line<00:11:51.320> files<00:11:51.639> included<00:11:52.040> in<00:11:52.200> the 00:11:52.350 --> 00:11:52.360 align:start position:0% two command line files included in the 00:11:52.360 --> 00:11:54.629 align:start position:0% two command line files included in the same<00:11:52.600> folder<00:11:53.079> that<00:11:53.279> either<00:11:53.480> turn<00:11:53.760> the<00:11:53.959> TV<00:11:54.320> on 00:11:54.629 --> 00:11:54.639 align:start position:0% same folder that either turn the TV on 00:11:54.639 --> 00:11:56.710 align:start position:0% same folder that either turn the TV on or<00:11:54.959> off<00:11:55.279> and<00:11:55.440> are<00:11:55.600> a<00:11:55.760> great<00:11:55.959> way<00:11:56.079> to<00:11:56.320> test<00:11:56.560> if 00:11:56.710 --> 00:11:56.720 align:start position:0% or off and are a great way to test if 00:11:56.720 --> 00:11:59.269 align:start position:0% or off and are a great way to test if sending<00:11:57.160> commands<00:11:57.880> also<00:11:58.240> works<00:11:58.880> but<00:11:59.000> we<00:11:59.240> we 00:11:59.269 --> 00:11:59.279 align:start position:0% sending commands also works but we we 00:11:59.279 --> 00:12:01.030 align:start position:0% sending commands also works but we we want<00:11:59.399> to<00:11:59.480> do<00:11:59.720> more<00:12:00.000> than<00:12:00.240> just<00:12:00.480> power<00:12:00.720> on 00:12:01.030 --> 00:12:01.040 align:start position:0% want to do more than just power on 00:12:01.040 --> 00:12:03.069 align:start position:0% want to do more than just power on devices<00:12:01.600> we<00:12:01.720> want<00:12:01.839> to<00:12:02.040> switch<00:12:02.320> to<00:12:02.480> the<00:12:02.720> right 00:12:03.069 --> 00:12:03.079 align:start position:0% devices we want to switch to the right 00:12:03.079 --> 00:12:05.590 align:start position:0% devices we want to switch to the right ports<00:12:03.480> for<00:12:03.680> the<00:12:03.880> PC<00:12:04.440> and<00:12:04.839> for<00:12:05.040> this<00:12:05.200> we<00:12:05.320> need<00:12:05.480> to 00:12:05.590 --> 00:12:05.600 align:start position:0% ports for the PC and for this we need to 00:12:05.600 --> 00:12:08.230 align:start position:0% ports for the PC and for this we need to send<00:12:05.920> a<00:12:06.160> specific<00:12:06.680> transmission<00:12:07.480> command 00:12:08.230 --> 00:12:08.240 align:start position:0% send a specific transmission command 00:12:08.240 --> 00:12:10.629 align:start position:0% send a specific transmission command this<00:12:08.399> has<00:12:08.480> to<00:12:08.600> be<00:12:08.720> in<00:12:08.800> the<00:12:08.959> form<00:12:09.200> of<00:12:09.320> an<00:12:09.560> echo<00:12:10.079> TX 00:12:10.629 --> 00:12:10.639 align:start position:0% this has to be in the form of an echo TX 00:12:10.639 --> 00:12:12.470 align:start position:0% this has to be in the form of an echo TX and<00:12:10.760> an<00:12:10.959> accomp<00:12:11.440> grouping<00:12:11.800> of<00:12:12.040> numbers 00:12:12.470 --> 00:12:12.480 align:start position:0% and an accomp grouping of numbers 00:12:12.480 --> 00:12:14.870 align:start position:0% and an accomp grouping of numbers separated<00:12:12.959> by<00:12:13.120> a<00:12:13.279> colon<00:12:13.959> and<00:12:14.160> ending<00:12:14.519> with<00:12:14.639> a 00:12:14.870 --> 00:12:14.880 align:start position:0% separated by a colon and ending with a 00:12:14.880 --> 00:12:18.509 align:start position:0% separated by a colon and ending with a pipe<00:12:15.240> and<00:12:15.480> C<00:12:16.199> client<00:12:16.839> DS<00:12:17.839> but<00:12:17.959> the<00:12:18.320> difficulty 00:12:18.509 --> 00:12:18.519 align:start position:0% pipe and C client DS but the difficulty 00:12:18.519 --> 00:12:20.870 align:start position:0% pipe and C client DS but the difficulty is<00:12:18.680> finding<00:12:19.000> the<00:12:19.240> right<00:12:19.519> code<00:12:20.360> theoretically 00:12:20.870 --> 00:12:20.880 align:start position:0% is finding the right code theoretically 00:12:20.880 --> 00:12:22.230 align:start position:0% is finding the right code theoretically you<00:12:20.920> should<00:12:21.120> be<00:12:21.199> able<00:12:21.399> to<00:12:21.519> see<00:12:21.760> it<00:12:21.959> while 00:12:22.230 --> 00:12:22.240 align:start position:0% you should be able to see it while 00:12:22.240 --> 00:12:24.430 align:start position:0% you should be able to see it while monitoring<00:12:22.760> the<00:12:22.920> signals<00:12:23.600> and<00:12:23.800> switching<00:12:24.199> to 00:12:24.430 --> 00:12:24.440 align:start position:0% monitoring the signals and switching to 00:12:24.440 --> 00:12:26.949 align:start position:0% monitoring the signals and switching to your<00:12:24.680> preferred<00:12:25.399> source<00:12:26.160> for<00:12:26.320> me<00:12:26.680> however 00:12:26.949 --> 00:12:26.959 align:start position:0% your preferred source for me however 00:12:26.959 --> 00:12:28.870 align:start position:0% your preferred source for me however this<00:12:27.199> never<00:12:27.519> worked<00:12:27.959> even<00:12:28.240> after<00:12:28.480> filtering 00:12:28.870 --> 00:12:28.880 align:start position:0% this never worked even after filtering 00:12:28.880 --> 00:12:31.310 align:start position:0% this never worked even after filtering for<00:12:29.199> Transmissions<00:12:29.760> I<00:12:29.880> could<00:12:30.079> never<00:12:30.399> spot<00:12:30.720> it 00:12:31.310 --> 00:12:31.320 align:start position:0% for Transmissions I could never spot it 00:12:31.320 --> 00:12:32.829 align:start position:0% for Transmissions I could never spot it however<00:12:31.639> after<00:12:31.839> some<00:12:32.000> soul<00:12:32.320> searching<00:12:32.760> I 00:12:32.829 --> 00:12:32.839 align:start position:0% however after some soul searching I 00:12:32.839 --> 00:12:34.550 align:start position:0% however after some soul searching I found<00:12:33.040> out<00:12:33.240> what<00:12:33.360> the<00:12:33.480> numbers<00:12:33.959> actually<00:12:34.240> mean 00:12:34.550 --> 00:12:34.560 align:start position:0% found out what the numbers actually mean 00:12:34.560 --> 00:12:36.230 align:start position:0% found out what the numbers actually mean and<00:12:34.680> I'm<00:12:34.800> going<00:12:34.959> to<00:12:35.120> try<00:12:35.279> to<00:12:35.480> explain<00:12:35.839> this<00:12:36.040> as 00:12:36.230 --> 00:12:36.240 align:start position:0% and I'm going to try to explain this as 00:12:36.240 --> 00:12:38.430 align:start position:0% and I'm going to try to explain this as best<00:12:36.480> as<00:12:36.600> I<00:12:36.800> can<00:12:37.279> without<00:12:37.720> fully 00:12:38.430 --> 00:12:38.440 align:start position:0% best as I can without fully 00:12:38.440 --> 00:12:40.550 align:start position:0% best as I can without fully understanding<00:12:38.680> it<00:12:38.959> myself<00:12:39.839> the<00:12:40.000> first<00:12:40.279> pair 00:12:40.550 --> 00:12:40.560 align:start position:0% understanding it myself the first pair 00:12:40.560 --> 00:12:42.509 align:start position:0% understanding it myself the first pair targets<00:12:41.000> the<00:12:41.160> destination<00:12:41.760> device<00:12:42.160> in<00:12:42.279> my 00:12:42.509 --> 00:12:42.519 align:start position:0% targets the destination device in my 00:12:42.519 --> 00:12:44.829 align:start position:0% targets the destination device in my case<00:12:42.760> that<00:12:42.880> is<00:12:43.000> the<00:12:43.199> AV<00:12:43.839> receiver<00:12:44.279> so<00:12:44.440> I<00:12:44.560> opened 00:12:44.829 --> 00:12:44.839 align:start position:0% case that is the AV receiver so I opened 00:12:44.839 --> 00:12:46.550 align:start position:0% case that is the AV receiver so I opened up<00:12:44.959> the<00:12:45.160> command<00:12:45.480> line<00:12:45.720> again<00:12:45.880> and<00:12:46.079> navigated 00:12:46.550 --> 00:12:46.560 align:start position:0% up the command line again and navigated 00:12:46.560 --> 00:12:48.710 align:start position:0% up the command line again and navigated to<00:12:46.720> where<00:12:46.839> the<00:12:47.000> CC<00:12:47.519> client<00:12:47.839> file<00:12:48.120> was<00:12:48.560> and 00:12:48.710 --> 00:12:48.720 align:start position:0% to where the CC client file was and 00:12:48.720 --> 00:12:54.069 align:start position:0% to where the CC client file was and typed<00:12:49.000> in<00:12:49.240> echos<00:12:49.680> scan<00:12:50.199> pipe<00:12:50.560> CC<00:12:51.160> C-<00:12:52.279> s-d<00:12:53.279> one 00:12:54.069 --> 00:12:54.079 align:start position:0% typed in echos scan pipe CC C- s-d one 00:12:54.079 --> 00:12:55.990 align:start position:0% typed in echos scan pipe CC C- s-d one this<00:12:54.240> gave<00:12:54.440> me<00:12:54.560> a<00:12:54.680> list<00:12:54.880> of<00:12:55.040> all<00:12:55.279> the<00:12:55.480> connected 00:12:55.990 --> 00:12:56.000 align:start position:0% this gave me a list of all the connected 00:12:56.000 --> 00:12:58.389 align:start position:0% this gave me a list of all the connected devices<00:12:56.639> amongst<00:12:57.000> which<00:12:57.199> was<00:12:57.440> also<00:12:57.680> the<00:12:57.839> AV 00:12:58.389 --> 00:12:58.399 align:start position:0% devices amongst which was also the AV 00:12:58.399 --> 00:13:00.550 align:start position:0% devices amongst which was also the AV receiver<00:12:58.639> with<00:12:58.760> the<00:12:58.920> S<00:12:59.199> signed<00:12:59.519> number<00:12:59.959> five 00:13:00.550 --> 00:13:00.560 align:start position:0% receiver with the S signed number five 00:13:00.560 --> 00:13:02.110 align:start position:0% receiver with the S signed number five meaning<00:13:00.839> the<00:13:00.959> first<00:13:01.240> pair<00:13:01.480> in<00:13:01.600> the<00:13:01.720> group<00:13:01.959> of 00:13:02.110 --> 00:13:02.120 align:start position:0% meaning the first pair in the group of 00:13:02.120 --> 00:13:05.150 align:start position:0% meaning the first pair in the group of numbers<00:13:02.560> is<00:13:02.800> 5f<00:13:03.760> the<00:13:04.120> f<00:13:04.519> is<00:13:04.720> just<00:13:04.880> a 00:13:05.150 --> 00:13:05.160 align:start position:0% numbers is 5f the f is just a 00:13:05.160 --> 00:13:07.189 align:start position:0% numbers is 5f the f is just a placeholder<00:13:05.720> from<00:13:05.880> what<00:13:06.000> I<00:13:06.399> understand<00:13:07.000> the 00:13:07.189 --> 00:13:07.199 align:start position:0% placeholder from what I understand the 00:13:07.199 --> 00:13:08.710 align:start position:0% placeholder from what I understand the second<00:13:07.440> pair<00:13:07.639> in<00:13:07.760> the<00:13:07.920> cluster<00:13:08.279> tells<00:13:08.519> the 00:13:08.710 --> 00:13:08.720 align:start position:0% second pair in the cluster tells the 00:13:08.720 --> 00:13:11.150 align:start position:0% second pair in the cluster tells the destination<00:13:09.320> device<00:13:09.720> so<00:13:10.000> the<00:13:10.160> AV<00:13:10.800> receiver 00:13:11.150 --> 00:13:11.160 align:start position:0% destination device so the AV receiver 00:13:11.160 --> 00:13:13.310 align:start position:0% destination device so the AV receiver what<00:13:11.360> we<00:13:11.480> want<00:13:11.760> to<00:13:11.959> do<00:13:12.399> in<00:13:12.560> our<00:13:12.800> case<00:13:13.000> we<00:13:13.120> want 00:13:13.310 --> 00:13:13.320 align:start position:0% what we want to do in our case we want 00:13:13.320 --> 00:13:15.790 align:start position:0% what we want to do in our case we want to<00:13:13.480> switch<00:13:13.839> the<00:13:14.199> active<00:13:14.760> source<00:13:15.639> which 00:13:15.790 --> 00:13:15.800 align:start position:0% to switch the active source which 00:13:15.800 --> 00:13:18.590 align:start position:0% to switch the active source which according<00:13:16.079> to<00:13:16.199> the<00:13:16.320> website<00:13:16.920> catic<00:13:17.920> is 00:13:18.590 --> 00:13:18.600 align:start position:0% according to the website catic is 00:13:18.600 --> 00:13:21.189 align:start position:0% according to the website catic is 82<00:13:19.600> the<00:13:19.760> third<00:13:20.040> pair<00:13:20.240> was<00:13:20.440> the<00:13:20.560> most<00:13:21.079> difficult 00:13:21.189 --> 00:13:21.199 align:start position:0% 82 the third pair was the most difficult 00:13:21.199 --> 00:13:23.350 align:start position:0% 82 the third pair was the most difficult to<00:13:21.360> decipher<00:13:21.880> and<00:13:22.120> is<00:13:22.240> the<00:13:22.440> physical<00:13:22.880> address 00:13:23.350 --> 00:13:23.360 align:start position:0% to decipher and is the physical address 00:13:23.360 --> 00:13:25.670 align:start position:0% to decipher and is the physical address of<00:13:23.480> the<00:13:23.680> devices<00:13:24.160> that<00:13:24.320> need<00:13:24.680> changing<00:13:25.480> from 00:13:25.670 --> 00:13:25.680 align:start position:0% of the devices that need changing from 00:13:25.680 --> 00:13:27.949 align:start position:0% of the devices that need changing from what<00:13:25.800> I<00:13:25.920> figured<00:13:26.240> out<00:13:26.519> during<00:13:26.839> a<00:13:27.040> blind<00:13:27.399> firing 00:13:27.949 --> 00:13:27.959 align:start position:0% what I figured out during a blind firing 00:13:27.959 --> 00:13:29.990 align:start position:0% what I figured out during a blind firing scenario<00:13:28.480> where<00:13:28.600> I<00:13:28.720> shot<00:13:29.160> random<00:13:29.560> numbers 00:13:29.990 --> 00:13:30.000 align:start position:0% scenario where I shot random numbers 00:13:30.000 --> 00:13:31.870 align:start position:0% scenario where I shot random numbers through<00:13:30.240> the<00:13:30.440> command<00:13:30.880> line<00:13:31.160> using<00:13:31.560> my 00:13:31.870 --> 00:13:31.880 align:start position:0% through the command line using my 00:13:31.880 --> 00:13:34.870 align:start position:0% through the command line using my remotely<00:13:32.399> connected<00:13:32.839> MacBook<00:13:33.320> Pro<00:13:33.600> to<00:13:33.720> the<00:13:33.920> PC 00:13:34.870 --> 00:13:34.880 align:start position:0% remotely connected MacBook Pro to the PC 00:13:34.880 --> 00:13:36.550 align:start position:0% remotely connected MacBook Pro to the PC the<00:13:35.000> first<00:13:35.320> number<00:13:35.639> appeared<00:13:35.959> to<00:13:36.079> be<00:13:36.199> for<00:13:36.399> my 00:13:36.550 --> 00:13:36.560 align:start position:0% the first number appeared to be for my 00:13:36.560 --> 00:13:39.350 align:start position:0% the first number appeared to be for my TV's<00:13:37.120> HDMI<00:13:37.800> ports<00:13:38.399> while<00:13:38.560> the<00:13:38.720> second<00:13:38.959> one<00:13:39.199> was 00:13:39.350 --> 00:13:39.360 align:start position:0% TV's HDMI ports while the second one was 00:13:39.360 --> 00:13:41.870 align:start position:0% TV's HDMI ports while the second one was for<00:13:39.560> my<00:13:39.720> AV<00:13:40.399> receivers<00:13:41.079> the<00:13:41.240> last<00:13:41.519> pair<00:13:41.720> is 00:13:41.870 --> 00:13:41.880 align:start position:0% for my AV receivers the last pair is 00:13:41.880 --> 00:13:43.629 align:start position:0% for my AV receivers the last pair is just<00:13:42.120> padding<00:13:42.440> as<00:13:42.560> I<00:13:42.959> understand<00:13:43.120> and<00:13:43.360> can<00:13:43.480> be 00:13:43.629 --> 00:13:43.639 align:start position:0% just padding as I understand and can be 00:13:43.639 --> 00:13:45.790 align:start position:0% just padding as I understand and can be left<00:13:43.839> at<00:13:44.040> double<00:13:44.399> zero<00:13:44.920> but<00:13:45.160> this<00:13:45.320> working<00:13:45.680> it 00:13:45.790 --> 00:13:45.800 align:start position:0% left at double zero but this working it 00:13:45.800 --> 00:13:48.350 align:start position:0% left at double zero but this working it was<00:13:46.000> time<00:13:46.160> to<00:13:46.360> wrap<00:13:46.760> things<00:13:47.079> up<00:13:47.399> and<00:13:47.959> get<00:13:48.120> it 00:13:48.350 --> 00:13:48.360 align:start position:0% was time to wrap things up and get it 00:13:48.360 --> 00:13:50.189 align:start position:0% was time to wrap things up and get it automated<00:13:49.360> the<00:13:49.519> goal<00:13:49.800> just<00:13:49.959> for 00:13:50.189 --> 00:13:50.199 align:start position:0% automated the goal just for 00:13:50.199 --> 00:13:52.030 align:start position:0% automated the goal just for clarification<00:13:51.000> is<00:13:51.160> that<00:13:51.360> this<00:13:51.519> is<00:13:51.639> triggered 00:13:52.030 --> 00:13:52.040 align:start position:0% clarification is that this is triggered 00:13:52.040 --> 00:13:54.509 align:start position:0% clarification is that this is triggered when<00:13:52.160> the<00:13:52.320> PC<00:13:52.639> turns<00:13:53.120> on<00:13:53.440> or<00:13:53.639> wakes<00:13:53.959> from<00:13:54.199> sleep 00:13:54.509 --> 00:13:54.519 align:start position:0% when the PC turns on or wakes from sleep 00:13:54.519 --> 00:13:56.829 align:start position:0% when the PC turns on or wakes from sleep so<00:13:54.680> it<00:13:54.800> tells<00:13:55.079> the<00:13:55.199> AV<00:13:55.839> receiver<00:13:56.320> to<00:13:56.519> switch 00:13:56.829 --> 00:13:56.839 align:start position:0% so it tells the AV receiver to switch 00:13:56.839 --> 00:13:59.590 align:start position:0% so it tells the AV receiver to switch the<00:13:57.000> HDMI<00:13:57.600> ports<00:13:57.920> to<00:13:58.040> the<00:13:58.240> PC<00:13:59.120> in<00:13:59.199> order<00:13:59.399> to 00:13:59.590 --> 00:13:59.600 align:start position:0% the HDMI ports to the PC in order to 00:13:59.600 --> 00:14:01.430 align:start position:0% the HDMI ports to the PC in order to achieve<00:13:59.959> this<00:14:00.279> we<00:14:00.399> must<00:14:00.680> first<00:14:00.959> get<00:14:01.160> these 00:14:01.430 --> 00:14:01.440 align:start position:0% achieve this we must first get these 00:14:01.440 --> 00:14:03.629 align:start position:0% achieve this we must first get these commands<00:14:01.880> into<00:14:02.120> an<00:14:02.320> executable<00:14:03.040> format<00:14:03.480> and 00:14:03.629 --> 00:14:03.639 align:start position:0% commands into an executable format and 00:14:03.639 --> 00:14:05.430 align:start position:0% commands into an executable format and being<00:14:03.880> inspired<00:14:04.360> by<00:14:04.480> the<00:14:04.600> command<00:14:04.920> line<00:14:05.120> files 00:14:05.430 --> 00:14:05.440 align:start position:0% being inspired by the command line files 00:14:05.440 --> 00:14:06.949 align:start position:0% being inspired by the command line files that<00:14:05.600> came<00:14:05.800> shipped<00:14:06.199> with<00:14:06.320> the<00:14:06.480> pulse<00:14:06.720> a 00:14:06.949 --> 00:14:06.959 align:start position:0% that came shipped with the pulse a 00:14:06.959 --> 00:14:09.590 align:start position:0% that came shipped with the pulse a library<00:14:07.639> I<00:14:07.759> opted<00:14:08.040> for<00:14:08.279> this<00:14:08.519> as<00:14:08.680> well<00:14:09.240> first<00:14:09.480> I 00:14:09.590 --> 00:14:09.600 align:start position:0% library I opted for this as well first I 00:14:09.600 --> 00:14:11.509 align:start position:0% library I opted for this as well first I added<00:14:09.839> the<00:14:09.959> power<00:14:10.160> on<00:14:10.399> command<00:14:10.839> I<00:14:10.959> stole<00:14:11.279> from 00:14:11.509 --> 00:14:11.519 align:start position:0% added the power on command I stole from 00:14:11.519 --> 00:14:14.030 align:start position:0% added the power on command I stole from the<00:14:11.800> pulse<00:14:12.079> 8<00:14:12.440> Library<00:14:12.920> demo<00:14:13.279> files<00:14:13.720> just<00:14:13.880> in 00:14:14.030 --> 00:14:14.040 align:start position:0% the pulse 8 Library demo files just in 00:14:14.040 --> 00:14:15.790 align:start position:0% the pulse 8 Library demo files just in case<00:14:14.320> everything<00:14:14.639> is<00:14:14.839> off<00:14:15.199> during<00:14:15.399> a<00:14:15.560> boot 00:14:15.790 --> 00:14:15.800 align:start position:0% case everything is off during a boot 00:14:15.800 --> 00:14:17.670 align:start position:0% case everything is off during a boot scenario<00:14:16.480> since<00:14:16.759> both<00:14:16.959> take<00:14:17.160> a<00:14:17.320> while<00:14:17.480> before 00:14:17.670 --> 00:14:17.680 align:start position:0% scenario since both take a while before 00:14:17.680 --> 00:14:19.430 align:start position:0% scenario since both take a while before they're<00:14:17.880> fully<00:14:18.160> operational<00:14:18.680> I<00:14:18.800> also<00:14:19.000> added<00:14:19.279> a 00:14:19.430 --> 00:14:19.440 align:start position:0% they're fully operational I also added a 00:14:19.440 --> 00:14:21.670 align:start position:0% they're fully operational I also added a 10-second<00:14:20.079> delay<00:14:20.600> which<00:14:20.839> seems<00:14:21.079> to<00:14:21.199> be<00:14:21.440> just 00:14:21.670 --> 00:14:21.680 align:start position:0% 10-second delay which seems to be just 00:14:21.680 --> 00:14:23.629 align:start position:0% 10-second delay which seems to be just enough<00:14:22.040> time<00:14:22.240> for<00:14:22.440> firing<00:14:22.800> the<00:14:23.079> commands<00:14:23.480> to 00:14:23.629 --> 00:14:23.639 align:start position:0% enough time for firing the commands to 00:14:23.639 --> 00:14:26.030 align:start position:0% enough time for firing the commands to switch<00:14:23.920> to<00:14:24.120> input<00:14:24.480> sources<00:14:25.279> I<00:14:25.360> saved<00:14:25.680> the<00:14:25.839> file 00:14:26.030 --> 00:14:26.040 align:start position:0% switch to input sources I saved the file 00:14:26.040 --> 00:14:27.790 align:start position:0% switch to input sources I saved the file in<00:14:26.160> my<00:14:26.360> documents<00:14:26.800> folder<00:14:27.120> and<00:14:27.279> fired<00:14:27.600> up 00:14:27.790 --> 00:14:27.800 align:start position:0% in my documents folder and fired up 00:14:27.800 --> 00:14:29.550 align:start position:0% in my documents folder and fired up Windows<00:14:28.199> task<00:14:28.519> schedule<00:14:29.160> which<00:14:29.279> I<00:14:29.360> didn't 00:14:29.550 --> 00:14:29.560 align:start position:0% Windows task schedule which I didn't 00:14:29.560 --> 00:14:31.910 align:start position:0% Windows task schedule which I didn't know<00:14:29.800> existed<00:14:30.199> before<00:14:30.480> making<00:14:30.800> this<00:14:31.000> video<00:14:31.720> in 00:14:31.910 --> 00:14:31.920 align:start position:0% know existed before making this video in 00:14:31.920 --> 00:14:33.910 align:start position:0% know existed before making this video in here<00:14:32.040> you<00:14:32.160> can<00:14:32.360> schedule<00:14:32.759> well<00:14:33.279> tasks<00:14:33.759> that 00:14:33.910 --> 00:14:33.920 align:start position:0% here you can schedule well tasks that 00:14:33.920 --> 00:14:35.910 align:start position:0% here you can schedule well tasks that fire<00:14:34.160> on<00:14:34.320> your<00:14:34.440> triggers<00:14:34.800> of<00:14:35.000> choice<00:14:35.560> it<00:14:35.800> kind 00:14:35.910 --> 00:14:35.920 align:start position:0% fire on your triggers of choice it kind 00:14:35.920 --> 00:14:37.749 align:start position:0% fire on your triggers of choice it kind of<00:14:36.040> reminds<00:14:36.360> me<00:14:36.440> of<00:14:36.560> Apple's<00:14:36.880> shortcuts<00:14:37.480> app 00:14:37.749 --> 00:14:37.759 align:start position:0% of reminds me of Apple's shortcuts app 00:14:37.759 --> 00:14:39.629 align:start position:0% of reminds me of Apple's shortcuts app but<00:14:37.920> a<00:14:38.040> little<00:14:38.240> less<00:14:38.480> friendly<00:14:38.959> but<00:14:39.240> way<00:14:39.399> more 00:14:39.629 --> 00:14:39.639 align:start position:0% but a little less friendly but way more 00:14:39.639 --> 00:14:41.790 align:start position:0% but a little less friendly but way more in-<00:14:39.880> depth<00:14:40.360> I<00:14:40.480> created<00:14:40.759> a<00:14:40.880> new<00:14:41.160> task<00:14:41.600> which<00:14:41.680> is 00:14:41.790 --> 00:14:41.800 align:start position:0% in- depth I created a new task which is 00:14:41.800 --> 00:14:43.670 align:start position:0% in- depth I created a new task which is triggered<00:14:42.199> by<00:14:42.320> an<00:14:42.480> event<00:14:42.880> in<00:14:43.120> particular 00:14:43.670 --> 00:14:43.680 align:start position:0% triggered by an event in particular 00:14:43.680 --> 00:14:45.710 align:start position:0% triggered by an event in particular system<00:14:44.079> and<00:14:44.440> then<00:14:44.680> power<00:14:45.079> troubleshooter 00:14:45.710 --> 00:14:45.720 align:start position:0% system and then power troubleshooter 00:14:45.720 --> 00:14:47.870 align:start position:0% system and then power troubleshooter with<00:14:45.839> the<00:14:46.000> event<00:14:46.360> code<00:14:46.720> one<00:14:47.519> this<00:14:47.639> should 00:14:47.870 --> 00:14:47.880 align:start position:0% with the event code one this should 00:14:47.880 --> 00:14:49.990 align:start position:0% with the event code one this should cover<00:14:48.160> waking<00:14:48.480> up<00:14:48.680> from<00:14:48.959> sleep<00:14:49.600> the<00:14:49.759> final 00:14:49.990 --> 00:14:50.000 align:start position:0% cover waking up from sleep the final 00:14:50.000 --> 00:14:52.030 align:start position:0% cover waking up from sleep the final step<00:14:50.199> was<00:14:50.320> to<00:14:50.480> add<00:14:50.720> the<00:14:50.920> file<00:14:51.360> as<00:14:51.560> the<00:14:51.800> action 00:14:52.030 --> 00:14:52.040 align:start position:0% step was to add the file as the action 00:14:52.040 --> 00:14:57.030 align:start position:0% step was to add the file as the action to<00:14:52.199> be<00:14:52.360> executed<00:14:52.839> for<00:14:53.320> both<00:14:53.639> and<00:14:53.880> then<00:14:54.120> save 00:14:57.030 --> 00:14:57.040 align:start position:0% 00:14:57.040 --> 00:14:59.389 align:start position:0% everything<00:14:58.040> I<00:14:58.199> finally<00:14:58.519> had<00:14:58.639> to<00:14:58.800> set<00:14:59.120> up<00:14:59.240> I 00:14:59.389 --> 00:14:59.399 align:start position:0% everything I finally had to set up I 00:14:59.399 --> 00:15:01.069 align:start position:0% everything I finally had to set up I always<00:14:59.680> envisioned<00:15:00.399> with<00:15:00.519> the<00:15:00.680> hit<00:15:00.839> of<00:15:00.959> a 00:15:01.069 --> 00:15:01.079 align:start position:0% always envisioned with the hit of a 00:15:01.079 --> 00:15:02.870 align:start position:0% always envisioned with the hit of a button<00:15:01.320> on<00:15:01.440> my<00:15:01.639> controller<00:15:02.160> the<00:15:02.320> PC<00:15:02.600> wakes 00:15:02.870 --> 00:15:02.880 align:start position:0% button on my controller the PC wakes 00:15:02.880 --> 00:15:04.670 align:start position:0% button on my controller the PC wakes from<00:15:03.079> sleep<00:15:03.440> and<00:15:03.680> automatically<00:15:04.240> launches 00:15:04.670 --> 00:15:04.680 align:start position:0% from sleep and automatically launches 00:15:04.680 --> 00:15:07.030 align:start position:0% from sleep and automatically launches into<00:15:04.920> steam's<00:15:05.399> big<00:15:05.680> picture<00:15:06.000> mode<00:15:06.560> Windows 00:15:07.030 --> 00:15:07.040 align:start position:0% into steam's big picture mode Windows 00:15:07.040 --> 00:15:08.870 align:start position:0% into steam's big picture mode Windows task<00:15:07.360> schedule<00:15:07.839> then<00:15:07.959> triggers<00:15:08.320> my<00:15:08.519> command 00:15:08.870 --> 00:15:08.880 align:start position:0% task schedule then triggers my command 00:15:08.880 --> 00:15:10.590 align:start position:0% task schedule then triggers my command line<00:15:09.079> file<00:15:09.399> which<00:15:09.560> sends<00:15:09.880> the<00:15:10.079> appropriate 00:15:10.590 --> 00:15:10.600 align:start position:0% line file which sends the appropriate 00:15:10.600 --> 00:15:12.790 align:start position:0% line file which sends the appropriate HDMI<00:15:11.120> signals<00:15:11.480> to<00:15:11.600> the<00:15:11.720> AV<00:15:12.240> receiver<00:15:12.440> and<00:15:12.639> the 00:15:12.790 --> 00:15:12.800 align:start position:0% HDMI signals to the AV receiver and the 00:15:12.800 --> 00:15:15.389 align:start position:0% HDMI signals to the AV receiver and the TV<00:15:13.680> both<00:15:13.959> turn<00:15:14.240> on<00:15:14.800> and<00:15:14.959> switch<00:15:15.199> to<00:15:15.279> the 00:15:15.389 --> 00:15:15.399 align:start position:0% TV both turn on and switch to the 00:15:15.399 --> 00:15:18.069 align:start position:0% TV both turn on and switch to the corresponding<00:15:16.000> inputs<00:15:16.920> everything<00:15:17.880> just 00:15:18.069 --> 00:15:18.079 align:start position:0% corresponding inputs everything just 00:15:18.079 --> 00:15:20.790 align:start position:0% corresponding inputs everything just like<00:15:18.240> a<00:15:18.360> gaming<00:15:18.720> console<00:15:19.720> I<00:15:19.959> absolutely<00:15:20.399> love 00:15:20.790 --> 00:15:20.800 align:start position:0% like a gaming console I absolutely love 00:15:20.800 --> 00:15:22.829 align:start position:0% like a gaming console I absolutely love this<00:15:21.120> and<00:15:21.360> I<00:15:21.480> have<00:15:21.720> no<00:15:21.959> idea<00:15:22.240> whether<00:15:22.399> or<00:15:22.519> not<00:15:22.680> I 00:15:22.829 --> 00:15:22.839 align:start position:0% this and I have no idea whether or not I 00:15:22.839 --> 00:15:24.870 align:start position:0% this and I have no idea whether or not I took<00:15:23.079> the<00:15:23.240> easiest<00:15:23.639> route<00:15:23.920> or<00:15:24.040> a<00:15:24.240> convoluted 00:15:24.870 --> 00:15:24.880 align:start position:0% took the easiest route or a convoluted 00:15:24.880 --> 00:15:26.870 align:start position:0% took the easiest route or a convoluted mess<00:15:25.199> I<00:15:25.320> brought<00:15:25.639> upon<00:15:26.000> myself<00:15:26.519> for<00:15:26.720> not 00:15:26.870 --> 00:15:26.880 align:start position:0% mess I brought upon myself for not 00:15:26.880 --> 00:15:28.670 align:start position:0% mess I brought upon myself for not knowing<00:15:27.199> any<00:15:27.399> better<00:15:27.880> but<00:15:28.040> it's<00:15:28.240> working<00:15:28.560> and 00:15:28.670 --> 00:15:28.680 align:start position:0% knowing any better but it's working and 00:15:28.680 --> 00:15:30.389 align:start position:0% knowing any better but it's working and it<00:15:28.800> has<00:15:29.000> has<00:15:29.120> been<00:15:29.240> working<00:15:29.639> very<00:15:29.839> reliably 00:15:30.389 --> 00:15:30.399 align:start position:0% it has has been working very reliably 00:15:30.399 --> 00:15:32.269 align:start position:0% it has has been working very reliably for<00:15:30.560> the<00:15:30.759> past<00:15:31.079> months<00:15:31.440> so<00:15:31.560> I'm<00:15:31.759> quite<00:15:31.920> a<00:15:32.040> bit 00:15:32.269 --> 00:15:32.279 align:start position:0% for the past months so I'm quite a bit 00:15:32.279 --> 00:15:34.629 align:start position:0% for the past months so I'm quite a bit ecstatic<00:15:32.800> about<00:15:33.120> this<00:15:33.639> setting<00:15:34.000> the<00:15:34.120> PC<00:15:34.399> to 00:15:34.629 --> 00:15:34.639 align:start position:0% ecstatic about this setting the PC to 00:15:34.639 --> 00:15:36.629 align:start position:0% ecstatic about this setting the PC to standby<00:15:35.120> is<00:15:35.240> super<00:15:35.560> easy<00:15:35.880> too<00:15:36.240> by<00:15:36.360> the<00:15:36.480> way 00:15:36.629 --> 00:15:36.639 align:start position:0% standby is super easy too by the way 00:15:36.639 --> 00:15:38.509 align:start position:0% standby is super easy too by the way steam<00:15:37.079> has<00:15:37.199> a<00:15:37.319> number<00:15:37.560> of<00:15:37.759> power<00:15:38.000> controls 00:15:38.509 --> 00:15:38.519 align:start position:0% steam has a number of power controls 00:15:38.519 --> 00:15:41.150 align:start position:0% steam has a number of power controls with<00:15:38.720> suspend<00:15:39.279> putting<00:15:39.519> the<00:15:39.680> box<00:15:40.000> to<00:15:40.279> rest<00:15:41.079> I 00:15:41.150 --> 00:15:41.160 align:start position:0% with suspend putting the box to rest I 00:15:41.160 --> 00:15:42.990 align:start position:0% with suspend putting the box to rest I didn't<00:15:41.399> add<00:15:41.600> any<00:15:41.800> further<00:15:42.120> automation<00:15:42.720> for 00:15:42.990 --> 00:15:43.000 align:start position:0% didn't add any further automation for 00:15:43.000 --> 00:15:45.389 align:start position:0% didn't add any further automation for this<00:15:43.319> as<00:15:43.519> I<00:15:43.720> most<00:15:44.040> often<00:15:44.360> will<00:15:44.600> continue<00:15:45.040> to<00:15:45.160> do 00:15:45.389 --> 00:15:45.399 align:start position:0% this as I most often will continue to do 00:15:45.399 --> 00:15:47.590 align:start position:0% this as I most often will continue to do something<00:15:45.839> else<00:15:46.240> after<00:15:46.480> play<00:15:46.800> time<00:15:46.959> is<00:15:47.120> over 00:15:47.590 --> 00:15:47.600 align:start position:0% something else after play time is over 00:15:47.600 --> 00:15:49.030 align:start position:0% something else after play time is over but<00:15:47.800> you<00:15:47.920> could<00:15:48.120> also<00:15:48.360> add<00:15:48.519> shutdown 00:15:49.030 --> 00:15:49.040 align:start position:0% but you could also add shutdown 00:15:49.040 --> 00:15:51.030 align:start position:0% but you could also add shutdown automations<00:15:49.800> using<00:15:50.079> the<00:15:50.279> same<00:15:50.519> methods<00:15:50.920> as 00:15:51.030 --> 00:15:51.040 align:start position:0% automations using the same methods as 00:15:51.040 --> 00:15:53.470 align:start position:0% automations using the same methods as shown<00:15:51.839> setting<00:15:52.199> this<00:15:52.360> up<00:15:52.560> has<00:15:52.680> been<00:15:53.000> a<00:15:53.120> lot<00:15:53.279> of 00:15:53.470 --> 00:15:53.480 align:start position:0% shown setting this up has been a lot of 00:15:53.480 --> 00:15:55.590 align:start position:0% shown setting this up has been a lot of fun<00:15:54.000> in<00:15:54.199> the<00:15:54.399> past<00:15:54.639> PCS<00:15:55.040> we're<00:15:55.279> heavily 00:15:55.590 --> 00:15:55.600 align:start position:0% fun in the past PCS we're heavily 00:15:55.600 --> 00:15:57.430 align:start position:0% fun in the past PCS we're heavily confined<00:15:56.000> to<00:15:56.160> a<00:15:56.319> desk<00:15:56.639> but<00:15:56.759> for<00:15:57.000> quite<00:15:57.199> some 00:15:57.430 --> 00:15:57.440 align:start position:0% confined to a desk but for quite some 00:15:57.440 --> 00:15:59.470 align:start position:0% confined to a desk but for quite some time<00:15:57.680> now<00:15:57.959> mostly<00:15:58.360> thanks<00:15:58.560> to<00:15:58.680> Steve<00:15:59.000> team 00:15:59.470 --> 00:15:59.480 align:start position:0% time now mostly thanks to Steve team 00:15:59.480 --> 00:16:01.309 align:start position:0% time now mostly thanks to Steve team have<00:15:59.639> made<00:15:59.880> their<00:16:00.079> way<00:16:00.240> into<00:16:00.600> a<00:16:00.720> lot<00:16:00.880> of<00:16:01.040> new 00:16:01.309 --> 00:16:01.319 align:start position:0% have made their way into a lot of new 00:16:01.319 --> 00:16:04.309 align:start position:0% have made their way into a lot of new areas<00:16:01.839> and<00:16:02.040> form<00:16:02.480> factors<00:16:03.319> the<00:16:03.519> times<00:16:03.839> are<00:16:04.120> a 00:16:04.309 --> 00:16:04.319 align:start position:0% areas and form factors the times are a 00:16:04.319 --> 00:16:06.110 align:start position:0% areas and form factors the times are a changing<00:16:04.800> if<00:16:04.880> you<00:16:05.040> will<00:16:05.319> and<00:16:05.519> with<00:16:05.720> more<00:16:05.920> and 00:16:06.110 --> 00:16:06.120 align:start position:0% changing if you will and with more and 00:16:06.120 --> 00:16:07.949 align:start position:0% changing if you will and with more and more<00:16:06.399> console<00:16:06.800> exclusives<00:16:07.319> now<00:16:07.519> also<00:16:07.759> being 00:16:07.949 --> 00:16:07.959 align:start position:0% more console exclusives now also being 00:16:07.959 --> 00:16:10.550 align:start position:0% more console exclusives now also being available<00:16:08.319> on<00:16:08.519> PC<00:16:09.279> this<00:16:09.440> is<00:16:09.600> becoming<00:16:10.120> quite<00:16:10.360> a 00:16:10.550 --> 00:16:10.560 align:start position:0% available on PC this is becoming quite a 00:16:10.560 --> 00:16:12.949 align:start position:0% available on PC this is becoming quite a compelling<00:16:11.279> alternative<00:16:12.279> it's<00:16:12.480> by<00:16:12.600> far<00:16:12.800> the 00:16:12.949 --> 00:16:12.959 align:start position:0% compelling alternative it's by far the 00:16:12.959 --> 00:16:14.949 align:start position:0% compelling alternative it's by far the most<00:16:13.240> high-end<00:16:13.720> gaming<00:16:14.079> experience<00:16:14.519> you<00:16:14.639> can 00:16:14.949 --> 00:16:14.959 align:start position:0% most high-end gaming experience you can 00:16:14.959 --> 00:16:16.790 align:start position:0% most high-end gaming experience you can get<00:16:15.120> at<00:16:15.240> the<00:16:15.399> moment<00:16:15.880> visually<00:16:16.279> speaking<00:16:16.639> of 00:16:16.790 --> 00:16:16.800 align:start position:0% get at the moment visually speaking of 00:16:16.800 --> 00:16:18.309 align:start position:0% get at the moment visually speaking of course<00:16:17.360> but<00:16:17.480> you<00:16:17.560> don't<00:16:17.720> need<00:16:17.880> the<00:16:18.000> biggest 00:16:18.309 --> 00:16:18.319 align:start position:0% course but you don't need the biggest 00:16:18.319 --> 00:16:19.829 align:start position:0% course but you don't need the biggest and<00:16:18.519> baddest<00:16:18.959> system<00:16:19.240> for<00:16:19.480> this 00:16:19.829 --> 00:16:19.839 align:start position:0% and baddest system for this 00:16:19.839 --> 00:16:22.150 align:start position:0% and baddest system for this theoretically<00:16:20.360> this<00:16:20.480> should<00:16:20.680> work<00:16:20.880> on<00:16:21.279> any<00:16:21.600> PC 00:16:22.150 --> 00:16:22.160 align:start position:0% theoretically this should work on any PC 00:16:22.160 --> 00:16:23.910 align:start position:0% theoretically this should work on any PC meaning<00:16:22.480> lower<00:16:22.800> powered<00:16:23.160> machines<00:16:23.600> can<00:16:23.720> be 00:16:23.910 --> 00:16:23.920 align:start position:0% meaning lower powered machines can be 00:16:23.920 --> 00:16:26.309 align:start position:0% meaning lower powered machines can be converted<00:16:24.360> into<00:16:24.639> gaming<00:16:25.079> consoles<00:16:25.720> just<00:16:26.079> as 00:16:26.309 --> 00:16:26.319 align:start position:0% converted into gaming consoles just as 00:16:26.319 --> 00:16:28.269 align:start position:0% converted into gaming consoles just as well<00:16:26.680> running<00:16:27.040> less<00:16:27.240> demanding<00:16:27.759> titles<00:16:28.160> but 00:16:28.269 --> 00:16:28.279 align:start position:0% well running less demanding titles but 00:16:28.279 --> 00:16:30.189 align:start position:0% well running less demanding titles but giving<00:16:28.480> you<00:16:28.600> the<00:16:28.920> same<00:16:29.199> Couch<00:16:29.560> Potato 00:16:30.189 --> 00:16:30.199 align:start position:0% giving you the same Couch Potato 00:16:30.199 --> 00:16:32.670 align:start position:0% giving you the same Couch Potato experience<00:16:31.199> or<00:16:31.440> have<00:16:31.560> a<00:16:31.759> tandem<00:16:32.199> system<00:16:32.480> in 00:16:32.670 --> 00:16:32.680 align:start position:0% experience or have a tandem system in 00:16:32.680 --> 00:16:34.309 align:start position:0% experience or have a tandem system in play<00:16:32.920> with<00:16:33.040> one<00:16:33.160> of<00:16:33.279> the<00:16:33.440> many<00:16:33.680> PC<00:16:34.000> gaming 00:16:34.309 --> 00:16:34.319 align:start position:0% play with one of the many PC gaming 00:16:34.319 --> 00:16:36.069 align:start position:0% play with one of the many PC gaming handhelds<00:16:34.880> available<00:16:35.319> these<00:16:35.560> days<00:16:35.880> giving 00:16:36.069 --> 00:16:36.079 align:start position:0% handhelds available these days giving 00:16:36.079 --> 00:16:37.710 align:start position:0% handhelds available these days giving you<00:16:36.160> the<00:16:36.279> switch<00:16:36.600> Pro<00:16:36.920> experience<00:16:37.399> you've 00:16:37.710 --> 00:16:37.720 align:start position:0% you the switch Pro experience you've 00:16:37.720 --> 00:16:39.829 align:start position:0% you the switch Pro experience you've always<00:16:38.040> been<00:16:38.240> waiting<00:16:38.560> for<00:16:39.319> but<00:16:39.440> I've<00:16:39.639> also 00:16:39.829 --> 00:16:39.839 align:start position:0% always been waiting for but I've also 00:16:39.839 --> 00:16:41.350 align:start position:0% always been waiting for but I've also been<00:16:40.040> wondering<00:16:40.360> if<00:16:40.480> it's<00:16:40.680> finally<00:16:41.040> time<00:16:41.199> to 00:16:41.350 --> 00:16:41.360 align:start position:0% been wondering if it's finally time to 00:16:41.360 --> 00:16:43.509 align:start position:0% been wondering if it's finally time to give<00:16:41.560> planite<00:16:42.079> a<00:16:42.199> shot<00:16:42.519> an<00:16:42.720> alternative<00:16:43.319> game 00:16:43.509 --> 00:16:43.519 align:start position:0% give planite a shot an alternative game 00:16:43.519 --> 00:16:45.790 align:start position:0% give planite a shot an alternative game launcher<00:16:43.880> to<00:16:44.079> steam<00:16:44.959> as<00:16:45.079> much<00:16:45.199> as<00:16:45.319> I<00:16:45.480> love 00:16:45.790 --> 00:16:45.800 align:start position:0% launcher to steam as much as I love 00:16:45.800 --> 00:16:47.670 align:start position:0% launcher to steam as much as I love Steam<00:16:46.199> and<00:16:46.319> it's<00:16:46.519> Big<00:16:46.720> Picture<00:16:46.959> Mode<00:16:47.319> it<00:16:47.480> does 00:16:47.670 --> 00:16:47.680 align:start position:0% Steam and it's Big Picture Mode it does 00:16:47.680 --> 00:16:49.949 align:start position:0% Steam and it's Big Picture Mode it does feel<00:16:48.000> and<00:16:48.279> behave<00:16:48.639> a<00:16:48.800> bit<00:16:49.000> finicky<00:16:49.480> from<00:16:49.720> time 00:16:49.949 --> 00:16:49.959 align:start position:0% feel and behave a bit finicky from time 00:16:49.959 --> 00:16:51.590 align:start position:0% feel and behave a bit finicky from time to<00:16:50.160> time<00:16:50.759> let<00:16:50.920> me<00:16:51.040> know<00:16:51.199> if<00:16:51.279> you'd<00:16:51.480> be 00:16:51.590 --> 00:16:51.600 align:start position:0% to time let me know if you'd be 00:16:51.600 --> 00:16:53.189 align:start position:0% to time let me know if you'd be interested<00:16:51.959> in<00:16:52.120> a<00:16:52.319> third<00:16:52.560> visit<00:16:52.800> to<00:16:53.000> this 00:16:53.189 --> 00:16:53.199 align:start position:0% interested in a third visit to this 00:16:53.199 --> 00:16:55.030 align:start position:0% interested in a third visit to this subject<00:16:53.800> and<00:16:54.040> if<00:16:54.199> you<00:16:54.279> would<00:16:54.480> consider<00:16:54.800> doing 00:16:55.030 --> 00:16:55.040 align:start position:0% subject and if you would consider doing 00:16:55.040 --> 00:16:56.870 align:start position:0% subject and if you would consider doing something<00:16:55.399> similar<00:16:55.839> or<00:16:56.199> have<00:16:56.399> done<00:16:56.600> so 00:16:56.870 --> 00:16:56.880 align:start position:0% something similar or have done so 00:16:56.880 --> 00:16:58.550 align:start position:0% something similar or have done so already<00:16:57.639> maybe<00:16:57.839> this<00:16:57.959> is<00:16:58.079> all<00:16:58.279> common 00:16:58.550 --> 00:16:58.560 align:start position:0% already maybe this is all common 00:16:58.560 --> 00:17:00.470 align:start position:0% already maybe this is all common knowledge<00:16:59.000> again<00:16:59.160> and<00:16:59.319> I<00:16:59.440> just<00:16:59.560> didn't<00:16:59.800> know 00:17:00.470 --> 00:17:00.480 align:start position:0% knowledge again and I just didn't know 00:17:00.480 --> 00:17:02.309 align:start position:0% knowledge again and I just didn't know anyway<00:17:01.160> thank<00:17:01.319> you<00:17:01.440> so<00:17:01.639> much<00:17:01.800> for<00:17:02.000> watching 00:17:02.309 --> 00:17:02.319 align:start position:0% anyway thank you so much for watching 00:17:02.319 --> 00:17:04.150 align:start position:0% anyway thank you so much for watching and<00:17:02.720> see<00:17:02.880> you<00:17:03.000> in<00:17:03.079> the<00:17:03.240> next<00:17:03.399> one<00:17:03.800> where<00:17:03.959> it's 00:17:04.150 --> 00:17:04.160 align:start position:0% and see you in the next one where it's 00:17:04.160 --> 00:17:07.870 align:start position:0% and see you in the next one where it's back<00:17:04.319> to<00:17:04.520> keyboards<00:17:05.199> one<00:17:05.520> that<00:17:05.799> really<00:17:06.880> kicks 00:17:07.870 --> 00:17:07.880 align:start position:0% back to keyboards one that really kicks 00:17:07.880 --> 00:17:10.880 align:start position:0% back to keyboards one that really kicks bye