Hi, welcome to Visual Studio Toolbox. I'm your host Robert Green and joining me today is Kendra Havens. Hey Kendra. Hello. Welcome back on the show. Thanks so much for having me. And we're going to talk about unit testing. Yeah. Which is not the most exciting subject maybe people are thinking, but that's why you're on the show to add it some excitement. It's just because they don't know about all these cool features. That's right. We're about cramming in. So this is why we're here to talk about it. Unit testing is a tricky subject because it's like everybody knows you should do it, but what are the tools? How do you write unit tests, et cetera, et cetera? We're going to do a series on that later on in the summer. But in the meantime, yes, we'll build your pixie back on to do a series on unit testing. Excellent, that'll be really good. In the meantime, you're going to show us great tooling in Visual Studio. Yeah, so the purpose of unit testing is actually one of the first things they want to talk about. And I can talk about our Roslyn team example. Then I'll go over learning resources that people tend to miss a lot. And just in general, this whole episode will be about announcements that are really easy to miss during conferences and all of our big releases and in blog posts and stuff. So I'm just going to be highlighting all of the ones that have to do a testing and more of a focused. Okay, you know what I'm saying. So learning resources, latest testing improvements, I'll demo all of those. And then more of our Visual Studio testing tools that maybe we haven't talked about in a while that I'd love to bring up again. Cool. Cool, so purpose of unit testing. I love using the Roslyn example. I work on the Roslyn team, which is the C-Sharp and Visual Basic Compiler. So as many people know, we went open source and we architected the compiler in a way to be extendable. So we wanted other community contributions. And as a result of that, last year 60% of .NET contributions were from open source. The only way our team could possibly keep up with that many PRs is through our tests. So we have 86,000 tests on Roslyn and learning how changes were affected in a pull request. Looking at your test is a great way to do that. So it helps the reviewing experience a ton. So that's a really big example. That is our bread and butter on the Roslyn team is actually having tests. That sounds like a awful high number of tests, is it? It is. But we got millions of people who use it and thousands of scenarios. It's kind of an important feature of the product, C-Sharp. It's definitely paid off with our team having those. It's the only way we could have kept up with those changes. Right, so here are the learning resources that I think a lot of people might have missed. I get a lot of questions about like, hey, how do you test legacy code? And I'm like, we've actually done an episode on that on Microsoft Virtual Academy. So yeah, just go to Microsoft Virtual Academy and you can look up our sessions on testing legacy code and test driven development. That's also a really nice one. A lot of people also miss that MS test and VS test are open source on GitHub. So you can look at docs and issues and they're very informative, especially if you're running into a bug. A solution actually might be on the repo or at least the discussion to know what's happening with it. So that's kind of a pivot like you could either go to developer community and just file the bug. But if you're actually trying to like find the workaround or see if we're already engaged with the community on that, there could be issues in those repos too, so that's really helpful. And of course, if you're using .NET test, the .NET CLI is also all open source on GitHub. So that's a third repository to look at. So very latest testing improvements, massive performance improvements. I've showed you a few of them before, but we'll go over to it and just focus on testing. A lot of that's due to real-time test discovery is the new source-based type of discovery that we checked in that no longer lies on assembly base. So it doesn't require a build, pretty cool. There's also been huge test framework improvements in in-unit, ex-unit, and MS test, qualifier for this episode. It's probably going to be a lot of .NET focused stuff because that's my life. So if you want to learn about C++ testing improvements, they actually wrote a blog post not too long ago with some of that. But that's what it is. So I do want to urge Big Push to update your test adapters because as you can see, execution, this is in our labs, test execution of over 10,000 generated tests by Visual Studio Update by Framework has gotten so much faster. So just updating your test adapter is such an easy thing to forget to do because you're always focused on the framework version. Don't often think about the test adapter version, so please do that. It's awesome. And that's your test discovery type of improvement as well. So just updating your test adapter there will also improve it a lot. Cool, so latest test experience improvements, we've got the hierarchy view in the test explorer. Latest being. Latest. Ooh, so the hierarchy view was added in 15.6, that update. Yeah, and that's all I have covered in this slide. So it sourced your tests alphabetically and it organizes your tests by project namespace. So in other words, it's there now, it's not coming in the Fable 15.8? No, it's here. Excellent. It's here. It's been here for months and people love it. Cool. If they know to update to get it, because they still get requests. Yeah, so we're still designing the hierarchy view and we're open for discussion, but enough talk. Enough talk. Geez, that was a lot of talk. Robert didn't want me to use a PowerPoint, but I was like, please. What if people forget what I said, because I talk too fast? Anyway, let's increase the front size there. Okay, so now you can see the Test Explorer over here.  So I have a large test project. If I go ahead and unload that project, you can see the Test Explorer will update automatically. And if I reload it, it can discover 5,000 tests within just a few seconds. Boom, done. Pretty sweet. So I'll go ahead and use the hierarchy to go ahead and navigate. So this is my project namespace and my class. And I can show you how the source-based discovery works. I can go ahead and add that test, and then it will also automatically appear right in the Test Explorer. Pretty sweet. And if I change the name. You don't have to build first? Don't have to build first. Oh, man, that's awesome. Yeah, pretty great. So if I comment it out, it will also then just disappear. That is extremely cool. Because in a large project like this, it can take some time to build. Yeah. And just having that context and having to rebuild and then refind your tests and then run it, big time saver. So what I also wanted to call out was this summary line is also something we added. So this is sort of a global view of how many tests are in your project. And then it says to failed, right at the top of the Test Explorer as well. That was also a pretty popular customer ask. And the last thing I wanted to show you is updating your test adopters. That's really easy to do. Just type in NuGet and open your NuGet package manager for your solution. And go ahead and type in test. Click on your test adopter and move to the latest table is my high recommendation if you want some sweet, sweet performance improvements. OK. OK. So next slide. So I also get asked a lot, how do we make writing tests easier? And I find a lot of people might have missed some of the awesome features that we've checked in. I'm completely automating it. By completely automating it. Right. That shouldn't be too hard. That could be pretty easy, especially if we've actually checked in that feature to Visual Studio. So we always want to kind of bring more attention to it, especially when people ask me for it. So right clicking and generating unit test stubs for .NET Framework projects, that's in all versions of Visual Studio, just really easy test method stub generation. The stub. Yeah. Not the test itself. Yeah, the test itself. How hardly difficult would that be, by the way? Well, that brings me to our next feature, IntelliTest. So this is also only for .NET Framework projects. And IntelliTest is only available in Enterprise. But that will actually generate and look at all of the logic in your method and generate a test for each logic branch. And I can show you that in just a minute. All right, cool. And the next thing I'm going to call out is code coverage, also an enterprise-only feature, and how it can integrate into the VSTS pipeline. Cool. Okay. So we'll escape PowerPoint again. Sorry. Now I feel like I'm using it way too much just because I know you're grinding your teeth. Like this is a cool conversational demo show. What are you doing, Kendra? Geez, sorry. Your word's not mine, I love it. Gosh, Kendra's the worst. Okay. So I can generate or create unit tests, just the stubs really easily, but from the class or the method level. So I already have a home controller test. And that's been in there for a very long time. Yeah, yeah. So I already have a home controller test class. But again, it's easy to forget these things. And we definitely get comments like, how do I discover all of these cool things in Visual Studio? And we're working on it. You just did an episode with Justin with his tip of the day thing, right? That's another good way. Maybe I should get this in there. Okay. So let's say I already generated the test for this class and I just added a method. And I want to now create a stub for that method. I can also go ahead and append a generated test to a file that already exists. So I'll go ahead and do that. And now it has my throw not implemented exception and it just depended tests to my method name. Super simple. You already snore in. It's okay. I'm just thinking that that'd be nice to have an extension or setting that automatically creates the unit test for you when you create the method in the first place. I like that feedback. I'm going to file that on developer. I'm just kidding. Sure. I got you. Okay, so the next thing I want to show you is IntelliTest. Now, let me show you what this project does really quickly. We put an episode on IntelliTest a couple of years ago, but I haven't really heard that much about it since. Exactly. So we want to talk about it more. Yes. Because people ask me for a better test generation. I'm like, have you checked out IntelliTest? And they're like, what's that? I'm like, gosh, I got to go on one of those cool Channel 9 shows. Do you know of any? No. So this is my obscure calculator. So it's taking normal measurements into obscure measurements, like days to fortnight, miles to furlongs, et cetera. So pretty simple methods right now. And so IntelliTest wouldn't generate very interesting tests for these methods. So let's look at a method that has a lot of branches in it. So this is my calculate trust method. This is from the old adage. I only trust them as far as I can throw them. Right. Right. Obviously. Excellent demo code. But it does have a lot of logic branches in it. So for every conditional branch and code, a case analysis performed in IntelliTest. So if statements, assertions, operations that can throw exceptions, all of these are analyzed. This analysis is then used to generate test data for parameterized unit tests for each of your methods. This also gives you really high code coverage. So I'm going to go ahead and right-click and generate IntelliTest. So I'll create my IntelliTest right here. On the X unit test project or on the obscure calculator. Oh, I don't think that's selected. It's going to generate a new test project in general for me. Okay. But does it matter what solution is highlighted when you right-click? No. It matters where in the editor you right-clicked from. Okay. So I'm going to right-click and create IntelliTest. So I want to put this all in a new test project. So I will call it my generated project. And it will go ahead and run that analysis right now. So now you can see that it generated a .cs file. But it is actually, when I run IntelliTest, will generate more .g.cs files. And those are all of our generated classes. So I'll go ahead and do that. So that's going to run the tests that you created through IntelliTest, not your entire suite of both IntelliTest unit tests and other unit tests. Correct. Yeah. I can still use the Test Explorer to do that. But yeah. Right now, definitely just focusing in on the IntelliTest. And you can actually see in the Test Explorer, I now have all of those tests that it just generated for me. You can see they are kind of randomly generated names with exception numbering after aid. So you can see in my solution Explorer that I now have that .g.cs file. And this is where all of those test cases live. So the test data for this is generated every time I run IntelliTest. So I don't want to actually spend my time editing any of these files because they'll be overwritten when I rerun it. So you can rerun it every time you run. Yeah. Okay. Yeah. So. How's the performance of that? Good. I'm not sure how often people will be regenerating everything, but you can rerun them without regenerating any tests. Okay. Sorry. I don't think I made that clear. Yeah. So you'll see this .cs file is sort of the higher node of the test suite. And these all rely on the PECS method, which would be from the Microsoft PECS framework, which was developed by Microsoft Research. Okay. So let's look at my results really quick. Looks like I have some divided by zero exceptions, some null reference exceptions. I have some problems with that code. Luckily, I have a handy-dirty code snippet because I'm a cheater. That's okay, right? You'd be cheating if you've already written it. You don't need to watch me throw out all of that stuff. This is basically just adding a null check and making sure that I'm not going to divide by the projectile person's weight, if it's zero. So now if I rerun those tests, and actually before I rerun, I do want to point out I have nine tests here right now, seven of which are failing. I'll go ahead and rerun them. So IntelliTest is looking over my logic branches again, and since I don't have as many logic branches or cases that it shows would cause a divide by zero error or something like that, you can see all my tests are passing now, but I also only have seven because I changed the conditions that we're generating the test to begin with. Okay. Interesting. Pretty sweet. Yeah, so that's basically IntelliTest. IntelliTest also provides great code coverage, so it's an easy way to kind of check that box. And it would seem also to be a great learning tool to learn how to write unit tests and what should be in unit tests. That's a very good point. Yeah, so it kind of takes maximum values and just use cases and certain exceptions that you would throw and kind of figures out what is most likely to be seen in this scenario. Right. So I'll go ahead and run code coverage in Visual Studio. That was just in Test, Analyze, Code Coverage, all our selected tests. And I'm not doing too great, but let's look at specifically the conversion calculator, which is what I just generated the tests for. And it's at 100% because it looked at the entire method as well as multiple blocks within that method. So the ones that you have low numbers for were not the ones you created with IntelliTest. No. I have to run those over the other Calculate Fortnight for a long time. And the ones that IntelliTest created would have much better coverage than like zero. Yeah. That was 100. Excellent. Which is great. Yeah, so it's a good way to bump up your code coverage score. Very cool. If you want to get code coverage results in VSTS, that's actually really simple to do. Just go to your build definition. So you can go to, whoops, actually I'll just stay. Build and Release. And, oh it gave me that message because I had been clicking in this. And you can hit this code coverage enabled button and then it'll run code coverage for you. Okay. And that'll be a part of your report that you see on that build. So that's not relying on the IntelliTest, right? Or is it? No. The code coverage is a different tool that the IntelliTest would help improve your code coverage score, for sure. Okay. So that's just a... So the point here is that the code coverage you get in Visual Studio in local development, you can also see in VSTS as part of your pipeline. Okay. Cool. Cool. One thing I also want to call out in VSTS is this newly added option. It's running only the impacted tests. So what are impacted tests? VSTS is actually able to look at your commits and what code was actually changed and figure out which tests were affected by those code changes and only run those tests. So if you've only changed like four files and maybe like 30 tests were affected, you don't need to run all 5,000, 86,000 of your tests. So it can save a lot of build time. Okay. Really nice feature. Cool. So speaking of only impacted tests, let's talk about live unit testing. Let's. That's the last feature I want to talk about. Okay. So if you haven't heard, live unit testing listens to your code changes and runs impacted tests in the background as you work. So test results are shown right in the code editor, right beside your code in like line by line feedback. So this is an enterprise only feature. But the recent improvements that we've checked in are better performance and easier configuration. So if you had issues opening your project in the past with live unit testing, it could just work. That was always pretty easy to begin with. Oh, that's fantastic. Yeah. Bye. I had some. I'm sure there were issues people were running into. Yeah. I can share internally. We have like customers in office who have odd project types. Well, don't tell them I said that. But they had configuration issues and live unit testing is just a lot smarter now and it can easily drop in the files that they need. So I asked them to retry it because they hadn't tried it out in a couple months and it just worked. Cool. Which is exactly the experience that we want. So I highly suggest just trying it out again if you ever had any issues in the past. So it now supports MS-Test V1 and .NET Core. We also added a test center notification which just gives more feedback on what live unit testing is doing in the background as well as a skip category. You can include and exclude test projects and we now have test method icon so they pop out a little bit better. Let me show you what all that means though. Enough talk. Okay. So I actually have a very large test project. That's almost 5,000 tests. So I don't want to include it when I start live unit testing right off the bat. I only want to include a certain test project. I can now go to the solution explorer, right click and only include that. So as you can see my large test project isn't running in the background. It didn't try to re-execute or anything super helpful. Another thing I called out earlier is the skip category and there we go. So my chocolate sentiment test, long story of why it's named that is basically using Azure Cognitive Services to analyze the comments that a guest left in our Hotel 360 app. Really negative we'd ask housekeeping to leave a few more chocolates on their pillow to sweeten the deal. But since this is Azure Cognitive Services I didn't want that test running every single time I made a code edit because that's way too often. I could probably rack up the bill. Stomping it out and doing a mock. So you can just say don't run it. Yeah I can just add the test category skip when live unit testing and now I have a little empty beaker instead of the usual beaker test method. Okay so you don't have to go to that and explicitly exclude that you can just say always skip it. Exactly. Cool. Okay so I'll go ahead and show you how live unit testing works really quick. Let's say I have a few failing tests. I can click on the icon in the editor. I can hover over the test that's failing and actually read the error message. If I click on it I can actually debug this test to learn more about why I'm getting a null reference. Though I'm pretty sure it's this one string message that I'm using. So I can go ahead and add, yep message was null. So I'll go ahead and add a null check for that. And I can do that using our handy dnd code fix for it. And of course I can highlight and drag it where I want and I'll do that just kind of clean this up a little bit. Let's only run message.normalize if message is not null and you can see in the background while I was editing live unit testing was re-running those tests when I typed. So now I can see that all things are passing and I feel way better. Cool. And then of course you can turn it off for that method while you're writing it. I could. Yeah. And if you're. I could have added a skip category right here. You can also write you can right click and do it as well. No, the right clicking was for excluding certain projects. So at the method level we have categories so you don't like lose track of them. But for projects since they're much bigger blocks we just have right clicking in the solution explorer. Got it. I want to be able to better navigate what tests are and are not a part of live unit testing maybe with like a new group by in the test explorer but we're working on it. Okay. Yeah. Cool. So those are testing improvements. They shared new resources for learning why we should be testing. We talked about teletest, code coverage and live unit testing. Sweet. And now my life is happy. So let me make it more let me make it difficult. Oh. Okay. So we had we had talked about IntelliCode which is the AI inside Visual Studio. So one could imagine a world in the hopefully not too distant future where as you are writing code Visual Studio is writing your complete set of unit tests for you. That is something I can definitely imagine. I think we'd still want because I think the organization of tests within test projects is really important to people because they probably already have a way of like even when I was right clicking and generating a test method stab it asked me what project do you want us to put that in and what class. I think that aspect is really important and I'm not sure if we're ready to decide how everyone's architecting their test project solutions. So if I have a choice between doing all that myself or having Visual Studio do it for me and then I'm not that crazy about the test high project hierarchy is that's a pretty small price to pay. Oh you think? Yeah. I think. Gosh trying to please everyone that's the that's the real gotcha yeah we're definitely taking a look at how to make test generation a lot easier because that is always a top ask in the testing space. So I'd love to incorporate more IntelliCode like features and actually use machine learning that because IntelliCode is a lot different from IntelliTest in that IntelliCode looked at 2000 open source dot net repositories that were out in the world and IntelliTest is just sort of more of a logical analysis of what cases you might hit and what would be good test data to plug in but if we took both of those and combine them. Like I test you know method per string message right yeah right then and there Visual Studio goes oh well I wonder what happens if the message is null oh I wonder what happens if you know whatever there's a couple things I mean IntelliTest is doing that right yeah in one big pass when I run it I'm just thinking that you would be cool if you had that kind of going on at the same time. I agree. In a future version. Keep working on it stay tuned for Visual Studio 2019 yeah. That's not a promise though. No. All right. Did it sound like a promise? No it didn't. I can't make promises. It didn't. I'm just a PM guys. Cool. So cool stuff. Thanks. So all that stuff is shipping today yeah additional enhancements that we might see in 158, 159. Wow. I didn't prepare any future looking stuff. Yeah we're thinking of we're always thinking about better test explorer design so stay vague about it but yeah there's a lot of asks that we've gotten especially targeting multiple frameworks and how the test explorer handles them today is not ideal. So that's a popular ask so getting a new like group buy that is by multi-TFM or something like that could be really helpful. All things we're thinking about it no promises. Okay. And then what's the state of how this works with .NET framework versus .NET core and what about potentially other languages you might be using? Yeah a top ask is for making and tele-test work for .NET core because I did mention it's only for .NET framework right now. That's definitely something we're thinking about in the 2019 timeframe. Okay. All right. It's on our plate. Okay. Cool. Well I'll keep you posted. I'll have you back when there's something to show for sure. Thanks for doing this. Thanks. Yeah this was fun. Hope you enjoyed that and we will see you next time on Visual Studio Toolbox.


