WEBVTT 00:00:00.000 --> 00:00:05.360 Oh, hi there. I didn't see you. 00:00:05.360 --> 00:00:08.600 Hi, I saw you. Well, I don't see you. 00:00:08.600 --> 00:00:12.640 I think I've done this before. I think I've done this at literal 00:00:12.640 --> 00:00:15.680 bit in the intro. 00:00:15.680 --> 00:00:19.720 Oh no, your video cannot be monetized 00:00:19.720 --> 00:00:23.440 due to copyright claims. Oh boy. 00:00:23.440 --> 00:00:27.080 Yeah, I assume it's because of the screen capture? 00:00:27.080 --> 00:00:30.680 The video of the TV. Yeah. 00:00:30.680 --> 00:00:35.080 They're trying different versions where they cut it down. 00:00:35.080 --> 00:00:39.480 Yeah, okay. I'm sure it'll be fine. 00:00:39.480 --> 00:00:43.400 We'll figure it out. I'm pretty sure that reviewing a video format is 00:00:43.400 --> 00:00:46.440 pretty defensible, fair use-wise. 00:00:46.440 --> 00:00:50.480 No one is watching that film like that. So we'll 00:00:50.480 --> 00:00:54.080 I'll give you guys a little bit of inside baseball. 00:00:54.080 --> 00:00:58.240 If you just re-upload a slightly changed video 00:00:58.240 --> 00:01:02.240 enough times to YouTube, eventually copyright ID doesn't notice it. 00:01:02.240 --> 00:01:06.160 So yeah, and realistically what paramount? 00:01:06.160 --> 00:01:09.760 Is it paramount for that one? I can't remember. Realistically the rights holder 00:01:09.760 --> 00:01:13.760 for that movie that we like have on screen for a little bit to do image 00:01:13.760 --> 00:01:18.120 quality comparisons is not gonna like come after us manually for that. 00:01:18.120 --> 00:01:21.240 Warner Bros. Warner Bros. Yeah. 00:01:21.280 --> 00:01:25.440 They're Bros. I heard. They also warned us. 00:01:25.440 --> 00:01:29.440 Warner, hardly even knew her. 00:01:29.440 --> 00:01:33.440 Are you mic'd? I think so. 00:01:33.440 --> 00:01:37.440 Okay, I'm just not sure if they can only hear half of this conversation. 00:01:37.440 --> 00:01:41.480 Good evening Linus. Where are you at? Evening. 00:01:41.480 --> 00:01:45.520 You must be in Euroland. How's it going over there? 00:01:45.520 --> 00:01:49.560 Hopefully better than it's going here. 00:01:49.960 --> 00:01:53.960 Is New Zealand still like... I heard that because all the billionaires 00:01:53.960 --> 00:01:57.960 are like running away to New Zealand, it kind of sucks there now too. 00:01:57.960 --> 00:02:01.960 Because New Zealand was like supposed to be the best, you know, of no strategic 00:02:01.960 --> 00:02:06.160 importance whatsoever, but also like of a pretty western standard of living. 00:02:06.160 --> 00:02:10.200 How are you guys doing? I don't know what time it is. 00:02:10.200 --> 00:02:14.240 Is anyone awake in New Zealand right now? 00:02:14.240 --> 00:02:18.240 New Zealand time right now. Oh yeah, someone could be tuning in over their breakfast 00:02:18.320 --> 00:02:22.320 in New Zealand. New Zealand is not Europe though. 00:02:22.320 --> 00:02:26.320 No, I was talking about 00:02:26.320 --> 00:02:30.320 places where things might be going better than here. 00:02:30.320 --> 00:02:34.320 That's all. 00:02:34.320 --> 00:02:38.320 Edgigan says 00:02:38.320 --> 00:02:42.320 Euroland is comparatively I eat. 00:02:42.320 --> 00:02:46.320 Alright, cool. Nice. Cool. 00:02:46.400 --> 00:02:50.400 Alright. 00:02:50.400 --> 00:02:54.400 Yeah, turbulence in New Zealand. 00:02:54.400 --> 00:02:58.400 It'd be kind of cool to be able to see 00:02:58.400 --> 00:03:02.400 a high-five guy says Germany not doing so hot right now. Oh yeah, the elections 00:03:02.400 --> 00:03:06.440 coming up. Yeah, yeah, Germany looks like things are... 00:03:06.440 --> 00:03:10.440 I don't follow German politics like at all. 00:03:10.440 --> 00:03:14.440 So take this for what it is, but 00:03:14.520 --> 00:03:18.520 what I have gleaned is it looks like some coalition basically 00:03:18.520 --> 00:03:22.520 broke down. The coalition of never cooperate with 00:03:22.520 --> 00:03:26.520 the far-right guys apparently just kind of broke down recently over 00:03:26.520 --> 00:03:30.560 some issue. So that's 00:03:30.560 --> 00:03:34.560 something. Yep. 00:03:34.560 --> 00:03:38.560 Mattie says the UK is just as terrible as it was 10 years ago. 00:03:38.560 --> 00:03:42.560 Dude, I don't understand. I was over there for vacation recently 00:03:42.560 --> 00:03:46.560 and I'm like obviously I was in touristy areas like Edinburgh or whatever. 00:03:46.560 --> 00:03:50.560 But I don't understand how people live over there at all. 00:03:50.560 --> 00:03:54.560 It's so expensive. Yeah, our cost of 00:03:54.560 --> 00:03:58.560 living here, especially in Vancouver, Canada is 00:03:58.560 --> 00:04:02.560 stupid. But like 00:04:02.560 --> 00:04:06.560 is stupider a word? Because it feels like 00:04:06.560 --> 00:04:10.560 that's kind of where things are going. 00:04:10.560 --> 00:04:14.560 Yes, C. Jackson, Canada's election is not too far away, 00:04:14.560 --> 00:04:18.560 but the tide has turned a little bit. Thankfully, 00:04:18.560 --> 00:04:22.560 Trudeau had the wisdom to pull out of the race early enough 00:04:22.560 --> 00:04:26.560 for someone else to conceivably take up the mantle. 00:04:26.560 --> 00:04:30.560 Because like there's a lot of folks like me 00:04:30.560 --> 00:04:34.560 that regardless 00:04:34.560 --> 00:04:38.560 of our politics and our personal beliefs, we're simply not 00:04:38.560 --> 00:04:42.560 going to be willing to vote for Trudeau again at this point, regardless of 00:04:42.560 --> 00:04:46.560 which platform we prefer, which I'm honestly not going to get into 00:04:46.560 --> 00:04:50.560 right now. But Trudeau was uniquely 00:04:50.560 --> 00:04:54.560 poorly positioned to win an election. 00:04:54.560 --> 00:04:58.560 Well, polls were, like conservators were doubling. Yeah. 00:04:58.560 --> 00:05:02.560 Linus Town still on the books. Linus Town has never been on the books. 00:05:02.560 --> 00:05:06.560 Linus Town was always a joke. No, that's why I'm here. 00:05:06.560 --> 00:05:10.560 No, no, no Linus Town. No taxes. 00:05:10.560 --> 00:05:14.560 Culp, culp, culp. Potato Culp. 00:05:14.560 --> 00:05:18.560 Someone sent me a town that was for sale pretty recently, and I was just like, 00:05:18.560 --> 00:05:22.560 no. We can just recreate Schitt's Creek. 00:05:22.560 --> 00:05:26.560 Oh man. 00:05:26.560 --> 00:05:30.560 Can we please get Linus Town? Dude, 00:05:30.560 --> 00:05:34.560 buy a cruise trip, you know, buy our cruise ship. Okay, I could afford 00:05:34.560 --> 00:05:38.560 a town before I could afford a cruise ship. You have any idea what cruise ships 00:05:38.560 --> 00:05:42.560 cost? 00:05:42.560 --> 00:05:46.560 I can't even wrap my brain around how that industry even functions, 00:05:46.560 --> 00:05:50.560 because like, yeah, people pay a lot to be on a cruise ship, 00:05:50.560 --> 00:05:54.560 but like, and I've never taken a cruise to be clear, so this is all just my perception 00:05:54.560 --> 00:05:58.560 as an outsider, but it seems like there's a lot of freaking staff 00:05:58.560 --> 00:06:02.560 on these ships. There's a lot of amenities that just make no 00:06:02.560 --> 00:06:06.560 sense, like ice rinks and things like that. 00:06:06.560 --> 00:06:10.560 They burn a ton of fuel, it's like, 00:06:10.560 --> 00:06:14.560 sure, good luck everybody. 00:06:14.560 --> 00:06:18.560 Apparently, 00:06:18.560 --> 00:06:22.560 it's about $300,000 a day for fuel. 00:06:22.560 --> 00:06:26.560 $300,000 a day. This is for marine insight, so I don't know how. 00:06:26.560 --> 00:06:30.560 In fuel. 130 for low grade fuel, but if it uses marine gas oil, 00:06:30.560 --> 00:06:34.560 which is cleaner fuel, it'll cost a ship $300,000 a day. 00:06:34.560 --> 00:06:38.560 So these things, well, they'll go for a week, and they'll blow 00:06:38.560 --> 00:06:42.560 a million dollars on fuel. That's wild. 00:06:42.560 --> 00:06:46.560 Like, what are we even 00:06:46.560 --> 00:06:50.560 doing here? It's like $50, $80 expensive, sure, 00:06:50.560 --> 00:06:54.560 but like, burning a thousand of these in a week 00:06:54.560 --> 00:06:58.560 just to like, go somewhere. If I burned $50, $80s at 00:06:58.560 --> 00:07:02.560 that rate, you guys would be up in arms. You'd be so mad. You'd be like, 00:07:02.560 --> 00:07:06.560 Linus, you gotta stop burning $50, $80s. You'd sit me down, you'd sit me right down. 00:07:06.560 --> 00:07:10.560 You'd get on my level for that eye contact, 00:07:10.560 --> 00:07:14.560 you'd go, Linus, it's not okay. 00:07:14.560 --> 00:07:18.560 I don't know, stop. 00:07:18.560 --> 00:07:22.560 No, no, it doesn't matter what your reason was. 00:07:22.560 --> 00:07:26.560 Sometimes the reason's not important. 00:07:26.560 --> 00:07:30.560 Think of the impact. Think of how many gamers 00:07:30.560 --> 00:07:34.560 can't have those GPs. Do you just sit me down? 00:07:38.560 --> 00:07:42.560 Alright, should we do this 00:07:42.560 --> 00:07:46.560 thing? Linus for NDP leader. 00:07:46.560 --> 00:07:50.560 Man, are you calling me a loser? You calling me 00:07:50.560 --> 00:07:54.560 a lifelong loser because the NDP are never going to win at a federal level. 00:07:54.560 --> 00:07:58.560 I'm sorry. And again, I'm not even getting 00:07:58.560 --> 00:08:02.560 into my politics. I don't feel like it right now, but like, 00:08:02.560 --> 00:08:06.560 I don't know, they're just like, it's almost comical 00:08:06.560 --> 00:08:10.560 how they just can't, they just can't, they can't win. 00:08:14.560 --> 00:08:18.560 Oh, Jacob Framework 00:08:18.560 --> 00:08:22.560 just solved it for me. Fun fact, 00:08:22.560 --> 00:08:26.560 most of the cruise lines make their money from the casinos on board. 00:08:26.560 --> 00:08:30.560 That makes so much more sense now. Cause I was looking at the ticket 00:08:30.560 --> 00:08:34.560 prices. Of course it's, the answer is always 00:08:34.560 --> 00:08:38.560 gambling. Why does anyone still care about a 00:08:38.560 --> 00:08:42.560 20 year old video game? Gambling. 00:08:42.560 --> 00:08:46.560 Why does anybody go to that godforsaken city in the middle of the freaking desert? 00:08:46.560 --> 00:08:50.560 Gambling. Why does anyone give two craps about 00:08:50.560 --> 00:08:54.560 cryptocurrency that has no real world utility? 00:08:54.560 --> 00:08:58.560 The answer is always gambling. 00:08:58.560 --> 00:09:02.560 Okay. It's always gambling. 00:09:02.560 --> 00:09:06.560 Man, how do we get into the gambling 00:09:06.560 --> 00:09:10.560 industry? Why do we have to be morally opposed to it? Don't we have merch mystery 00:09:10.560 --> 00:09:14.560 boxes? We do have the occasional 00:09:14.560 --> 00:09:18.560 merch item where there's a slightly different like thing on the shirt. You still get this shirt though. 00:09:18.560 --> 00:09:22.560 It's not really the same. Yeah, we explicitly 00:09:22.560 --> 00:09:26.560 disable gambling through even AdSense. We don't do 00:09:26.560 --> 00:09:30.560 gambling-ness, but man, would it ever be 00:09:30.560 --> 00:09:34.560 lucrative. The amount of money that sports betting 00:09:34.560 --> 00:09:38.560 apps spend on advertising tells me all I need to know about how much money 00:09:38.560 --> 00:09:42.560 is being wasted on sports betting. Yeah, cause it's 00:09:42.560 --> 00:09:46.560 literally is a zero sum game. Every dollar 00:09:46.560 --> 00:09:50.560 that a betting app spends is a dollar that they collected 00:09:50.560 --> 00:09:54.560 from some Joe Chump who 00:09:54.560 --> 00:09:58.560 guessed wrong which, you know, Superman could put the rubber 00:09:58.560 --> 00:10:02.560 thing in the goalpost or whatever. You know, like it's 00:10:06.560 --> 00:10:10.560 in certain mean with the guy mining for diamonds. Okay, in all seriousness 00:10:10.560 --> 00:10:14.560 I have a new retirement dream. So my old retirement dream 00:10:14.560 --> 00:10:18.560 was to drive a school bus just like Pete. Pete was my 00:10:18.560 --> 00:10:22.560 school bus driver when I was in high school and what was really 00:10:22.560 --> 00:10:26.560 special about Pete was that he didn't need to drive the bus. 00:10:26.560 --> 00:10:30.560 He was retired with a full pension and 00:10:30.560 --> 00:10:34.560 just kind of did it to get out of the house and 00:10:34.560 --> 00:10:38.560 have some fun being a complete jackass to children. 00:10:38.560 --> 00:10:42.560 And he would, so the way he would like 00:10:42.560 --> 00:10:46.560 yell at us to, like if we sat, you know, if we man-spreaded a little 00:10:46.560 --> 00:10:50.560 bit in the edge seat, you know, and we had like a toe in the aisle, he 00:10:50.560 --> 00:10:54.560 would stop the bus. Like he wasn't the kind of bus driver to be like, don't make me stop this bus 00:10:54.560 --> 00:10:58.560 and then never do it. He would stop the bus. He would come in the back. He'd get all his 00:10:58.560 --> 00:11:02.560 head, face all red and his like veins popped and he would be like, keep the 00:11:02.560 --> 00:11:06.560 aisle clear. And I was like, whoa. And so 00:11:06.560 --> 00:11:10.560 I figured out eventually that Pete didn't have to be there at all. He just 00:11:10.560 --> 00:11:14.560 did it for the sheer joy of it. Now, I wouldn't necessarily be a Pete, 00:11:14.560 --> 00:11:18.560 but I had this dream of kind of driving a school bus as my 00:11:18.560 --> 00:11:22.560 sort of get out of the house in the morning in the afternoon. You work 00:11:22.560 --> 00:11:26.560 like, you know, three hours a day, three and a half hours a day or whatever. 00:11:26.560 --> 00:11:30.560 You pick up the odd shift when you do like a, you know, a class ski trip or whatever 00:11:30.560 --> 00:11:34.560 else, just to kind of, kind of keep busy, but not really, you know, not really 00:11:34.560 --> 00:11:38.560 think too much. So, so, so Pete was my inspiration so that I could, 00:11:38.560 --> 00:11:42.560 he was like what not to do, but also seemed like a pretty good retirement 00:11:42.560 --> 00:11:46.560 plan. I have a new retirement plan, speaking of mining diamonds. 00:11:46.560 --> 00:11:50.560 I was on Facebook marketplace of all places. Dude, my Facebook marketplace is 00:11:50.560 --> 00:11:54.560 frickin' wild. Frickin' wild. I train the algorithm to just give me weird stuff 00:11:54.560 --> 00:11:58.560 and someone was selling like gold claims 00:11:58.560 --> 00:12:02.560 and I was like, what is a gold claim? I don't know that. Okay, so 00:12:02.560 --> 00:12:06.560 a gold claim is the mining and 00:12:06.560 --> 00:12:10.560 like extraction rights for any gold within 00:12:10.560 --> 00:12:14.560 an area of land and typically 00:12:14.560 --> 00:12:18.560 they're quite large, like measured on the order of like hectares. They're 00:12:18.560 --> 00:12:22.560 enormous. Basically, you're buying the right to go 00:12:22.560 --> 00:12:26.560 like faffing about in the wilderness looking for 00:12:26.560 --> 00:12:30.560 looking for gold. 00:12:30.560 --> 00:12:34.560 And I don't know man, I came across this YouTube channel where they 00:12:34.560 --> 00:12:38.560 bought a claim and they, you don't own the land. So, you just own 00:12:38.560 --> 00:12:42.560 temporarily the rights to mine the land 00:12:42.560 --> 00:12:46.560 to prospect the land. And so, they're like DIYing 00:12:46.560 --> 00:12:50.560 this like, you know, breaking down the ore and frickin' 00:12:50.560 --> 00:12:54.560 like extracting the gold and they got these. I don't know. 00:12:54.560 --> 00:12:58.560 It sounds cool. It actually sounds like a blast. 00:12:58.560 --> 00:13:02.560 And if I was at a stage in my life where I didn't need to be successful 00:13:02.560 --> 00:13:06.560 or I could just like, you know, go out and like put on my prospecting 00:13:06.560 --> 00:13:10.560 hat and get my pickaxe or whatever, like obviously that's like a caricature 00:13:10.560 --> 00:13:14.560 of what, you know, a miner might look like. But like, I don't know, dude. 00:13:14.560 --> 00:13:18.560 Oh, sorry. No, these guys bought, they bought a mine. So, it was like 00:13:18.560 --> 00:13:22.560 an actual, it was an actual mine, but it was like not being used anymore because I guess 00:13:22.560 --> 00:13:26.560 it wasn't yielding enough to be like commercially viable, but as 00:13:26.560 --> 00:13:30.560 like a small group of individuals, they were able to make, I don't know, it sounds like a blast, dude. 00:13:30.560 --> 00:13:34.560 Obviously, I wouldn't be able to do that if I'm like, you know, well into 00:13:34.560 --> 00:13:38.560 my 40s or whatever. So, it would have to be relatively soon. I guess 00:13:38.560 --> 00:13:42.560 this is how you guys find out I'm retiring to become a gold miner. 00:13:42.560 --> 00:13:46.560 I think we make a video about it. Yeah, but I don't know, dude, I don't know. 00:13:46.560 --> 00:13:50.560 I think it'd be cool. Retirement 00:13:50.560 --> 00:13:54.560 dream for me is living in Linestown. No, there is 00:13:54.560 --> 00:13:58.560 no Linestown, damn it. I've told you people. See, I thought your retirement plan was going 00:13:58.560 --> 00:14:02.560 to be like buying a bus, making it like a camper bus, and then driving to Mexico 00:14:02.560 --> 00:14:06.560 or something. I don't know why your retirement plan includes work. Oh, no, 00:14:06.560 --> 00:14:10.560 yeah, no, it has to be, it has to be work. I don't think I could handle it. 00:14:10.560 --> 00:14:14.560 I don't think I could just like, I don't think I could just be idle. 00:14:14.560 --> 00:14:18.560 I think I would like turn to jelly. I think I'd be unhappy. 00:14:18.560 --> 00:14:22.560 I'd have to have something to do. And like, if that thing to do involved 00:14:22.560 --> 00:14:26.560 like, you know, finding, you know, gold flakes 00:14:26.560 --> 00:14:30.560 and then like learning how to, learning how to, you know, 00:14:30.560 --> 00:14:34.560 make the aqua regia and, you know, get the purity really 00:14:34.560 --> 00:14:38.560 high and like, like I'd be so excited to make that first, you know, 00:14:38.560 --> 00:14:42.560 little, you know, two ounce gold bar or something like that. 00:14:42.560 --> 00:14:46.560 You know, like, I think that'd be super cool. I spent 00:14:46.560 --> 00:14:50.560 four million dollars to make ten thousand dollars. Yeah, right. 00:14:50.560 --> 00:14:54.560 Like, if I actually just like completely 00:14:54.560 --> 00:14:58.560 didn't care and I could just like 00:14:58.560 --> 00:15:02.560 spend money without actually like working, you know, doing streams like this or whatever 00:15:02.560 --> 00:15:06.560 and I could just do things that didn't make any sense, 00:15:06.560 --> 00:15:10.560 I think becoming a gold prospector would be pretty high up on my list. 00:15:10.560 --> 00:15:14.560 I think for a limited amount of time. Oh yeah, yeah, I think for like a year. 00:15:14.560 --> 00:15:18.560 I think for like a year, that would be really fun. Canadian winter would roll around 00:15:18.560 --> 00:15:22.560 and like, even in BC, like it's like kind of 00:15:22.560 --> 00:15:26.560 wet, miserable, like, yeah, and I'd be like, ah, that's probably enough of this, but 00:15:26.560 --> 00:15:30.560 still, that'd be cool. I owned a gold site 00:15:30.560 --> 00:15:34.560 fuel and COVID made me go bankrupt. I don't know what a gold site fuel is, 00:15:34.560 --> 00:15:38.560 but I'm sorry to hear that. 00:15:38.560 --> 00:15:42.560 I guess we should probably start the video at some 00:15:42.560 --> 00:15:46.560 point. Hey, start the stream. Should we do that? Are you guys down? 00:15:46.560 --> 00:15:50.560 Okay. All right, Dan's ready. 00:15:50.560 --> 00:15:54.560 Oh, that is that blue. Okay. Yeah, neat. 00:15:54.560 --> 00:15:58.560 Cool. 00:15:58.560 --> 00:16:02.560 Yeah, my dad's technically retired, but now works as a 00:16:02.560 --> 00:16:06.560 high school teacher just for the fun of it. That does not sound fun. 00:16:06.560 --> 00:16:10.560 Yeah, working as a teacher doesn't sound that fun. If you've only had teenagers in the 00:16:10.560 --> 00:16:14.560 last 10 years, you know it's not fun. Yeah. 00:16:14.560 --> 00:16:18.560 Speedrun going bankrupt as many times as possible 00:16:18.560 --> 00:16:22.560 in retirement. I wouldn't actually want to go bankrupt, 00:16:22.560 --> 00:16:26.560 but I do think it would be fun to like find out what businesses are viable 00:16:26.560 --> 00:16:30.560 if you like go hard at them for a year or something 00:16:30.560 --> 00:16:34.560 like that. I think that'd be super cool. 00:16:34.560 --> 00:16:38.560 I have not called the boat guy yet. Dan has given me his contact info, but I have 00:16:38.560 --> 00:16:42.560 not made the call yet. 00:16:42.560 --> 00:16:46.560 Yeah, not yet. 00:16:46.560 --> 00:16:50.560 Yes, yes, yes, yes, yes. I'm going to give a whole new meaning to Whale Land. 00:16:50.560 --> 00:16:54.560 I will call the guy. I will call the guy. Geez, I will call the guy. 00:16:54.560 --> 00:16:58.560 Relax, Wansho audience. 00:16:58.560 --> 00:17:02.560 Oh, live monetization settings. Is this new? 00:17:02.560 --> 00:17:06.560 These settings will apply to all new streams created in YouTube studio. 00:17:06.560 --> 00:17:10.560 Oh. 00:17:10.560 --> 00:17:14.560 Okay. 00:17:14.560 --> 00:17:18.560 I'm just going to screenshot this and send it to Colton because I don't know 00:17:18.560 --> 00:17:22.560 what our, I don't know what our processor policy is for this. I don't know 00:17:22.560 --> 00:17:26.560 why it's prompting me. I just, I opened up the dashboard. 00:17:26.560 --> 00:17:30.560 Sorry, excuse me. I opened up the dashboard and it just like prompted me to change 00:17:30.560 --> 00:17:34.560 our monetization settings and I don't, I'm not in charge of that stuff anymore. 00:17:34.560 --> 00:17:38.560 To be clear, 00:17:38.560 --> 00:17:42.560 I do weigh in on it. Like if they try to increase 00:17:42.560 --> 00:17:46.560 things too much, I'm all like, hey, we probably shouldn't do that. We ended up cutting 00:17:46.560 --> 00:17:50.560 a bunch of the sponsor stuff from that 00:17:50.560 --> 00:17:54.560 stream, not stream. That React video we did that had frankly 00:17:54.560 --> 00:17:58.560 too many inserts. I agree with you guys. 00:17:58.560 --> 00:18:02.560 I don't know. These are supposed to be 00:18:02.560 --> 00:18:06.560 but this prompted me when I opened 00:18:06.560 --> 00:18:10.560 the thing. Okay. I will press cancel. 00:18:10.560 --> 00:18:14.560 Okay. So I'm just going to press cancel and then he 00:18:14.560 --> 00:18:18.560 will set it to something later. Discard changes. Nice. 00:18:18.560 --> 00:18:22.560 Nice. Okay. 00:18:22.560 --> 00:18:26.560 Wow. They're really pushing this. Like I'm here in 00:18:26.560 --> 00:18:30.560 the dashboard and they're all like creators adopting live 00:18:30.560 --> 00:18:34.560 automated midrolls on average saw over 20% uplift in in stream 00:18:34.560 --> 00:18:38.560 ad revenue per hour. Wow. A 20% uplift on in stream ad 00:18:38.560 --> 00:18:42.560 revenue per hour. It's not a major 00:18:42.560 --> 00:18:46.560 revenue source for us. So it's like whatever per 00:18:46.560 --> 00:18:50.560 hour. But for someone who like their bread and butter is 00:18:50.560 --> 00:18:54.560 streaming for six, eight hours a day or whatever, that's a huge difference. 00:18:54.560 --> 00:18:58.560 Because maybe instead of six, eight hours, it could be six hours. 00:18:58.560 --> 00:19:02.560 Which is pretty nice, man. I don't know how those folks do it streaming 00:19:02.560 --> 00:19:06.560 all day like that. It's freaking wild. I'm not 00:19:06.560 --> 00:19:10.560 built for that. In fact, I've actually I've found as I'm maybe as I'm getting older 00:19:10.560 --> 00:19:14.560 or whatever. As time is passing 00:19:14.560 --> 00:19:18.560 these long streams, like especially the ones that go for like three or four 00:19:18.560 --> 00:19:22.560 hours, they like wipe me. Like it was the 00:19:22.560 --> 00:19:26.560 next day, I think two streams ago that I was like I was talking to Alex and I was like 00:19:26.560 --> 00:19:30.560 man, like my brain is just fry sizzled today. 00:19:30.560 --> 00:19:34.560 I can't think. I can't focus on anything. He's like, oh yeah, 00:19:34.560 --> 00:19:38.560 it's probably for me being live for like five hours. I was like 00:19:38.560 --> 00:19:42.560 oh, that makes sense. 00:19:56.560 --> 00:20:00.560 Okay. Alright, we're real close. We're real close. 00:20:04.560 --> 00:20:08.560 Okay. 00:20:08.560 --> 00:20:12.560 We're just waiting for an answer on the momentization thing. 00:20:12.560 --> 00:20:16.560 Okay, let's do this thing. We ready? 00:20:16.560 --> 00:20:20.560 Or wait, sorry, did you say we're waiting for something? No, I was asking what we were waiting for. 00:20:20.560 --> 00:20:24.560 Oh, we're not waiting for anything. We're waiting for me to be mentally prepared. 00:20:24.560 --> 00:20:28.560 Okay, Andy, you good to go? Yep. You ready? Yep. Alright, let's do this thing. 00:20:28.560 --> 00:20:32.560 I am 00:20:32.560 --> 00:20:36.560 Maybe I'll start in front of the 00:20:36.560 --> 00:20:40.560 Yeah, I'm going to start in front of the table. Is that cool? Does that work? 00:20:40.560 --> 00:20:44.560 And then David, could I, after I see the thing, can I like just 00:20:44.560 --> 00:20:48.560 hand this to you off camera and then we'll do it like that? Okay. 00:20:48.560 --> 00:20:52.560 You're going to have to throw it at me. 00:20:52.560 --> 00:20:56.560 Oh, right. Which direction do I throw? 00:20:56.560 --> 00:21:00.560 Continuity? What's that? 00:21:00.560 --> 00:21:04.560 To my left, to my left. That's always easy to remember. 00:21:04.560 --> 00:21:08.560 Okay, cool. Okay, so to my left. What's the thing I throw again? 00:21:08.560 --> 00:21:12.560 It's the first part. Ah, yes. Oh, wow. 00:21:12.560 --> 00:21:16.560 Okay. To me. Got it. That makes sense. 00:21:16.560 --> 00:21:20.560 That's why I'm here. 00:21:20.560 --> 00:21:24.560 That totally makes sense. I would not want to 00:21:24.560 --> 00:21:28.560 actually throw that. Yeah, I don't want to actually throw that and damage it. 00:21:28.560 --> 00:21:32.560 Oh, yeah. 00:21:32.560 --> 00:21:36.560 Oh, yeah. 00:21:36.560 --> 00:21:40.560 I'm pushing 40 pretty quick here, so it is what it is. 00:21:40.560 --> 00:21:44.560 Alright, let's resume the selected, shall we? 00:21:44.560 --> 00:21:48.560 Oh, wow, that's going really fast. 00:21:48.560 --> 00:21:52.560 Oh, but the controls are working, so that's great. Okay. Resuming the 00:21:52.560 --> 00:21:56.560 selected, now. No, no, I give it to you once it 00:21:56.560 --> 00:22:00.560 goes. 00:22:12.560 --> 00:22:16.560 No one likes watching a progress bar 00:22:16.560 --> 00:22:20.560 all across their screen. And thanks to their dated workstations, 00:22:20.560 --> 00:22:24.560 our poor editors have been watching a lot 00:22:24.560 --> 00:22:28.560 of slow progress bars. The only reasonable thing to do then 00:22:28.560 --> 00:22:32.560 is build them new ones, but the PC landscape has changed 00:22:32.560 --> 00:22:36.560 a lot since 2021 when we made our 00:22:36.560 --> 00:22:40.560 last big improvements to our editing stations. So, we are 00:22:40.560 --> 00:22:44.560 teaming up with ASUS who sponsored this stream and sent over some 00:22:44.560 --> 00:22:48.560 awesome parts to try, like the AMD Ryzen 7 00:22:48.560 --> 00:22:52.560 9800X3D, which we are not going 00:22:52.560 --> 00:22:56.560 to use. 00:23:00.560 --> 00:23:04.560 Did you roll the thing? Yeah. Oh, when do I come back? You're back. Oh! 00:23:04.560 --> 00:23:08.560 In fact, our CPU upgrade 00:23:08.560 --> 00:23:12.560 might be a little controversial. We're going 00:23:12.560 --> 00:23:16.560 with the AMD Ryzen 9 9950X. That's 00:23:16.560 --> 00:23:20.560 right. Desktop CPUs, like 00:23:20.560 --> 00:23:24.560 peasant consumer CPUs. But here's the thing, 00:23:24.560 --> 00:23:28.560 even without the 3D vCache, which doesn't consistently boost 00:23:28.560 --> 00:23:32.560 productivity performance, the gamers watching this are probably agreeing 00:23:32.560 --> 00:23:36.560 with our choice going, heck yeah! AMD dominance! 00:23:36.560 --> 00:23:40.560 But the content creators that are watching might know 00:23:40.560 --> 00:23:44.560 that video editing performance is actually one of Intel's last 00:23:44.560 --> 00:23:48.560 strongholds, thanks in part to QuickSync. Now, 00:23:48.560 --> 00:23:52.560 QuickSync, yeah, let's stand over here. QuickSync is Intel's branding 00:23:52.560 --> 00:23:56.560 for the dedicated hardware that accelerates video encoding and decoding 00:23:56.560 --> 00:24:00.560 on their CPUs and their GPUs. And it really 00:24:00.560 --> 00:24:04.560 does work, allowing Intel to outperform AMD in Adobe Premiere 00:24:04.560 --> 00:24:08.560 timeline performance. And I actually encode it as well 00:24:08.560 --> 00:24:12.560 in many cases. That is why we went with their Core i9 00:24:12.560 --> 00:24:16.560 1300K in our last behind the scenes editing rig 00:24:16.560 --> 00:24:20.560 upgrade. But here's the issue. We've heard a lot 00:24:20.560 --> 00:24:24.560 of complaints from our editors about system stability. A lot. 00:24:24.560 --> 00:24:28.560 And when it comes to getting work done, it doesn't matter how 00:24:28.560 --> 00:24:32.560 smooth you can scrub your timeline if the system crashes on the daily. 00:24:32.560 --> 00:24:36.560 So now that the Core Ultra launch has come and gone with the resounding 00:24:36.560 --> 00:24:40.560 womp-womp, we thought maybe it's time for a 00:24:40.560 --> 00:24:44.560 walk on the red side. Besides, the 9950X seems to have 00:24:44.560 --> 00:24:48.560 solid performance with intraframe codecs, which we use. 00:24:48.560 --> 00:24:52.560 And it's got a potential upgrade path thanks to AMD's long-term 00:24:52.560 --> 00:24:56.560 commitment to the AM5 platform. Though it is 00:24:56.560 --> 00:25:00.560 worth noting that we made a significant 00:25:00.560 --> 00:25:04.560 investment in editing stations based on AMD promises of 00:25:04.560 --> 00:25:08.560 long-term socket support back in the Threadripper 3000 days. 00:25:08.560 --> 00:25:12.560 And we all know how that worked out, don't we? 00:25:12.560 --> 00:25:16.560 Oh, we don't. Some of us don't. Bad. It worked out bad. 00:25:16.560 --> 00:25:20.560 It sucked. AMD just abandoned the platform immediately 00:25:20.560 --> 00:25:24.560 and was like, sorry, not sorry. 00:25:24.560 --> 00:25:28.560 Anywho. The 9950X 00:25:28.560 --> 00:25:32.560 has 16 Zen 5 cores. 24 threads. 00:25:32.560 --> 00:25:36.560 32 threads. Sorry about that. A base clock of 4.3 GHz 00:25:36.560 --> 00:25:40.560 and it turbos to up to 5.7 GHz. Other than the 00:25:40.560 --> 00:25:44.560 X3D, which, again, are productivity benchmarks, don't seem to really 00:25:44.560 --> 00:25:48.560 benefit from that much, it is the top of the flipping 00:25:48.560 --> 00:25:52.560 line. Now, we could have gone with a workstation CPU still. 00:25:52.560 --> 00:25:56.560 AMD does still have them, even though they abandoned that particular 00:25:56.560 --> 00:26:00.560 platform on me. Way to go, AMD. 00:26:00.560 --> 00:26:04.560 But here's the issue. AMD has kind of gutted 00:26:04.560 --> 00:26:08.560 their Threadripper offerings, dramatically increasing pricing for their top 00:26:08.560 --> 00:26:12.560 core-count models and lagging behind their desktop chips 00:26:12.560 --> 00:26:16.560 in terms of core technology pretty much across the board. 00:26:16.560 --> 00:26:20.560 You still can't get a Zen 5 Threadripper. 00:26:20.560 --> 00:26:24.560 What the freaking heck? So if you care about single-threaded 00:26:24.560 --> 00:26:28.560 performance, which some things, even in a productivity environment, 00:26:28.560 --> 00:26:32.560 do, then a desktop chip becomes 00:26:32.560 --> 00:26:36.560 the reasonable option. Not to mention that the mother 00:26:36.560 --> 00:26:40.560 boards for the current Gen Threadripper pros cost about as much as a desktop 00:26:40.560 --> 00:26:44.560 CPU and a desktop motherboard combined. 00:26:44.560 --> 00:26:48.560 Though that won't be the case for the desktop board 00:26:48.560 --> 00:26:52.560 that ASUS wanted to show off today. The ROG Crosshair X870e 00:26:52.560 --> 00:26:56.560 Hero, a $700 monster 00:26:56.560 --> 00:27:00.560 with absolutely everything. I'm talking 5GB 00:27:00.560 --> 00:27:04.560 and 2.5GB Ethernet. Wi-Fi 7, 5M.2 00:27:04.560 --> 00:27:08.560 Where the devil even are they all? Okay, 1, 2, and then 00:27:08.560 --> 00:27:12.560 I assume there's 3 more under this plate right here. 00:27:12.560 --> 00:27:16.560 Look at that, look at it go. It's got their AI 00:27:16.560 --> 00:27:20.560 advisor. Everyone's hot on AI features, but this one may 00:27:20.560 --> 00:27:24.560 actually be helpful for beginner builders and can highlight ASUS specific features for 00:27:24.560 --> 00:27:28.560 veterans. We're going to have a look at it when we finish building. And it's also got 00:27:28.560 --> 00:27:32.560 support for 4 dim slots with up to 256 gigs of RAM at 00:27:32.560 --> 00:27:36.560 surprisingly high speeds or 00:27:36.560 --> 00:27:40.560 up to 8200 megatrans per second on Ryzen 9000 00:27:40.560 --> 00:27:44.560 series with not 4 dims. Their 00:27:44.560 --> 00:27:48.560 NitroPath DRAM technology means that there are shorter gold finger 00:27:48.560 --> 00:27:52.560 pins, which results in optimized single pathways that ensure faster data transfers between 00:27:52.560 --> 00:27:56.560 your DRAM and CPU, as well as stronger slot retention force. 00:27:56.560 --> 00:28:00.560 And if I said the CPU choice for this build 00:28:00.560 --> 00:28:04.560 was going to be controversial, it is nothing compared to what we've got 00:28:04.560 --> 00:28:08.560 for our RAM. ASUS, because of their 00:28:08.560 --> 00:28:12.560 whole NitroPath optimization, Tom Foolery that they've got 00:28:12.560 --> 00:28:16.560 going on here, worked with Kingston on support 00:28:16.560 --> 00:28:20.560 for these specific modules. These are 00:28:20.560 --> 00:28:24.560 161 US dollars each 00:28:24.560 --> 00:28:28.560 for a total of 256 gigs of RAM in this thing. 00:28:28.560 --> 00:28:32.560 Now, normally on Ryzen platforms, if you want to run all four 00:28:32.560 --> 00:28:36.560 slots, especially at high capacities, you are looking at 00:28:36.560 --> 00:28:40.560 pretty slow speeds, but they claim that with all 00:28:40.560 --> 00:28:44.560 four of these running, you can hit up to, what was it, 5200? 00:28:44.560 --> 00:28:48.560 5600. We will have to see 00:28:48.560 --> 00:28:52.560 if that works, because the really mind blowing thing for me, 00:28:52.560 --> 00:28:56.560 if you want to get the installation, is that these are CU dims. 00:28:56.560 --> 00:29:00.560 Yes, my friends, CU dims. Those 00:29:00.560 --> 00:29:04.560 special high capacity dims that 00:29:04.560 --> 00:29:08.560 AMD doesn't really support other than in bypass mode, 00:29:08.560 --> 00:29:12.560 which just completely ignores the benefit 00:29:12.560 --> 00:29:16.560 of a CU dim, because there's like a CKD 00:29:16.560 --> 00:29:20.560 thing on it, and AMD 00:29:20.560 --> 00:29:24.560 just supports it in the sense that they just bypass it and don't 00:29:24.560 --> 00:29:28.560 use it. So the idea behind these is that they run at super high speeds 00:29:28.560 --> 00:29:32.560 on Intel, but then ASUS and Kingston 00:29:32.560 --> 00:29:36.560 were like, oh yeah, we're going to use these dims 00:29:36.560 --> 00:29:40.560 something, AMD, something. High speeds, very high capacity. 00:29:40.560 --> 00:29:44.560 Sure. Let's see how it goes. 00:29:44.560 --> 00:29:48.560 Cool. I'm going to put that there. 00:29:48.560 --> 00:29:52.560 And we're all going to hope for the best. Alright, now, it is 00:29:52.560 --> 00:29:56.560 worth noting that not everything in our configurations is changing. 00:29:56.560 --> 00:30:00.560 Our storage, oh, where is our storage? I was just starting to wonder 00:30:00.560 --> 00:30:04.560 that, is it in the motherboard? Did we lose the storage? Yeah, it could be. 00:30:04.560 --> 00:30:08.560 Anything's possible. Do we have tools? Yes, I do have tools. 00:30:08.560 --> 00:30:12.560 There you are, back there. Where do you get that? Let me tell 00:30:12.560 --> 00:30:16.560 you, lttstore.com, let's go precision screwdriver set. 00:30:16.560 --> 00:30:20.560 These are, these are moving like hotcakes. Y'all are 00:30:20.560 --> 00:30:24.560 loving these for the longer skinny parts of the shaft 00:30:24.560 --> 00:30:28.560 so they get into recessed places a little bit more easily on things 00:30:28.560 --> 00:30:32.560 like laptops and game consoles. The stronger 00:30:32.560 --> 00:30:36.560 magnetism compared to some competitors in the market. 00:30:36.560 --> 00:30:40.560 The nice smooth spinning top that 00:30:40.560 --> 00:30:44.560 I saw a really funny post on the subreddit where someone was holding it up to 00:30:44.560 --> 00:30:48.560 their cat who was like super suspicious of it and then eventually 00:30:48.560 --> 00:30:52.560 goes after it and it's really funny. I can see 00:30:52.560 --> 00:30:56.560 a cat not really liking that noise. Apparently the SSD was just left in here. It was just left in here. 00:30:56.560 --> 00:31:00.560 Okay, perfect. Well, here we go. 00:31:00.560 --> 00:31:04.560 Dang it, where are the, this is the, this is 00:31:04.560 --> 00:31:08.560 an issue. Oh, I see. Well, why did I take off the one that, anyway, okay, well 00:31:08.560 --> 00:31:12.560 there's four of our M.2 slots on this thing. This was totally 00:31:12.560 --> 00:31:16.560 intentional so that I could show you guys where all the SSD 00:31:16.560 --> 00:31:20.560 slots are on this motherboard, this fine sample of the motherboard. 00:31:20.560 --> 00:31:24.560 Anyway, parts that stayed the same. We've kept our 00:31:24.560 --> 00:31:28.560 one terabyte Crucial P5 pluses. Wait, what? 00:31:28.560 --> 00:31:32.560 Only one terabyte line is? Yes, and there's a very good reason 00:31:32.560 --> 00:31:36.560 for that. We used to have some editors that would 00:31:36.560 --> 00:31:40.560 you know, sneakily even upgrade their stations with 00:31:40.560 --> 00:31:44.560 larger SSDs and what the temptation was 00:31:44.560 --> 00:31:48.560 at that time was for them to dump footage onto their local 00:31:48.560 --> 00:31:52.560 drives and then, oh man, I'm just making a quick fix 00:31:52.560 --> 00:31:56.560 so like, I'll just throw it in the timeline, I'll export the video and then 00:31:56.560 --> 00:32:00.560 it doesn't matter. But what happens when you do that is you don't have 00:32:00.560 --> 00:32:04.560 all your stuff in one place and when you're sick the next day and someone needs to go 00:32:04.560 --> 00:32:08.560 make another fix to that video, they go, what's this media off line? 00:32:08.560 --> 00:32:12.560 Oh, they didn't copy it to the server. So we actually 00:32:12.560 --> 00:32:16.560 go out of our way to have small storage drives in our editing 00:32:16.560 --> 00:32:20.560 systems so that nobody is tempted to copy raw footage onto their local 00:32:20.560 --> 00:32:24.560 drive and work on it. We all work off of our redundant and backed 00:32:24.560 --> 00:32:28.560 up server. So there you go. Not 00:32:28.560 --> 00:32:32.560 only do we save a buck, but this Gen 4 drive is reasonably 00:32:32.560 --> 00:32:36.560 performant and has a DRAM cache and all it needs is to store the OS 00:32:36.560 --> 00:32:40.560 and the software that we use. We also kept our case 00:32:40.560 --> 00:32:44.560 hold on, let me just throw this back on. I actually, ooh, I'm liking this tooless mechanism 00:32:44.560 --> 00:32:48.560 for this. Not bad. So it's got a little clip there, you pop that off 00:32:48.560 --> 00:32:52.560 and then you got a little slide there. I mean, it feels very expensive 00:32:52.560 --> 00:32:56.560 but I guess that's cause it is. 00:32:56.560 --> 00:33:00.560 So we're still using the Phanteks Eclipse G500A. It's not the world's 00:33:00.560 --> 00:33:04.560 most exciting case, certainly, but it's really easy to 00:33:04.560 --> 00:33:08.560 work in and has decent build quality. We don't need our workstation to be exciting 00:33:08.560 --> 00:33:12.560 anyway. It's a workstation, not an excitement station. 00:33:12.560 --> 00:33:16.560 Oh, what are we doing for cooling? You know what? I think I want to put my 00:33:16.560 --> 00:33:20.560 cooler on before we put this in here. So why don't we talk about that next. 00:33:20.560 --> 00:33:24.560 We are still using the Noctua NHD 15. 00:33:24.560 --> 00:33:28.560 Again, it's not the world's most exciting choice, but it's 00:33:28.560 --> 00:33:32.560 hard to argue with a great air cooler that offers good thermal performance 00:33:32.560 --> 00:33:36.560 with low noise and this is a really key one for me. 00:33:36.560 --> 00:33:40.560 Super easy installation because right now, as I build 00:33:40.560 --> 00:33:44.560 this machine, it's not necessarily the only time anyone will have to work on this 00:33:44.560 --> 00:33:48.560 system. Things go wrong, especially the motherboards 00:33:48.560 --> 00:33:52.560 and those threadripper systems. Those went wrong a lot. 00:33:52.560 --> 00:33:56.560 And so when it's someone's job to go in and fix 00:33:56.560 --> 00:34:00.560 up these systems, it's nice when they're working with a retention mechanism that 00:34:00.560 --> 00:34:04.560 is easy to use and not only that, but quick to apply. 00:34:04.560 --> 00:34:08.560 This will take me a minute, so 00:34:08.560 --> 00:34:12.560 I'll put my screwdriver. This will take me a minute to install though. So Dan, 00:34:12.560 --> 00:34:16.560 do you want to hit me with a merge message? You don't have any merge messages? 00:34:16.560 --> 00:34:20.560 Is the dashboard working or is it just because I didn't tell people that there are merge messages? 00:34:20.560 --> 00:34:24.560 Oh, probably because you didn't tell people. I mean, I did get one. 00:34:24.560 --> 00:34:28.560 Let's see. Thanks for the bag Linus. I will use it until it falls apart 00:34:28.560 --> 00:34:32.560 or blows up. Huh. Well, 00:34:32.560 --> 00:34:36.560 hopefully neither of those things will happen, but if 00:34:36.560 --> 00:34:40.560 one of them does, I hope your bag falls apart. 00:34:40.560 --> 00:34:44.560 Can't wait for that to be clipped out of context anyway. If you guys want to interact with the stream, 00:34:44.560 --> 00:34:48.560 the best way to do it is with a merge message. All you got to do is head over to 00:34:48.560 --> 00:34:52.560 lttstore.com and if you add some high quality 00:34:52.560 --> 00:34:56.560 merchandise to your cart and when, oh, does this one come 00:34:56.560 --> 00:35:00.560 with the offset mount? No, this is an older one. Okay, we'll just use the standard 00:35:00.560 --> 00:35:04.560 mount. And when you're in the cart, you will see a little 00:35:04.560 --> 00:35:08.560 prompt, a little box to send us a merge message. That'll go 00:35:08.560 --> 00:35:12.560 to producer Dan, who will either just push it up 00:35:12.560 --> 00:35:16.560 to the bottom of the stream. So, you know, you can do like a, you know, hey mom or 00:35:16.560 --> 00:35:20.560 happy anniversary or will you marry me or you know, whatever it is that you want to put down 00:35:20.560 --> 00:35:24.560 there for the LTC fan in your life and or he will 00:35:24.560 --> 00:35:28.560 respond to it himself or he will curate it and 00:35:28.560 --> 00:35:32.560 I can respond to it later on in the stream. 00:35:32.560 --> 00:35:36.560 Let's get this installed. 00:35:36.560 --> 00:35:40.560 Oh, I could also bring up the chat. Oh, where the heck did I put my computer? 00:35:40.560 --> 00:35:44.560 I do not remember. David, do you have my laptop? 00:35:44.560 --> 00:35:48.560 Yeah, I put it on the table. One second. Sick. Yeah, Ken has. 00:35:48.560 --> 00:35:52.560 Thank you. Do you want it right here? 00:35:52.560 --> 00:35:56.560 Oh, yeah, sure. Yeah, here's good. Let me just make sure that it doesn't have 00:35:56.560 --> 00:36:00.560 the panel with all of our stream keys open. It totally did. That would 00:36:00.560 --> 00:36:04.560 have been extremely not funny. I mean 00:36:04.560 --> 00:36:08.560 it would have been a little funny, but 00:36:08.560 --> 00:36:12.560 Hopefully it's not like a social security number. You can change them. Only later. Well, no, you can 00:36:12.560 --> 00:36:16.560 change them, but it would have been very challenging 00:36:16.560 --> 00:36:20.560 to change them quick enough for it to not be a problem. Oh, fair. 00:36:20.560 --> 00:36:24.560 Google signed me out. 00:36:24.560 --> 00:36:28.560 I had the dashboard open earlier in the stream and it signed me out of my 00:36:28.560 --> 00:36:32.560 account. It's so infuriating. 00:36:32.560 --> 00:36:36.560 I swear it signs me out way more 00:36:36.560 --> 00:36:40.560 than every 30 days. Like there's no way. 00:36:40.560 --> 00:36:44.560 Okay. 00:36:44.560 --> 00:36:48.560 I am going to successfully type my 00:36:48.560 --> 00:36:52.560 password on the fourth 00:36:52.560 --> 00:36:56.560 fifth try. Fifth try. There we go. We've got this. 00:36:56.560 --> 00:37:00.560 All right. Motherboard prices need 00:37:00.560 --> 00:37:04.560 to chill, says the tech tempest over in Floatplane chat. Yeah, 00:37:04.560 --> 00:37:08.560 I agree with you 100%. Like on the one hand 00:37:08.560 --> 00:37:12.560 there are components that have gone way up in price that I 00:37:12.560 --> 00:37:16.560 kind of understand. Like 00:37:16.560 --> 00:37:20.560 yes, NVIDIA owns absolutely some of the blame for 00:37:20.560 --> 00:37:24.560 GPU prices being completely out of control, but they don't own 00:37:24.560 --> 00:37:28.560 all of it. TSMC doesn't publish their price lists publicly 00:37:28.560 --> 00:37:32.560 or anything like that, but the industry scuttle butt is that a wafer 00:37:32.560 --> 00:37:36.560 is costing several times what it used to. So there have been 00:37:36.560 --> 00:37:40.560 legitimate cost increases that have driven at least some of the 00:37:40.560 --> 00:37:44.560 price ballooning that has gone on for GPUs. Clearly 00:37:44.560 --> 00:37:48.560 not all of it, but at least some of it. Whereas like 00:37:48.560 --> 00:37:52.560 motherboards? I don't know man. 00:37:52.560 --> 00:37:56.560 Like coppers obviously up 00:37:56.560 --> 00:38:00.560 10 or 20 years ago. I think that in general they're built 00:38:00.560 --> 00:38:04.560 to a higher standard of quality than they used to be. 00:38:04.560 --> 00:38:08.560 Like I bet you could build a pretty cheap motherboard with 00:38:08.560 --> 00:38:12.560 little caps all over it and stuff these days still, but nobody wants to 00:38:12.560 --> 00:38:16.560 do that because nobody wants them all to just explode a couple years later 00:38:16.560 --> 00:38:20.560 while they're still under warranty. 00:38:20.560 --> 00:38:24.560 I don't know man, it just feels like 00:38:24.560 --> 00:38:28.560 and okay yeah, here's another example. It's like part of the cost of this board 00:38:28.560 --> 00:38:32.560 is definitely these gigantic heat sinks 00:38:32.560 --> 00:38:36.560 that are machined out of solid friggin' piece of aluminum. Have you priced 00:38:36.560 --> 00:38:40.560 like a brick of aluminum lately? I have. 00:38:40.560 --> 00:38:44.560 I don't remember the price, but I remember being surprised at the price. It's freakin' 00:38:44.560 --> 00:38:48.560 expensive. Oh, I forgot what I was doing. I was supposed to be putting this cooler 00:38:48.560 --> 00:38:52.560 on. Alright, let's put it on some thermal goop. Just so you know guys 00:38:52.560 --> 00:38:56.560 if you buy a cooler these days from Noctua 00:38:56.560 --> 00:39:00.560 it comes with a different version of the hold down hardware here 00:39:00.560 --> 00:39:04.560 and basically it has two holes 00:39:04.560 --> 00:39:08.560 in it and if you have a CPU that has the compute dies 00:39:08.560 --> 00:39:12.560 down at the bottom which I believe is all of Ryzen 7000 00:39:12.560 --> 00:39:16.560 and Ryzen 9000 then you can move the cooler down a little bit 00:39:16.560 --> 00:39:20.560 that is clearance permitting on your motherboard and you can 00:39:20.560 --> 00:39:24.560 position more of your cooler's 00:39:24.560 --> 00:39:28.560 heat pipes directly over the hottest part of the 00:39:28.560 --> 00:39:32.560 IHS which is the heat spreader that sits over top of those compute dies 00:39:32.560 --> 00:39:36.560 Ouch! Oh! Shoot 00:39:36.560 --> 00:39:40.560 I need a bandaid and I have to fill up the form 00:39:40.560 --> 00:39:44.560 I cut myself. Yeah. 00:39:44.560 --> 00:39:48.560 Dang it. Wow, that's really sharp. Okay, if ASUS 00:39:48.560 --> 00:39:52.560 is watching, which I assume they are because they did kind of sponsor the video 00:39:52.560 --> 00:39:56.560 this little piece right here wouldn't normally be a problem 00:39:56.560 --> 00:40:00.560 but because of the sheer weight of the 00:40:00.560 --> 00:40:04.560 power and cooler, the pressure 00:40:04.560 --> 00:40:08.560 when my finger got stuck under it sliced through me 00:40:08.560 --> 00:40:12.560 Oh man. Ah! You know what? She might not bleed 00:40:12.560 --> 00:40:16.560 I might not have to fill up the form. Anyway, why don't we finally 00:40:16.560 --> 00:40:20.560 put thermal compound on this? Dan, do you have any messages for me? 00:40:20.560 --> 00:40:24.560 Yes, I have a couple here actually 00:40:24.560 --> 00:40:28.560 they are starting to come in pretty intensely. Why don't you go ahead and hit me 00:40:28.560 --> 00:40:32.560 Any chance of reviving the summer jacket even if it's not ocean friendly? 00:40:32.560 --> 00:40:36.560 I would love something light for dog walks in the sun 00:40:36.560 --> 00:40:40.560 The summer jacket. Oh, you mean the UV hoodie? Is that what they are talking about? 00:40:40.560 --> 00:40:44.560 Maybe, I don't know. Oh, they said revive though 00:40:44.560 --> 00:40:48.560 because the UV hoodie never actually got released. It was a product 00:40:48.560 --> 00:40:52.560 that we made a couple of samples of and then 00:40:52.560 --> 00:40:56.560 we found out that we couldn't achieve the level of UV 00:40:56.560 --> 00:41:00.560 resistance that we wanted without resorting to nasty coatings 00:41:00.560 --> 00:41:04.560 and there was actually 00:41:04.560 --> 00:41:08.560 manufacturing issues with the fabric that we had that didn't require 00:41:08.560 --> 00:41:12.560 the coatings. Dude, we did a production 00:41:12.560 --> 00:41:16.560 run with the factory and they were the ones who told us 00:41:16.560 --> 00:41:20.560 I really don't think you guys can sell this. That 00:41:20.560 --> 00:41:24.560 never happens because apparently the sizing for a medium 00:41:24.560 --> 00:41:28.560 could be anywhere from small to XL just because of how difficult that 00:41:28.560 --> 00:41:32.560 fabric was to work with. So we are still working on a 00:41:32.560 --> 00:41:36.560 sun like a UV blocking hoodie because I love 00:41:36.560 --> 00:41:40.560 mine and Tatiana is 00:41:40.560 --> 00:41:44.560 giving it her attention. I believe Bridget on the like 00:41:44.560 --> 00:41:48.560 so she's on the material side and then I believe Bridget from the fashion 00:41:48.560 --> 00:41:52.560 team is giving it some of her attention although it might actually be Lisa 00:41:52.560 --> 00:41:56.560 we want to do it but it won't be until summer 00:41:56.560 --> 00:42:00.560 2026 and that assumes that we managed to find 00:42:00.560 --> 00:42:04.560 a material that is suitable. I am 00:42:04.560 --> 00:42:08.560 no, I shouldn't say that. 00:42:08.560 --> 00:42:12.560 I am a little more open to coatings 00:42:12.560 --> 00:42:16.560 than I used to be. There is one garment 00:42:16.560 --> 00:42:20.560 that I have tentatively greenlit like a coating 00:42:20.560 --> 00:42:24.560 in order to achieve, I forget if it was stain resistance or 00:42:24.560 --> 00:42:28.560 water repellency or UV resistance. I forget what it 00:42:28.560 --> 00:42:32.560 was but it's some kind of treatment and I have tentatively greenlit 00:42:32.560 --> 00:42:36.560 that one but the reason that I greenlit it is because 00:42:36.560 --> 00:42:40.560 it was the kind of garment that would only be washed 00:42:40.560 --> 00:42:44.560 ten times over a span of several years. Like I think 00:42:44.560 --> 00:42:48.560 it might have been like a jacket or something like that where you're not 00:42:48.560 --> 00:42:52.560 washing it every week as part of your cycle because 00:42:52.560 --> 00:42:56.560 I read your guys' comments, I use the products, I know that you guys 00:42:56.560 --> 00:43:00.560 are beating the absolute stuffing out of this stuff. 00:43:00.560 --> 00:43:04.560 I see the posts on Reddit and stuff where people 00:43:04.560 --> 00:43:08.560 show off their collection of LTT gear and I can tell a lot of it is 00:43:08.560 --> 00:43:12.560 extremely well worn and I know you guys because I'm one 00:43:12.560 --> 00:43:16.560 of you guys, I know you ain't separating your delicates 00:43:16.560 --> 00:43:20.560 from your cotton stuff in the wash and I know you're just washing 00:43:20.560 --> 00:43:24.560 everything on warm or whatever, right? So it does 00:43:24.560 --> 00:43:28.560 limit us a little bit in terms of what kinds of materials that we can use 00:43:28.560 --> 00:43:32.560 because we know that you guys are going to mistreat it and that 00:43:32.560 --> 00:43:36.560 product design philosophy has worked out really well for us because we know 00:43:36.560 --> 00:43:40.560 our customer. Like when you guys saw the project farm 00:43:40.560 --> 00:43:44.560 video where Todd benchmarked our t-shirts against other t-shirts 00:43:44.560 --> 00:43:48.560 and he found that they didn't shrink nearly as much, that's not because we have 00:43:48.560 --> 00:43:52.560 magic cotton that doesn't shrink, it's because we 00:43:52.560 --> 00:43:56.560 pre-shrink everything to an obsessive level as much as we are able 00:43:56.560 --> 00:44:00.560 because we know that you guys are going to not take care of things properly 00:44:00.560 --> 00:44:04.560 and that's exactly what Todd did. In his benchmark test 00:44:04.560 --> 00:44:08.560 he washed the clothes like a guy, 00:44:08.560 --> 00:44:12.560 which you know makes sense, he's a guy or whatever, but that is 00:44:12.560 --> 00:44:16.560 not how you properly wash clothes and so we performed really well 00:44:16.560 --> 00:44:20.560 in that test because we knew that was going to happen. That doesn't 00:44:20.560 --> 00:44:24.560 mean that those other garments were bad, it just means that they were designed for people 00:44:24.560 --> 00:44:28.560 who take care of their clothes properly. But anyway 00:44:28.560 --> 00:44:32.560 I got to send a very gloaty message to the fashion team because they're always going 00:44:32.560 --> 00:44:36.560 after me about like oh we could use this material, we just have to put 00:44:36.560 --> 00:44:40.560 really good care instructions on the tag and people will totally not contact support 00:44:40.560 --> 00:44:44.560 about it falling apart, I'm like no. 00:44:44.560 --> 00:44:48.560 Alright let's go ahead and get this motherboard installed. Dan do you want to hit me with another 00:44:48.560 --> 00:44:52.560 merge message? Yeah sure, let's see what you've got a couple more. 00:44:52.560 --> 00:44:56.560 When I stream music using Plex Amp on my phone over data 00:44:56.560 --> 00:45:00.560 my carrier Mint mislabels it as hotspot data. 00:45:00.560 --> 00:45:04.560 Have you heard of this or no effects? Support is being useless. 00:45:04.560 --> 00:45:08.560 Oh wow hotspot data. 00:45:08.560 --> 00:45:12.560 I can't say that with any of the carriers that I've used here in Canada 00:45:12.560 --> 00:45:16.560 I've had a problem with them mischaracterizing 00:45:16.560 --> 00:45:20.560 any of the data that I've used on my phone 00:45:20.560 --> 00:45:24.560 and honestly speaking I'm not 00:45:24.560 --> 00:45:28.560 fully sure what that means because which carrier was it? 00:45:28.560 --> 00:45:32.560 Mint. Mint sorry. That's Ryan Reynolds. That's right because 00:45:32.560 --> 00:45:36.560 don't some of the more budget oriented carriers have separate data limits 00:45:36.560 --> 00:45:40.560 for different uses? I do not know. 00:45:40.560 --> 00:45:44.560 I believe so. I know for sure that T-Mobile does because they have partnerships 00:45:44.560 --> 00:45:48.560 and stuff where there's certain things that you can do that do not 00:45:48.560 --> 00:45:52.560 count against your data cap. I don't know 00:45:52.560 --> 00:45:56.560 it's been a whole conversation in the US around 00:45:56.560 --> 00:46:00.560 whether the carriers should have the right to prioritize certain data 00:46:00.560 --> 00:46:04.560 or treat certain data differently and 00:46:04.560 --> 00:46:08.560 all I can tell you is if you don't like that behavior you might just have to 00:46:08.560 --> 00:46:12.560 kind of talk to your local representation. Do we have the hardware for 00:46:12.560 --> 00:46:16.560 this case anywhere by any chance? No I was counting on it being in those 00:46:16.560 --> 00:46:20.560 shelves. Ah okay well I will find some hardware 00:46:20.560 --> 00:46:24.560 if it's not then I will. No no we got this we got this 00:46:24.560 --> 00:46:28.560 um 00:46:28.560 --> 00:46:32.560 I don't see the 632 bin 00:46:32.560 --> 00:46:36.560 where do people take this stuff? I don't know why people take these 00:46:36.560 --> 00:46:40.560 things. Counter sunk hard drive screws? Yeah I really 00:46:40.560 --> 00:46:44.560 don't see either the M3 bin. Oh I've got the M3 bin. Got the M3 cap. 00:46:44.560 --> 00:46:48.560 You gonna make it work? 00:46:48.560 --> 00:46:52.560 Lost your mic. 00:46:52.560 --> 00:46:56.560 Yeah. 00:46:56.560 --> 00:47:00.560 Yeah I probably leaned against the thing. We got band-aids for you. Sorry about that. 00:47:00.560 --> 00:47:04.560 Oh cool. Yes. 00:47:04.560 --> 00:47:08.560 May I please have the smallest band-aid? Smala please. 00:47:08.560 --> 00:47:12.560 That's our smallest band-aid? 00:47:12.560 --> 00:47:16.560 Okay to be clear 00:47:16.560 --> 00:47:20.560 if I was at home on my own time I would not even like put a band-aid 00:47:20.560 --> 00:47:24.560 on this it's no big deal and I especially wouldn't need a team of people to 00:47:24.560 --> 00:47:28.560 apply it for me. I think if you weren't on stream you wouldn't have done it. 00:47:28.560 --> 00:47:32.560 I always fill up the form. Yeah because it's not 00:47:32.560 --> 00:47:36.560 oh my gosh okay yeah yeah I know I know I know 00:47:36.560 --> 00:47:40.560 disinfecting wipe. So the 00:47:40.560 --> 00:47:44.560 reason is that in the workplace even something 00:47:44.560 --> 00:47:48.560 like this could theoretically lead to an infection 00:47:48.560 --> 00:47:52.560 it could be blood-borne you can however remote the possibility 00:47:52.560 --> 00:47:56.560 you can die from a little owie and or like 00:47:56.560 --> 00:48:00.560 lose a hand or an ARM or whatever and so with that in mind 00:48:00.560 --> 00:48:04.560 from like a workplace safety 00:48:04.560 --> 00:48:08.560 standpoint we have policies that ensure that if anyone does get a little 00:48:08.560 --> 00:48:12.560 boo-boo at work we have processes 00:48:12.560 --> 00:48:16.560 to document that and treat it so that in the event 00:48:16.560 --> 00:48:20.560 that something really really terrible happens 00:48:20.560 --> 00:48:24.560 they will at least get compensation for it 00:48:24.560 --> 00:48:28.560 so as a leader here at the company 00:48:28.560 --> 00:48:32.560 I feel that I should lead by example 00:48:32.560 --> 00:48:36.560 and even though I kind of gripe about it and meme about it a little bit 00:48:36.560 --> 00:48:40.560 make sure that if I am injured however small 00:48:40.560 --> 00:48:44.560 I fill out the proper forms and do the proper documentation because I don't want someone to be 00:48:44.560 --> 00:48:48.560 hurt or injured and then not be able to get coverage 00:48:48.560 --> 00:48:52.560 because what the 00:48:52.560 --> 00:48:56.560 is trying to protect against is people who get a little owie at home 00:48:56.560 --> 00:49:00.560 and say oh no I got that at work so we have to have the documentation 00:49:00.560 --> 00:49:04.560 for when it happened and what happened and what was done to treat it to ensure that we can prove 00:49:04.560 --> 00:49:08.560 that it did in fact happen at work to make sure they get their coverage 00:49:08.560 --> 00:49:12.560 that is why we do it not because I need someone to put a band-aid on for me 00:49:16.560 --> 00:49:20.560 I am going to tilt this up so I can finish installing this here did we find 00:49:20.560 --> 00:49:24.560 3632 screws or did we give up okay well hopefully we won't need any 00:49:24.560 --> 00:49:28.560 we may not need any oh I might need a thumb screw at the very least 00:49:28.560 --> 00:49:32.560 alright Dan do you want to hit me with a merge message 00:49:32.560 --> 00:49:36.560 yeah sure here is another one for you why don't you guys edit on 00:49:36.560 --> 00:49:40.560 Apple machines either a beefed out MacBook Pro or Mac 00:49:40.560 --> 00:49:44.560 Studios Adobe applications are way more stable on Mac and they are more 00:49:44.560 --> 00:49:48.560 compact and power efficient also why not knock to a black 00:49:48.560 --> 00:49:52.560 why no what black knock to a 00:49:52.560 --> 00:49:56.560 knock to a black oh I don't know you like the brown one 00:49:56.560 --> 00:50:00.560 yeah I don't know brown is fine it doesn't really matter they are editing work stations 00:50:00.560 --> 00:50:04.560 they are not gaming rigs as for your first question why we don't edit on Mac 00:50:04.560 --> 00:50:08.560 under certain circumstances we actually do 00:50:08.560 --> 00:50:12.560 so whenever we do like a trade show 00:50:12.560 --> 00:50:16.560 or an industry event or whatever else where we need to do on-site editing 00:50:16.560 --> 00:50:20.560 we do tend to travel with Macs as for 00:50:20.560 --> 00:50:24.560 why we don't how much tether you got there Andy 00:50:24.560 --> 00:50:28.560 you got a lot of tether oh look at that you got plenty of tether okay come on with me then 00:50:28.560 --> 00:50:32.560 I truthfully 00:50:32.560 --> 00:50:36.560 oh we have new people I didn't see anybody oh nobody 00:50:36.560 --> 00:50:40.560 is here are they like out for a hey Alfred can I borrow you for a minute 00:50:40.560 --> 00:50:44.560 oh yeah no yeah no sounds good 00:50:44.560 --> 00:50:48.560 oh okay Alfred we had a question from a viewer 00:50:48.560 --> 00:50:52.560 I don't know if you guys have like met Alfred yet but he's our 00:50:52.560 --> 00:50:56.560 production manager guy now so they wanted to know 00:50:56.560 --> 00:51:00.560 why we're like using custom PCs instead of just switching over to Mac because 00:51:00.560 --> 00:51:04.560 of the better stability of Adobe applications on Mac you'll have to be 00:51:04.560 --> 00:51:08.560 uncomfortably close to me because I have the mic alright well that's a great 00:51:08.560 --> 00:51:12.560 question so we have used a combination of Macs and 00:51:12.560 --> 00:51:16.560 PC but for I mentioned for like travel we take Mac books with us but 00:51:16.560 --> 00:51:20.560 why not Mac here first of all we're using what we 00:51:20.560 --> 00:51:24.560 have oh but we're building new machines yes 00:51:24.560 --> 00:51:28.560 so we could oh we're open to it okay we're 00:51:28.560 --> 00:51:32.560 apparently open to it we are open to it okay thanks Alfred I know 00:51:32.560 --> 00:51:36.560 that some of our editors do strongly prefer PC I know that 00:51:36.560 --> 00:51:40.560 not every application that we use in our workflow is 00:51:40.560 --> 00:51:44.560 part of the Adobe suite I do know that 00:51:44.560 --> 00:51:48.560 our info team would strongly prefer that we have 00:51:48.560 --> 00:51:52.560 as few Macs as possible because please most of their 00:51:52.560 --> 00:51:56.560 administration is for PCs and so most of our processes are 00:51:56.560 --> 00:52:00.560 set up for PC but other than that apparently we are open to it 00:52:00.560 --> 00:52:04.560 what we're also open to is using 00:52:04.560 --> 00:52:08.560 and add in network card 00:52:08.560 --> 00:52:12.560 hmmm 00:52:12.560 --> 00:52:16.560 sonnet technologies wait we use sonnet 00:52:16.560 --> 00:52:20.560 10 gig network cards why they're technically still the fancy 00:52:20.560 --> 00:52:24.560 fancy Intel chip that we like oh okay I'm just 00:52:24.560 --> 00:52:28.560 surprised that we have new ones from sonnet when we have like an entire 00:52:28.560 --> 00:52:32.560 shelf of x5 40 cards sitting over in the warehouse 00:52:32.560 --> 00:52:36.560 this one wasn't given to me by infra this one was I oh I need a 00:52:36.560 --> 00:52:40.560 card and I went and grabbed it got it okay this might not be actually represented 00:52:40.560 --> 00:52:44.560 all right well anyway even with boards that have 10 gig on board 00:52:44.560 --> 00:52:48.560 LAN we use these add in next because we've just found them to be 00:52:48.560 --> 00:52:52.560 more reliable is that true David no Dan 00:52:52.560 --> 00:52:56.560 yet maybe I mean we used to have like 00:52:56.560 --> 00:53:00.560 fiber to every station and now we do 10 gig 00:53:00.560 --> 00:53:04.560 boards one they're really reliable but also I think a lot of the boards before 00:53:04.560 --> 00:53:08.560 didn't have 10 gig built in I thought a big part of it too was the Kyoksia 00:53:08.560 --> 00:53:12.560 or whatever it was in the motherboards doesn't play well with our 10 gig I can't 00:53:12.560 --> 00:53:16.560 remember it's probably not important anymore well we no longer remember 00:53:16.560 --> 00:53:20.560 why we use these add in 10 gig network cards but we do so 00:53:20.560 --> 00:53:24.560 there you go this is the kind of thing that happens in a corporate environment that I think a lot of 00:53:24.560 --> 00:53:28.560 enthusiasts don't necessarily get 00:53:28.560 --> 00:53:32.560 exposed to is sometimes a decision is made for a reason that 00:53:32.560 --> 00:53:36.560 totally makes sense in the time that it's made and it costs 00:53:36.560 --> 00:53:40.560 so little to continue making that decision forever that there's 00:53:40.560 --> 00:53:44.560 never any incentive to change it even if nobody who is left at 00:53:44.560 --> 00:53:48.560 the company remembers why the decision was made or understands 00:53:48.560 --> 00:53:52.560 why you continue to make it 00:53:52.560 --> 00:53:56.560 oh man I mean there's nothing wrong certainly with using an Intel 00:53:56.560 --> 00:54:00.560 nick there just isn't maybe necessarily any reason to do it we just 00:54:00.560 --> 00:54:04.560 we already have so many of them that I guess we might as well just throw them in our systems 00:54:04.560 --> 00:54:08.560 all right done for oh my goodness good gravy is 00:54:08.560 --> 00:54:12.560 that ever heavy all right let's take a look at this power supply 00:54:12.560 --> 00:54:16.560 sheesh this is the ROG 4 1200 00:54:16.560 --> 00:54:20.560 watt platinum 3 it is 00:54:20.560 --> 00:54:24.560 $515 so 00:54:24.560 --> 00:54:28.560 full honesty this stream is sponsored by ASUS 00:54:28.560 --> 00:54:32.560 but this is probably more than I would spend on a power supply 00:54:32.560 --> 00:54:36.560 for a run of the mill video editing workstation 00:54:36.560 --> 00:54:40.560 however it is jam packed full of features that ASUS would like 00:54:40.560 --> 00:54:44.560 me to tell you about including their GAN MOSFET which ASUS claims 00:54:44.560 --> 00:54:48.560 offers 30% more power efficiency their GPU first voltage 00:54:48.560 --> 00:54:52.560 sensing with a patented intelligent voltage stabilizer 00:54:52.560 --> 00:54:56.560 their magnetic OLED display magnetic 00:54:56.560 --> 00:55:00.560 display are you guys even serious right now oh my god 00:55:00.560 --> 00:55:04.560 oh my god I figured out why 00:55:04.560 --> 00:55:08.560 it's so you can put it on either side 00:55:08.560 --> 00:55:12.560 that's so smart so you can have 00:55:12.560 --> 00:55:16.560 so you can have your OLED display and eat it too 00:55:16.560 --> 00:55:20.560 depending on whether you want your fan oriented down or oriented up 00:55:20.560 --> 00:55:24.560 I'm gonna go with fan oriented down 00:55:24.560 --> 00:55:28.560 because I believe yes this case has a filtered bottom intake here I'll get you a closer 00:55:28.560 --> 00:55:32.560 look at that Andy that is hilarious 00:55:32.560 --> 00:55:36.560 no those aren't the pins those are just graphics but yes it looks 00:55:36.560 --> 00:55:40.560 it kind of looks like it so that goes on there or it comes off 00:55:40.560 --> 00:55:44.560 according to your preference that is 00:55:44.560 --> 00:55:48.560 so funny 00:55:48.560 --> 00:55:52.560 screwed it up way to go Linus you 00:55:52.560 --> 00:55:56.560 dropped the ball that's what I dropped today 00:55:56.560 --> 00:56:00.560 okay I mean they can't do it oh no oh yeah 00:56:00.560 --> 00:56:04.560 oh look at that yeah and all the text is right side up regardless of which way you put it into 00:56:04.560 --> 00:56:08.560 hilarious um 00:56:08.560 --> 00:56:12.560 Anywho it's fully modular with compliance with the ATX 00:56:12.560 --> 00:56:16.560 3.1 standard and comes with a 10 year warranty 00:56:16.560 --> 00:56:20.560 let's go ahead and get it installed then do you want to hit me with a merchant message 00:56:20.560 --> 00:56:24.560 or a thing heck yeah 00:56:24.560 --> 00:56:28.560 Hey Linus any chance of offering a certificate like Coursera with LTT being well known 00:56:28.560 --> 00:56:32.560 in the tech world wouldn't it be great to offer something like that for a refresher course 00:56:32.560 --> 00:56:36.560 LTT University it's something that Colton has wanted to 00:56:36.560 --> 00:56:40.560 develop for a long time and not necessarily that specifically 00:56:40.560 --> 00:56:44.560 but some kind of course 00:56:44.560 --> 00:56:48.560 courses can be extremely lucrative and when your job 00:56:48.560 --> 00:56:52.560 title is business development manager I can understand 00:56:52.560 --> 00:56:56.560 why trying to pursue something like that would be 00:56:56.560 --> 00:57:00.560 very appealing but my issue every time we bring it up 00:57:00.560 --> 00:57:04.560 is that our whole thing from day 0 00:57:04.560 --> 00:57:08.560 has been taking advantage of YouTube 00:57:08.560 --> 00:57:12.560 and it's incredible ability to democratize information 00:57:12.560 --> 00:57:16.560 and knowledge 00:57:16.560 --> 00:57:20.560 to democratize knowledge about 00:57:20.560 --> 00:57:24.560 PCs and software and 00:57:24.560 --> 00:57:28.560 troubleshooting and configuration and like all these things 00:57:28.560 --> 00:57:32.560 all these things that we do are about the sharing of information 00:57:32.560 --> 00:57:36.560 and so how do I reconcile that with a paid course 00:57:36.560 --> 00:57:40.560 that is sort of blocked off like we do exclusive content 00:57:40.560 --> 00:57:44.560 absolutely like over on LMG.GG 00:57:44.560 --> 00:57:48.560 you'll find all kinds of wonderful exclusives like you can 00:57:48.560 --> 00:57:52.560 have interviews with various members of our team 00:57:52.560 --> 00:57:56.560 Sammy has a really cool series running right now he manages the Floatplane content 00:57:56.560 --> 00:58:00.560 for us he's got a really cool series called Why is WAN late 00:58:00.560 --> 00:58:04.560 where he kind of looks at the behind the scenes of what's going on around here 00:58:04.560 --> 00:58:08.560 on a Friday afternoon but none of that is critical 00:58:08.560 --> 00:58:12.560 that's fun but you don't need it to 00:58:12.560 --> 00:58:16.560 make a good decision you know 00:58:16.560 --> 00:58:20.560 you don't need it to help your friends build the best gaming computer for the money 00:58:20.560 --> 00:58:24.560 and so I've always just felt like 00:58:24.560 --> 00:58:28.560 yeah we could do a course on how to build a 00:58:28.560 --> 00:58:32.560 computer or whatever we could do a course on 00:58:32.560 --> 00:58:36.560 you know tech knowledge 00:58:36.560 --> 00:58:40.560 but how do we differentiate that from our standard content that is our bread and butter 00:58:40.560 --> 00:58:44.560 the reason that you guys engage with us 00:58:44.560 --> 00:58:48.560 and how do we make that not just kind of a 00:58:48.560 --> 00:58:52.560 how do we justify charging for what we would normally 00:58:52.560 --> 00:58:56.560 give you for free so we would have to come up with a way to 00:58:56.560 --> 00:59:00.560 really differentiate that content whether it's through 00:59:00.560 --> 00:59:04.560 making it like super professional and super awesome 00:59:04.560 --> 00:59:08.560 or whether it's going to another 00:59:08.560 --> 00:59:12.560 layer of depth or to your point including like 00:59:12.560 --> 00:59:16.560 a certificate with it or something like that but I just 00:59:16.560 --> 00:59:20.560 I don't know man I 00:59:20.560 --> 00:59:24.560 I just don't really 00:59:24.560 --> 00:59:28.560 think people need a certificate to do this kind of 00:59:28.560 --> 00:59:32.560 work I think what you really need is some experience and it can be useful 00:59:32.560 --> 00:59:36.560 to get a certificate just to demonstrate that you 00:59:36.560 --> 00:59:40.560 have some experience and you have some knowledge 00:59:40.560 --> 00:59:44.560 but I don't think that's for us to develop 00:59:44.560 --> 00:59:48.560 I think that if we were going to make a piece of content 00:59:48.560 --> 00:59:52.560 that was you know focused on arming people with a whole 00:59:52.560 --> 00:59:56.560 whack ton of knowledge you know something like how to build a PC 01:00:00.560 --> 01:00:04.560 for and the kind of thing where there would obviously 01:00:04.560 --> 01:00:08.560 be enough demand to make a ton of money 01:00:08.560 --> 01:00:12.560 you know for the business development team 01:00:12.560 --> 01:00:16.560 like I think the first one ended up getting like 10 million views or something 01:00:16.560 --> 01:00:20.560 like that and the second one I think is already closing in on like two or 01:00:20.560 --> 01:00:24.560 three like it's a really valuable resource 01:00:24.560 --> 01:00:28.560 it's just with that in mind then 01:00:28.560 --> 01:00:32.560 why are we paywalling it right like we don't really paywall anything 01:00:32.560 --> 01:00:36.560 that is valuable beyond just kind of hanging out with us 01:00:36.560 --> 01:00:40.560 right? 01:00:40.560 --> 01:00:44.560 12.5 on the OG wow okay it's even more than I thought 01:00:44.560 --> 01:00:48.560 and that's a long video that's a dense video that is not an 01:00:48.560 --> 01:00:52.560 entertaining video that is an educational video that we 01:00:52.560 --> 01:00:56.560 we obviously give our you know some of our entertainment flair to but it's meant 01:00:56.560 --> 01:01:00.560 to be a resource 01:01:00.560 --> 01:01:04.560 3.7 on the new one okay so yeah they're both doing better than I 01:01:04.560 --> 01:01:08.560 thought actually I don't know I'm not saying 01:01:08.560 --> 01:01:12.560 never it's possible Colton will talk me into it or we will come up 01:01:12.560 --> 01:01:16.560 with an angle that really makes it feel sufficiently 01:01:16.560 --> 01:01:20.560 different from our regular content that I think we could you know justify 01:01:20.560 --> 01:01:24.560 it but right now there is nothing 01:01:24.560 --> 01:01:28.560 there's nothing in the plan and we have other 01:01:28.560 --> 01:01:32.560 feminist opportunities that we're looking at more eminently than that 01:01:32.560 --> 01:01:36.560 yeah money for gold like yeah like becoming a gold prospector if you were 01:01:36.560 --> 01:01:40.560 tuned into the pre-stream which is archived exclusively 01:01:40.560 --> 01:01:44.560 on full plane if you guys want to go back and watch the 01:01:44.560 --> 01:01:48.560 pre-show before WAN Show or the pre-stream before streams like this 01:01:48.560 --> 01:01:52.560 that's a good kind of value for that membership 01:01:52.560 --> 01:01:56.560 but that doesn't take away from you know just the tech 01:01:56.560 --> 01:02:00.560 knowledge that we're disseminating 01:02:00.560 --> 01:02:04.560 Dan you got another one for me yes I do 01:02:04.560 --> 01:02:08.560 nice noise 01:02:08.560 --> 01:02:12.560 hi little D little L and no big L just 01:02:12.560 --> 01:02:16.560 built my first PC with ARGB 01:02:16.560 --> 01:02:20.560 any suggestions on control software that won't make me run programs from three different 01:02:20.560 --> 01:02:24.560 manufacturers to work for RAM GPU and motherboard 01:02:24.560 --> 01:02:28.560 I think I'm using Signal RGB on my system 01:02:28.560 --> 01:02:32.560 my NCIX signed PC in my office and that seems 01:02:32.560 --> 01:02:36.560 to be going okay for me I feel like that landscape 01:02:36.560 --> 01:02:40.560 is kind of always changing and you know who has the low 01:02:40.560 --> 01:02:44.560 overhead application kind of all over the place 01:02:44.560 --> 01:02:48.560 for my own system I can tell you right now I don't bother 01:02:48.560 --> 01:02:52.560 like for my system at home where I actually care about performance 01:02:52.560 --> 01:02:56.560 I just don't bother with it I just let it be rainbow vomit which 01:02:56.560 --> 01:03:00.560 doesn't have any CPU overhead and I don't care but 01:03:00.560 --> 01:03:04.560 if you care about it and you want to configure it then maybe give Signal RGB a try 01:03:04.560 --> 01:03:08.560 I'd say that would probably be your best bet 01:03:08.560 --> 01:03:12.560 full disclosure they have been a sponsor of ours in the past I don't think we've worked with them recently 01:03:12.560 --> 01:03:16.560 but hey there you go make of that what you will 01:03:16.560 --> 01:03:20.560 you use Signal as well okay cool 01:03:20.560 --> 01:03:24.560 there is no perfect one though yeah that's fair 01:03:24.560 --> 01:03:28.560 just plugging in a fan 01:03:28.560 --> 01:03:32.560 connector here or I'm going to try this is going to be pretty tough okay Dan 01:03:32.560 --> 01:03:36.560 you want to hit me again while I try and fight with this thing yeah sure 01:03:36.560 --> 01:03:40.560 I really wish I did this before I put in this NIC I put PTM 01:03:40.560 --> 01:03:44.560 7950 on my CPU and I have seen no cooling benefit over the 01:03:44.560 --> 01:03:48.560 core cell thermal paste I had on there is my cooler the bottleneck 01:03:48.560 --> 01:03:52.560 or did I probably apply it wrong 01:03:52.560 --> 01:03:56.560 I doubt that you applied it wrong I think it would be pretty hard to screw up applying PTM 01:03:56.560 --> 01:04:00.560 and also I want to 01:04:00.560 --> 01:04:04.560 make it clear that while we sell PTM 7950 and we think it's a great 01:04:04.560 --> 01:04:08.560 product it's not magic you know it's 01:04:08.560 --> 01:04:12.560 thermal paste you should not expect to get a meaningful 01:04:12.560 --> 01:04:16.560 performance boost from thermal paste you might see 01:04:16.560 --> 01:04:20.560 a couple degrees lower temps depending on the processor type 01:04:20.560 --> 01:04:24.560 but PTM is really best suited for direct 01:04:24.560 --> 01:04:28.560 die processors like you might find in a 01:04:28.560 --> 01:04:32.560 laptop for instance so 01:04:32.560 --> 01:04:36.560 oh I've been using these straps wrong for years interesting 01:04:36.560 --> 01:04:40.560 oh check this out I will come back to your question 01:04:40.560 --> 01:04:44.560 I for all this time have been going like this 01:04:44.560 --> 01:04:48.560 and then strapping it down like that which works but that's not what you're 01:04:48.560 --> 01:04:52.560 supposed to do you're supposed to put them all the way 01:04:52.560 --> 01:04:56.560 under then put this under then go like that 01:04:56.560 --> 01:05:00.560 brilliant I just tech tipped myself 01:05:00.560 --> 01:05:04.560 I am so happy 01:05:04.560 --> 01:05:08.560 I can't believe that I've been doing this wrong all this time 01:05:08.560 --> 01:05:12.560 I mean it's one of those things where it's like you know if it's working then whatever right if it fits 01:05:12.560 --> 01:05:16.560 but no this is way better this ah this is great 01:05:16.560 --> 01:05:20.560 oh actually no I don't like it as much on this one 01:05:20.560 --> 01:05:24.560 because if I do it this way 01:05:24.560 --> 01:05:28.560 then it's going to sit right there and I'm going to see the stupid cable 01:05:28.560 --> 01:05:32.560 okay well hmm 01:05:32.560 --> 01:05:36.560 okay well do whatever way works for you and this way works for me better for this one 01:05:36.560 --> 01:05:40.560 so that I can get it over to this side and I can trap it 01:05:40.560 --> 01:05:44.560 there between the hook and loop so it doesn't make its way back over 01:05:44.560 --> 01:05:48.560 okay well I'm less annoyed with myself for doing it wrong 01:05:48.560 --> 01:05:52.560 now that I know that this way can also be valid 01:05:52.560 --> 01:05:56.560 what question was I answering again I no longer remember oh yeah PTM 01:05:56.560 --> 01:06:00.560 so really it's best for bear dies so GPUs 01:06:00.560 --> 01:06:04.560 are a great example we used PTM7950 in the last 01:06:04.560 --> 01:06:08.560 scrapyard wars and that ended up getting us really nice temps 01:06:08.560 --> 01:06:12.560 that contributed to our system being quieter because 01:06:12.560 --> 01:06:16.560 the lower the temps on your GPU the lower it will spin the fans 01:06:16.560 --> 01:06:20.560 especially in the default profile before you tune anything so there's a definite benefit there 01:06:20.560 --> 01:06:24.560 but if you just throw it on a CPU with an 01:06:24.560 --> 01:06:28.560 IHS like an integrated heat spreader and you expect like a 01:06:28.560 --> 01:06:32.560 performance difference compared to what is already a pretty high performance 01:06:32.560 --> 01:06:36.560 thermal paste then yeah I can see how you'd be disappointed 01:06:36.560 --> 01:06:40.560 if it was released out of the gate but the thing about PTM 01:06:40.560 --> 01:06:44.560 or the other thing about PTM is that it's designed for longevity 01:06:44.560 --> 01:06:48.560 that stuff is super low validated 01:06:48.560 --> 01:06:52.560 to last for an extremely long time many many many many many heating and cooling cycles 01:06:52.560 --> 01:06:56.560 and my understanding is it actually tends to instead of 01:06:56.560 --> 01:07:00.560 drying out like some other lesser thermal compounds 01:07:00.560 --> 01:07:04.560 it actually has a tendency to perform a little bit better once it's broken in 01:07:04.560 --> 01:07:08.560 which used to be I feel like more of a thing back in the day 01:07:08.560 --> 01:07:12.560 you know back with like Arctic Silver and then 01:07:12.560 --> 01:07:16.560 became something that thermal paste manufacturers would market 01:07:16.560 --> 01:07:20.560 you didn't need for their compound but then I guess it kind of became a thing again 01:07:20.560 --> 01:07:24.560 so I don't know there's a lot of mixed 01:07:24.560 --> 01:07:28.560 information about that and frankly don't take 01:07:28.560 --> 01:07:32.560 this the wrong way but I simply don't care enough 01:07:32.560 --> 01:07:36.560 we're at the point now where if you buy a high quality thermal compound 01:07:36.560 --> 01:07:40.560 the difference of a 01:07:40.560 --> 01:07:44.560 degree or two here or there is not particularly meaningful to me 01:07:44.560 --> 01:07:48.560 so for me what I like about PTM is that I can use it in an 01:07:48.560 --> 01:07:52.560 application like a laptop or wherever and I can 01:07:52.560 --> 01:07:56.560 know that it's not going to like dry out or wear out in a 01:07:56.560 --> 01:08:00.560 reasonable amount of time I have as I've gotten older 01:08:00.560 --> 01:08:04.560 and gotten busier and gotten less patient 01:08:04.560 --> 01:08:08.560 I have found that I care far more about stuff just 01:08:08.560 --> 01:08:12.560 working and a little less about 01:08:12.560 --> 01:08:16.560 getting one degree more out of something you know 01:08:16.560 --> 01:08:20.560 alright I'm just plugging in so what is this what am I looking at here 01:08:20.560 --> 01:08:24.560 it's for the voltage sense I guess it's a voltage sense yeah oh interesting 01:08:24.560 --> 01:08:28.560 so it kind of what I guess prioritizes making 01:08:28.560 --> 01:08:31.560 sure that you don't get any v-drup on the to the gpn 01:08:31.560 --> 01:08:34.560 I can show you what the website says I don't really understand 01:08:34.560 --> 01:08:38.560 alright so yeah we plug that little purple one in directly to the power supply 01:08:38.560 --> 01:08:42.560 and then that is spliced into 01:08:42.560 --> 01:08:46.560 these two pins right here 01:08:46.560 --> 01:08:50.560 gp cp voltage sensing mode so you can set it to either CPU 01:08:50.560 --> 01:08:54.560 or GPU first 01:08:54.560 --> 01:08:58.560 even during demanding games alright 01:08:58.560 --> 01:09:02.560 maybe we haven't we haven't looked at this in the lab or anything so I don't 01:09:02.560 --> 01:09:06.560 actually know for sure if it does anything or if it matters but 01:09:06.560 --> 01:09:10.560 I can tell you it probably doesn't hurt anything so here we go 01:09:10.560 --> 01:09:14.560 and Linus are we giving these systems to all of the editors I do not know 01:09:14.560 --> 01:09:18.560 what the plan is for these systems that is a good question for infra 01:09:18.560 --> 01:09:22.560 hey Dan are we building systems like this for all the editors 01:09:22.560 --> 01:09:26.560 this is like the tester one oh this is a test system 01:09:26.560 --> 01:09:30.560 yeah right because I guess if switching to 01:09:30.560 --> 01:09:34.560 AMD doesn't actually even address the stability issues then there would be no reason to do it 01:09:34.560 --> 01:09:38.560 understood that makes perfect sense 01:09:38.560 --> 01:09:42.560 I expect it to be better than what we have now I built a very similar system for myself 01:09:42.560 --> 01:09:46.560 and it's been rock solid we've been running AMD on the WAN and this computer 01:09:46.560 --> 01:09:50.560 knock on wood but it's okay ah that's the WAN is a very different 01:09:50.560 --> 01:09:54.560 application than this though we don't even use Premiere 01:09:54.560 --> 01:09:58.560 I guess we'll see we'll see we'll see guys maybe oh maybe what we should 01:09:58.560 --> 01:10:02.560 do is let's commit now to do a like a Floatplane follow 01:10:02.560 --> 01:10:06.560 up just like we did with the hard line tubing thing 01:10:06.560 --> 01:10:10.560 so we can do a follow up and we can let you guys know what we settled on or maybe what we'll do 01:10:10.560 --> 01:10:14.560 is if we do settle on these we could do another stream where we build like half a 01:10:14.560 --> 01:10:18.560 dozen machines and we we build a bunch of them on camera like we've done in the past 01:10:18.560 --> 01:10:22.560 that maybe ill-advisable oh really 01:10:22.560 --> 01:10:26.560 we shouldn't build computers on stream anymore are you saying that I didn't build them good last time 01:10:26.560 --> 01:10:30.560 I thought the ones that we were using last time were all built blindfolded 01:10:30.560 --> 01:10:34.560 that's a rumor that I heard no I think 01:10:34.560 --> 01:10:38.560 I think what they're thinking of was the time that I built alongside 01:10:38.560 --> 01:10:42.560 someone else so the ones other than I did make one 01:10:42.560 --> 01:10:46.560 error on one of mine but other than that the ones I built were fine but the ones that we 01:10:46.560 --> 01:10:50.560 had built by the randoms I think had a lot of problems I think that was the problem 01:10:50.560 --> 01:10:54.560 yeah so but I could build them all 01:10:54.560 --> 01:10:58.560 I could supervise we could build them together 01:10:58.560 --> 01:11:02.560 speaking of making mistakes I several times 01:11:02.560 --> 01:11:06.560 have noted oh yeah I haven't plugged in my front connectors yet and then 01:11:06.560 --> 01:11:10.560 like oh I should do that now and then not done it 01:11:10.560 --> 01:11:14.560 so I'm gonna do that before we put the GPU in real quick here 01:11:14.560 --> 01:11:18.560 Dan do you have a merch message for me yes absolutely 01:11:18.560 --> 01:11:22.560 don't get more blood on it 01:11:22.560 --> 01:11:26.560 with the possible advent of steam OS around the corner is it true that AMD 01:11:26.560 --> 01:11:30.560 GPUs are preferable for Linux these days or am I out of date or 01:11:30.560 --> 01:11:34.560 misinformed my understanding is that NVIDIA has made 01:11:34.560 --> 01:11:38.560 some progress on being more friendly for Linux 01:11:38.560 --> 01:11:42.560 however 01:11:42.560 --> 01:11:46.560 however 01:11:46.560 --> 01:11:50.560 valve specifically supports 01:11:50.560 --> 01:11:54.560 AMD to a greater degree than they do NVIDIA 01:11:54.560 --> 01:11:58.560 so what is going on here does this only 01:11:58.560 --> 01:12:02.560 have a power switch oh so it 01:12:02.560 --> 01:12:06.560 does okay cool well that makes plugging this in a relatively 01:12:06.560 --> 01:12:10.560 simple affair okay cool that's there 01:12:10.560 --> 01:12:14.560 so because valve only builds in native support for AMD cards 01:12:14.560 --> 01:12:18.560 they strongly recommend if you go look at the requirements on 01:12:18.560 --> 01:12:22.560 their site for the steam OS image they strongly recommend that if you want to 01:12:22.560 --> 01:12:26.560 run it on a desktop you configure that desktop to be as similar 01:12:26.560 --> 01:12:30.560 to a steam deck as possible for the best 01:12:30.560 --> 01:12:34.560 compatibility and stability experience 01:12:34.560 --> 01:12:38.560 and I would recommend whatever valve recommends when it comes to running 01:12:38.560 --> 01:12:42.560 their operating system because yes it's under the hood 01:12:42.560 --> 01:12:46.560 just Arch Linux but it also isn't arch is highly 01:12:46.560 --> 01:12:50.560 customizable and can be 01:12:50.560 --> 01:12:54.560 very temperamental if not configured expertly 01:12:54.560 --> 01:12:58.560 which is exactly what we are counting on valve to do that's what makes 01:12:58.560 --> 01:13:02.560 it steam OS is all the work that they've put into 01:13:02.560 --> 01:13:06.560 building out features and support and 01:13:06.560 --> 01:13:10.560 making sure that it all works together seamlessly 01:13:10.560 --> 01:13:14.560 alright this can go and I think we're ready to talk about our GPU 01:13:14.560 --> 01:13:18.560 this is the last big 01:13:18.560 --> 01:13:22.560 ASUS featured piece it is their RTX 5080 01:13:22.560 --> 01:13:26.560 ROG Astral and 01:13:26.560 --> 01:13:30.560 5080s look like they might be where we end up for our 01:13:30.560 --> 01:13:34.560 editing stations regardless of whether we stick with an AMD platform 01:13:34.560 --> 01:13:38.560 or go crawling back to Intel 01:13:38.560 --> 01:13:42.560 there's a couple of things that I wanted to kind of run through first of all 01:13:42.560 --> 01:13:46.560 this is a two generation upgrade for us if you look back at both 01:13:46.560 --> 01:13:50.560 of our previous iterations there that's the 2021 edition with threadripper 01:13:50.560 --> 01:13:54.560 that's over on the right and then that's the upgrade that we did behind 01:13:54.560 --> 01:13:58.560 the scenes to Intel 13th gen over on the left there both 01:13:58.560 --> 01:14:02.560 of them are featuring 3090s so we're going all the way 01:14:02.560 --> 01:14:06.560 to Ampere to Blackwell skipping over Ada Lovelace or Ada 01:14:06.560 --> 01:14:10.560 I think they ended up calling it so that's going to 01:14:10.560 --> 01:14:14.560 give us not only additional performance but with these 50 series 01:14:14.560 --> 01:14:18.560 oh my goodness this thing is 01:14:18.560 --> 01:14:22.560 huge 01:14:22.560 --> 01:14:26.560 there we go 01:14:26.560 --> 01:14:30.560 with the 50 series that's going to give us their brand new media engine 01:14:30.560 --> 01:14:34.560 which I am personally extremely excited for 01:14:34.560 --> 01:14:38.560 do we have any notes about that in here? No but it can do 422 01:14:38.560 --> 01:14:42.560 HBBC encoding and decoding 01:14:42.560 --> 01:14:46.560 so much higher quality encoding is the main thing that I care about 01:14:46.560 --> 01:14:50.560 and that's going to come down to software support whether we can utilize it 01:14:50.560 --> 01:14:54.560 at all but if we're building new stations today 01:14:54.560 --> 01:14:58.560 especially with the way that performance 01:14:58.560 --> 01:15:02.560 40 series isn't really any cheaper then this seems 01:15:02.560 --> 01:15:06.560 like the sweet spot for us with that said that I'll kind of realize 01:15:06.560 --> 01:15:10.560 on getting these things for something resembling MSRP which 01:15:10.560 --> 01:15:14.560 has not been a thing yet but that's okay we can be patient 01:15:14.560 --> 01:15:18.560 anyway this has an overclocked mode up to 2790MHz engine clock 01:15:18.560 --> 01:15:22.560 16 gigs of GDDR7 memory we don't really do any 01:15:22.560 --> 01:15:26.560 AI stuff on our editing workstations so we don't really need the extra VRAM of their 01:15:26.560 --> 01:15:30.560 top tier 1590 and ASUS claims that their quad fan 01:15:30.560 --> 01:15:34.560 design boosts their flow and pressure by up to 20% they've also got their 01:15:34.560 --> 01:15:38.560 patented vapor chamber with milled heat spreader for lower GPU 01:15:38.560 --> 01:15:42.560 temperatures and their phase change GPU thermal pad along with 01:15:42.560 --> 01:15:46.560 powerful 50 amp MOSFETs to help enhance performance, stability 01:15:46.560 --> 01:15:50.560 and higher overclocking potential we won't be overclocking any of our workstations 01:15:50.560 --> 01:15:54.560 or anything like that but I have heard through the grapevine 01:15:54.560 --> 01:15:58.560 that these 5080s are absolutely monster overclockers 01:15:58.560 --> 01:16:02.560 they also have a protective PCB coating that can guard against 01:16:02.560 --> 01:16:06.560 moisture apparently so if you work in a like obviously don't 01:16:06.560 --> 01:16:10.560 like throw it in the pool or whatever but if you work in an extremely humid 01:16:10.560 --> 01:16:14.560 environment that can be a legitimate concern it can also help with dust and 01:16:14.560 --> 01:16:18.560 extreme temperatures apparently and whoop I just 01:16:18.560 --> 01:16:22.560 mushed my cable oh boy what that crap 01:16:22.560 --> 01:16:26.560 look at this bloody thing it makes even a 3090 01:16:26.560 --> 01:16:30.560 look kind of like comical you know like that's 01:16:30.560 --> 01:16:34.560 two 3090s back there because that we were using that for some kind of 01:16:34.560 --> 01:16:38.560 AI something or other that was that's the one from the color booth I think 01:16:38.560 --> 01:16:42.560 look at this thing it's one card 01:16:42.560 --> 01:16:46.560 anyway their GPU tweak 3 softwares included for 01:16:46.560 --> 01:16:50.560 performance tweaking advanced thermal controls and system monitoring let's go ahead and get this plugged in 01:16:50.560 --> 01:16:54.560 David are we ready to run this thing I think we are all right Dan do you want to hit me 01:16:54.560 --> 01:16:58.560 with a couple merge messages while we get this all kind of get a monitor on the desk 01:16:58.560 --> 01:17:02.560 and get this all set up absolutely all right good stuff 01:17:02.560 --> 01:17:06.560 Linus you and your team are super awesome sauce loved all the LMG channels 01:17:06.560 --> 01:17:10.560 since the day I found them thank you excited for my bag pen 01:17:10.560 --> 01:17:14.560 and precision screwdriver that's not a question 01:17:14.560 --> 01:17:18.560 but that was just super nice oh that is super nice as a micron 01:17:18.560 --> 01:17:22.560 I love seeing the crucial storage Linus how do you go about deciding 01:17:22.560 --> 01:17:26.560 how to hire engineers for Labs and CW how did you 01:17:26.560 --> 01:17:30.560 know what qualifications you needed that is an excellent question 01:17:30.560 --> 01:17:34.560 one that would probably be best met handled by 01:17:34.560 --> 01:17:38.560 the people who do hiring for us these days truthfully speaking 01:17:38.560 --> 01:17:42.560 I am not really involved in the hiring process anymore 01:17:42.560 --> 01:17:46.560 I can tell you that we don't necessarily you know require 01:17:46.560 --> 01:17:50.560 someone to have their PNG so their like official engineering 01:17:50.560 --> 01:17:54.560 certification in fact I don't 01:17:54.560 --> 01:17:58.560 think anyone on the CW team has technically 01:17:58.560 --> 01:18:02.560 completed it even though the reason for it is 01:18:02.560 --> 01:18:06.560 not necessarily because they're like not good enough or whatever 01:18:06.560 --> 01:18:10.560 like one of them I'm gonna I'm gonna mangle the details 01:18:10.560 --> 01:18:14.560 on this but it's something along these lines but one of them 01:18:14.560 --> 01:18:18.560 basically was on the brink of doing it but then their mentor 01:18:18.560 --> 01:18:22.560 or like their proctor or whatever I don't 01:18:22.560 --> 01:18:26.560 remember what the term is for it but their mentor person died 01:18:26.560 --> 01:18:30.560 and then for them to do it after that 01:18:30.560 --> 01:18:34.560 would require them to like redo 01:18:34.560 --> 01:18:38.560 something and they were just like well I'm working already 01:18:38.560 --> 01:18:42.560 like forget it 01:18:42.560 --> 01:18:46.560 so just because they don't necessarily 01:18:46.560 --> 01:18:50.560 have the credentials doesn't mean that they don't have the skills 01:18:50.560 --> 01:18:54.560 I will say that we definitely care a lot 01:18:54.560 --> 01:18:58.560 about hiring for attitude and for willingness to 01:18:58.560 --> 01:19:02.560 learn because knowledge can be taught but 01:19:02.560 --> 01:19:06.560 a natural curiosity and a willingness to learn new things can't 01:19:06.560 --> 01:19:10.560 I think like a great example of that is actually walking around 01:19:10.560 --> 01:19:14.560 over there like David started here as a camera guy 01:19:14.560 --> 01:19:18.560 slash editor found that he really didn't enjoy the editing part of it 01:19:18.560 --> 01:19:22.560 transition to camera guy 01:19:22.560 --> 01:19:26.560 editing is awful even though 01:19:26.560 --> 01:19:30.560 even though frankly his camera skills when he started 01:19:30.560 --> 01:19:34.560 were a little rough around the edges sometimes but that was when he started 01:19:34.560 --> 01:19:38.560 he got way better at it he has a great attitude and now 01:19:38.560 --> 01:19:42.560 he's gone from first he started on the writing team as a junior writer 01:19:42.560 --> 01:19:46.560 now he's a full writer and has just taken 01:19:46.560 --> 01:19:50.560 that passion and that willingness to learn 01:19:50.560 --> 01:19:54.560 and made this place go from like a McJob doing something he hated 01:19:54.560 --> 01:19:58.560 editing to I think he's having a lot more fun these days 01:19:58.560 --> 01:20:02.560 I think so yeah so I don't know so that's 01:20:02.560 --> 01:20:06.560 what's really important is prioritizing attitude and willingness 01:20:06.560 --> 01:20:10.560 to learn because like yeah you could I think you could be stuck in a 01:20:10.560 --> 01:20:14.560 dead-end position at a job and you could go oh my company is not doing 01:20:14.560 --> 01:20:18.560 enough to provide career advancement or change opportunities 01:20:18.560 --> 01:20:22.560 for me or you can you know just 01:20:22.560 --> 01:20:26.560 get in there and contribute and learn 01:20:26.560 --> 01:20:30.560 and find new things to do I don't know 01:20:30.560 --> 01:20:34.560 I personally have been having a lot of fun working on David's projects 01:20:34.560 --> 01:20:38.560 which to me is always a strong indicator that 01:20:38.560 --> 01:20:42.560 we're having fun creating them overall because I tell the team 01:20:42.560 --> 01:20:46.560 this like all the time this is on our like laws of 01:20:46.560 --> 01:20:50.560 making good videos have fun because the audience's 01:20:50.560 --> 01:20:54.560 bullshit detector is like finely tuned and if you're faking it 01:20:54.560 --> 01:20:58.560 if you're pretending that you're having fun they pick up on that immediately 01:20:58.560 --> 01:21:02.560 and they're not having fun and then no one's having fun and why are we even here 01:21:02.560 --> 01:21:06.560 right and it's like yeah we could be here just to get raw 01:21:06.560 --> 01:21:10.560 dry information like from our 5080 review 01:21:10.560 --> 01:21:14.560 we found that the Davidchi Puget Bench results 01:21:14.560 --> 01:21:18.560 were about 25% better than our old systems 01:21:18.560 --> 01:21:22.560 with the 3090 and we found that our 01:21:22.560 --> 01:21:26.560 Premiere Puget Bench results were about 22% better 01:21:26.560 --> 01:21:30.560 compared to our old 3090 01:21:30.560 --> 01:21:34.560 really useful valuable information but if we don't make it fun 01:21:34.560 --> 01:21:38.560 then we're not making it accessible to as many people so that's really 01:21:38.560 --> 01:21:42.560 important to us oh another thing I'm supposed to do while David finishes 01:21:42.560 --> 01:21:46.560 that off is I'm supposed to change into 01:21:46.560 --> 01:21:50.560 our featured shirt for today 01:21:50.560 --> 01:21:54.560 this right here is our sport button up shirt because 01:21:54.560 --> 01:21:58.560 we are serious business people now we're no longer 01:21:58.560 --> 01:22:02.560 our early 20s you know creating a tech channel 01:22:02.560 --> 01:22:06.560 and you know whatever now we're expected to kind of look somewhat 01:22:06.560 --> 01:22:10.560 decent and this is a great way to do it I think 01:22:10.560 --> 01:22:14.560 oh I'm sorry I'm probably mangling the audio I think this is part of our 9-5 lineup 01:22:14.560 --> 01:22:18.560 I actually can't remember but basically it looks 01:22:18.560 --> 01:22:22.560 like a professional button up shirt see 01:22:22.560 --> 01:22:26.560 looks all professional but it's like super comfy 01:22:26.560 --> 01:22:30.560 so it's like really stretchy see that it's like crazy 01:22:30.560 --> 01:22:34.560 stretchy it's also nice and breathable 01:22:34.560 --> 01:22:38.560 and is like wicking and stuff so you can 01:22:38.560 --> 01:22:42.560 be a sweaty boy and be doing real work in this thing and still 01:22:42.560 --> 01:22:46.560 be reasonably comfortable so yeah there you go lttstore.com 01:22:46.560 --> 01:22:50.560 uh David do you need any help now that I am 01:22:50.560 --> 01:22:54.560 doing all the stuff I'm supposed to oh okay there should be some grabbing goes in 01:22:54.560 --> 01:22:58.560 there's two as well right usually I have one set maybe 01:22:58.560 --> 01:23:02.560 I don't know if there's a dongle for it nope the dongle for this mice is missing 01:23:02.560 --> 01:23:06.560 I can't even really get mad at people about that 01:23:06.560 --> 01:23:10.560 because that is anyone about it 01:23:10.560 --> 01:23:14.560 do you have enough grab and go no for the whole class 01:23:14.560 --> 01:23:18.560 wait oh really yeah there might be some over here 01:23:18.560 --> 01:23:22.560 okay well hey here's a little bit of inside baseball for you guys 01:23:22.560 --> 01:23:26.560 we are supposed to have grab and go 01:23:26.560 --> 01:23:30.560 keyboards, mice, power supplies, microphones 01:23:30.560 --> 01:23:34.560 uh wait what is he talking about there's total 01:23:34.560 --> 01:23:38.560 uh David there's totally grab and go keyboards 01:23:38.560 --> 01:23:42.560 here what's that there's so many grab and go keyboards here 01:23:42.560 --> 01:23:46.560 there's no mice though yeah there's mice 01:23:46.560 --> 01:23:50.560 I don't like those oh you don't like 01:23:50.560 --> 01:23:54.560 these mice I just uh I knew that there was a couple 01:23:54.560 --> 01:23:58.560 that had been moved okay 01:23:58.560 --> 01:24:02.560 alright that makes way more sense then 01:24:02.560 --> 01:24:06.560 so funny 01:24:06.560 --> 01:24:10.560 I very regularly get called 01:24:10.560 --> 01:24:14.560 well he's got two keyboards too I very regularly get called sort of like out of 01:24:14.560 --> 01:24:18.560 touch because I have enough money that realistically 01:24:18.560 --> 01:24:22.560 I can afford any keyboard I want and any GPU I want and all of that 01:24:22.560 --> 01:24:26.560 but the biggest divas we have here 01:24:26.560 --> 01:24:30.560 are not me like I regularly have to bring Ploof back down to earth 01:24:30.560 --> 01:24:34.560 in terms of what normal people expect from a monitor and what 01:24:34.560 --> 01:24:38.560 normal people are willing to spend on a monitor and stuff like that 01:24:38.560 --> 01:24:42.560 and like I am willing to use not all 01:24:42.560 --> 01:24:46.560 not any mouse but like almost any mouse on set but you'll have 01:24:46.560 --> 01:24:50.560 people like David that are just like oh I was being silly these are my stuff were you 01:24:50.560 --> 01:24:54.560 oh alright okay nevermind 01:24:54.560 --> 01:24:58.560 still I think you I think you care a fair bit about your stuff I do 01:24:58.560 --> 01:25:02.560 I mean if you've seen his garage you know 01:25:02.560 --> 01:25:06.560 you know buddy's a gamer no yeah no yeah sure 01:25:06.560 --> 01:25:10.560 sure we're missing one Ethan do we really only have one cable 01:25:10.560 --> 01:25:14.560 um no there's a blue one right there you can just plug 01:25:14.560 --> 01:25:18.560 that in anywhere on the switch and then we're good to go uh Dan you want to hit me with a merge message 01:25:18.560 --> 01:25:22.560 oh in case you guys are wondering what the heck we're setting up uh this is a drag race 01:25:22.560 --> 01:25:26.560 between the new machine and the less 01:25:26.560 --> 01:25:30.560 new machine uh let's see oh let's see 01:25:30.560 --> 01:25:34.560 if she fires up I do 01:25:34.560 --> 01:25:38.560 and oh no guys I did it 01:25:38.560 --> 01:25:42.560 I whammyed us I put the side panels on 01:25:42.560 --> 01:25:46.560 there is there is no chance 01:25:46.560 --> 01:25:50.560 that this just fires up on the first try I don't know it's got 01:25:50.560 --> 01:25:54.560 aces components in it it might be perfect well no it doesn't matter 01:25:54.560 --> 01:25:58.560 the four sticks of RAM might it doesn't matter when you close the side panel 01:25:58.560 --> 01:26:02.560 there is literally no chance 01:26:02.560 --> 01:26:06.560 no chance that it will fire up the first time without issue editors are cursed 01:26:06.560 --> 01:26:10.560 do you want a merge message while we wait for it to fail yeah sure I'm checking 01:26:10.560 --> 01:26:14.560 by my first LTT product I really hope the quality matches the 01:26:14.560 --> 01:26:18.560 expectations also question in the scribe driver negative reviews 01:26:18.560 --> 01:26:22.560 I heard some people complaining about the clicking sound is it 01:26:22.560 --> 01:26:26.560 still an issue still an issue clicking sound on the scribe driver 01:26:26.560 --> 01:26:30.560 I don't think I have a scribe driver on me does anybody have a scribe driver around 01:26:30.560 --> 01:26:34.560 I don't have one mine is it my desk there's one on 01:26:34.560 --> 01:26:38.560 uh that's not gonna help us much it's kind of far 01:26:38.560 --> 01:26:42.560 away from you in 20 minutes do I have a 01:26:42.560 --> 01:26:46.560 where's the little I thought the scribe driver was supposed to click 01:26:46.560 --> 01:26:50.560 yeah no it definitely is supposed to you know make a satisfying 01:26:50.560 --> 01:26:54.560 noise let me see if I can just steal one from someone's desk I'll be back 01:26:54.560 --> 01:26:58.560 David will host for now 01:26:58.560 --> 01:27:02.560 the uh does anyone have a scribe driver the configuration is very challenging so the memory 01:27:02.560 --> 01:27:06.560 very long time it's gonna take a while to try anyway 01:27:06.560 --> 01:27:10.560 yeah um but this capacity is very very high 01:27:10.560 --> 01:27:14.560 when I was testing it before we got 128 gigs working yeah we did not 01:27:14.560 --> 01:27:18.560 succeed at getting 256 well I've done um I've done streams with the Linus before 01:27:18.560 --> 01:27:22.560 and he's freaking out because he thinks the computer is broken and it's just taking a long time 01:27:22.560 --> 01:27:26.560 to train for the first time so just give it extra extra time 01:27:26.560 --> 01:27:30.560 yeah even when we I did it with the or the person doing it did it with 01:27:30.560 --> 01:27:34.560 one stick it took three four minutes so let's uh 01:27:34.560 --> 01:27:38.560 I'm here to entertain 01:27:38.560 --> 01:27:42.560 business team will almost certainly have one I sure hope so 01:27:42.560 --> 01:27:46.560 uh it looks like I've got Windows on the other one so that's working okay fantastic 01:27:46.560 --> 01:27:50.560 that is our old system um it's funny 01:27:50.560 --> 01:27:54.560 we were originally gonna do the thumbnail where we put the two computers side by side but they're gonna look 01:27:54.560 --> 01:27:58.560 so similar it's the same case same cooler so just the gp would be 01:27:58.560 --> 01:28:02.560 different and then a thumbnail uh that would really be 01:28:02.560 --> 01:28:06.560 unimpressive you know that's not what we go for we go for 01:28:06.560 --> 01:28:10.560 uh blowing you away you know what I'm saying 01:28:10.560 --> 01:28:14.560 oh found one listen I click so it's like it's a bolt action pen 01:28:14.560 --> 01:28:18.560 so there's not really a click when you slide it into place 01:28:18.560 --> 01:28:22.560 but there's a bit of a snap 01:28:22.560 --> 01:28:26.560 from the spring when you rock it back so 01:28:26.560 --> 01:28:30.560 yep that's that's how it's supposed to work uh 01:28:30.560 --> 01:28:34.560 who's destiny I take this from well we'll take it out later 01:28:34.560 --> 01:28:38.560 in the meantime try to time to probably shoot this pc should we let it memory train longer do you think 01:28:38.560 --> 01:28:42.560 I think it should memory train for longer you want to let it keep memory training is that what it's doing is that what 01:28:42.560 --> 01:28:46.560 code 15 is it's a memory thing yeah oh boy 01:28:46.560 --> 01:28:50.560 so that's the thing right AMD platforms can take 01:28:50.560 --> 01:28:54.560 a minute to memory train and the more you have and the more 01:28:54.560 --> 01:28:58.560 ridiculous your configuration the longer you can expect to wait 01:28:58.560 --> 01:29:02.560 Jesus code 15 for people that don't know when he says a minute 01:29:02.560 --> 01:29:06.560 he means that metaphorically and it could be like 20 minutes it's like the 01:29:06.560 --> 01:29:10.560 it's a concerning amount of time and then it's fine yeah 01:29:10.560 --> 01:29:14.560 Q code 15 okay yes it's definitely 01:29:14.560 --> 01:29:18.560 definitely memory related if the memory 01:29:18.560 --> 01:29:22.560 worked fine on another board it was probably okay all right well 01:29:22.560 --> 01:29:26.560 yeah one hit me with another merge message sure yeah I've got a few here 01:29:26.560 --> 01:29:30.560 um let's see hey Linus Dan and David 01:29:30.560 --> 01:29:34.560 as what what did he say I said yo 01:29:34.560 --> 01:29:38.560 oh I thought Linus was freaking out about the computer 01:29:38.560 --> 01:29:42.560 as someone who finds himself screaming at Windows at work regularly 01:29:42.560 --> 01:29:46.560 I'm curious what do you all do when things aren't going your way do research take a break 01:29:46.560 --> 01:29:50.560 cry 01:29:50.560 --> 01:29:54.560 yeah first get really frustrated then I mean the next thing 01:29:54.560 --> 01:29:58.560 is like a Google search unless I you know have already encountered it 01:29:58.560 --> 01:30:02.560 before a lot of the time when I encounter a tech issue it's I've seen something like it 01:30:02.560 --> 01:30:06.560 at some point in the past so I will have like at least a starting point 01:30:06.560 --> 01:30:10.560 but I mean for example right now you know my system just like randomly closes 01:30:10.560 --> 01:30:14.560 Chrome every once in a while has that happened in the script review with you no oh yeah it just happens 01:30:14.560 --> 01:30:18.560 sometimes just Chrome just like shuts down it just shuts down 01:30:18.560 --> 01:30:22.560 um also occasionally I'll come into the office and it doesn't 01:30:22.560 --> 01:30:26.560 wake up from sleep anymore it has some serious issues and I think they're 01:30:26.560 --> 01:30:30.560 related to probably the IMC on my CPU 01:30:30.560 --> 01:30:34.560 because that's something I've learned over the years is if something is completely 01:30:34.560 --> 01:30:38.560 inexplicable then it's the power supply or RAM 01:30:38.560 --> 01:30:42.560 if nothing makes sense or it's 01:30:42.560 --> 01:30:46.560 intermittent power supply or RAM 01:30:46.560 --> 01:30:50.560 already done a fresh Windows install because it could also definitely be Windows 01:30:50.560 --> 01:30:54.560 research go find a guide 01:30:54.560 --> 01:30:58.560 I mean we have we have the you know 01:30:58.560 --> 01:31:02.560 whatever wonder of the world that is YouTube available to us 01:31:02.560 --> 01:31:06.560 you can do just about anything there until they pull the video down about how to 01:31:06.560 --> 01:31:10.560 de-google your life I'm a big believer in stepping away for 10 minutes 01:31:10.560 --> 01:31:14.560 and then just hoping it fixes itself and coming back and sometimes it does 01:31:14.560 --> 01:31:18.560 oh dude and and if it doesn't then it can also 01:31:18.560 --> 01:31:22.560 fix your mind the number of times that I've been stumped on like a word scapes 01:31:22.560 --> 01:31:26.560 puzzle for like 10 minutes and then just put it away and come back to it the next day 01:31:26.560 --> 01:31:30.560 and solved it like instantly it's wild what a what a fresh 01:31:30.560 --> 01:31:34.560 perspective will do for you oh yeah when you're like facing a boss in a video game and you can't 01:31:34.560 --> 01:31:38.560 be like this is impossible and then you go away and first try it when you come back 01:31:38.560 --> 01:31:42.560 my son is seven 01:31:42.560 --> 01:31:46.560 getting really curious about circuits and computers and how they work cool 01:31:46.560 --> 01:31:50.560 any ideas for how to get him engaged or excited 01:31:50.560 --> 01:31:54.560 my best idea now is rebuilding an old beater off of craigslist 01:31:54.560 --> 01:31:58.560 I mean it depends how interested they are in like like actual 01:31:58.560 --> 01:32:02.560 circuits and stuff versus just building computers 01:32:02.560 --> 01:32:06.560 but there was this this kit that we picked up a while back 01:32:06.560 --> 01:32:10.560 that was pretty cool is less electronics and more 01:32:10.560 --> 01:32:14.560 electricity let me see if I can find the one 01:32:14.560 --> 01:32:18.560 snap circuits is that the one 01:32:18.560 --> 01:32:22.560 oh yes here's your CAPTCHA 01:32:22.560 --> 01:32:26.560 just to go to amazon.ca really yeah snap circuits 01:32:26.560 --> 01:32:30.560 it's pretty cool so it comes with a book and it comes 01:32:30.560 --> 01:32:34.560 with like a bunch of different stuff like there's a fan and there's a light and there's 01:32:34.560 --> 01:32:38.560 little resistor boards and stuff like that 01:32:38.560 --> 01:32:42.560 and it basically has like a project book that it comes with 01:32:42.560 --> 01:32:46.560 and you use these snapping pieces to build a whole 01:32:46.560 --> 01:32:50.560 bunch of different projects so they'll learn about DC electricity 01:32:50.560 --> 01:32:54.560 and switches and the different functions of all the 01:32:54.560 --> 01:32:58.560 different little modules pretty cool my son played around 01:32:58.560 --> 01:33:02.560 with it a fair bit actually when he was younger and then got bored of it 01:33:02.560 --> 01:33:06.560 as kids are apt to do but yeah definitely seems pretty cool are we going to call that 01:33:06.560 --> 01:33:10.560 a bit for memory training? I think so I think we should go to 2.6 01:33:10.560 --> 01:33:14.560 yeah so we ran into this when we were preparing for this build 01:33:14.560 --> 01:33:18.560 we did not actually manage to get all four sticks running so 01:33:18.560 --> 01:33:22.560 your mileage may vary on that but apparently a Seuss and Kingston 01:33:22.560 --> 01:33:26.560 are working on getting 256 gigs of RAM working 01:33:26.560 --> 01:33:30.560 on these cu dims in bypass mode as it is 01:33:30.560 --> 01:33:34.560 even getting just 128 gigs working at the speed 01:33:34.560 --> 01:33:38.560 that we were able to get it working at is pretty cool so I think we got 01:33:38.560 --> 01:33:42.560 5600 or 5200? We actually with the 128 we're getting above 01:33:42.560 --> 01:33:46.560 6000. Really? They claim 256 at 5600. Okay got it 01:33:46.560 --> 01:33:50.560 so let's go ahead and shut this bad boy down 01:33:50.560 --> 01:33:54.560 your mileage may vary though 01:33:54.560 --> 01:33:58.560 I mean compared to the old system 01:33:58.560 --> 01:34:02.560 of 120 gigs which was set at 4000 megatransfers per second 01:34:02.560 --> 01:34:06.560 even 5600 would be a huge upgrade 01:34:06.560 --> 01:34:10.560 although in editing the capacity is more important than the speed 01:34:10.560 --> 01:34:14.560 certainly for after effects it's like 100% just everything's 01:34:14.560 --> 01:34:18.560 done to RAM. Oh boy 01:34:18.560 --> 01:34:22.560 I didn't like that sound. Okay 01:34:22.560 --> 01:34:26.560 she's in there. I'm going to need to get her out of there. Oh there we go 01:34:26.560 --> 01:34:30.560 that'll work. There's one of the sticks 01:34:30.560 --> 01:34:34.560 on the front stick. Alright. Yeah high 01:34:34.560 --> 01:34:38.560 capacity memory compatibility on AMD is a big challenge. Do we need a sag bracket for that card? 01:34:38.560 --> 01:34:42.560 Does it come with one? No I don't think so 01:34:42.560 --> 01:34:46.560 She's heavy. She's heavy. She's saggy 01:34:46.560 --> 01:34:50.560 DIY something beautiful. She's saggy. Nah she's okay 01:34:50.560 --> 01:34:54.560 it's not going to break it. Is it a second one? No 01:34:54.560 --> 01:34:58.560 no no no that'll be okay. Yeah that's right you need two. She's alright. 01:34:58.560 --> 01:35:02.560 That is not a reason to buy multiple 01:35:02.560 --> 01:35:06.560 precision screwdriver sets. I think we should put that on the sales page 01:35:06.560 --> 01:35:10.560 where it says an excellent sag bracket for your stupidly large GPU. 01:35:10.560 --> 01:35:14.560 Buy a three pack. Okay we're still stuck 01:35:14.560 --> 01:35:18.560 on 15 but this time it could just be training. I wonder 01:35:18.560 --> 01:35:22.560 if that other time it was, I wonder if it was training stuff. 01:35:22.560 --> 01:35:26.560 I told you. Did we try leaving it for like half an hour? 01:35:26.560 --> 01:35:30.560 We didn't have time. We were in such a rush this morning. Oh because Jake has told me 01:35:30.560 --> 01:35:34.560 that he has seen it in the past with these AMD systems where he will literally 01:35:34.560 --> 01:35:38.560 give up and like walk away and come back and memory training 01:35:38.560 --> 01:35:42.560 is complete. I told you it's a concerning length of time. 01:35:42.560 --> 01:35:46.560 So your mileage may vary. Hopefully this will 01:35:46.560 --> 01:35:50.560 train and be good in a reasonable amount of time but in the meantime Dan will kill some time with 01:35:50.560 --> 01:35:54.560 another merge message. Sure. Hi I'm planning on building a new 01:35:54.560 --> 01:35:58.560 PC and I was looking to use it for gaming slash productivity 01:35:58.560 --> 01:36:02.560 slash streaming. I was looking at getting the Ryzen 99D950X 01:36:02.560 --> 01:36:06.560 or should I wait for the X3D or go with the 9950X? 01:36:06.560 --> 01:36:10.560 If gaming is your primary consideration 01:36:10.560 --> 01:36:14.560 then it's hard not to justify the 01:36:14.560 --> 01:36:18.560 extra upcharge for the X3D versus the non X3D variant. 01:36:18.560 --> 01:36:22.560 But if realistically it's like a family computer 01:36:22.560 --> 01:36:26.560 slash like sort of workstation, you do a bunch of other stuff on it 01:36:26.560 --> 01:36:30.560 it's... 01:36:30.560 --> 01:36:34.560 I don't know that I would bother waiting. Like if you want a new computer then 01:36:34.560 --> 01:36:38.560 get a new computer. There's always always something around the corner 01:36:38.560 --> 01:36:42.560 and what we have found is that particularly if you're gaming at higher resolutions 01:36:42.560 --> 01:36:46.560 like even 1440p 01:36:46.560 --> 01:36:50.560 if you have a modern CPU it's not going to be your bottleneck anyway. 01:36:50.560 --> 01:36:54.560 So it kind of is what it is. 01:36:54.560 --> 01:36:58.560 And the thing is you're buying into AM5 which AMD has still committed 01:36:58.560 --> 01:37:02.560 to supporting until I think 2027. So you will have 01:37:02.560 --> 01:37:06.560 future upgrade options available to you. So you could always 01:37:06.560 --> 01:37:10.560 maybe throw an X3D in later once they come down in price and you just kind of 01:37:10.560 --> 01:37:14.560 flip your 9950 or whatever the case may be. 01:37:14.560 --> 01:37:18.560 This is still not to... 01:37:18.560 --> 01:37:22.560 4 plus minutes for one stick. So it takes... 01:37:22.560 --> 01:37:26.560 Why don't you tell us about the old system that we're going to be upgrading from? 01:37:26.560 --> 01:37:30.560 Sure, I could do that. So this is the 01:37:30.560 --> 01:37:34.560 old Intel based one. So we've got a 01:37:34.560 --> 01:37:38.560 1300K. This also has 128 gigs of memory 01:37:38.560 --> 01:37:42.560 but running at much lower speeds because we're populating all 4 memory slots. 01:37:42.560 --> 01:37:46.560 This particular system has dual 3090s because I believe 01:37:46.560 --> 01:37:50.560 it was used for some AI inferencing stuff 01:37:50.560 --> 01:37:54.560 in addition to being used as an editing station in one of the isolated 01:37:54.560 --> 01:37:58.560 booths. Same SSD, same 1TB crucial 01:37:58.560 --> 01:38:02.560 P5. We're using these pro-art motherboards not because they make any 01:38:02.560 --> 01:38:06.560 sense whatsoever at the price but because I think ASUS gave us 01:38:06.560 --> 01:38:10.560 like a sweetheart of a deal on them and I wouldn't say no to that. 01:38:10.560 --> 01:38:14.560 There's certainly nothing wrong with them. We're using CSONIC Prime power supplies 01:38:14.560 --> 01:38:18.560 good power supply but so is the ASUS. As long as you're 01:38:18.560 --> 01:38:22.560 using a good power supply I don't think that's going to have any kind of impact on performance 01:38:22.560 --> 01:38:26.560 or stability. CSONIC doesn't have a magnetic OLED though. Yeah, that's true. 01:38:26.560 --> 01:38:30.560 CSONIC does not have that. Way to go CSONIC. Get with the times. 01:38:30.560 --> 01:38:34.560 Alright Dan, hit me. 01:38:34.560 --> 01:38:38.560 Sure, sure, sure. 01:38:38.560 --> 01:38:42.560 Hey Linus, do you think the computer industry will outlast the games industry? 01:38:42.560 --> 01:38:46.560 I got a game design degree and we'll see how that's going 01:38:46.560 --> 01:38:50.560 so I'm going to law school. We're eating on some LSAT results. 01:38:50.560 --> 01:38:54.560 Everything is cyclical in both 01:38:54.560 --> 01:38:58.560 tech and gaming and those two cycles 01:38:58.560 --> 01:39:02.560 in those two industries do contribute to each other. 01:39:02.560 --> 01:39:06.560 They've both seen a 01:39:06.560 --> 01:39:10.560 major pullback. The tech industry one I kind of understand 01:39:10.560 --> 01:39:14.560 because things were reaching a point of somewhat 01:39:14.560 --> 01:39:18.560 ridiculousness for how hard the big tech giants were 01:39:18.560 --> 01:39:22.560 bidding for any employee, like literally anyone fresh out of 01:39:22.560 --> 01:39:26.560 school was just getting bombarded with job offers for a little while there 01:39:26.560 --> 01:39:30.560 to the point where it just kind of didn't 01:39:30.560 --> 01:39:34.560 seem to be sustainable forever. So I understand 01:39:34.560 --> 01:39:38.560 where the pullback is coming from there. I wish they weren't pulling back so hard 01:39:38.560 --> 01:39:42.560 because the impact on people who have spent 01:39:42.560 --> 01:39:46.560 years of their lives educating themselves to work in the 01:39:46.560 --> 01:39:50.560 tech industry or in some cases spent years of their lives working 01:39:50.560 --> 01:39:54.560 at these companies are just being summarily 01:39:54.560 --> 01:39:58.560 let go or being put 01:39:58.560 --> 01:40:02.560 in a position where they feel like they're being pushed to quit 01:40:02.560 --> 01:40:06.560 and that sucks. The games industry is one that I don't really get 01:40:06.560 --> 01:40:10.560 as much like yeah there was a big COVID boom and some 01:40:10.560 --> 01:40:14.560 studios overhired and ambitious projects were begun 01:40:14.560 --> 01:40:18.560 that maybe weren't going to pan out and so I can see a little bit of that happening but when you 01:40:18.560 --> 01:40:22.560 have some of these companies and David falls the games industry 01:40:22.560 --> 01:40:26.560 a little bit closer than I do but when you have some of these companies 01:40:26.560 --> 01:40:30.560 announcing a big layoff and then literally talking record profits 01:40:30.560 --> 01:40:34.560 like a week later it doesn't really track for me. I don't really 01:40:34.560 --> 01:40:38.560 understand it. I think there's multiple layers to the issue of how it happens 01:40:38.560 --> 01:40:42.560 I think that you know the chase for profits is one of it. I think part 01:40:42.560 --> 01:40:46.560 of it is we've seen the collapse of new live service games like new 01:40:46.560 --> 01:40:50.560 live service games rarely succeed and that for a little bit that was what the big investments 01:40:50.560 --> 01:40:54.560 were like Concord's the big one 200 plus million dollars 01:40:54.560 --> 01:40:58.560 just down the drain. Gone. How long was it live? Like a 01:40:58.560 --> 01:41:02.560 week? Two weeks? Something like that. Ten days or something. Yeah and then they just 01:41:02.560 --> 01:41:06.560 funded everyone and walked away from it. They might bring it back but who knows. 01:41:06.560 --> 01:41:10.560 But then you got to look at it and you got to go like okay so 01:41:10.560 --> 01:41:14.560 fine. The investments that we've made in live service games we're just not going to be able 01:41:14.560 --> 01:41:18.560 to topple Fortnite. We're not going to be able to 01:41:18.560 --> 01:41:22.560 we're not going to be able to draw that audience away from it 01:41:22.560 --> 01:41:26.560 but then from software Larry and 01:41:26.560 --> 01:41:30.560 have shown that there's a massive appetite for not 01:41:30.560 --> 01:41:34.560 live service games like so do we have to lay all these people off? 01:41:34.560 --> 01:41:38.560 Oh hey. That's a different code. Dude I wonder if we just 01:41:38.560 --> 01:41:42.560 didn't wait long enough. I told you. I don't know if I want to try 01:41:42.560 --> 01:41:46.560 on stream but I do want to say that it is very possible 01:41:46.560 --> 01:41:50.560 given how long this was hanging on 15 that this was just memory 01:41:50.560 --> 01:41:54.560 training before and it was 256 gigs of flipping memory and 01:41:54.560 --> 01:41:58.560 needed a hot minute to finish training. Okay well that's pretty cool 01:41:58.560 --> 01:42:02.560 anyway the point is like I feel like 01:42:02.560 --> 01:42:06.560 people could have been reassigned. I got something. I got something? 01:42:06.560 --> 01:42:10.560 On mine. It was on 96 for a bit. Yeah no I've got 01:42:10.560 --> 01:42:14.560 bias. Is this displaying? 01:42:14.560 --> 01:42:18.560 It's not getting signal. This is not plugged in. Oh it must have come unplugged. 01:42:18.560 --> 01:42:22.560 So there's your problem. Oh wait it is plugged in I lied. 01:42:22.560 --> 01:42:26.560 Yeah this one. Okay. It was working before 01:42:26.560 --> 01:42:30.560 Oh it's not the monitor seems to be the one that's having the issue. Oh no 01:42:30.560 --> 01:42:34.560 Let's give it a sec. I've got it on my side. 01:42:34.560 --> 01:42:38.560 Sick. We're close guys. We're close. Dan are you 01:42:38.560 --> 01:42:42.560 troubleshooting something or do you want to hit me with a... No I'm just waiting for this monitor. 01:42:42.560 --> 01:42:46.560 Hey let's go. Alright. You'll want to go into BIOS and 01:42:46.560 --> 01:42:50.560 make sure. I sure will. Oh we got to go test that AI assistant too. 01:42:50.560 --> 01:42:54.560 Oh that's right. Okay how does that work? 01:42:54.560 --> 01:42:58.560 Do you know anything about it? Nope. Alright tools maybe? 01:42:58.560 --> 01:43:02.560 Let me look it up. 01:43:02.560 --> 01:43:06.560 Well it's not in there. Q dashboard? Nope. 01:43:06.560 --> 01:43:10.560 Oh is that a walk diagram? That's cool. Oh wow. 01:43:10.560 --> 01:43:14.560 Not quite. It does give you the device ID though. That can be really useful if you're 01:43:14.560 --> 01:43:18.560 doing like pastor or whatever. I think you can look it up in Linux anyway but 01:43:18.560 --> 01:43:22.560 I don't know what's there. Okay full 01:43:22.560 --> 01:43:26.560 HD setup. Whoa you can have full HD in the setup screen? 01:43:26.560 --> 01:43:30.560 At any rate we already 01:43:30.560 --> 01:43:34.560 appear to have our memory profile 01:43:34.560 --> 01:43:38.560 enabled because it's already running at 5600. No we don't. 01:43:38.560 --> 01:43:42.560 Interesting. AEMP. 01:43:42.560 --> 01:43:46.560 Huh. We are not going to try to go 01:43:46.560 --> 01:43:50.560 all the way to 6800. Try it. No. That's not going to happen. 01:43:50.560 --> 01:43:54.560 We're going to go to, what was it? 5600 you guys got 01:43:54.560 --> 01:43:58.560 working or 6000? He got 64 working. 64? 01:43:58.560 --> 01:44:02.560 Yeah he was above 6000. Okay sure. 01:44:02.560 --> 01:44:06.560 No we could do 64. I think he said he got 68 but I'm not 100% sure on that. 01:44:06.560 --> 01:44:10.560 Okay you know what? Fine we're going to try it. I will be very surprised 01:44:10.560 --> 01:44:14.560 and also we might be, it's not always better to just 01:44:14.560 --> 01:44:18.560 go for pure frequency especially on AMD these days but what the heck. 01:44:18.560 --> 01:44:22.560 Let's give it a shot. Let's see if it happens. It won't have to fully retrain 01:44:22.560 --> 01:44:26.560 it should just reset and oh boy 01:44:26.560 --> 01:44:30.560 it stuck on 15 again. Cool Dan quick stall for time go go go. Yeah it's going to have to 01:44:30.560 --> 01:44:34.560 retrain. I'm considering upgrading my RAM from 01:44:34.560 --> 01:44:38.560 5600 megatransfers C36 to 6000 megatransfers 01:44:38.560 --> 01:44:42.560 C30. Just can't decide if the performance is 01:44:42.560 --> 01:44:46.560 worth it or if I should just keep waiting until the latencies get even tighter. 01:44:46.560 --> 01:44:50.560 I don't know how much tighter we're going to see 01:44:50.560 --> 01:44:54.560 DDR5 latencies and you're going to be limited not just by 01:44:54.560 --> 01:44:58.560 the memory that's available but also by the integrated memory controller on your CPU 01:44:58.560 --> 01:45:02.560 which understandably tends to be kind of 01:45:02.560 --> 01:45:06.560 targeting the memory that is available during the 01:45:06.560 --> 01:45:10.560 development of said CPU. As for whether you're 01:45:10.560 --> 01:45:14.560 going to notice a meaningful performance difference, you might see a little bit 01:45:14.560 --> 01:45:18.560 from that. Not enough to justify the full price of that 01:45:18.560 --> 01:45:22.560 new memory kit but if you sell your old memory kit get a decent price for 01:45:22.560 --> 01:45:26.560 it and you're only paying like another you know 30 bucks 40 bucks or something like that 01:45:26.560 --> 01:45:30.560 on top of what you were able to sell for and I'd say that that could be a worthwhile 01:45:30.560 --> 01:45:34.560 upgrade. So the AI thing is a desktop thing. Oh it's a desktop thing. 01:45:34.560 --> 01:45:38.560 I thought it was in the BIOS based on the marketing but it is a desktop thing. 01:45:38.560 --> 01:45:42.560 Right we'll get to that when we get to it then. We'll have to install it. Alright Dan hit 01:45:42.560 --> 01:45:46.560 me. Linus, what DIY projects are you working on 01:45:46.560 --> 01:45:50.560 apart from Lambo Bike? Thoughts on more DIY or maker content? 01:45:50.560 --> 01:45:54.560 I love the VPN video and would love to get more videos on 01:45:54.560 --> 01:45:58.560 Pine As or HexOS builds set up start to 01:45:58.560 --> 01:46:02.560 finish. Given I cannot finish that project 01:46:02.560 --> 01:46:06.560 do I need another project right now? I will 01:46:06.560 --> 01:46:10.560 say that I am learning about casting. I've always 01:46:10.560 --> 01:46:14.560 been kind of interested in it. I did a metal art and jewelry class back in high school 01:46:14.560 --> 01:46:18.560 and I had a ton of fun. I made like a cool chain out of 01:46:18.560 --> 01:46:22.560 just like silver wire and I what else did I make? I made a small 01:46:22.560 --> 01:46:26.560 cast pendant and I just I thought it was such 01:46:26.560 --> 01:46:30.560 a blast. So I'm reading this book called Practical 01:46:30.560 --> 01:46:34.560 Guide to Casting. I'm about halfway through and I just finished the part where 01:46:34.560 --> 01:46:38.560 it talks about sling casting. So to 01:46:38.560 --> 01:46:42.560 sling the metal into the investment that the 01:46:42.560 --> 01:46:46.560 mold is in there's multiple ways to do it. So you can use 01:46:46.560 --> 01:46:50.560 like a centrifugal thing where you like wind up a spring and then you let go and it 01:46:50.560 --> 01:46:54.560 spins and it flings the molten metal into the mold. 01:46:54.560 --> 01:46:58.560 You can do ones that are just like gravity 01:46:58.560 --> 01:47:02.560 gravity driven. So what you do is you just have like 01:47:02.560 --> 01:47:06.560 or sorry not gravity driven vacuum 01:47:06.560 --> 01:47:10.560 driven. So you have like a vacuum that you pull around the mold 01:47:10.560 --> 01:47:14.560 and it like sucks the metal into it. And I just got 01:47:14.560 --> 01:47:18.560 to the one about sling casting where basically 01:47:18.560 --> 01:47:22.560 what you do is you take your mold and then the gate 01:47:22.560 --> 01:47:26.560 at the top you make it narrow enough that the surface tension of the 01:47:26.560 --> 01:47:30.560 molten metal will keep it from going down 01:47:30.560 --> 01:47:34.560 so you can melt it all. You melt it all and then you put it in a sling 01:47:34.560 --> 01:47:38.560 and you basically like whip it around like this to drive the 01:47:38.560 --> 01:47:42.560 metal down through the gate into the mold and I'm like 01:47:42.560 --> 01:47:46.560 what? Cause that's pretty cool. So I 01:47:46.560 --> 01:47:50.560 want to learn about casting. 01:47:50.560 --> 01:47:54.560 ZOS015 says please finish the SV650S 01:47:54.560 --> 01:47:58.560 it's my old bike and I'd love to see it decked out. Yeah I know. And we want 01:47:58.560 --> 01:48:02.560 the beard back. I want the beard back too and I will do 01:48:02.560 --> 01:48:06.560 it as soon as I finish painting that stupid, stupid bike. I gave a 01:48:06.560 --> 01:48:10.560 progress update on Wancher a little while ago. I haven't touched it since then but 01:48:10.560 --> 01:48:14.560 most of the parts are white now which is the layer before 01:48:14.560 --> 01:48:18.560 pink which is the layer before effect layer which is the layer before 01:48:18.560 --> 01:48:22.560 clear coat. So yeah 01:48:22.560 --> 01:48:26.560 oh it's booted. Yeah. No way. Is this at 01:48:26.560 --> 01:48:30.560 6800 or did it reset? Yeah. 01:48:30.560 --> 01:48:34.560 Okay well that's pretty cool. 01:48:34.560 --> 01:48:38.560 We'll see how stable it is. Yeah. We are asking a lot. Yeah. 01:48:38.560 --> 01:48:42.560 Oh 1080p right? Yeah for captured. Yep that makes sense. 01:48:42.560 --> 01:48:46.560 And we need to, Dan's going to come over and connect this to the server so we can end up with a project. 01:48:46.560 --> 01:48:50.560 I have to do my job. Alright I don't have the merge message panel 01:48:50.560 --> 01:48:54.560 open so I'm going to hang out with Flowplain Chat for now. 01:48:54.560 --> 01:48:58.560 I am going to beat GTA 6. My bike will 01:48:58.560 --> 01:49:02.560 be done before GTA 6 launches. I promise you that. It's coming out this fall. 01:49:02.560 --> 01:49:06.560 What? It's coming out this fall. Shut up. Yeah. Get on it. 01:49:06.560 --> 01:49:10.560 They just told it to investors 01:49:10.560 --> 01:49:14.560 that it's still coming 2025. Okay. 01:49:14.560 --> 01:49:18.560 It's really tough because like it's actually really hard to paint with the tennis 01:49:18.560 --> 01:49:22.560 elbow. The gun and the hose 01:49:22.560 --> 01:49:26.560 and then the hopper and all the different angles and stuff. 01:49:26.560 --> 01:49:30.560 So I don't know if I've really talked about this much but I developed tennis elbow 01:49:30.560 --> 01:49:34.560 after that tournament I played late last year and we're now 01:49:34.560 --> 01:49:38.560 in February of this year and it is still causing a significant 01:49:38.560 --> 01:49:42.560 amount of pain. I haven't basically been able to play badminton 01:49:42.560 --> 01:49:46.560 since Smash Champs fully opened. I did play a little bit 01:49:46.560 --> 01:49:50.560 last night. I hit one smash last night and I'm not 01:49:50.560 --> 01:49:54.560 suffering today. Oh that's good. So I'm wondering if the physio's helping 01:49:54.560 --> 01:49:58.560 actually gave me this thing which like 01:49:58.560 --> 01:50:02.560 looks like some kind of medieval torture device or something 01:50:02.560 --> 01:50:06.560 and it honestly feels like one. Harder these. 01:50:06.560 --> 01:50:10.560 They're not that hard but what you do is you 01:50:10.560 --> 01:50:14.560 you sit like this because it's what I learned 01:50:14.560 --> 01:50:18.560 is that it's not actually the inflammation that is 01:50:18.560 --> 01:50:22.560 the problem of the tendon. That's not good 01:50:22.560 --> 01:50:26.560 these little micro tears are just a natural part of 01:50:26.560 --> 01:50:30.560 stretching out ligaments and building muscle and all that. So the 01:50:30.560 --> 01:50:34.560 micro tears are not what caused the inflammation in the pain. It's the micro tears 01:50:34.560 --> 01:50:38.560 combined with an overuse like a repetitive 01:50:38.560 --> 01:50:42.560 strain kind of overuse of the muscles on either side that are 01:50:42.560 --> 01:50:46.560 pulling it apart while you have all the micro tears 01:50:46.560 --> 01:50:50.560 and causing the inflammation and the swelling and the pain. 01:50:50.560 --> 01:50:54.560 So what you have to do when you use this thing is you 01:50:54.560 --> 01:50:58.560 what's this weird thing called? Roll flex 01:50:58.560 --> 01:51:02.560 not two L's. Roll flex not roll flex. 01:51:02.560 --> 01:51:06.560 Roll flex. So you kind of like 01:51:06.560 --> 01:51:10.560 you kind of clamp it with your other ARM and you kind of like 01:51:10.560 --> 01:51:14.560 get into the spot and you're like oh it hurts so much. 01:51:14.560 --> 01:51:18.560 But like the good hurts? No. No it hurts. Okay. For you it probably hurts 01:51:18.560 --> 01:51:22.560 because you're actually injured. And you're not supposed to do these the site of the injury 01:51:22.560 --> 01:51:26.560 so what you're supposed to do is you're supposed to like really work out the 01:51:26.560 --> 01:51:30.560 the tension that's pulling 01:51:30.560 --> 01:51:34.560 the injury site apart above and below it. 01:51:34.560 --> 01:51:38.560 You're supposed to like move the ARM around like especially down here 01:51:38.560 --> 01:51:42.560 and between this and just sort of getting a little bit better at 01:51:42.560 --> 01:51:46.560 identifying the right spots to do the massage. It's been 01:51:46.560 --> 01:51:50.560 helping a lot. I also did some physio. They did like ultrasound. And then they did 01:51:50.560 --> 01:51:54.560 the weird one where they hook up the electrodes to it. 01:51:54.560 --> 01:51:58.560 They did it a little bit too high one time. 01:51:58.560 --> 01:52:02.560 And like my hand got stuck like this. And I was like 01:52:02.560 --> 01:52:06.560 come on. Anyway. 01:52:06.560 --> 01:52:10.560 Oh hey! 01:52:10.560 --> 01:52:14.560 Oh okay. 01:52:14.560 --> 01:52:18.560 Let's see how it goes. Oh hi Mark. Hi how are you? Never better. 01:52:18.560 --> 01:52:22.560 Really? I think we might have to play which computer? That one. 01:52:22.560 --> 01:52:26.560 This is the new station. So we wanted to bring one of our editors out and the script 01:52:26.560 --> 01:52:30.560 says do something. Okay. 01:52:30.560 --> 01:52:34.560 We won't drag race the premiere between the two. Oh sure. 01:52:34.560 --> 01:52:38.560 So basically we want to get your, oh you can turn that on. We want to get your impression of if this 01:52:38.560 --> 01:52:42.560 would be, if we took your workstation away tomorrow and we gave you this 01:52:42.560 --> 01:52:46.560 would you be happy, sad or somewhere in between? Probably happy. 01:52:46.560 --> 01:52:50.560 Okay yeah. 01:52:50.560 --> 01:52:54.560 You're picking up the vibe now that I was talking about before. 01:52:54.560 --> 01:52:58.560 I'm lost. Oh where am I supposed to go? This PC. 01:52:58.560 --> 01:53:02.560 This PC? There we go. Ah there we go. 01:53:02.560 --> 01:53:06.560 Don't open the HR full day. We are live. 01:53:06.560 --> 01:53:10.560 Is he mic'd? He's mic'd. Oh brilliant. Wonderful. 01:53:10.560 --> 01:53:14.560 So what are your main complaints with the current stations? 01:53:14.560 --> 01:53:18.560 I'm going to switch spots with you. Okay Andy I'm going to kind of stack up on Mark here. 01:53:18.560 --> 01:53:22.560 The current ones are fine. It was 01:53:22.560 --> 01:53:26.560 actually the thread rippers that were the problem. The current ones the issue 01:53:26.560 --> 01:53:30.560 is there's not enough VRAM on the 3090s 01:53:30.560 --> 01:53:34.560 for like 01:53:34.560 --> 01:53:38.560 resolve. I feel like we need to upgrade the VRAM. 01:53:38.560 --> 01:53:42.560 Uh oh. No one told me that. 01:53:42.560 --> 01:53:46.560 They didn't tell me you needed more VRAM so these are 5080s. They have less VRAM. 01:53:46.560 --> 01:53:50.560 These are 5080s. Yeah this is a 5080. Less VRAM than the 01:53:50.560 --> 01:53:54.560 maybe it's just better VRAM I don't know. Okay well let's see. Let's see 01:53:54.560 --> 01:53:58.560 good lord. Well okay the good thing is 01:53:58.560 --> 01:54:02.560 we don't use a resolve very often. It's usually Premiere. Yeah but still. 01:54:02.560 --> 01:54:06.560 So I was told Quick Sync was causing stability issues though. Quick Sync? 01:54:06.560 --> 01:54:10.560 Or just the Intel ones had stability issues. So lots of editors that have been having 01:54:10.560 --> 01:54:14.560 daily problems. Oh yeah yeah okay yeah yeah I can see that might be the issue. 01:54:14.560 --> 01:54:18.560 I know that Threadripper was causing a lot more issues though that 01:54:18.560 --> 01:54:22.560 I don't even know what they were. Okay. Or what the what was causing it but 01:54:22.560 --> 01:54:26.560 so basically there's ghosts 01:54:26.560 --> 01:54:30.560 living in computers and if you anger the ghosts 01:54:30.560 --> 01:54:34.560 they will punish you and so Mark apparently doesn't 01:54:34.560 --> 01:54:38.560 use his Intel machine but we have gotten a lot of complaints from the other. I mean our editing 01:54:38.560 --> 01:54:42.560 team is almost a dozen people now I think. So even if 01:54:42.560 --> 01:54:46.560 you know 10% of systems have an issue 01:54:46.560 --> 01:54:50.560 that's one to two of our editors is going to have a problem with it right. 01:54:50.560 --> 01:54:54.560 During scrapyard wars. Oh yeah yeah. During scrapyard wars 01:54:54.560 --> 01:54:58.560 we would have late night editing sessions and it would delay us like an hour 01:54:58.560 --> 01:55:02.560 or two because it would just crash consistently and we'd have to reload just waiting 01:55:02.560 --> 01:55:06.560 and it was very frustrating. That was on the Intel systems. That was on the Intel ones. 01:55:06.560 --> 01:55:10.560 Hold on give me one second I'm just going to close that. 01:55:10.560 --> 01:55:14.560 Are you just like looking for your favorite project or? Yeah I'm looking for the one I'm working on right now. 01:55:14.560 --> 01:55:18.560 Oh okay cool. Gaming at 8k. On the 5090. Yeah. 01:55:18.560 --> 01:55:22.560 On the amount of VRAM you thought you were going to get in your new station. 01:55:22.560 --> 01:55:26.560 I was hopeful. I heard we were switching to 50 series. I just thought it was going to be 01:55:26.560 --> 01:55:30.560 equivalent 50 series. I was more interested 01:55:30.560 --> 01:55:34.560 in the better media encoder. I didn't realize you guys needed 01:55:34.560 --> 01:55:38.560 a ton of VRAM for Resolve. Are you going to click OK? Yeah. 01:55:38.560 --> 01:55:42.560 A lot of it I think is just Resolve optimization issues. 01:55:42.560 --> 01:55:46.560 Okay. Linus would you just 01:55:46.560 --> 01:55:50.560 open your shirt a bit? You're rubbing quite heavily. 01:55:50.560 --> 01:55:54.560 Sorry about that. Is that better? One more. One more. 01:55:54.560 --> 01:55:58.560 Seriously? I'm going full like 01:55:58.560 --> 01:56:02.560 Italian. Yeah there you go. Thank you. I don't know. 01:56:02.560 --> 01:56:06.560 I don't edit. Okay so Mark you have to come this way 01:56:06.560 --> 01:56:10.560 and then Andy goes over there and then no 01:56:10.560 --> 01:56:14.560 you still use the computer. No no but with your right hand. This is what happens 01:56:14.560 --> 01:56:18.560 when we let not on camera people. Oh like this. Just like that. 01:56:18.560 --> 01:56:22.560 And then I go right here. He's an on camera people now. It's good. 01:56:22.560 --> 01:56:26.560 And then when you talk to me you just kind of turn your head this way but don't bother looking at me it's fine. Got it. 01:56:26.560 --> 01:56:30.560 It'll look natural to them. 01:56:30.560 --> 01:56:34.560 Offline all. Okay cool. 01:56:34.560 --> 01:56:38.560 Alright here we are. 01:56:38.560 --> 01:56:42.560 Well you definitely offline all. Yeah well no it's pending. 01:56:42.560 --> 01:56:46.560 Multiple languages dude. Now are we 01:56:46.560 --> 01:56:50.560 at 10 gig Dan? No. Did we check? No because we have to install 01:56:50.560 --> 01:56:54.560 the driver specifically for that card. We did. 01:56:54.560 --> 01:56:58.560 Okay well it wouldn't. It wouldn't resolve. 01:56:58.560 --> 01:57:02.560 Maybe that's because I had it. It was in the wrong port on the switch. Okay one sec. 01:57:02.560 --> 01:57:06.560 So throw it back in there. Okay. 01:57:06.560 --> 01:57:10.560 See if that connects. Sorry Mark that's probably going to impact your 01:57:10.560 --> 01:57:14.560 ability to load that footage. 01:57:14.560 --> 01:57:18.560 What's happening? There you go. Well I unplugged your network. 01:57:18.560 --> 01:57:22.560 See if it's gotten an IP at least. Oh there it is. 01:57:22.560 --> 01:57:26.560 Oh yeah sorry. No it's not good. Yeah. 01:57:26.560 --> 01:57:30.560 I would strongly recommend against doing that while you're loading a project. 01:57:30.560 --> 01:57:34.560 That's not great. Not recommended. Oh did I? 01:57:34.560 --> 01:57:38.560 No no it's okay. Did I ruin everything? Yeah. 01:57:38.560 --> 01:57:42.560 Our editors are used to just the infrastructure collapsing 01:57:42.560 --> 01:57:46.560 in the middle of their editing. Used to happen all the time remember when the UPS caught fire? 01:57:46.560 --> 01:57:50.560 Yeah I do remember when the UPS caught fire. 01:57:50.560 --> 01:57:54.560 Yes I didn't mean that as a dig at our infer team. Our infer team does a great job these days 01:57:54.560 --> 01:57:58.560 but we didn't used to have an infer team and Mark is from the old times. 01:57:58.560 --> 01:58:02.560 You're over five years now. Yeah. Yeah. So he 01:58:02.560 --> 01:58:06.560 remembers when the infer team was me and my spare time. 01:58:06.560 --> 01:58:10.560 And Jake. Yeah and Jake. Sometimes. Sometimes. 01:58:10.560 --> 01:58:14.560 When you can find them. Okay. 01:58:14.560 --> 01:58:18.560 So if I told you this is your station now what would you think? 01:58:18.560 --> 01:58:22.560 Right now I'd be fine. This is not bad. The responsiveness 01:58:22.560 --> 01:58:26.560 is actually better. Hold on where I have. 01:58:26.560 --> 01:58:30.560 Okay so we're going full res here boys. Yeah. Full res 01:58:30.560 --> 01:58:34.560 here boys. 01:58:34.560 --> 01:58:38.560 Oh hey. That's offline. 01:58:38.560 --> 01:58:42.560 Oh more guards haven't loaded. 01:58:42.560 --> 01:58:46.560 Motion graphics. Yeah motion graphic templates yeah. 01:58:46.560 --> 01:58:50.560 How's it feel? Ah pretty good. Pretty good. There's no 01:58:50.560 --> 01:58:54.560 nothing that stands out. Let's see. 01:58:54.560 --> 01:58:58.560 We'll obviously do a more 01:58:58.560 --> 01:59:02.560 detailed analysis at some point before we just 01:59:02.560 --> 01:59:06.560 roll these out to everybody but that looks really good. Like is that 01:59:06.560 --> 01:59:10.560 on par with what you have now or is that like really good? Yeah. 01:59:10.560 --> 01:59:14.560 Yeah this is 01:59:14.560 --> 01:59:18.560 solid. I would like to, I know we're not Benchmarked 01:59:18.560 --> 01:59:22.560 but can I do an expert? Yeah I mean you could do whatever you want 01:59:22.560 --> 01:59:26.560 in this country. Actually no maybe just a render. Wait 01:59:26.560 --> 01:59:30.560 what? That's control right? 01:59:30.560 --> 01:59:34.560 Oh it doesn't have my keyboard shortcuts. Oh that makes sense. 01:59:34.560 --> 01:59:38.560 One sec. One sec. No 01:59:38.560 --> 01:59:42.560 no no no. Okay here we go. So what are you expecting 01:59:42.560 --> 01:59:46.560 for? Nothing. Okay cool. I'm not 01:59:46.560 --> 01:59:50.560 entirely sure what I should be expecting but it seems to be 01:59:50.560 --> 01:59:54.560 rendering on par with what we have at least. Okay. 01:59:54.560 --> 01:59:58.560 Yeah it's pretty good. Okay so if this could solve some of these 01:59:58.560 --> 02:00:02.560 stability issues that some of the other folks are having would you be 02:00:02.560 --> 02:00:06.560 are we really seeing 90% usage of that RTX 5080? 02:00:06.560 --> 02:00:10.560 Oh yeah. 02:00:10.560 --> 02:00:14.560 There is a GPU optimized now. She's hungry. Yeah 02:00:14.560 --> 02:00:18.560 well yeah. She's a hungry boy. That's what I was saying. Oh my god 02:00:18.560 --> 02:00:22.560 we're using, we're capping out our memory. Yeah. Just about. 02:00:22.560 --> 02:00:26.560 Oh crap. Oh crap. 02:00:26.560 --> 02:00:30.560 I thought you knew this Linus. No I didn't know this. I thought the 5080s were going to be 02:00:30.560 --> 02:00:34.560 okay for the editing stations. Isn't there something higher than the 5090 though? 02:00:34.560 --> 02:00:38.560 No well no. No there isn't. 02:00:38.560 --> 02:00:42.560 Not that cost less than like $10. No there isn't. 02:00:42.560 --> 02:00:46.560 No didn't they call those Wattros before? No I don't know what you're talking about. The 02:00:46.560 --> 02:00:50.560 5100s. Oh man. Oh this 02:00:50.560 --> 02:00:54.560 blows. How many desks are in here? 02:00:54.560 --> 02:00:58.560 13. Dang it. Dang it. Lucky 13. 02:00:58.560 --> 02:01:02.560 This is because you put the panels on. Even at 02:01:02.560 --> 02:01:06.560 even at MSRP that's another 02:01:06.560 --> 02:01:10.560 $1,000 US dollars. And ain't nobody getting any 5090s 02:01:10.560 --> 02:01:14.560 at MSRP. How much did you pay $13,000? Yeah because one for 02:01:14.560 --> 02:01:18.560 every system. Are they even $100 bucks? Well they're 02:01:18.560 --> 02:01:22.560 two grand. Two grand. Nobody has an M. But 02:01:22.560 --> 02:01:26.560 $5080s a thousand dollars. Yeah so I'm talking the additional cost 02:01:26.560 --> 02:01:30.560 over the 5080. I have an idea. Look what you did Mark. 02:01:30.560 --> 02:01:34.560 Yo little jerk. What if you get two 5080s 02:01:34.560 --> 02:01:38.560 and then you got like, what is it called SLI? Yeah we don't have SLI anymore. 02:01:38.560 --> 02:01:42.560 NV Link? No NV Link anymore. Not on the 02:01:42.560 --> 02:01:46.560 consumer cards. So you need a monster case to fit two of those in there. 02:01:46.560 --> 02:01:50.560 Yeah no kidding. Oh this 02:01:50.560 --> 02:01:54.560 blows. Dang it. 02:01:54.560 --> 02:01:58.560 I mean it's workable. It's not going to be the 02:01:58.560 --> 02:02:02.560 end of the world. Yeah I don't want workable. I want good. 02:02:02.560 --> 02:02:06.560 You know? Yeah Apple is really. Oh yeah he's an Apple fan. 02:02:06.560 --> 02:02:10.560 We actually have a video coming out very soon. 02:02:10.560 --> 02:02:14.560 Linus switches to Mac for a month. And I believe it's probably going 02:02:14.560 --> 02:02:18.560 to be coming out this weekend. The shopping segment. And Mark 02:02:18.560 --> 02:02:22.560 was sort of our resident advisor to make sure that we 02:02:22.560 --> 02:02:26.560 picked the right Mac. So I ended up, dude I'm so upset. 02:02:26.560 --> 02:02:30.560 So I ended up with a MacBook Air with an M3. And I think I went 02:02:30.560 --> 02:02:34.560 with 16 gigs of RAM which I think will be enough for me for mobile. 02:02:34.560 --> 02:02:38.560 So I want the Mac mini. The M4 Mac mini. Just this week 02:02:38.560 --> 02:02:42.560 Apple announced that they're doing first party refurb 02:02:42.560 --> 02:02:46.560 M4 Mac minis. I would have bought a refurb. Yeah yeah yeah 02:02:46.560 --> 02:02:50.560 M4 Mac minis? Yeah. Already? Already. 02:02:50.560 --> 02:02:54.560 What are you refurbing? Well I don't know exactly. But that 02:02:54.560 --> 02:02:58.560 concerns me because like how many Mac minis M4 Mac minis 02:02:58.560 --> 02:03:02.560 have been refurbished? No I think they're just 02:03:02.560 --> 02:03:06.560 selling a butt ton of these things. And I think that 02:03:06.560 --> 02:03:10.560 anytime you sell a butt ton of something, even if 1% of people don't like it 02:03:10.560 --> 02:03:14.560 if you sell a million of them that's 100,000 returns. 02:03:14.560 --> 02:03:18.560 So I think it's just a natural part of doing 02:03:18.560 --> 02:03:22.560 a high volume business. So with that in mind, like dude I'd have bought one of 02:03:22.560 --> 02:03:26.560 those no problem. I'd have totally saved a few bucks. So part of the premise 02:03:26.560 --> 02:03:30.560 is that I wasn't allowed to just shop for a Mac just by 02:03:30.560 --> 02:03:34.560 grabbing one out of our warehouse. I had to actually buy it after I settled on it. 02:03:34.560 --> 02:03:38.560 So I ended up cheaping out a little bit more than I would if I just grabbed whatever 02:03:38.560 --> 02:03:42.560 I wanted. So would you be interested in moving to Mac minis or 02:03:42.560 --> 02:03:46.560 Mac studios? Yeah I wouldn't be opposed to it. 02:03:46.560 --> 02:03:50.560 I mean cost analysis here. 02:03:50.560 --> 02:03:54.560 Like Mac mini M4 versus 02:03:54.560 --> 02:03:58.560 like readily available. Okay tell me this, is there anything 02:03:58.560 --> 02:04:02.560 that you do that would benefit from having like a fatter 02:04:02.560 --> 02:04:06.560 because this is a way more powerful system than the Mac mini in any configuration. 02:04:06.560 --> 02:04:10.560 Is there anything that you do that would benefit from just more raw horsepower? 02:04:10.560 --> 02:04:14.560 Not now that we're off the red cameras. 02:04:14.560 --> 02:04:18.560 Okay but it's not like we don't still have them. If we pulled them out of 02:04:18.560 --> 02:04:22.560 mothballs for a project would you wish you had more power? 02:04:22.560 --> 02:04:26.560 I think, okay I hate to say this because 02:04:26.560 --> 02:04:30.560 you can never have too much power when you're editing. 02:04:30.560 --> 02:04:34.560 So it depends on what we're doing. So 02:04:34.560 --> 02:04:38.560 complex effects, layers and layers of animations 02:04:38.560 --> 02:04:42.560 it can really, or keying 02:04:42.560 --> 02:04:46.560 keying is another big one. Right. So whether that's for TechLinked or 02:04:46.560 --> 02:04:50.560 if in one we bring tech we key back. Yeah. 02:04:50.560 --> 02:04:54.560 If we do it much there's not many LTTs that call for it. Right. 02:04:54.560 --> 02:04:58.560 And we have the Ultimat now too that can handle that. So that does the keying 02:04:58.560 --> 02:05:02.560 in the box at the point of recording which is so cool. 02:05:02.560 --> 02:05:06.560 That was a smart acquisition by Blackmagic. That thing is so cool. 02:05:06.560 --> 02:05:10.560 So honestly I think this would be enough. 02:05:10.560 --> 02:05:14.560 This would be enough. Yeah. 02:05:14.560 --> 02:05:18.560 Oh sorry I was talking Mac mini versus this. Would you be happy to have the extra power 02:05:18.560 --> 02:05:22.560 of this? Oh yeah. I wasn't even talking about 5090. So do you think I could get away with 5080? 02:05:22.560 --> 02:05:26.560 Here's the problem. If we switch to Mac minis it would be a very 02:05:26.560 --> 02:05:30.560 contentious subject. We are as editors we are split 02:05:30.560 --> 02:05:34.560 pretty much 5050 Apple and PC users at home. 02:05:34.560 --> 02:05:38.560 And I know the PC users at home would be a lot more upset 02:05:38.560 --> 02:05:42.560 working at Linus Tech Tips with Mac minis. 02:05:42.560 --> 02:05:46.560 That's true. The optics aren't the greatest. Okay that's fair 02:05:46.560 --> 02:05:50.560 that's fair. Alright well anyway thank you Mark for coming 02:05:50.560 --> 02:05:54.560 and sort of talking us through this. It looks like there's no obvious 02:05:54.560 --> 02:05:58.560 game breaking issues at least here out of the gate. Other than that 02:05:58.560 --> 02:06:02.560 our VRAM usage is higher than I anticipated. 02:06:02.560 --> 02:06:06.560 It's come down a little bit but come down now doesn't help me. I need it 02:06:06.560 --> 02:06:10.560 to be like if that's what we needed at the beginning of the render then that's what 02:06:10.560 --> 02:06:14.560 we need. So we may be seriously considering 5090s 02:06:14.560 --> 02:06:18.560 rather than 5080s. So alright thank you very much. 02:06:18.560 --> 02:06:22.560 Now since we're here I don't know should we fire up a game on it? 02:06:22.560 --> 02:06:26.560 Alright cool thanks Mark. 02:06:26.560 --> 02:06:30.560 Alright I'm just going to cancel that. 02:06:30.560 --> 02:06:34.560 It's very responsive. I know that's something that used to be a big issue on lesser 02:06:34.560 --> 02:06:38.560 systems in particular with Premiere is like when you cancel something you take out hot 02:06:38.560 --> 02:06:42.560 minute to decide that it's ready to actually cancel. Man that is 02:06:42.560 --> 02:06:46.560 good. Lord is timeline performance ever smooth on a brand new machine 02:06:46.560 --> 02:06:50.560 these days. Sorry this is my first time touching it. 02:06:50.560 --> 02:06:54.560 That's that full res. 02:06:54.560 --> 02:06:58.560 4k please. 02:06:58.560 --> 02:07:02.560 Wow there's like no leg. 02:07:02.560 --> 02:07:06.560 That's pretty cool. Alright so was the idea that we would both 02:07:06.560 --> 02:07:10.560 game side by side on the system? Sure why not. In that case Dan do you want 02:07:10.560 --> 02:07:14.560 to just put some merge messages since we're just kind of killing time hanging out with these people right now 02:07:14.560 --> 02:07:18.560 anyway? Yeah sure I think that sounds like a good idea. Sure. Hello Linus and Dan 02:07:18.560 --> 02:07:22.560 with a huge gap between the 5080 and 5090 should I wait for the 5080ti 02:07:22.560 --> 02:07:26.560 with more VRAM? I'm coming from a 3080 10G 02:07:26.560 --> 02:07:30.560 and the need for more VRAM is 02:07:30.560 --> 02:07:34.560 scaring me that 16 gigabytes is not enough. 02:07:34.560 --> 02:07:38.560 I don't know if a 5080 class card 02:07:38.560 --> 02:07:42.560 with more VRAM is going to be in your future. 02:07:42.560 --> 02:07:46.560 That's the concern and you can really see 02:07:46.560 --> 02:07:50.560 how NVIDIA has strategically chosen 16 gigs. 02:07:50.560 --> 02:07:54.560 It happens to be the amount of unified 02:07:54.560 --> 02:07:58.560 memory in both current generation consoles. 02:07:58.560 --> 02:08:02.560 Happens to be. So we're still at the point in the 02:08:02.560 --> 02:08:06.560 PS5 and Xbox would you like me to help you with that Andy? 02:08:06.560 --> 02:08:10.560 We're still at the point in the series and the PS5's 02:08:10.560 --> 02:08:14.560 life cycle where game development is probably 02:08:14.560 --> 02:08:18.560 not focused on a next generation PlayStation 6 02:08:18.560 --> 02:08:22.560 or Xbox whatever the crap they end up calling it. So 02:08:22.560 --> 02:08:26.560 NVIDIA knowing this knows that no game developer in their right mind 02:08:26.560 --> 02:08:30.560 is going to be targeting more than 16 gigs of memory. 02:08:30.560 --> 02:08:34.560 So there is no need for them to 02:08:34.560 --> 02:08:38.560 get in more. Yes if you wanted to crank texture resolution 02:08:38.560 --> 02:08:42.560 or if you wanted to run advanced features there could be a benefit to additional 02:08:42.560 --> 02:08:46.560 VRAM and we've seen that even today 02:08:46.560 --> 02:08:50.560 but there's no need and they're way more interested 02:08:50.560 --> 02:08:54.560 in pursuing things like AI compression techniques to bring down 02:08:54.560 --> 02:08:58.560 VRAM usage rather than putting more VRAM on the card because 02:08:58.560 --> 02:09:02.560 an AI compression technique cost them development time 02:09:02.560 --> 02:09:06.560 once more VRAM on the card cost them VRAM 02:09:06.560 --> 02:09:10.560 every single time they build a card so it's in their best interest to see if they can just 02:09:10.560 --> 02:09:14.560 develop their way around it. So with that in mind 02:09:14.560 --> 02:09:18.560 even if we do get a mid life cycle refresh 02:09:18.560 --> 02:09:22.560 unless it happens to coincide with like a new console 02:09:22.560 --> 02:09:26.560 generation which probably what two years, three years maybe? I think at least three years 02:09:26.560 --> 02:09:30.560 it feels like the current gen is like just getting its wings 02:09:30.560 --> 02:09:34.560 NVIDIA has no motivation to put 02:09:34.560 --> 02:09:38.560 more than 16 gigs of RAM on. The 32 gig 5090 is obviously 02:09:38.560 --> 02:09:42.560 a budget AI play and an enthusiast play and is priced 02:09:42.560 --> 02:09:46.560 as such. The 5080 is the gaming flagship 02:09:46.560 --> 02:09:50.560 and they have deemed it thusly that 16 gigs is enough 02:09:50.560 --> 02:09:54.560 now AMD might come and be disruptive I think the word on the street is that the 02:09:54.560 --> 02:09:58.560 oh man what is this stupid thing called 02:09:58.560 --> 02:10:02.560 what's it called? 9070? What's the new AMD card called? 02:10:02.560 --> 02:10:06.560 9070XT. There's some rumors that it could be equipped with up to 32 gigs of RAM 02:10:06.560 --> 02:10:10.560 There's going to be a card that's in that class with 32 02:10:10.560 --> 02:10:14.560 not the base one. Got it. Is that confirmed or is that still 02:10:14.560 --> 02:10:18.560 got it? Oh frame view. Oh yes 02:10:18.560 --> 02:10:22.560 but that doesn't help you if you're 02:10:22.560 --> 02:10:26.560 you want an NVIDIA card basically 02:10:26.560 --> 02:10:30.560 why am I reloading in the middle of the thing? 02:10:30.560 --> 02:10:34.560 Oh goodness I see. Is that 40 frames? 02:10:34.560 --> 02:10:38.560 No no no. Man we are 02:10:38.560 --> 02:10:42.560 actually surprisingly close. All things 02:10:42.560 --> 02:10:46.560 considered we are at the same settings I mean we're at 1080p anyway right? 02:10:46.560 --> 02:10:50.560 We're far past the point of dimension returns 02:10:50.560 --> 02:10:54.560 Yep. Dude we were thinking of doing 02:10:54.560 --> 02:10:58.560 like a 1000 FPS gaming PC you know getting like a 9800x3D 02:10:58.560 --> 02:11:02.560 come on over here come on get over here 02:11:02.560 --> 02:11:06.560 Is it possible on modern competitive games 02:11:06.560 --> 02:11:10.560 to get 1000? Well that was the question we were going to try and answer 02:11:10.560 --> 02:11:14.560 with like a tuned 9800x3D plus an RTX 5090 02:11:14.560 --> 02:11:18.560 could we actually run at 1000 FPS? 02:11:18.560 --> 02:11:22.560 It might be that you're helped out because I don't have any AI because it's a training session 02:11:22.560 --> 02:11:26.560 I have to do this before I can play or there's very few AI 02:11:26.560 --> 02:11:30.560 Oh there's no AI 02:11:30.560 --> 02:11:34.560 This just isn't actually running that fast. I don't still have Premiere open in the background or anything do I? I don't 02:11:34.560 --> 02:11:38.560 I don't know I was expecting more than 500 02:11:38.560 --> 02:11:42.560 FPS. Yeah is there something going on? 02:11:42.560 --> 02:11:46.560 Nope I just checked. Maybe I messed up the settings 02:11:46.560 --> 02:11:50.560 let's just double check. Sure yeah we can do that. Okay so video 02:11:50.560 --> 02:11:54.560 could just be CPU bottlenecked man. Yeah maybe 02:11:54.560 --> 02:11:58.560 just check if you're actually 1080p maybe it's 4k somehow 02:11:58.560 --> 02:12:02.560 I don't think so yeah 1080p. Advanced video. It should be medium except everything 02:12:02.560 --> 02:12:06.560 like let's just do it again so hit medium and then 02:12:06.560 --> 02:12:10.560 turn off FSR at the bottom 02:12:10.560 --> 02:12:14.560 Wow that's default hey? I know it's crazy 02:12:14.560 --> 02:12:18.560 Man even in a competitive game 02:12:18.560 --> 02:12:22.560 upscaling techniques is really changing and I'm not sure 02:12:22.560 --> 02:12:26.560 if I'm here for it. I'm gonna have to get on board because it's just a happening 02:12:26.560 --> 02:12:30.560 I don't hate it. I sit far enough away from my displays 02:12:30.560 --> 02:12:34.560 that I don't really mind it like I play I'm playing the Witcher 3 right now 02:12:34.560 --> 02:12:38.560 and I have FSR on. Interesting 02:12:38.560 --> 02:12:42.560 I mean Ploof meanwhile is like militantly against it except 02:12:42.560 --> 02:12:46.560 in our recent videos looking at 4k and 8k gaming on the 02:12:46.560 --> 02:12:50.560 5090 there was one or two 02:12:50.560 --> 02:12:54.560 games that he was like I would turn it on 02:12:54.560 --> 02:12:58.560 Really? No frame gen for him at least not yet but 02:12:58.560 --> 02:13:02.560 DLSS yeah there was a couple games where he at least thought about 02:13:02.560 --> 02:13:06.560 it and one where he confirmed yeah I would turn it on. Which is 02:13:06.560 --> 02:13:10.560 if you know that guy it's a big deal 02:13:10.560 --> 02:13:14.560 It's a big shift for him 02:13:14.560 --> 02:13:18.560 Well now we're just playing games and it's pretty on par. I think you might have a slight edge 02:13:18.560 --> 02:13:22.560 actually. Yeah I mean I should. Like right now I'm a little bit ahead but like 02:13:22.560 --> 02:13:26.560 Given I'm running it. Yeah you are actually. I mean when we go to the same spot on the map 02:13:26.560 --> 02:13:30.560 maybe that has a bigger difference than I realized. It's a non X3D. Yeah I don't know 02:13:30.560 --> 02:13:34.560 Do you want to come over here? Yep. Is a non X3D chip really gonna take 02:13:34.560 --> 02:13:38.560 the AMD advantage away that much? It's possible 02:13:38.560 --> 02:13:42.560 Oh my goodness I sucked 02:13:42.560 --> 02:13:46.560 Oh my goodness oh wow I just got 02:13:46.560 --> 02:13:50.560 That was embarrassing. He came all the way here just for nothing 02:13:50.560 --> 02:13:54.560 That was embarrassing 02:13:54.560 --> 02:13:58.560 I'm about to run out of time 02:14:02.560 --> 02:14:06.560 Alright don't worry I got this. I got my P-shooter 02:14:06.560 --> 02:14:10.560 Without AI we're pretty dang close 02:14:14.560 --> 02:14:18.560 Oh gosh darn it 02:14:18.560 --> 02:14:22.560 I'm heading back toward you 02:14:22.560 --> 02:14:26.560 Are you just playing deathmatch? 02:14:26.560 --> 02:14:30.560 That is so annoying 02:14:30.560 --> 02:14:34.560 I understand why they do it because it can be really frustrating for more 02:14:34.560 --> 02:14:38.560 experienced players to have people drop in the match and just like think they're going to learn on the fly 02:14:38.560 --> 02:14:42.560 Like you know have the bomb and not know how to plant that stuff 02:14:42.560 --> 02:14:46.560 Yeah I just needed to kill that guy in case. Oh shoot okay I'm coming I'm coming 02:14:46.560 --> 02:14:50.560 Oh please don't make me with the whole round 02:14:50.560 --> 02:14:54.560 This is embarrassing. Dan do you want to hand us with a merge message? Yeah sure 02:14:54.560 --> 02:14:58.560 As someone who is taking my first serious crack at switching from Windows to Linux 02:14:58.560 --> 02:15:02.560 Have you ever considered a follow up on your covert era Linux 02:15:02.560 --> 02:15:06.560 Challenge and if not why? Yes we are going to do a 02:15:06.560 --> 02:15:10.560 follow up to the Linux challenge once SteamOS goes gold 02:15:10.560 --> 02:15:14.560 I'm so ready for it 02:15:14.560 --> 02:15:18.560 I'm going to die 02:15:18.560 --> 02:15:22.560 Oh my goodness I'm coming back 02:15:22.560 --> 02:15:26.560 Dan hit me again 02:15:26.560 --> 02:15:30.560 I forgot for you here 02:15:30.560 --> 02:15:34.560 Will there be an HDD revisit for 2025 games maybe not just for 2024 hard drives but early 02:15:34.560 --> 02:15:38.560 SATA or IDE. My upgrade cycle for storage is when it dies 02:15:38.560 --> 02:15:42.560 So my first non OS SSD was quite recent 02:15:42.560 --> 02:15:46.560 Oh interesting 02:15:46.560 --> 02:15:50.560 Man I don't think so looking at how 02:15:50.560 --> 02:15:54.560 kind of dead hard drives are in the gaming space 02:15:54.560 --> 02:15:58.560 I just don't think too many people I mean obviously you're asking for it 02:15:58.560 --> 02:16:02.560 but I don't think too many people are at this point 02:16:02.560 --> 02:16:06.560 Stand on that barrel on the left and then look right at this pot 02:16:06.560 --> 02:16:10.560 Okay look at the pot 02:16:10.560 --> 02:16:14.560 Dude you are outperforming me 02:16:14.560 --> 02:16:18.560 By a significant margin I guess non X3D 02:16:18.560 --> 02:16:22.560 May not be the way to go for CS2 02:16:22.560 --> 02:16:26.560 Graphically demanding 02:16:26.560 --> 02:16:30.560 What else did you have in mind for today? We can do some Alan weight 2 or we can do some cyberpunk 02:16:30.560 --> 02:16:34.560 Yeah let's fire up cyberpunk 02:16:34.560 --> 02:16:38.560 That seems like a good place to go okay Dan hit me 02:16:38.560 --> 02:16:42.560 That's all you got oh sick okay cool we'll do cyberpunk and then we'll wrap it up 02:16:42.560 --> 02:16:46.560 Let's see 02:16:46.560 --> 02:16:50.560 Actually I don't even know how many people are watching 02:16:50.560 --> 02:16:54.560 Look at the YouTube dashboard today 02:16:54.560 --> 02:16:58.560 And it is not 02:16:58.560 --> 02:17:02.560 Oh that's the wrong stream that's still the 24-7 stream 02:17:02.560 --> 02:17:06.560 Oh interesting 02:17:06.560 --> 02:17:10.560 But the event still does in our event calendar 02:17:10.560 --> 02:17:14.560 The way that you handle YouTube streams is 02:17:14.560 --> 02:17:18.560 It's good it's a lot better than it was before but it's sort of unintuitive 02:17:18.560 --> 02:17:22.560 Because you can either do it like Twitch where you just go live 02:17:22.560 --> 02:17:26.560 Or you can have scheduled events 02:17:26.560 --> 02:17:30.560 Your menu is outperforming mine 02:17:30.560 --> 02:17:34.560 I mean sure 02:17:34.560 --> 02:17:38.560 Yeah this wasn't specced out as a gaming system 02:17:38.560 --> 02:17:42.560 But it's pretty darn good 02:17:42.560 --> 02:17:46.560 And I'm actually going to lose some of my advantage of having a much more powerful GPU 02:17:46.560 --> 02:17:50.560 Because of our HDMI switcher over here 02:17:50.560 --> 02:17:54.560 Dan is there a reason that this thing couldn't do 4K? I thought this thing does 4K It does do 4K like we could try it 02:17:54.560 --> 02:17:58.560 Oh okay I don't feel like 02:17:58.560 --> 02:18:02.560 Throwing a wrench in the gears tell you what Let's do our comparison at 1080p 02:18:02.560 --> 02:18:06.560 Then we'll try and run it 4K And if it doesn't work then it doesn't work 02:18:06.560 --> 02:18:10.560 I think we do yeah ray tracing overdrive is still going to be challenging enough with no DLSS 02:18:10.560 --> 02:18:14.560 Oh dude ray tracing overdrive will be super challenging 02:18:14.560 --> 02:18:18.560 Ultra no DLSS Ultra no DLSS? 02:18:18.560 --> 02:18:22.560 No frame gen And then just everything as it was 02:18:22.560 --> 02:18:26.560 Window border list or? 02:18:26.560 --> 02:18:30.560 Yes I believe so Oh can we go full screen? 02:18:30.560 --> 02:18:36.560 I know it doesn't matter anymore Did you put low latency? 02:18:36.560 --> 02:18:40.560 Oh I didn't turn on reflex I don't think On with boost enabled? 02:18:40.560 --> 02:18:44.560 Sure Which marker just play? 02:18:44.560 --> 02:18:48.560 Oh yeah I want to play We'll just find a kind of similarish area 02:18:48.560 --> 02:18:54.560 We'll drive around or whatever Coffee Loki says PC not good enough 02:18:54.560 --> 02:18:58.560 I don't think they're actually referring to these 02:18:58.560 --> 02:19:04.560 Spend more money I'm going to ride my 3090 until I die 02:19:04.560 --> 02:19:10.560 Brandon the IT guy in Floatplane chat asks Is there a Linux distro for video editing? 02:19:10.560 --> 02:19:16.560 Not that I'm aware of And it's less to do with the distro or lack thereof 02:19:16.560 --> 02:19:20.560 And more to do with the tools or lack thereof 02:19:20.560 --> 02:19:26.560 Black magic is doing a good job of supporting it But to my knowledge none of the other major players in the space 02:19:26.560 --> 02:19:30.560 Have shown much of an appetite for Linux 02:19:30.560 --> 02:19:36.560 Are you going to try and get to the exact same spot as me? Because I don't really think that's necessary 02:19:36.560 --> 02:19:40.560 Yeah I'm already outperforming you by a pretty significant margin 02:19:40.560 --> 02:19:44.560 You're at like 70 FPS and I'm at like 90 02:19:44.560 --> 02:19:48.560 Oh I dropped down a little bit But you're also dropped into the 60s now 02:19:48.560 --> 02:19:51.560 I feel like where you are is harder to run than where I am 02:19:51.560 --> 02:19:55.560 But I don't know the map well enough to be able to get around 02:19:55.560 --> 02:19:59.560 The 3090 to the 4090 was a big jump in performance 02:19:59.560 --> 02:20:03.560 So if we were looking at this 5080 versus a 4090 02:20:03.560 --> 02:20:06.560 Then it wouldn't be that impressive 02:20:06.560 --> 02:20:10.560 But looking at it compared to the 3090 02:20:10.560 --> 02:20:14.560 You can go from the workstation slash enthusiast card of that generation 02:20:14.560 --> 02:20:19.560 To the gamer card of this generation and expect a performance uplift honestly 02:20:19.560 --> 02:20:24.560 Not enough though If I had a 3090 02:20:24.560 --> 02:20:28.560 I would just run this at 75 FPS rather than going for the extra 15 FPS 02:20:28.560 --> 02:20:33.560 I don't think it's an upgrade It's a big enough boost that you'll really have a noticeable experience 02:20:33.560 --> 02:20:37.560 With that said if I could get a 5080 for MSRP 02:20:37.560 --> 02:20:40.560 Knowing that I can sell my 3090 for a lot 02:20:40.560 --> 02:20:43.560 I could probably almost do it as a cross trade 02:20:43.560 --> 02:20:47.560 So if my priority was just gaming 02:20:47.560 --> 02:20:50.560 It's true you don't need that extra VRAM 02:20:50.560 --> 02:20:55.560 I'd rather have the raw performance than the VRAM at that point 02:20:55.560 --> 02:20:58.560 Likewise for gaming For just gaming Yeah I agree 02:20:58.560 --> 02:21:03.560 And let some AI tinkerer have that 3090 and use that VRAM for what they're doing 02:21:03.560 --> 02:21:07.560 Yep So that's a totally valid option 02:21:07.560 --> 02:21:11.560 I mean both David and I are very PC of theseus people 02:21:11.560 --> 02:21:15.560 So we're always kind of thinking like Oh what can I sell from my rig 02:21:15.560 --> 02:21:18.560 And then acquire and kind of optimize as we go 02:21:18.560 --> 02:21:23.560 But a lot of people are not like that So I totally understand too if you have a 3090 02:21:23.560 --> 02:21:27.560 And you're just looking at your machine going is it still good enough The answer is yep 02:21:27.560 --> 02:21:33.560 If you don't feel like making any changes But I've found that kind of staying on top of things a little bit 02:21:33.560 --> 02:21:37.560 Has been the best value way to get the most out of my system 02:21:37.560 --> 02:21:41.560 Yeah there's kind of a weird transition period where the old stuff is still really high value 02:21:41.560 --> 02:21:46.560 Especially now Yeah exactly GPU transitions are so weird 02:21:46.560 --> 02:21:49.560 Not at all like they used to be 02:21:49.560 --> 02:21:52.560 Okay I'm ready to try 4K 02:21:52.560 --> 02:21:55.560 What do you think Dan is this gonna work Yeah it should 02:21:55.560 --> 02:22:00.560 Oh I can't even select it Oh Are you gonna have your desktop set to 4K 02:22:00.560 --> 02:22:03.560 Or do you 02:22:03.560 --> 02:22:06.560 I don't know I didn't think so Usually you can 02:22:06.560 --> 02:22:09.560 Yeah I can't change it Oh maybe the Yep 02:22:09.560 --> 02:22:13.560 Is there a mode selection on this thing that's like 02:22:13.560 --> 02:22:17.560 I don't even know if it is capable of doing It is that's definitely it can do 8K 02:22:17.560 --> 02:22:20.560 Oh dude this will do 4K 120Hz Yeah it's like a 02:22:20.560 --> 02:22:24.560 Well this is like a high end matrix Oh yeah I'll fiddle with it 02:22:24.560 --> 02:22:27.560 Shut up No I don't think we need to fiddle with it It's okay 02:22:27.560 --> 02:22:32.560 Maybe pro edge I think what we're gonna do is hey hey Thank you guys very much for tuning into the stream today 02:22:32.560 --> 02:22:37.560 There's definitely some things we like about this configuration 02:22:37.560 --> 02:22:41.560 But as you heard from Mark Our editing team is very divided 02:22:41.560 --> 02:22:44.560 On the subject of PC versus Mac 02:22:44.560 --> 02:22:50.560 And if we stick with PC There's a chance that we're gonna end up going 5090 02:22:50.560 --> 02:22:53.560 Maybe we'll do an update on Floatplane 02:22:53.560 --> 02:22:57.560 We'll get you guys a look at the final system Otherwise maybe we'll do a stream 02:22:57.560 --> 02:23:01.560 And we'll build a bunch of the final systems And we'll hand deliver them to our editors 02:23:01.560 --> 02:23:05.560 In the editing den on the other side of the wall See you later guys