 Welcome to the Minecraft DevSync, October 13th, whatever day that is, Wednesday. Derek, kick it off. Alright, so I'm continuing my progress through this back on the skills markups. And actually I was doing a little bit of planning for next week. And so I shot off an email maybe 30 minutes an hour ago about two big topics pertaining to our next big upcoming sprints. And I think while we're all together, it would be really great to spend ideally like a day on each of those topics. So the skills interaction and then the music sprint. And the benefit I think on the music sprint is we can actually take advantage of the business team and legal team while they're there because there's a huge legal component of it to have them take a look at all that legal ease and see if we can make sure we're staying on the right side of things. So that's what Chris alluded to. And in the team meeting was, was those kind of sessions, those two sessions so I imagine that we are still going to have a lot of unresolved issues on the skills interactions side of things at that point so just be good to. So to be talking, talking face to face about that stuff. So yeah, I guess we'll I guess, none of us is concrete by the way so we don't have that but I'll do my, my best to mix those times it, you would be able to attend. Is your fun for all activity making mark twos. That that is also something we should do is get something like help them along and give them all screwdrivers. We'll have 10 of the dev kits the laser cut dev kits there. And then there'll be six. I'm trying to get six of the 3d printed prototypes completed while I'm there too so I would love to have a 3d print prototype. Yeah, that's also another goal. So yeah, I don't know that's definitely something I'm planning on doing it like in my own free time in the evenings and stuff but that would be a good activity to, you know, get the whole team together and and do a little bit of as well. So, but yeah, just just to be clear, you know, things aren't things aren't necessarily there. There isn't really a talk to Chris. There's a really hard schedule yet. So if anyone else has ideas, you know, throw my way and I'll try my best to get them in the mix. So yeah, that's what I'm up to. On the school's interaction front, I did that blog post and I just saw it but the idea is, you know, that it introduces the whole feedback process that we want to go through to the broader community. And then we'll release out, you know, videos on a regular basis to get feedback on the interactions that are shown in those. So, yeah, maybe have a look at that if you haven't. Other than that, I did a bit more work on the wiki skill, still a little way to go there. And was mostly merging, working on community PRs and feedback and that sort of thing. Yeah, it feels like we, it feels like I haven't talked to you guys in a couple of days. It seems like we're actually getting through the GUI sprint relatively quickly. Well, we've only got a few things left. So I'm going to do the GUI for the Wikipedia skill. And I'm hoping that we can just reuse the basically the exact same thing for DuckDuckGo and Wolfram Alpha, at least to start with. And then we can sort of tweak it and customize it from there if there's a need. But it might be good enough for this pass of the skills for us to just have the same thing on all of them. And Chris V, since we're talking goodies, do you want to take it from there? Yeah, I just finished the pairing skill. So I want to commit that today. I'll give it to all of you a bit. If you're already paired and may not matter, but you can certainly remove your identity file and repair to see the difference. I did have to remove pagination from it for the same reason I had to remove pagination from the weather skill that was crashing the plasma shell. So it's one page at a time. I mean, I mean, well, it's always one page at a time, but you don't see the little dots at the bottom anymore. Tomorrow, I'm guessing I will move on to the Wi-Fi setup skill, which is very similar to the pairing skill and then it already has a GUI. It just needs to be tweaked to use the new guidelines we use for GUI design. The plasma shell crashing is a concern. When I talked about this, when I did the weather skill, I removed all pagination and I removed all animation from that skill for the same reason. I think I was crashing the GUI all the time. So I almost forgotten about it until I started using this skill and yeah, it was crashing pretty regularly. Do we have a version of the skill that we can point like blue systems to to say, you know, check this out and see if they can dig into it? Yeah, you can pick and use my version. All you got to do is comment out the self.gui.clear that I put in there. It basically clears it before I show every screen. Comment that out. It'll work as it used to. Ken. I'm working on the alarm skill JIRA tickets. So there's different version of the alarm skill on this job there. So I'm fixing that. I dug up the old version and comparing voc files. That'll be done tomorrow, I think. And that's it. I just had a question in general about blog posts. I'm doing a lot of stuff outside of work. Like I'm getting a Minecraft running on a Jetson Nano and I, you know, building the TTS, getting it running on a GPU device and stuff. Is there a place where we post that kind of stuff? Yeah, some of those stuff would probably be helpful for the community if they're trying to run on different devices or getting GPUs working in different environments for different packages. Is there a place we post? We do blog posts or how does that work? Yeah, absolutely. On Minecraft.ai slash blog. So if there's, you know, something that you think would be interesting, then that'd be awesome to write it up as a blog post and share it out. I'll write it up and then I'll send it to you, right? And then you'll, like, proof it and then put it out there? Yeah, yeah. If it's just like a little thing that, you know, you don't want to spend the time writing it into an actual full-on blog post, then I'd still, you know, post it in the forums, for example. No, I just think, you know, instructions for how to get, you know, a Minecraft running on a Jetson Nano with the GPU working and stuff. Yeah, that'd be awesome. Yeah. Really cool. And then there's, like, you know, you got to build PyTorch from scratch and that takes, like, 16 hours and so here's all the little crap you've got to do to get it. No, it literally doesn't. I'd start these things on a night and they're done in the next day. But yeah, I mean, I just figured some of these experiences might be helpful for other members of the community. Yeah, yeah. How's it going on the Nano? So far, so good. The TTS no-go because of incompatibilities, the PyTorch has to be built from source for the Nano because of its GPU and special configuration, even though it's an NVIDIA. So, you know, they don't really have any wheels for 3.7. And then when you go to run that TTS, Coqui Engine, the latest one, that requires, like, PyTorch and Numba and a bunch of stuff I didn't know about before last week, which is cool stuff, by the way, the CUDA compilers that convert Python code to CUDA kernel code. So yeah, I mean, that's incompatibility, so I have to build these massive optimization libraries for CUDA on the target device, because cross compiling doesn't work because the makes pick up the CUDA environment from the environment they're compiling in. These guys, it's like a Raspberry Pi. In fact, Mike, I don't know if you know, but I bought a Nano last week. And the pinout, it's a $49 device. It's basically the Raspberry Pi to the point where the pin edge connector is 100% compatible. In other words, our hat should run on the Nano. Yeah, I remember that we actually talked about this last year in Hawaii, that guy keyed us into the fact that there's a bunch of, like, a one-time supply of Jetsons out there that were leftovers from the Nintendo Switch. So they didn't make that. Yeah, these are the two gigs. These just came out this year. I don't know, it used to be a hundred bucks and they were four gig. This is a $49 two gig. And I ordered it literally, this was weird. Freaking Amazon, they're just, even though I was there, it's still magic. I ordered it at 10 o'clock at night, and I paid an extra 10 bucks for expedited shipping. And it sent me an email and said your device will be there between four and eight a.m. And in a row of it, six a.m. Which is between four and eight. But yeah, the Nano is cool if you can get inventory on them because it probably will run our hat. And it has a GPU. Yeah, cool. Speaking of things, just remind me that the TF Lite plugin, I've been testing that a little bit more. And it is, it works. But it's getting that pulse audio, it's triggering that pulse audio failure. And so that's what's causing the, for it to just stop working at different points in time. And so it is definitely the plugin. If I switch, if I change the configuration to not use the plugin, then no issues for multiple days. And then switch back to the plugin and after some number of hours, eventually it triggers that failure. Has our audio patch discontinued becoming part of our build? No, nothing changed there. Well, then it shouldn't be happening. That's what the whole patch for port audio is all about. Okay, well, I mean. We patched port audio to specifically not generate that exception to gobble it up and just, you know, reset the buffer pointer. Well, maybe it's a different. Maybe it's a different. It's been back for a while. I mentioned it in the dev team chat months ago that I saw these coming, you know, up with the latest build. And this is very concerning considering the fact that this has already been fixed. So it looks like the build has regressed somehow. Unless it's a different era, potentially. But. Potentially. Have you been using it at all? Have I been using the TensorFlow Lite plugin? Yeah, yeah. I had it running on my mark two before I put the new build on, which was like Saturday or Sunday. But it was, as I told you, it was locking up with precise anyway. Yeah, right. Okay. Well, yeah. So we need to come back like, like about a month ago, if you go back far enough in the dev chat, you'll see I pointed it out. I says, you know, this is, this is an old friend that shouldn't be here. Okay. Well, we need to dig into that then. Yeah. Fortunately, I retained the email where I emailed the file to somebody. So I have the file in its entirety. Once a year now, I guess. Okay. We should qualify that they're building the, you know, they may have said, Hey, you know what? The fix was upstream and we hit the upstream and we decided to stop patching. But still, I'm pretty sure we have to double check the build recipe, but I'm pretty sure we have a dead package like just included in the build recipe. If they can verify that, if they can verify that and send me back the source file so I can do a diff on them. Worst case, if necessary, I'll dig into it. So what do you want? You want the source, the actual debt package that we're not the debt package, the source to the file that changed. I think there was two or three dot C files that changed. I mean, there was a dot H, I think, and two dot Cs. It's been almost a year, but I can dig it all up. I'll send you a link to the, to the, where it's, where it's pulling it in. Cool. Is that, that was everyone. We need to paste that down because that's a showstopper. I mean, that basically lock up the system. Yeah. Yeah. You have to restart the voice service. Yeah. All right. Michael, anything from you? No, I appreciate the feedback. I've been getting on the, the interactions document. And definitely looking forward to talking about that. I think that would be a good, good thing to discuss in Hawaii. But I want to also talk about the hiring process and how that's going. It's probably not appropriate to talk about on the recorded part of the call. But I do want to start picking that up. Well, if you want to talk about that now, we can say farewell to everyone else. Bye.