 Welcome to the Microsoft 30th of September. Dobsync me. So we're mid sprint and we're just going to do a real quick check in to see how things are going. There's any blockers or any news. I don't think we need to go through each issue issue by issue, but just give us a quick update. Let's start again with guests. Yeah, so the, I put up a branch with a new Jenkins file to cover across the microflogs when we run like comp. It seems like the going the proper route and using the attachments in a lure is probably going to be far more difficult than I originally anticipated because that's all handled by an independent package. So we'd need to maintain our own fork, which just seems like more work than than we get out of it. If that's not the case, then, you know, but that's my read of it at the moment. So anyway, I've done a branch with a new Jenkins file that I'll test out today. I found a few bugs or actually, you know, figured out a few bugs that or a bug that had been reported previously yesterday. Thanks to Derek running into some audio issues and that sort of uncovered some stuff. So I had a chat with OK about them yesterday and he was going to take a look at them when he got home from work. So I need to go back and see if there's any success there. But they both come down to multiple messages being handling handling multiple messages within the message bus client and basically race conditions around that. So resolution is presumably, you know, better handling of that or ensuring that each call is essentially unique in some way so that, you know, yeah, they can all be handled individually. So assuming those work out all right, I want to get back to taking a look at the lingua franca changes the last few days. So we'll see how I go there. All right, thanks. I'll call on Ken because he just got up now. Let's go. You had to turn the AC down. I'm good. I've got everything integrated. A couple of issues that block me a little bit regarding elevated privileges that I worked around. The point where I'm at right now is the switch handlers need to send out a volume increase and decrease message on the message bus. That's all that remains to be done. And then I'll put a pull request together. I was hoping to have that done today, but I got caught up in some stuff yesterday. The only question I have is if somebody can send me a link to the branch that I should be cloning and creating my pull requests from so that I can get it submitted to the right place. Or at least update or refresh or pull, I guess is the technical term from the proper branch that we're using. Once I have that, then I will create a new, you know, code line and then submit a pull request to that branch. Limited functionality. Not really sure what the activate button should do short of maybe put turning on the listener. But I'm just not sure. That's, that's what we do right now with the equivalent of the action button on the mark one. Yeah, sorry. Yeah, but I think eventually, yeah, we wanted to maybe do some other things, but they're not flushed out yet. I'm trying to avoid a round trip to say, hey, because remember the switch handlers are often they're on in our proteins. I'm trying to avoid a round trip to the message bus to say, what's the current volume increase or decrease it by 10%. So I may actually add a call message bus handler that works off of a percentage variance rather than a percentage value, which is what it does now. So right now you say, set it to 75%, set it to 50%, which is wonderful. If you knew what the previous percent was, but if you don't, then you have several things you could do. I could query the message bus and say what's the current volume setting and then send out a message to change it. But that just seems like a really wonky way to do it. So I'll probably just send out a new message that will say increase whatever it is 10% or decrease 10%. And that'll solve that problem. So I should have that ready to go. And once I have a branch, I'll go ahead and get together. Right. So that's interesting. This is actually coming from the button activation. So we shouldn't have any ambiguity on what that means. If you were to issue a verbal command like increase the volume by 10% or increase the volume to 10%, those could be very different things, right? If the volume is currently at 5%, one of them is going to set it to 5.5 and the other one is going to set it to 10. That's exactly right. But with the buttons, the interpretation, I would think that we should have a very predictable behavior. It just goes up by 3 dB each button press or something like that. Right. Okay, but there is no such thing. You know what the value currently is. Remember, there's three or four places where the volume is getting changed. There's a volume skill. There's a QT mark to skill. There's a Kivi mark to skill. And there's the switches. So it's really not a good idea to try to save that current value in all of those places. I mean, I could have gotten crazy and said, listen for all volume changes, messages on the message bus in a switch handler and update them. But that just seemed like the wrong way to do it. So it seems like the right way is every time you push the up button, it increases it by 10% every time or whatever, configurable percent decreases it by some percent. And let the the destination of that message be the system of record for the current volume level and act on it accordingly. Isn't there a, so there's the switch handler, which is one thing, but isn't there a little bit of driver code that maintains the interface, you know, the volume control on the device itself, right? That's basically talking to you. The best of my knowledge is stored in three separate places, the two different mark to skills and the actual enclosure. But I'm talking about the actual volume setting in the register on the amplifier chip. Yeah, that's that's an I to see it, right? And you can certainly pull it from there. Okay. And while I could certainly pull it using I to see from the switch handler interrupt handler, that just seems architecturally incorrect. Okay, let's take this offline and we're getting too far into the weeds, but that's where I'm at and we can talk about that later. Okay, the detail. Got it. Okay. And so I assume it seems like to have wrapped up by the end of this week and Well, I'll have the code ready to go. I certainly won't be able to test it until I get a working SJ 201 that I can record on and change the volume. The SJ 201 here, the old one probably still changed the volume because the itc device shows up not so on the new one. It doesn't show up at all. But this one has blown mics. So good luck testing volume up and down beyond the switches. Well, you can at least test all switches though. So that sounds like absolutely. Okay, yes. Got it. All right. And then Chris there, you are muted. I'm muted and you're muted. So I got the angular 10. Task done submitted a pull request. Chris took a look at it. I did change the base branch Chris. So Is there anything else you needed for me to. Okay, so if you want to approve that then That will go into the next version of Salini. Then I was going to start on the tagging UI, but after discussion today. I will be going back to the collection. And changing how we name. The audio files we collect. So that'll be my next task that I'll get done this week. So tagging was included. The tagging UI was included in the sprint, but it's not going to. I'm not going to get to it between now and Friday. I'm going to get started after I get this new hashing algorithm done. I will not finish it. Okay. I've got a little helper here. So bear with me. I've, I got a stuff running on the printer for the. SJ 240. So all goes well. We can take a look at that on Friday. I did a little bit more work on the GUI tagger. I'm just, there was a couple of things that we talked about from Monday with Chris and I that were left to wrap up. Although there's, there's a lot that's done. So not, not blocking him there. And it sounds like he's not going to get to work on it until next week anyway. Then I've been sourcing a lot of little things here and there. And one of the things is these little rubber mounts and stuff that I'm using, I'm trying to find some off the shelf stuff to mount the speakers and also little tiny ones to mount our boards and stuff for mechanical that'll, in theory, reduce vibrations and such from, you know, working their way through the chamber up to the mics. So little details like that that I hadn't quite gotten to and won't really be included in the first pass of the first prototype, but I'd like to get to quickly onto the second one. So yeah, that's where I'm at. So let's see. I think the light thing I probably won't get to there's a couple of things with rollover in here that, you know, we're blocked on until we hear from them. And then the the re-speaker testing bit where I was going to make a kind of an adapter to allow the DevKit for the new version and the re-speaker for Apple's Apples. I'm not going to get to that this week. Other than that, yeah, let's be excited to look at the, show you guys the prototype on Friday. Awesome. That sounds fun. Good question for you on the mounting holes change for the latest rev. Would it be completely useless if we had a version of the board that did not have those mounting locations changed? Will we be able to use those boards? Oh, yeah. So they're okay. Yeah, they're totally usable for where we're at right now. Okay. It's just this. So the board holes about the holes are too far away from where the buttons are. So I moved them closer to where the buttons are, and the boards were flexing too much in my opinion when you're doing the button presses. But it's not, I don't think they're going to break. It's just they flex, you know, for the real product is too much flex. Got it. But for now, it's not really a problem. Okay, great. Yeah. I'm cooking up a scheme with Kevin on the next round. So I wanted to know. If we need to push that off for the next after that, I think that would be fun. Okay, got it. Okay, thanks. Has it some of the children are becoming YouTube sensations? Yeah. Has anybody considered maybe making money off them as influential? That's way outside my expertise. I'm happy if I can get them to go to school. So. Oh, I just noticed that I'm cutting off half of your heads in this video recording, so I apologize for that. People on the bottom row. Oh, technology. So I guess that's it for this week then. I was promised a quick update, and we'll be back on Friday to see how things went and start thinking about the next year, unless there's anything else from anyone. Michael, did you want to stay on and talk to me real quick about the volume issue or you just want to let it go? Yeah, let's go ahead. Let's do that. Okay. All right. Thanks. Bye for now.