Hey everyone, welcome back to Nintendo Prime for a special Sunday video. Now, this video is dealing with some rumors.  I don't really consider anything that's completely unverifiable to be a leak, although I know that kind of loses its meaning. It's whatever. I wanna remind you that we are giving away a Nintendo Switch OLED, a PlayStation 5, or an Xbox Series X. It will be a current console of choice to one lucky winner. Just go check out the Gleam.io link down in the pinned comment and the description.  All right, we're talking about Breath of the Wild Tube rumors here, and yes, they come from 4chan. So if you wanna click off because of that, it's cool. I get it. I don't hold it against you, but I do think these rumors are interesting just because they present some semi-believable information. We do get legit information off of 4chan here and there. I'm not gonna sit here and pretend that it's even remotely close to even 50%. When something comes across that feels believable, we'll talk about it. I also wanna know before we talk about these rumors that stuff from Zelda basically hardly ever leaks. It's pretty rare, especially before there's gonna be a major showing of the game. But this does come from a 4chan user that claims to have played it. Maybe they're part of the testing team. Usually if there is going to be leaks, it would come from the QA testers. So I guess let's just go through these rumors. It was all collected up by a user over on Reddit, so we'll go over the Reddit post here and here's some footage and let's just read these rumors. All right, reason that the Master Sword is not with Link is that it was returned to the Korok Forest, which is now floating in the sky. The game difficulty is about the same. It's not really harder or easier than Breath of the Wild. More traditional dungeons as well as replacements for shrines, which are even older runes located all over the world. Setup is just like the first game. However, there's actually a more dramatic introduction to the game. Mostly the same enemies with some evolutions and the music is still simple, but for some reason sounds out of tune. There are new underground enemies that can play around with time mechanics. I find that to be interesting. Items still have the same durability, but there are some enemies that have a time reversal mechanic that ends up with your weapon healing each time you strike them. The plot revolves around time manipulation and another dimension. We've actually seen this in Zelda before. We've seen time manipulation and other dimensions. So I guess that's not really a new concept. The green arm is a motif for courage. The arm is the last power from a sage that gives you new mechanics. And I find that to be rather interesting. I think all of us felt like the arm is something you get early game and replaces maybe the Sheikah Slate. So kind of interesting. Zelda plays a role in character swap mechanics. She's in another dimension and you have to switch characters for puzzles to influence the regular Hyrule Overworld and vice versa. Lots of teamwork between Link and Zelda. Also Link has, or Zelda has the Sheikah Slate. No real combat for her from what was played. Mostly stealth and puzzle solving for Zelda. No gear, inventory, just materials and quests. This is obviously interesting because the Sheikah Slate abilities aren't with Link. At least we haven't seen them in the trailers. We haven't even seen them with the Sheikah Slate and the Sheikah Slate was originally Zelda's. So it would make sense that she has it and that there's some sort of play between the two. It's been a hinted at but never really thrown in there. Obviously, we've had games in the past play around with Zelda being partially playable, things like Spirit Tracks. But yeah, I think this is gonna be a rather interesting change assuming that any of this is actually true. All right, Link only uses the new powers from the sages while Zelda uses slate features from Breath of the Wild One. Lots of Ocarina of Time references. I mean, I guess if you have time manipulation, it's hard not to reference one of the biggest time manipulation games in the series. Identity of the lead sage should satisfy you, whatever that means. We obviously have no idea. Also, there's a surrealist tone and kill the past story about champions taking the place as new sages with more traditional Link, Ganon, Zelda plot, which I think the champions becoming sages is a fairly common presumption because the champions really seem to fill the role of sages just in a more interactive way in the original game. So it would make sense if they were actually becoming sages or did become sages. But again, all, I don't know, do we call it speculation? This person claims to have played the game. So there are six total dungeons, which is probably a decent amount. I mean, I know some people wanna see like nine, like Twilight Princess or something, but six along with things that replace shrines, I think that's gonna be plenty, especially if they're really massive like the old dungeons used to be. See, it takes place immediately after Breath of the Wild, one which that shouldn't surprise anyone, never saw Ganon, but from what he saw, he can understand that the undead form of Ganon is invincible and Link and Zelda have to work to restore Ganon's physical form to be able to injure him, which I find interesting because if he's undead and you can't harm him, but you're gonna restore him to a physical state, so you can harm him. Once I just make him undead again, which means you can't harm him. Seems like a catch 22. Be very interesting to see how they handle that in the plot. Yeah, maybe you don't kill him. Maybe you just see in the back of the physical forms you could reseal him. I don't know, there's gonna be some interesting things there and let's not pretend that there's never been plot holes in the Zelda series before. Bolson dies and now is a ghost who gives hints like cast from Breath of the Wild 1. Very interesting. And when Astel is three things that weren't in the trailers, he replies, there's a landmola that are like the size of the two horses that burrow between sky islands, double sword weapons and a power that both slows time and speeds up Link. So that's very interesting. Obviously, all of this stuff sounds extremely plausible and possible, but isn't even gonna end up being true. I mean, if it's just guesses, well, I mean any sort of, any part of this guess could end up being correct. If it is someone who's actually been QA testing the game, which they do have QA testers all over the world, not just local in Japan, especially if the game's coming out this year, there's gonna be a lot of QA testing going on right now if it's actually coming out this year. Yeah, it's possible to see leaks like this and 4chan is probably the only place you would see a QA tester possibly leak anything because it's impossible to track. That's the one neat thing about 4chan and why we do sometimes get some legitimate massive things leaked at 4chan is because it's impossible to backtrack a user on 4chan. Everyone is anonymous. There's no IPs logged, nothing. It's a very much the safest place to leak things without getting busted. That being said, obviously if this stuff is true, that'd probably be an internal investigation from Nintendo to try to see who's been on 4chan. But if they're smart, they were doing this from a separate computer in their home that Nintendo can't touch. All I know is this is really, really interesting to just think about if this is true again. I can't sit here and be like, you should believe this.  But also it's completely okay to just imagine the possibilities. You know, I think of a possibility like Zelda actually being playable and needing to work together between two different dimensions.  What is going on there? There's new enemies in the underground area. What are those new enemies? You know, what about the sky? We saw new enemies in the sky, but that was also in the trailers. So maybe that's why he wasn't. It's gonna be really, really interesting because you didn't really provide an explanation for why things are in the sky, right? I think that's probably one of the questions I would had is, hey, why are we in the sky in the first place? Okay, so the master store was put back and that somehow raised, you know, the lost woods or whatever up into the sky. Fine, but why are things in the sky? Maybe that's something this person doesn't know yet because that could be a late game thing. As he said, he hasn't actually ran in to Ganon or Ganondorf at this point, but the plot line does revolve around it. As he says, a traditional, you know, Zelda plot line of Zelda, Link and Ganon, which I mean, I don't really, I mean Breath of the Wild was sort of a traditional plot line so much in that it was Zelda, Link and Ganon as well. Just Beast Ganon, Calamity Ganon, whatever. I don't know. So it'll be really interesting to see what happens there if he just went Ganondorf. I don't know, this looks so cool. Like, I couldn't at times not my favorite Zelda game, but I do like a lot of the elements that are in that game. I'd like to see them. I think a lot of long times, Zelda fans would really appreciate that. And things like the game difficulty being about the same is, I think just right. I think the game difficulty in Breath of the Wild was perfect as is. Although it would be cool to see the master mode included without needing to buy DLC, like unlocked when you beat the game or, you know, in my opinion, just available from the very beginning because it's a difficulty setting. So why not just let us have it? But, you know, that's neither here nor there. I do like this. The game obviously has been in development for a very long time, just as long as Breath of the Wild without the need to build an engine or an art style. So without the need to build an art style or an engine, I'm very curious how much they put into this. Obviously we have to realize there was a pandemic and that could have caused some delays as well. But man, I'm really, really excited for this. I hope that there's some truth to this just because it's so exciting to fundamentally talk about. But also, it's nice to know nothing which really feels like that's what we know about Breath of the Wild 2 at this point. Link's in the sky. He's got a shiny yarn. He's got some new powers. And that's about it. Everything else has been speculations because Nintendo's been very good. We don't even have the title. Like I'd be very curious, does the person know the title or maybe the QA testers don't because the demos don't have a title. They're just calling it the sequel to Breath of the Wild or Breath of the Wild 2 or whatever. I'm very curious how this is all coming together and if any of this is true. And if this is true, this does mean there is a QA tester leaking things which means we should find out much more information later this year as they get to test more parts of the game. Cause if you didn't know, QA testers get to play through the entire game but they play it in chunks and segments as development's going. And right now, if they're in the home stretch I would imagine this QA testers are gonna get to play all the way to the end probably at some point this summer. Anyways folks, I am Nathanne Robledance from Nintendo Prime. It's been a lot of fun dropping a nice Zelda rumor video on the weekend. Gotta love it. Now if you don't mind me, I need to go get back to Pokemon Legends Arceus because that game's out right now. We don't need rumors for that. It's amazing. It's fun. And for my money, the best Pokemon game I've played in my entire life. And I mean that and I haven't even beat it yet. Alright folks, catch you in the next video.


