 Today is January 5th, 2021. This is the DevSync. And so we've just been having a little bit of a discussion on some debugging problems. Sounds like we might need to get back into that after this check in here. But let's just go around and see what the nominal status is of things. Gez, we'll start with you. Kind of a bit of time on that debugging stuff. We also finally got merged in the fix to that enclosure service. And so that I didn't forget about it. I did a quick PR to do the same thing to all the other services. Part of the point was pulling out some common code and sticking it in methods so that we had fixed things once and it improves everything. Okay, seems to think that it is good, which is always surprising when you code good the first time around. Shouldn't be the case. I can't really remember much. We had a good chat with Derek and I had a good chat with the Blue Systems crew around the new onboarding flow and particularly around the Wi-Fi setup and the interplay between the two ways of setting up Wi-Fi. So there's some things we have to overcome, but they all seem doable. So I'm going to chat with Panicor about that next and try and get all that into place. That's about me, I think. Derek? So yesterday, last night, it worked a bit on that flow and got it to a good spot for the next revision. With gas and I need to get it kind of in a more presentable format to Panicor so I need to still get that done today. But then the rest of the day, I've been doing some audio cleanup. The raw audio from the Kusall recordings the end of last year. Just a lot of editing had to be done to get those into individual audio clips that we can use. So I've just been cleaning up audio mostly today. I did spend a little bit of time on the shipment stuff and it's a pain, but I got to figure out how to send to China via DHL with the new requirements the government passed the last couple of months. So that shipment to our assembler should arrive on Monday, Michael. I will send you the tracking number. Unfortunately, that was the fastest way. Fastest we could get it there is Monday. The plastics are moving. The ship date is February 9 is when we're going to get these off the line. So I think we're in good shape to hit that date. Okay. I do have some stuff from Kevin, but they delivered. They try to deliver very early today at the, at the main office Lawrence and no one was in yet. So I'll go pick that up tonight at the UPS station here in town. Yeah, so that's, that's been me. Okay, good. Chris Vera. So I spent my day banging my head against the wall with this microphone thing some more. I think I've, I've hit the brick wall. There's a bunch of more I can contribute to the problem. But so I was going to see today if there's anything else I could contribute and if not, I was going to move on to. Back onto the lakeward stuff. So my day tomorrow will be either more banging or. Implementing a materialized view in the court stuff. Okay. Ken. Would you call. It's your turn again. Okay. So, yeah, so I got the, the port audio debugging from port audio working. It's pretty extensive. I'm going to hack up the make file and rebuild it. And now I see it coming out. I'm going on the assumption that. Whatever hypervisor they're using pantomizer. Goodness knows what container system they're using. It's engendering some overhead that's causing the. Low level calculations to be wrong because the host isn't able to get back fast enough. So I'm pursuing that. And I'm pretty sure I can work around their problem and fix the problem with configuration by this time tomorrow night. But again, you know, that that's kind of. Not that great to begin with it. They're engendering that kind of overhead on the system. But you know, whatever it takes to get it working. One of the things that confuses me and, and I don't know, I can't seem to get a straight answer out of them is. I saw this today. You know, like I asked. Chris was asking, let me bring it up and I'll tell you what confuses me. Just hold on. But anyway, I said, I'm confused. Should we run as a mycroft or as root or what should we not do Sue Sue. And he says you need to be a mycroft user to run system control. User stop mycroft. But I'm pretty sure Chris was and it's not working. And he says if it says root at local host your root, but we're not roots. I'm not sure what you're talking about. And it's a little hard to figure it out. But anyway, I think the issue was that it was using pseudo on the system control. And all I asked Chris was, are you doing Sue dash L mycroft. And I did not understand his answer at all. I don't know if you're supposed to be running it as root or not. I don't know if the system D is loading them as services before it gets to start mycroft. And if it is, and it's running start mycroft, is that why I'm seeing it running multiple versions of it? Or I just can't get a straight answer. I don't know. I'm not going to worry about that. They are running system data. Yeah. Right. So then how is mycroft start mycroft working? It's in the boot up sequence. So if they started them, the system D services, they would be running start mycroft. You mean the shell group? Yeah. That doesn't run them as system D services. It runs in this command line. Anyway, I don't think I don't know that that's the issue. I'm hoping they didn't make a mistake that simple. I'm assuming it's down in what's called the period size. And when I look at the debug out, but I think I'm on the right track, it says hope suggested, what it does is it tries to figure things out like latency and number of frames. And then it says adjusted host buffer period 2016. Then later it says a determined period of 2016 is less than the minimum of 6,000. It's a big difference. And then it says adjusting to 6,000. It sets the minimum and maximum period to 6,000. And I just don't think that's right. So I'll figure it out. There's formulas for figuring all these numbers out. I just have to know that I have the data. I have to spend some time going through and setting them and testing them. And that's why I think I can work around it, but I shouldn't have to. But maybe it'll be working by tomorrow night. That's my update. That's what I'm working on and what I'm working on. All right. Well, there's kind of a yellow flag in there for me and that maybe Giz understands this. But you raise the question of are the Microsoft executables running as system D services? Or are they running as regular processes? And I certainly don't want to double those up. So if it looks like that's happening, we should raise that with panic currency. What do you think, Giz? Can you speak to that? In other words, we're still running start-microff.sh, correct? They're not. If we run that, then we're running it. And that's when they get doubled up. But they should only be running into some data. So you think that the blue system guys took out the call to start-microff? There's certainly part of their bring-ups. Let me go in and find the exact lines where it gets cold. OK. So that sounds like we can follow up. I'm losing everybody. Kind of slow. Some people are slow. But my point is, Giz, why don't you and I stay on after this and let's discuss that. That sounds great. Josh, any updates? Aside from the one you already gave us? No. Nothing significant. I'm still twiddling, waiting for a video of working to DevKit. And then your plastics are moving. So other than that. All right. Chris and I are doing a review of the, Chris Adair and I are doing a review of the, making sure that every single last part and screw and whatever got ordered. And then finally, you and I had a good discussion this morning about milestones for 2021. And I think that we're in alignment. And then finally, you've got me looking at silicon that can do some of the stuff we're supposed to be doing here. So I'm going to go chase some of that. All right. Great. Yeah. So the last of the hardware to get ordered for the dev kits, as Josh mentioned, was the, the plastic enclosures. So those are the last pieces that are coming in as well. There may be a number of dev kits. If not, everybody chooses to, to upgrade that we can ship before those plastics come in. So I want to get a call set up with Joe and Derek and Chris at least. And just make sure we have a good solid plan on when the fulfillment, various steps in the fulfillment are going to happen. So there's a lot of that that can be prepped. So it'll be ready to go when the plastics arrive. Yeah. We should get Johnny in on that too. Cause he's going to be handling shipment to Joe. Okay. All right. Well, we'll get that set up for tomorrow. That's a, yeah, that's the extent of my update for today. What I got today is a rev five. Is that correct? Yes. And that should be software. I haven't had a chance to open the box yet. I've been kind of busy. So, um, that, uh, should be software compatible. There should be no changes. I should be able to plug and play that, pull out the rev for plugging in the rev five and it magically works. Right. That is my understanding. Yes. Okay. Good. You may have some difficulty. Did he ship you a new plastic enclosure? Or no. I'm not using an enclosure right now. So it's okay. Okay. Yeah. I'll get you a new one. Ken. It's okay. It's okay. Until I get this software bug fixed better. I don't have an enclosure anyway. It's easier to get it everything and change stuff. So yeah, but I'll. Well, you can get it to me, you know, when, when you have time and I'll put it together. But I'm just saying it's, I'd like to get this thing working before I button it up. Sure. Okay. Uh, any other issues? Um, how are we going to resolve Chris Vair's dilemma as to what to work on next? Maybe you can stay on with, uh, guess and Ken and see if there's some way to contribute there. And if not, then, um, move back over to the wake word. Okay. Great. Well, um, so it sounds like you guys are having a productive, just productive discussion when I joined, uh, just, you know, you don't have to wait till these calls to get together and chat. So I'm just going to keep harping on that. No, we do, we do chat there in the day. You can see in the dev team and in the panic work. Oh yeah. No, the online chat is one thing, but you know, it's a little bit of a challenge to face and verbally is, is, uh, can be higher bandwidth. So that's what, that's what guys and I are going to do now. Yeah. All right. All right. Thanks everybody. We'll, uh, catch you again tomorrow.