 Today is January 12th, 2021. This is the DevSync for Tuesday. Let's get started. We'll start with Chris, because he's got a double report to make. I do it now today, so I'll be making this report for him, but we're working on kind of the same thing. I got my R5 board up and working today. That's one thing I did. And I'm working with Ken on the microphone issue. Right now, my R5 board is running the latest, well, it was running last night's Panicor build, with a two-par patch from Ken that basically restarts the mic whenever we encounter the issue. And it's been running, my device has been running for a few hours now without issue. In fact, I've also fixed the performance of the wake work tagger today while I'm tagging my wake origin. It constantly makes my device go off. So I think we're in a good place with the patch. And as far as Ken goes, he implemented the patch. And he and I are gonna talk, it's kind of a hack right now, just to see if the idea works. And it looks like it does. I like this run overnight and make sure. But if this patch is working, then we just need to clean up the code that he put in and make it official. So I also submitted a PR today because this is working and I kind of moved off of the device for a while in spite of working on the wake word stuff again. I have a PR out there there for my new materialized view that can make the request four times faster. So that's good. So that's on there for Ken and Ken said he was moving on to the wake word stuff as well unless something else comes up with the device. Okay, all right. That sounds good. Are we benchmarking the full interaction so that we can look and see where we can start trimming latency? Not yet. Right now we're just trying to get it to work. I've got to do the next step. Okay. Gez, how's it going? Yeah, pretty good. We, I wrote a blog post yesterday unintentionally. I had a rant in the community. And so basically someone did a bit of work contributing translations to Lingua Franca but took some stuff from a third party website which basically means that we can't use any of their work. And so that really sucks for them. Sucks for everyone really. So I had a discussion about how you shouldn't be able to copyright a language and everyone was not happy about it. And so decided that we should A, say that and B, try and make that as explicit as possible to the people before they try and contribute to the project so that we don't have it happen again. So this is also a, if anyone watches, like don't try and contribute stuff that is not your own explicitly your own. Other than that, created change the Mark II skill to remove all the listener stuff that Ken has sort of thought might be an issue. But even if it's not, we do want to remove it out of there because we're going to shift it directly into core and the GUI framework, which should improve the responsiveness of it. So between when you say the wake word and when it starts showing the little animation, that should speed up. So I've got all the pieces of that ready to stand to put all together into an image to physically test. Published a video, one of our one of our stratus videos around reviewing PRs to try and encourage and help people to help us out by reviewing new features that may not be the priority for the internal team but that the community really want. And so if we can get help and have trusted people reviewing those, then we'll be able to get those in more quickly. And yeah, helped a number of people out with their variety of projects. Sounds like you've been busy. Yeah. All right. Yeah. Great. So what's next with the, as far as the image that we're putting on the Mark II DevKits? It sounds like all three of you are moving on to other things at this point. So does that mean that it's solid enough to use? So there's a couple of things. Well, so there's the audio stuff and if we've got that fixed then that's a very big step forward. Were you gonna say something about that, Chris? Yeah, it even works on first boot. So the first boot probably more either. Great. So I think there's polishing still to do but I think it's in a demoable state now. So I think we should probably consider doing a demo as soon as we're sure that the kinds of changes are in the image. Because I've been interacting with mine all day and had zero problems with it. So. On the Wi-Fi front, there's still a bit of work to do. So the way that we test for an internet connection in the onboard Wi-Fi setup process to show the onboard Wi-Fi setup process is probably detecting the access point that Panicor creates and assuming that that is an internet connection. And so that's why that screen is not showing up at the moment, we think. But I need to go back and forth with Panicor a bit more on that, that was from a chat with Blue Systems. They're also seeing, Aditya's been doing some work on the pairing skill and improve it in line with what Derek's designs have been and the open voice operating system OVOS, formerly Microsoft OS, basically taking the same kind of path, but they use Balina Wi-Fi. Anyway, they're using the same sort of themes and they're taking a lot of the work that we're doing now and using that as well. But one of the issues that they have raised is currently the way that when Microsoft Core detects that it's not paired, it basically just emits this fake STT message as if a user had said, pair my device and then that triggers the intent in the pairing skill to pair the device. And they've been having some trouble with the fact that that's just constantly happening while you're trying to pair the device and the way that that's triggering that intent and it's kind of messing with the UI for that skill. My assumption is that that is just a very, like the quickest way that it got implemented three or four years ago and has never been changed since. It seems like a pretty hacky way to do it and something that we really don't need to do. So I was gonna have a look at how we can improve that. So there's a few things left in the startup process that would certainly not be a production system. Initially, my screen does not orient correctly on first boot. Oh, really? Yeah, I still get the, like it's standing on one vertically. And my screen turns off after a few minutes, which is the other, no, we've talked about it. And I think they're aware of it. It must be some kind of power save mode they're working in, but... Yeah, it's just like the default, like power save mode. So they obviously just haven't gotten in and deactivated it. If you could tap the screen twice, it comes back on. So I have found that. So I just keep tapping my screen. But yeah, I mean, I think we're in a demoable state, but maybe not quite in a demoable state. I guess I'll go out. Yeah, so that's where I think we're at too. Okay, great. Well, then we'll talk about that some more, probably tomorrow in terms of priorities. But yeah, continue on with the wake word stuff. We need to get that to a point where we can really make the current wake word solid. So we need to get that process finished off. Okay, great. And Derek. Yeah, so I'll add my two cents on what I think we need to do. Some of this is, like you said, we could discuss like what's acceptable for the dev kits. But as soon as you can get it, so Josh and I can boot it and it just works, which I'm not there yet. I mean, I could do the patch, but I think it's best I just wait until it's in actual. Then we can put it, the Josh and I can put it through some bases and we'll give you like a whole, like I have a ton of stuff that I'd like to see fixed. Like things like the GUI volume not thinking with the mechanical button volume, the sound, it's way too loud to start up. We got to go through a lot of the audio prompts. We haven't really looked at the long happy path stuff and get those new Cusol. We got all these new Cusol recordings that are good, get them all in there. So like when you put in your password wrong and stuff like that, we haven't scrutinized any of that stuff. Yeah, and also the skills are a little behind. I think as I need to go through a process to get the skills up to the most recent commit because some of the screen, the GUI fixes I did and know why you're not there unless you do a get pull. So I think we just need to spend a little time getting the marketplace stuff up to the latest revisions for some of the GUI things. But yeah, I mean, I would say like you guys, once you can get to a point where Josh and I can boot it, you guys can go and do stuff and we can make a list and decide what is important right now and what can wait. That's my two cents on that. So yeah, today I was basically still working on some of the mechanical stuff I had a few tweaks I was still doing on the fan and then noticed some issues with the camera. Just I was not quite getting the feel of view of the camera. It was being blocked by the housing to a certain degree. So how to update that. And then I got some more parts. So I put together another one of the SJ230 laser cut housings and so yeah, I'm just waiting for an image. And I sort of prepped in to take some photos for marketing for the dev kits, for crowd ox and such. Johnny gave me a call earlier about that. And so I got some stuff put together to do that tomorrow. So we'll have some nice photos for that. I actually try to shoot a video showing some differences between the enhanced kit and the basic kit that doesn't include the acoustic chamber. And if we can actually capture in a video, it's not going to be perfect, but the audio difference it might help sell that. So Johnny pitched me on that. So I'll try and get that done tomorrow. Yeah, we're also talking about the fact that one's going to look nice and neat and clean like my desk where I've got a thing in a nice housing. And then this other thing, which is like wires and crap hanging out all over the place. And enhanced dev kit is worth a very small amount of money. Right, yeah, I'll just try and get as much as I can. And I'll assemble it one with everything just strewn about on the table, the regular kit. And then, yeah, we'll have that to compare. One of the things worth noting is that I noticed I switched the speaker out on my R4 board and still had the static key problem. I have not had any static key problems on my R5 board. So I don't know if there was something wrong with my R4 board, but it shouldn't be a concern because we're on R6 now. But worth mentioning I haven't seen, heard any audio issues since I moved to my R5 board. So it's likely not the speaker drivers that was the problem, right? That's what you're saying? Yeah, that's one of the reasons I asked you for a second speaker set so that I could plug it in and see if that changed anything. And it didn't change anything on that R4 board, so. Cool, okay, cool, cool. Okay, yeah, it might be worth sending them back to Kevin so that we can take a look at it. But I'll ask him about that. Okay. All right, Josh just stepped away. Oh, there he is. I have an SJ201 V5 board. Gaz has sent me a link. I am building things now and we'll be bringing it up as soon as I have a, as soon as I can. So that is that. And my children went to school today and that was very happy. All right. And Josh, just based on the conversation, I'll send you a new link in like an hour or something. It's fine, that's taken me a little while. I'm going to assemble it, I'm going to assemble it twice. Once quick and dirty and get it all working and then once I'm going to photograph every step. So. All right. Well, thanks everybody. Will, is there any other topics that we need to discuss? Oh, I just, just when, when will that patch be in the, are they doing nightly builds? Do you think that patch will be in tomorrow? It looks like, it looked, I was looking at the CI pipeline and it looks like it's building in the moment, so. Oh, cool. Well, as soon as, yes. As soon as there's an image that I can just download and it should just work, let me know. And I'll, yeah. My guess is this image is building right now should be that image. Sweet. Cool. Okay. Anything else? Oh, Chris, if you can told me the patch though, I'd be curious to see what, what it is. Yeah, I'll send that on to you. Okay. All right. Well, thanks everybody. As I mentioned earlier this week, I'm going to be pretty low availability for the rest of the week. I will try to make the dev sinks, but if I am not able to make it, then I will appoint somebody in my stead to handle things. Josh has volunteered. I don't know if that happens. I don't know if that, but we'll be able to record them or not. But just giving you a heads up there. So, all right. Well, that's it for today. Thanks everybody. We'll talk again tomorrow.