Hello everyone and welcome to Blackstar Potential. My name is Lee Fuge and I'm here to do with MusicTeacher.com and in this video we're going to be checking out three classic red hot chili peppers riffs and checking out how to dial in some of those John Friscianti style tones using only the St. James 6R6 and Cabrig. All of the tones you're hearing in this video are coming from the Blackstar St. James 6R6. The settings I'm going to be using will appear on screen right now. I'm actually running the amp on the drive channel but with the drive set very very low. These settings will get you in that Friscianti Tonal Ball Park. He's also known for playing many different guitars but predominantly he's associated with a Strat. So I'm using my early 1980s Tokai Strat for this. I'm staying on the neck pickup for all of the examples you hear. If you enjoy any of the tones you hear in this video you can download the patches for Cabrig down below by hitting the link in the description. Put them into your own St. James Cabrig set up and use those settings that came up on screen from the top of the amp to get you in that Friscianti Tonal Ball Park. So what we're going to do now is we're going to check out three classic chili peppers riffs and the tones that go with them. I put each of these tones into a mix with other instruments to give you an idea of how it sounds in the finished track and you can let me know at the end of the video how close you think I got. Like I said you can download these patches yourself and try them out in your own set up too. The first one we're going to check out is the tone for the track California Cation and it sounds like this. So now we're going to jump over into Cabrig and find out how I got that tone. So Friscianti usually uses a pretty simple amp set up. He definitely favors a combination of Fender style guitars especially Strat's plugged into British voiced amps. Now even though the St James 6L6 is predominantly leaning towards an American voice because of those 6L6 tubes, the drive channel does actually have a slight British voice to it. So we can really get quite close to some of these Friscianti tones. So let's head over to Cabrig now and you'll see that I'm using a pair of 4x12 cabs. Now these are pound hard left and right so if you listen to this with headphones you'll hear each of these cabs left and right. The cab on the left is a 4x12 classic UK. So again going with the British voice here and on the right we have a modern UK ceramic. Now Friscianti doesn't really use any modern gear. He's definitely more of a vintage tone guy but for this track I definitely found the modern ceramic speakers gave it a little bit more of a top end sparkle for this particular riff. Now this is completely dry so we've got no reverb on this. It's a pretty dry sound. The first cab is spiked with a 414 condenser mic and the second cab is mic'd with a 421 dynamic mic. So we've got those dynamic mics they really give a nice full balanced sound and I've also applied some EQ treatment to each cab as well. So the first cab we've got a low cut at 155 Hertz. We've got a slight scoop here in the low mids just taking some of those out and really bumping up that top end to get some sparkle and the high cut is actually set at 13k. The EQ for the second cab is even more extreme so we've got a low boost and a high boost with even more scoop in there in the mids. The high cut set very high here 15k and the low cut at 144 Hertz and I've also applied some EQ to the master bus. Bring the high cut back to about 8 just to shave off some of the additional top end that we don't want that we got by boosting the cabs and then again a slight scoop there in the lower mids just to clean up the tone a little bit. Now Friscianti did have a slightly scooped tone this just kind of replicates what you would hear on the recorded version of the track so that's why I put that EQ on the master bus to kind of simulate the treatment that the recorded guitar tone would have gone through in the record making process. The guitars might not have sounded like this in the room but by the time they hit the record that is what happened to them. The second tone we're going to check out is from the track Can't Stop and it sounds like this. So for this tone we have a slightly different approach if we head over to cab rig we're actually using some different cabs here. On the left we're still using the 4x12 Classic UK but this time it's mic'd with an SM57 mic. The dynamic mic is great for capturing really punchy and percussive guitar tones. On the right side we've got a 412 vintage now this is definitely more in line with John's vintage vibes and the sort of gear that he prefers to use. This cab is mic'd with a 421 dynamic mic once again just to get that nice big round sound. EQ was on the first cab we've still got that low mid scoop very very important to get that scooped sound even though this is the British voice we still want to scoop it back a little bit and again the highs are pushed and the very same thing on cab 2 this is actually the same EQ settings as the first patch we've got a bit more of an extreme scoop just the different shape between the two cabs and the master bus is actually a lot flatter this time so you've got a very slight scoop in the low mids but everything else is more or less a round above zero so there's nothing too extreme going on there we do have a medium room sound for this one running in stereo just blend it in about six and a half dB below unity gain so just a little bit of space there and obviously you can add more space to taste if you want the third and final tone we're going to break down is from the track Danny California and it sounds like this so for this one i'm actually using exactly the same cab arrangement so on the left you've got the 412 classic and on the right the 412 vintage mics are the same as well we've got a 57 on the left and a 421 on the right now what is different here is some of the EQ sets so the first cab is a lot less extreme now in terms of scoop we've only dipped the low mids by about a dB and a half and the highs are only boosted by about two and a half dB just a little push there on the top end and then the second cab's EQ is much flatter but there's actually a bit more of a low end bump here just to give us a nice round sound to this track with a very very slight high-end boost as well then we've got the room we're using a medium room here which is blended in quite a bit more we're just below zero dB there just to give a bit more space and then on the mass 3q we've actually got quite a scoop on the high mids so this track is actually very kind of low mid focused it's quite punchy it's almost like a Hendrixy type sound so the lows in the mids are pushed a bit to give it a bit more of a percussive sound the high mids are brought down a little bit just to retain a slight bit of that scoop and we don't want too much brightness in this riff so the highs are actually brought down by about a dB and a half and we've actually got the high cut set to just under 8k for this so we are sweeping off quite a lot of the brightness there this guitar is very sort of Hendrixy it's very mid focused and quite percussive sounding so we don't want too much going on in the top end so there's a breakdown of three John Froschanti style guitar tones using just the same james 6x6 and cab rig you guys can use these patches yourself that all link down below in the description you can use them as standalone patches or jam along with your favorite chili pepper songs like I've done in this video let me know what you think of the sound of these patches and let me know how close you think I got Froschanti predominantly sets his amps quite clean which is what we've gone for here and obviously in different chili pepper songs you can stack up different effects John is a big fan of things like overdrive and fuzz but in these particular riffs we focused on just the call clean tones if there are any other artists you guys would like to see us make these videos about and dial in tones in the style of using the saint james amp and cab rig let us know down below in the description don't forget to check out black star amplification on youtube for more videos just like this and like I said the patches are down below in the description if you want to download those go and hit that link and put these into your own saint james cab rig setup and if you're looking for a guitar teacher in your local area please check out musicteacher.com it's a great network of teachers all around the country waiting to help you guys out thank you so much for watching and i'll see you very soon


Hello there, ladies and gentlemen. I thought I might take a look at a particular scene from the MCU now that Phase Four is in full effect. I think it would be fascinating to compare not only how much the writing discipline has changed, but how much can be achieved when using every last word on the page to your advantage. So let's go with a familiar character. We can talk about why she's so effective. Natasha Romanov is incredibly formidable because of her creative, yet grounded thinking. Perfect for solving problems that would likely have killed her otherwise.  To fully illustrate what's been lost, let's compare an aspect of her abilities that should be top notch as it's specific to her training and she's practiced it for decades, making her a master. Natasha conducts two interrogations in The Avengers. One in her opening scene and one with Loki. She also conducts one in her own movie, taking place in the third act with Dreykov. Let's compare that opening scene with the Dreykov scene. The first thing we see happen is Natasha getting hit, to then express to the audience frustration and boredom. Only to her captors she poses as very much afraid and completely out of her depth. Her captor then makes an assumption on who she's working for. Whoever Salahub is, Nat needs information on him as well as the lads here. By posing as an agent with poor information, misplaced confidence and a subtextual admittance that the interrogator is correcting her, she's coaxing information she may otherwise come across as desperate for. As a form of boast, the captor is telling Natasha that Lementov is not the man who moves their materials and that she has outdated information, prompting the correction. He's asking that Natasha pass this on to her boss. Of course she's lied about having a boss that isn't shield, while simultaneously trying to come across as having given that up by accident. Only Coulson interrupts her and her glamour drops, talking to Phil in a completely different tone, surprising her interrogators. And this is the climax. We have a complete demeanor change from Nat as she speaks to shield, chastising them for interrupting her work and insulting her captors for having given her what she needs. This is Natasha Romanov, creative, resistant, fantastic under pressure, superbly intelligent, manipulative and of course seductive. This scene completes with her dominating her captors, grabbing her shoes and revealing she was conducting the interrogation the entire time, only to be told she has to see Bruce, giving her pause for thought. A wonderful juxtaposition to how bold she just was, assisting the audience's understanding of the Hulk and his reputation. Now, let's take a look at her solo movie. The interrogation opens with this.  An interesting choice when dealing with Draykov, the man who for 30 years plus has controlled the most secret espionage institution with a deft hand having complete victory within his grasp. But let's see what happens. Again, she focuses on belittling him, a single track that if fails leaves her with nothing.  All she's highlighted is his success, a success she shares in her line of work, being that she is desperate for people to never know what she has or what she's capable of. He has control of a major empire with the potential to control every single person in the world. I would say that's pretty incredible. More so when it's being conducted entirely in secret. Yet that very element is what she's trying to shame him with.  And to add insult to injury, Natasha is doing this to the guy who organized the entire system that taught Natasha how to do this in the first place. In a way that's the saddest part. Why wouldn't Draykov announce that this is the most embarrassing display he's ever seen? That in his many decades of teaching Black Widows how to siphon information from a subject without their knowledge, he's never seen such a sorry attempt. In a way he's ashamed she would try. She could then evolve the conversation into a meta back and forth about his guidance, his teachings, and the program itself.  When he either oversteps defensively or the interrogation fails, she could realize that being sincere about her own history is exactly how she can get to him. There were so many options here and instead of any of them we did this.  This made him upset, and like any king of the incels, he spilled his entire design to her, on top of revealing the access requirements. He gave her everything in the hopes that she'll say something positive about him. You can see the writer's hand throughout this scene.  The only thing we need to finish this off is her spelling it out. And that's pretty much it.  It doesn't even line up with the film's own logic. She's telling him the problem is that he's achieved it without people knowing. And his response was oh yeah, well look at just how much everyone doesn't know. Like if we're pretending she made a good point, which is how he feels, then he didn't counter it at all.  In this instance she got punched and says you're pathetic. And it worked. She is rewarded for her brain dead approach, telling her subject what she wants while using absolutely no tact, no physical expertise, and no manipulation beyond getting incredibly lucky. And that's on top of the luck of seeing how to access the console. Had he faced away from her while accessing it she would have been fucked. In the first scenario the subject doesn't even realize their own taunts have provided information.  Natasha Romanov in terms of her abilities as Black Widow has been completely reduced, from her general intelligence to her battle plans to her primary abilities of manipulation and interrogation of subjects to even her combat have been crippled significantly, or entirely stripped away in the movie that's supposed to be all about her. It's a huge shame because these elements help give her an enormous impact on screen, especially in the Loki interrogation. Alright enough, let's break that scene down.  And it's far from the only one in The Avengers, one of the strongest movies in the MCU. Loki has been captured by SHIELD, and they want to know why he gave up so easily, as well as where he's taken the Tesseract, leading us to this scene. We open nice and subtle with a smile. The God of Mischief, a king of illusion appreciating a human's ability to surprise him with her arrival, and an appreciation from Natasha that Loki is smart enough to know she was on the way. Not just because this is one of her roles in SHIELD, but because she has an investment in Barton, and Loki has been privy to Clint's insight. It's clear he is excited to have this exchange. So, this is pretty good for a few seconds. Both parties understand that Natasha needs information from Loki. However, Loki holds all of the leverage in this conversation. He has nothing to lose while having everything to gain in causing this stalwart woman who has taken down so many in this very environment, a lasting moment of anguish. Something hundreds of people have likely failed to do, as is her reputation, giving him an increased sense of purpose at this stage. Because Loki, despite ideas from future writers, does indeed adore causing pain and fear. This is the opening gambit. Natasha lets Loki know she cares about Barton more than the end of the world. A declaration that likely has a lot of truth within it, so he counters with a barb about love triumphing over all. A concept they both find childish compared to specific and meaningful investments for a person and your history with them. She goes on to explain when he asks that Barton saved her and set her life on a lighter path, that before him she didn't care who she hurt. This is quite a blatant yet prompted explanation, giving the audience much more of her history to chew on, but it's entirely warranted in that it supports her opening and Loki is left with one response to confirm Barton's value to Natasha. Loki is now very excited, knowing that Natasha cares more for this man than herself, shield or the world.  This is engaging for him because it means he can dig deep into her. If he says the right thing, she'll be distraught and terrified, but like any power dynamic flip, they hit harder with the soon to be victims sitting in some level of comfort. This is her completed bargain, she's at the peak of her confidence and she's made it clear that in exchange for something, Barton must be spared. She's also provided a motivation to convince him she is telling the truth alongside a brief history topped with a desire to wipe said history of misdeeds, ones she's only alluded to. Natasha could be given the information she wants here to then reveal her lie being that she won't help Loki at all and that she merely tricked him along the way. Only Loki is a lot smarter than that and he's ready to spring his trap. Now the balance has shifted significantly. Loki has revealed he knows far more of her history than she could have accounted for, that he was just humoring her in the prior half of the conversation.  Loki then strips down shield and humanity as a whole while we pan through the avengers realizing that shield has lied to them. He does however make it clear that it isn't simply her history or her organization, it's her existence alone that's enough for condemnation. He charges forward smashing her sharp build up of confidence and with his knowledge of her history as well as Barton's makes a very convincing threat of having Barton torture her himself in ways he knows will be effective. Natasha is horrified and Loki completes his counter proposal and then he'll wake just long enough to see his good work and when he screams I'll split his skull. The choice of words to split Barton's skull after his good work is complete ends a very complex and terrifying description of what he can do to her through his own puppet, the man she cares so much about. Loki has finished his interrogation, he's struck Natasha exactly where she lives scarring her for an indefinite time giving him the satisfaction he wanted from the outset. We have flipped the dynamic of power and the payoff is now complete but the scene isn't over.  He further detailed the nature of his victory, the agitation and release of the monster, which as a plan is entirely close to completion. What he says is a simple jab. He's not the monster, he's the truth seer. The big green psychopath spawned from the human race is the monster and the fact that this is what he has to say in relation to Banner tells us how he views him, making certain payoffs to come that much more satisfying. Regardless, he gave away just a bit too much when celebrating. Loki hasn't yet understood what just happened, it was too quick. He's still under the impression that he won, but Natasha's new attitude doesn't match that whatsoever. And now that it's dawned on him, Loki won't even look at her as she leaves. He's now realizing what he just gave up and that his plan could be compromised as a result. That small dopamine hit of torturing Natasha wasn't even close to worth it, which completes the leverage being switched once again in one scene. It shows us exactly who these people are, two powerhouse intelligent characters at their best, acting in ways that bolster their values, progressing the plot significantly and providing introspection for them both in the future. Being capped off with what could have been an awesome catchphrase Natasha could land on anyone she defeats in this environment. Instead, it's pilfered in an attempt to evoke a better time.  This, however, is one of Loki and Natasha's greatest scenes. It's from a story that wanted to boost them both as characters while clashing them in such a way that damage hits both sides.  And it only gets stronger as the movie progresses. One could ask, how did Loki manage to fall for Natasha's ruse? How is it that she convinced him it tore her up? How did he fall for it? It was real. Loki did do the damage he thought he dealt, hence his confusion. Natasha was convincing because she felt it. She's incredibly invested in Clint, not just as a friend. He represents what gave her a chance to become a better, stronger person. A hero. Her identity is tied to him. She is, however, experienced enough to compartmentalize this. She got what she wanted, and she did what she could with the information, only later does she reconcile with what she felt. The scene is incredible because both characters were simultaneously victorious and damaged. The power levels shift throughout. These two highly skilled individuals were represented perfectly. The Avengers is one of the greatest installments of the MCU, and it's a shame that one scene from that film is better than anything Marvel has produced in years. And that is why the Loki interrogation scene is my one marvelous scene.  Assisted in fruition by the people at makeshift, I have finally converted the long man into a far more cutesy and approachable form. Esports a suit and tie, a dual filtered gas mask, a rather sunny disposition, and tentacles to grab those hard to reach movies from the shelf. If you want to have your own little long man to watch movies with, then please visit makeshift.com forward slash products forward slash mohler dash plush. These things are on a timer, so you may want to hurry if you want one. If you do, don't forget to pick up rags as well. The most adorable doggo in plushie form. If you add both a mohler and rags to your cart, an automatic 10% discount will be applied, and with them both you can complete the every framer pours first generation plushie set. Depending on if you folks like these, we will happily consider getting a second generation going next year. So grab them now. Again, you can find a long man at makeshift.com forward slash products forward slash mohler dash plush. A link for both will be at the top of the description.


And thankful for the life that I get to live and experience with the awesome family that I have. And I'm just so thankful that this organization has the faith and trust in me to get this deal done and to lock me in for the future here. It's just an awesome feeling. Obviously, the security is something that you wanted, but how important was it for you to stay intact with the other guys on that front, being as though how well you guys played together? Oh yeah, nah, it's awesome. We were just talking about it. It's just awesome, man, because the football part plays a big factor in it, obviously. But it's just the people here, man. It's just so awesome. That's one of the main reasons why I wanted to come back here is just because when I walk into that locker room, it's not just guys that I work with. It's like best friends, you know what I'm saying? And to be able to stay here and be able to continue my career here and going out on that field with them and going to work with them, it's just awesome. And I'm just extremely thankful to be able to come back and keep grinding with them. Carol, I know in the movie, I remember Moneyball, they said, it's not always what the money is, but what the money says and says about you. How important is what this money says about you and your career?  And, you know, I feel like that's the player I am. And I just feel like, you know, this contract says that, you know, that they believe in me and they feel the same way. And like I said, I'm just extremely grateful and thankful, you know, for all of this.  With you back kind of in the fold, what do you think is the next step for this front four that you guys have? How much room for growth do you think you guys have? There's always room for improvement. Really, you know, I just said, you know, if like for me personally, I'm picking one or two things that I know I can improve on going into this offseason while also enhancing things that I know I do well. And you know, I'm sure the coach is already working on it. And I know for a fact, you know, that we're going to go over the things that we did well, but also the things, mainly the things that we know that we can improve on to take this group to the next level. You know, I'm excited for that. I'm excited to come back and get back to work and being able to take that next step as a group. Versatility and all the Titans have asked you to do with being able to drop and rush from so many different positions. Do you feel like a defense like this is one that is maybe built well to maximize what you can do? Yeah, no, I feel like the coaches do a great job of putting all of us in positions to succeed. I feel like the coaches, you know, they have a great understanding for everybody's skill set on this defense. And you know, I feel like they maximize our skill sets. But yeah, no, I mean, I just feel like I'm a guy that can play in any defense, you know what I'm saying? And we can line it up and play a normal defense and we can go make I can go make plays or, you know, we can do some multiple things. So we'll see. When you first got here, I guess four years ago, just what how you wanted things unfold and have they kind of unfolded like you had hoped to maybe even better? Yeah, no, I mean, I feel like these past four years, you know, they've been amazing to be honest. If you look at the big scheme of things, obviously there's ups and downs.  And I feel like I've experienced a lot in my four years here and it's done nothing but take me to the next level and kind of like just make me a better player for it. But now these past few years have been awesome. I feel like I've grown so much as a player and as a man, to be honest in these last four years.  You mentioned as a man, so I guess how have you grown as a man and also as a football player? I would say just like in life, you know, I feel like when I first got here, you know, I used to take things like so serious.  Like I had to take a step back and just realize like how blessed I am. You know, the family that I have, the two kids, Grayson and Holly and my amazing wife, Danielle, you know, coming into this league, you know, my first year in the league, I used to always just be so hard on myself. But now I'm just like seeing, you know, full picture of just like how blessed I am with the people that I have in my life and, you know, the experiences that I get to experience. It's just awesome. And then as a player, like I've just grown so much like run game, pass game, hands, set in the edge coverage and pretty much honestly to from a mental standpoint just like understanding situations. That's something that varies as a great job of teaching. I feel like that's something that I've grown in over the years, like the game has just slowed down for me. You know, I'm seeing formations easier that the offense come out in which triggers like something in my head saying, oh, this is a pass or this is a run, just stuff like that. Have you visited Nashville before you came in? You maybe came on a visit here, but before you played here, do you spend much time here? And what's it been like living here? How much does the city maybe embrace you and how happy you are that you don't have to pack up and go somewhere else? Yeah, no, I was never, I never came here before my pre-jump visit. But yeah, no, it's been awesome living here. Like I've said before, you know, that's also one of the main reasons why I wanted to come back here. My family loves living here and I love living here and love playing here. But yeah, no, it's been awesome. Where we live at on Old Hickory Lake in Mount Juve is awesome living out there. But I would say the biggest thing is just the people, like the people here are awesome. You know, they've embraced me ever since I got drafted, stuck with me through the ups and downs. And I just feel like it's the people here that make this place awesome. Do you expect to be back? I mean, to be honest, you know, all the talks that I had with my agent, shout out Tommy Khan and CA, best agent in the game. But just talking to him, I was confident, you know, that I wasn't going to leave Nashville. Like, regardless of the tag or anything, like, not because, you know, I knew what was coming or anything like that. I knew how much I loved being here, and I knew that I was going to do whatever I had to do to make sure that, you know, that I came back here. So I wasn't thinking about it after the loss to Sensi, but when things started heating up, I just knew deep down that this is where I wanted to be.  You can kind of move on from that? Uh, yeah, no, I mean, I don't know. It's just, it's nice. I'm for sure to have this locked in and down. And now it's all about ball, just focusing on ball and improving my craft this off season. And I don't got to worry about that. But yeah, no, I mean, it is nice having it done. A lot of fans have been rejoicing about the fact that not only will you be sticking around, but you still got Danico, Jeff and Bud, beyond just your talents and abilities as a group before, how nice is it going to be to develop that communication, that being on the same page that you guys did so well last year with stunts and things like that? Oh yeah, nah, it's really important. I feel like as the year went on, even starting in training camp, I just feel like as the year went on, we just got better and better as a unit and we started playing off of one another more and more consistently and efficiently. And I just feel like that's when we were all at our best and we were all playing together. And you know, yeah, I just feel like we just grown and, you know, this continued time now is just going to only enhance that. Oh yeah, nah, we're real confident that, you know, we have the team to go out and win a Super Bowl. I think our front four can lead the charge, but I just know deep down that's another main reason why I came back here is because the culture here is a winning culture, it's a proving winning culture. And that was really important to me because we know we have the team to do it. It's a bunch of past rush the last few years and then the way everything started clicking this last year. Do you really, you said front four can lead the charge? Do you really feel like this is, you guys can set up to be the strength of a team that makes a run? Oh, no question for sure. Like we got some dogs on our front four and I just feel like none of us are ever content. We're always hungry, always looking to improve. And I think that's the most important thing is that I think all four of us kind of share that same mindset to where like when we step out on the field, we want to be the best players on the field. And I just think that that's a that's a characteristic you need to like lead the charge and to to have that impact on the team to go out and win a Super Bowl. As a provider father, husband, what's it like to be able to present this to your family? It's awesome because people that know me know that my family is the most important thing to me. So like, I don't know, it's just like, it's just like I'm just so speechless because like it's just I'm just like so like it's just like it's not every day you're signing deals like this, you know what I'm saying. So it's just like such an unbelievable feeling. It's like, it's like I look at and I'm just like, damn, like, all I can do is just thank God, you know what I'm saying? Like, I'm just so thankful and blessed. But like you said, like my wife, Danielle has been such a major factor in my career and in my life. And I'm just so thankful for her and my two boys. You know, they're the main reason why I do all this stuff and why I work so hard, you know what I'm saying? Because I just want to make them proud and and to make them be proud of their dad and her husband. But no, it's definitely an amazing feeling to be able to go home and to be able to celebrate this with them. The doctor cleaned out the priest said they need to sign you today. Kevin Byrd said he'll take a cut.  And were they in contact with you throughout the process? Yeah. So that's honestly one of the most like amazing feelings to be to see guys like that. I'm in this locker room doing that for me. I was doing the interview not too long ago, a couple minutes ago. And I was saying how like when I'm done with the ball, like, it's not going to be like the money or the stats really that, you know, that I remember, but it's going to be the relationships that I built in that locker room.  You just start laughing about it. Like those are the things that I'm going to cherish. And you know, that's another reason why I really wanted to come back here is because of the guys in that locker room. Sometimes these deals can be a weight on guys. How do you keep this from being a weight on your shoulders? Like I said, an interview for this. I feel like the money is like, like obviously I'm extremely blessed and grateful for this contract. But at the same time, I feel like the money is just a byproduct of the work that I put in to become the best player that I can possibly be. And that's really all I focus on is it's trying to be, you know, when I step on the field, I want people to think that, you know, I'm the best player on that field. You know, I'm saying that's my motivation is to be the best. So I'm extremely thankful, you know, obviously for the money, but the motivation is to be the best.  When you see the AFC getting stronger, you know, particularly at the quarterback position, the Broncos getting Russell Wilson, you know, Burrow, Lamar, you know, just the long list of guys in the AFC. Does that at all maybe motivate you guys even more? Or maybe you can speak more specifically for yourself about just kind of being able to get to the, you know, just impact games. Does that kind of motivate you at all when you see these quarterbacks, these teams kind of getting stronger in that regard? Yeah, no, I mean, we feel like me personally, I'm going to speak for me personally. I feel personally that the game is going to come down to the quarterback and the guys that can affect the quarterback. That's just how I see it. And even before the since the game, you know, I told the guys in the room that I feel like it's going to come down to us and how we can affect Burrow. And that's just how I feel. That's how I motivate myself, you know what I'm saying? So, yeah, you know, we see, you know, all these quarterbacks and taking the game to the next level each year. And we just got to do the same. That's what this game come down to, I feel like, is you got a dominant front forward, you got a chance to win any game. What's the best congratulatory text that you've gotten after you got your deal and if there's not one, what's kind of been the outpouring of congrats like?  Vraves was pretty funny. I'm not going to say any of that, but not probably just my best friend and my family. You know, the people that have been with me this whole time and the people that, you know, were there for me when, you know, I might not have been at my best and was there for me when I was. Those are the people that, you know, I feel like when they reached out to me it meant a lot and the words they said to me meant a lot. John said that he was going to try to do his absolute best to hold on to you, whatever it takes. When you look back at this process, how much faith did you have in the team, the front office and trying to make that deal, trying to keep you here? Was there ever a doubt that that wasn't going to happen? No, there wasn't really any doubt really in my mind. I just, I don't know, I just felt like the relationships that I built here was just so like, so real and then it went past just football. I just felt like, you know, I had a lot of trust that a deal was going to get done. I'm not going to lie. Yeah, I would just say I had a lot of trust. I was confident that, you know, we would be able to get a deal done. Let's go. Thank you, Herald. Congrats. Thank you.