Hello, everyone. This is the Adafruit Circuit Python, or the Circuit Python Weekly meeting for April 8, 2024. This is the time of the week where we get together to talk about all things Python. I'm Scott, and I'm sponsored by Adafruit to work on Circuit Python. First, I'll apologize for the frog in my throat, but I have a daycare cold courtesy of my two-year-old. Circuit Python is a version of Python designed for on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support Adafruit and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to the URL, adafru.it, slash discord. We hold the meeting in the Circuit Python DevText channel and the Circuit Python Voice channel. This meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with the U.S. holiday. In the notes doc, there's a link to a calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you'd like to receive these notifications, ask us to add you to the Circuit Python needs to Discord role. There's a notes document that accompanies the meeting and recording. You can contribute to this document beforehand. The final notes document includes timestamps to go along with the video, so you can use the doc to skip around to view the parts of the meeting that interest you most. The meeting tends to run 30 to 60 minutes. After each meeting, we post the link to the next meeting's Discord or notes document to the Circuit Python Dev channel on the Adafruit Discord. Check the PIN messages to find the latest notes doc so you can add your notes for the following meeting. If you wish to participate but cannot attend, the notes doc is the place to leave hug reports and status updates for us to read during the meeting. This meeting is held in five parts. The first is community news. This is a brief look at all things Circuit Python and Python on hardware in the community. It's a chosen set of items from our Python on microcontrollers newsletter. The second part is the state of Circuit Python libraries in Blinka. This is a quantitative overview of the entire project as a chance to look at the project by the numbers separate from our status updates. The third part is hug reports. Hug reports is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. It's done as around Robin. Status updates is also done as around Robin. Excuse me. Status updates is an opportunity to report on what we've been up to. Take a couple of minutes and talk about what you've been doing in the last week, since last meeting and what you'll be up to over the next week. The fifth part is in the weeds. In the weeds is an opportunity for more long form discussions. These discussions can come out of status updates or be something you've identified. The head of time is too long for status updates. That covers how the meeting will go and I'll get started. Take a time code and do community news. And if you do hear pauses, I'm trying to... I do have some coughs and I'm trying to pause or mute my mic. Not for the live folks, but for the recording folks. All right. So community news is a preview of the newsletter. We'll talk about that in a little bit. The headline here is CircuitPython 9.0.3 was released. It's the latest bug fix release of CircuitPython and is a new stable release. The only changes from 9.0.3 to 9.0.2 are fixed for analog in on Nordic NRF boards in the addition of a WaveShare RP2040 Geek board. And there's links to the release notes there. Next up, expressive chip news. Back in our January 10th, 2023 issue, we discussed the new ESP32-C6 and ESP32-P4. The C6 is on the market and the expressive has more P4 news. Adafruit has announced that the Adafruit ESP32-C6 Feather, a C6 development board in the ubiquitous feather form factor, it integrates 2.4 gigahertz Wi-Fi 6, BLE 5, and the 802.15.4 protocol. It brings the goodness you know for the low-cost C3 series and improves it with ZigBee, also known as 802.15.4 at 2.4 gigahertz. It can make for great matter development hardware. There's also a BME280 temperature and humidity sensor to make an integrated sensor node. Regarding the P4, there's a new video just released by Espressive saying unveiling the ESP32-P4, a high-performing SOC with extensive IO connectivity, HMI, and security features. There's a YouTube video and a product page link there as well. And DJ Devon 3 notes in the chat that the P4 does not have Wi-Fi. So just heads up, that's one of the first chips from Espressive that doesn't have Wi-Fi or a radio at all actually. It's the first one I know without a radio completely. I'm sure that'll change. Okay, last up in our community news, the Python Software Foundation has news and brief. First, the PSF has joined the Open Initiative for Cyber Security Standards. There's an April 2024 newsletter including Picon 2024 information and more and then also a blog post about reporting malware on Pi PI. So check and look at those things. Newsletter details. These stories come from the Python and Microcontrollers Weekly newsletter which is a CircuitPython community-run newsletter emailed every Monday. The complete archives are available at the URL adafruitgaly.com slash category slash CircuitPython. It highlights the latest Python on hardware-related news from around the web including CircuitPython, Python, and MicroPython developments. To contribute your own news or project, edit next week's draft on submit a pull request with the changes. You may also email cpnews at adafruit.com or tag a post with hashtag CircuitPython on Mastodon, LooseGuy, or X. Alright, that's it for community news. Next we have the state of CircuitPython libraries in Blinka. This is a kind of objective view on how CircuitPython and its core components are doing. To balance the later parts, we'll talk more subjectively about how things are going. First, the numbers overall. Over all of the CircuitPython-related repos, we had 28 pull requests merged from 15 different authors. Some new folks to me are Brushmate, Sean the IT guy, and Fabian Chateau. Those are all new-ish names to me, so thanks to the new folks. We had seven reviewers. Thank you again to all of our reviewers who support our authors. Overall we had 18 closed issues by seven people, and 19 opened by 19 people. So lots of engagement in terms of different folks filing issues, and we're only net up one, which is great. Now for the core. So this is the C core of CircuitPython. We had 16 pull requests merged from 10 different authors. Those new names are listed here as well, and two reviewers, myself and Dan. We have 21 open pull requests, so I think we're comfortably under that 25 limit, where we have to have more than one page. We have 12 closed issues by four people, and nine opened by nine people. So we're net down three, which is awesome, and getting close to double digits in terms of folks involved. We have a total of 673 open issues. We have nine active milestones. The core ones are 910, which is going to be the next kind of feature release, which has no open issues actually. 9XX is like work we want to do kind of soonish. It has 25 open issues. There is one open issue for 8.2X, which I will talk about later if I don't forget. It's not necessarily an 8.2 issue, but it's an interaction between some of the NRF bootloaders and CircuitPython. And we have three issues not assigned to milestone when these stats were taken, so we're just going to have to do our normal post-weekend triage as well. And with that, I'm going to hand it off to Dan to read the update for the libraries. Okay, thanks, Scott. Normally, Tim Foley Guy would read this section, but he's off watching the Eclipse. So covers things that all the CircuitPython libraries and related code. And in the past week, and pull requests merged by five authors and there were seven reviewers. A lot of these pull requests, none of them was more than two weeks old, more or less, that were merged. And so we have left. There are 71 open pull requests across all the libraries in which there are hundreds. There are, in the past week, there were five issues closed by four people and nine issues opened by nine people. That leaves 737 open issues, of which five were marked as good first issue. So if you'd like to contribute to CircuitPython, working in the libraries is a good way to do that because it's all Python code. You don't have to do low-level C code on the CircuitPython core. If you want to look at CircuitPython.org slash contributing, where you'll find a list of the open pull requests and list of open issues, you can look for, there's a few issues that are marked good first issue, which are relatively simple or straightforward, and you might look at those, but you could also just look over. There's a lot of issues that aren't marked that are probably pretty easy to deal with also. So take a look at those. And I think that's, please feel free to ask us for mentoring help. We love having contributors to both libraries and CircuitPython. So with that, I'll turn it back over to Scott. All right. I will cover PyPI Weekly downloads. I'm sorry, I forgot to do that. Go ahead. I have never read the library before or not from the past three years. You're doing great, Dan. You're doing great. Okay. So PyPI is the main, regular Pythons place to download libraries from, and we do upload all our libraries to there for download for various purposes. There have been 136,852 PyPI downloads over 325 libraries, and the most popular libraries tend to be Request and Bus Device and then some other related libraries. In the past week, only two libraries were updated of the CircuitPython Request Library and the CircuitPython Tommel Library, which I believe is a community library. And those have been, so those are in the latest bundle. And that, now I'm really finished. Thanks, Dan. All right, and next we're going to ask Melissa for a Blinka update. Yeah, Blinka is our CircuitPython compatibility layer for MicroPython, RaspberryPy, and other single board computers. And this week we had two pull requests merged by two authors and two reviewers. There are currently four open pull requests amongst all the repositories. There was one closed issue by one person and one open by one person, leaving a net of 85 open issues. I believe most of those are like new board requests at this point. There were 14,264 PyPI downloads in the last week, 11,356 PyWheels downloads in the last month, and we are at 133 boards. And that's it. Thank you, Melissa. All right, that's it for the State of CircuitPython libraries in Blinka. Next up we have hug reports. This is the first of two round robin sections where I will start and then it will go somewhat alphabetically through the folks in the Discord channel and those who have dropped notes in the note stock. If folks have said that they are not present, there's actually, we're recording this during or close to an eclipse in part of the U.S., so there's a number of folks that are doing things for that. But I'll read them off. They've dropped notes in here prior. Hug reports is a chance to say thanks to folks for what they've been working on and highlight all the cool things that people are doing within. And Fed A2 says the eclipse is partial in Costa Rica as well. Okay, so hug reports. Let me start and then we'll go through the list. For me I have a quick hug to all of the PyCascades organizers for a well-run conference full of Pythonistas this past weekend. Next up is Dan. Okay, so thanks to Brushmate who added code to CircuitPython to be able to change the various names that USB MIDI presents when the USB MIDI device comes up. So there are two what are called interface names and there are two MIDI jack names and those were fixed at a certain thing and a lot of people have asked to be able to change them and thanks to Brushmate for adding the code to do that. Thanks to Kevin J. Walters who found a very odd issue where if you reuse an analog pin as a digital pin on NRF 52040, it doesn't work right. And we thought maybe first this was a new nine bug but it's present in eight and it could have been present since the beginning of time. So it's not a common use case so we'll look at it for sure though. And thanks to Scott for a 9x issue triage meeting which we had last Friday. That's it. Thanks, Dan. All right, next up I have notes from David Globe. He says, hug to P3-LIM, Adrian L. Lung and Dan for hinting the use of microcontroller.nvm for hiding circuit pi. Hug to Dan for taking care of all of the circuit pipeline releases and myself for working on the USB host feathering support. Next up is DJ Devon 3. Thank you. I have a hug for FOMI guy for going through my commits with a fine-tooth comb especially the typing PR where Pilant almost calls me to throw my keyboard across the room. Another hug for the Saturday morning stream on refactoring and improving circuit. A hug to L. Pakenin for advice on catching line endings using ordinal values. I didn't end up using it but I learned a lot from the process. A hug to Todd Butt for helping troubleshoot an SD card issue just a couple minutes ago. It's turned out to be bad soldering on my part. Very nice catch, Todd Butt. And a hug to Tanute for a nice Cascades preview on Deep Dive this week and I hope you get better soon. It does sound like you have a frog stuck in there. Yeah, and I like your frog emoji in the notes too. Thanks, Devon. Okay, next up I have notes from FOMI guy who says hug reports to Scott myself for reviews and offering improvements to the circuit refactoring work. A hug to L. Pakenin and Dan H for helping me work through a bill-wildering issue with Pi test and Discord. Also hugs to L. Pakenin for sharing ideas and improvements to an on-device testing utility that I've started to build and a group hug. Next up from Jep where we have a group hug as well. And now is Mika Melissa. Let's see. I have a hug for everybody who's been submitting their new boards at circuitpython.org to Rich Turf, Gabby's Rich Turf that is for opening an issue for a Blikabug and PWMIO that I accidentally introduced and group hug to Brunos. Thanks, Melissa. Last up I have notes from Mika Pacusa who says hug to Andres the cat for posting the issue about using Adafruit HTTP server with an AP and hugs to AnakData for testing the PR with AP and connection manager examples in HTTP server. That's it for hug reports. Next up we have status updates which is also done in a similar manner. But this time we want to hear what you've been working on in the past week and what you plan on working on in the coming week. It's a great opportunity for folks to share knowledge if somebody's working on something that you've done before or if you want to collaborate together. So it's cool to see all the different things that people are working on. I'll start and then we'll go down the list just like last time. So for me, my Pi Cascades talk went as well as you could if I sound like this. I'm really happy I did it on Friday before I started sounding like this on the deep dive stream. I'm wrapping up the USB host feathering support today and tomorrow. I did a good refactor during my stream on Friday and I want to just bring it over to CMD in particular and I have to update the documentation as well. I may spend a little time to finish adding clang support to our make files so not necessarily switching over to clang fully but at least getting a CI run that builds under clang so that we can ensure that we keep support. There's a CLI tool called bear which you can use to generate a compile commands.json which is used by the clang-d language server to determine how each individual C file is actually compiled like what include past there on things. I got it set up on my laptop last night and it looks really helpful so I'm going to actually do that this afternoon for myself on my desktop. I'm out most of next week for a Zephyr conference here in Seattle and then on Friday we're taking a family long weekend so I won't be running much next week and then just a heads up I'll also be gone the first full week I think it's the first full week of May the 6th through 10th for a road trip with my dad so I'll be out then too. Alright next up is Dan. Today I released CircuitPiketon 903 as mentioned above it's just one additional board and one port fixed. As I mentioned Scott and I also treehouse the 9XX bug list and we reduced the number of issues we want to work on from 33 to 25. Some of those we push forward some of them we closed so forth. Somebody some people noticed or at least one person noticed that there were some read-the-docs bills that were really ancient and it turns out like we added some feature and they said I didn't even know that feature was there because it wasn't in the documentation that was because around December read-the-docs decided that they wanted for all their webhooks they wanted a secret which is basically just a password that they generate a long key and many of the webhooks in the libraries did not have them about 10% didn't have those secrets either because they weren't copied over or because the webhook had been created so long ago that it was before read-the-docs was even using secrets. So I went through all of these by hand which was an interesting amount of clicking and fixed the ones that needed secrets. We ran some builds if it looked like they were really out of date and also fixed some other problems with these webhooks. I didn't look at anything else kind of in this process but I think that now nearly all the documentation will build reliably. There are a few documentation, RTT bills that are in the wrong style and I think that's probably because there's something wrong with the read-the-docs YAML file that's in those repos but I neglected to write down which of those were there so if you find one bring it to our attention. Otherwise I'm looking at bugs to fix in 910 and later versions of 9XX looking at them, triaging them, figuring out if they're really bugs and fixing them if I can. That's it. Okay, next up I'm going to read for David who says, Improved my mouse jiggler by making it stealth but switchable by the boot button on the QDPI 2040 using microcontroller.nvm0 to store a behavior flag. Soldering for the first time with prescription glasses and this is a game changer. Great. The USB host feathering is ready to test my work and the DVI RB 2040 feather is to be ready to replicate the CPM emulator by Jeff. Next up we have DJ Devon 3. Thank you. This week I submitted a new API example for qtimes.com API to add a free request. The API interacts with many different theme parks. The example only pulls from Disneyland shows the name of the ride, the Q-time if the ride is open or closed and I handed that idea off to the Ruiz brothers who might turn that into a project somehow because they're really interested in Disney stuff. I finally figured out a way to address the GitHub desktop issue where it automatically converts all line endings to CRLF during checkout. I wrote a playground note on using Windows PowerShell to automatically convert them to LF line endings and then it runs black and then reuse and then pre-commit all in one shot with two mouse clicks. This issue has plagued GitHub desktop users since its debut. Pretty sure every Windows GitHub desktop user on the entire planet will want to know about this. I'm not going to call it a fix, but it's definitely a nice workaround. I made some more progress on the ATEC crypto chip bug. I fooled it into thinking it's receiving a correct CRC match and it started working as intended. Upon more investigation I found that CRC1 and CRC2 randomly do not match. Early indications are pointing at some kind of analog voltage oscillator counter rollover. Not working properly. The CRC mismatch error seems to occur when CRC1 reaches 65535 and I don't think that's a coincidence. And I finally got a working belt sander. I broke two of them this week. And I can sand and stain some new shelves. That's it. Nice. Thanks, David. Alright. Next up we have notes from FOMI guy because he's out, well, missing the live meeting to catch the eclipse. Refactoring CIRCUP to break it up into smaller chunks to hopefully make it easier to understand, maintain and develop new features for. Resolving a few of the existing issues while I'm there and trying to work toward a new feature that would allow CIRCUP to be used for loading library examples onto the connected device. In order to make my wish of CIRCUP loading examples easier to achieve, I'd like to resolve a long-standing issue slash idea and CIRCUP I can build tools to break up the examples directory into one directory per library rather than the existing way which puts all examples from all libraries into one folder together. Received all hardware and started wiring buttons for a Simon like game, but I was too rough with the thin grove cable wiring and my buttons are flaky if the wires it held perfect, absolutely perfectly. I'm planning to drop the grove wing all together and just wire the buttons to a perma-proto breadboard instead. All right. And that's from FOMIGuy and now we have Notes from Jepler who says, out watching the eclipse today, hopefully works a bit on the POSIX port. I found an interesting crash when trying to enter safe mode. I should make up a PR to fix it. The problem can occur if a safe mode reset message is printed before the cue strip pool is fully initialized. This happens to me in the POSIX port, but may or may not happen in quote in real life. And last up, let's hear from maker Melissa. Hi. Let's see. I always have trouble finding that unmute button. I worked through going through the Raspberry Pi related guide feedback and updating the guides as needed and it's really good to continue doing. Awesome. Thanks, Melissa. And that's it for status updates. The last section we have here is in the weeds, which is a chance for any longer form discussion or questions that we have. We've got one topic here today from DJ Devon 3, so I'll hand it over to them to introduce the topic. Thank you. Currently, all request API examples that I've contributed use an explicit response.close to disconnect the socket. Anecdata brought up a good point that using with request.data and then the source as request or as response does not require an explicit close. Any preference, does anyone have a preference on the syntax or method used? Anecdata says to me, quote unquote, to me with is simpler than close, but it's another concept to grasp. So it might be better for beginners to see the dot close, the explicit dot close, in order to see what the script is doing. I can submit a new API example that uses both methods so that somebody could see the with method right up against another identical that doesn't use the with and uses the response.close instead. But this is because it's in the adder for request library, that's not a decision that I can make that's up to you guys. So with is better. And it's better because if an exception happens with ensures that the close is still called. It's not obvious that it works that way, but... I did not know that, okay. Yeah. It's a general Python thing that with is better because it happens even when exceptions are raised. And I assume that works for a circuit by then too, but yeah, I understand that it's a new mechanic, but I think with is really useful. The term for it in circuit by then is actually context managers, if you want to find more information on how that works. Okay. Are there any objections to me just going in and rewriting all of this stuff that has dot close to use with statements instead? Do one first, please. Okay. It can get a little tricky because you end up nesting stuff. Oh, I have already done it on multiple examples. Okay. Yeah, just push them in. So let's just double check that it looks okay. Okay. I would say one thing that's missing is going up a level on all this is that you don't actually have like a guide about kind of like canonical and best practices for doing networking. Yeah. There's a lot of like, there are these mirrored pages that show you, okay, here's how to do a simple something or other on this board and that board on the other board. But there isn't like, you know, we now have this display IO guide, but we don't have like a networking guide. And I know David Claude said that he assumed there is a guide and there is not a guide as far as I know. So you might think about that in the long run. Like all these examples, for instance, that you're doing in the library are great, but a lot of people don't know to look at the examples directory in the library. And so it doesn't, there aren't links to those things. And so maybe we'll bring this up internally about whether someone might write a guide or if someone writes to write a playground note or something like that, that would be great too. I could do that. I've done all of the API examples. I'm probably the best person to do it. Yeah. I mean, I'm thinking that you might want to write up your examples as playground notes. All of them? No, no, no. Well, you can do what you want. No, no, I don't want to do all of them. But to say to make, it makes them more findable in Google searches and stuff like that. And we could cross-reference them. And because otherwise they're just like, oh, you can, here's this neat thing that you could use to get this obscure data or this interesting data off this website. But the only place you're going to find a pointer to that is in a search result that's from GitHub. OK. So how do we make that more visible? I think it's best if you guys do something internally and have at least a guide that can be pointed to and then I can point to that. That's, yeah. I think that's probably a good idea. Yeah. If only you guys work on Cirque-Up to make examples more accessible, it might help too. Like in the Arduino world, in the editor, you had that big dropdown with loading examples. And a Cirque-Up Python equivalent like that would be really helpful. That's interesting. I think maybe we might even figure out some interesting way of listing them on circuitpython.org or something like that. Yeah, and it's also, I've also thought about making a PyLeap library for Cirque-Up Python where you could use, you're like, PyLeap is good for projects and pulling projects down and doing discovery like that. Maybe there's a world where we have a PyLeap module that does that from Cirque-Up Python itself. That's interesting, yeah. It's also, maybe it's a feature to add to Mew, but that's, they would be very careful about that. Or code.circupython.org. Yeah. Is that a thing they can do? Because that would be cool. Is it what, Mew? Yeah, because Mew is like the beginner level IDE that pretty much any beginner in Cirque-Up Python goes straight for, unless they're on Linux, I guess. But for Windows, yeah, it's straight to Mew. Yeah, a lot of people use VS, and people who are programmers, a lot of people use VS code, which unfortunately... Right, but then those people are beginners.  I mean, making it on a website might also be interesting because that's, it's certainly... Maybe someday incorporate it with like Web workflow. Maybe, yeah. Right. The other thing that I was thinking about in this vein is whether, like some people are exploring, like in Python land, there's these notebooks and it crossed my mind to whether we could run like notebook formatted Python code from the device itself, which would be neat, I think. And if editors have support to automatically format like the text parts of that nicely, that would be cool too. I'll have to look more into it, but yeah. There is somebody that's made a plugin for Jupyter already for Cirque-Up Python, but I'm thinking... I think it has to be tethered in that case, but I'm thinking more of like it's code that's formatted and stored in Cirque-Up Python in a way that when you load it, it runs well or it like looks well in your editor, but still can run standalone in the device too. So yeah, thinking about that. Okay, that'll keep me busy. Awesome, thanks. You want to add, like if you just... Maybe just if there's some... I'm not sure I have time right now, but if somebody wants to add like a few bullet items to the end-of-weeds so that it'll... This extra part will show up in the published notes. That would be interesting. Oh, like more description of what we... Examples, like right, like... Networking guy, you know, there might be a place to put examples. That was a topic that Fummy Guy brought up in Dead Chat that probably should get added to the end-of-weeds, yeah. Yeah. All right, can somebody summarize that in the notes talk, please? I can do it. I might be able to just copy and paste what Fummy Guy posted earlier. Just a bit. So that is it for in-the-weeds. Thanks, Devin. I'm going to go back to my script to get us out and done for the day. So thanks everybody. This has been the Circuit Python Weekly for April 8th, 2024. Thanks to everybody who's participated. Even if you're looking at any clips and just added notes, I still appreciate you adding notes and hearing what you're up to. If you want to support Adafruit and Circuit Python and those of us that work on Circuit Python for Adafruit, consider purchasing harder from the Adafruit shop at adafruit.com. The video this meeting will be released on YouTube at youtube.com.adafruit and the podcast will be available on major podcast services. It will be also featured in the Bython for Mac controllers newsletter. Visit adafruitdaily.com to subscribe to that. Next meeting will be held next Monday, I believe. Yep. At the normal time. No holiday next week. This meeting is held on the Adafruit Discord server, which you can join by going to the URL adafru.it slash discord. To be notified about the meeting and any changes to the time or day, you can ask to be added to the Circuit Python and EASIS role on Discord. That, we hope to see you all next week. Thanks. Have a great week. We'll see you on Discord. Thanks for hosting, Scott. Hope you feel better. Thanks.


This is the animation minute Packed week, so let's go straight into Phil's tweet here that posts really neat art here And you can see the Studio Ghibli version of a Star Wars inspired design very nice Daniel is posting here a really cool clip about flying and free-falling he says here But it has really cool action and this section is really neat Dino was character in the back while this character comes down and starts running on the side of the wall Very cool watch the whole thing on history count. Speak of awesome. He was really cool animation from animation students Matei Niaugofoxa, I hope that is pronounced correctly, but it's super cute Basically characters, but it's really well-executed nice look nicely done Cool thread from cross on talking about how he feels animation It's more about flow and rhythm kind of piggybacking off last week's animation minute post that a featured of his Where he has a really cool shot with a nice animation nice camera move talking about flow and rhythm Next up Jasmine is posting this unreal engine project. It's so cute You can click on the art station link and you can see here The process how awesome it is. I highly recommend the check this out. So so cool Speaking of cool, you know, we can't go by without pixel art out of chill. I love it Mike is posting the anim state industry server results over 400 replies a lot of information to go through That's oh, that's right more pixel art, but I love it. Look at that. That's super cool How to put that in there Justin is posting a peek at his 80s He meant formation clip and one more tweet here. You can see the time lapse Absolutely insane stop motion never ceases to amaze me. It's so brutal the amount of work. I can never do that I love this is so cool more animation mentor this time They are announcing the 2d animation walk cycles and character move in the workshop nice This was really cool animated looping if here look at that. Here's the designs really nice shapes nice flow How to put that in there? Snoop cat really cute little 2d animation all done grease pencil and blender So you may Allah is hiring 2d frame-by-frame animators and cleanup artists There's a post here about mainframe industries and Anna saying they're looking for a lead and a senior animator That's very cool. Look at that You can see the inside of it and then how it finishes. I love this really cool presentation The antique is looking for a 3d animator a 3d artist in the San Francisco location and not a job posting Couture brew is posting a book preview anime architecture imagine worlds and endless mega cities. That is going to be absolutely Fantastic. I can't wait to get this Not animation related per se in terms of showing animation or anything we draw postings But I thought this was really cool Their motive is giving full credit to the people who lift the team as Dan says here That is absolutely a classy move and I wish more studios would be a bit more relaxed in terms of their credit Policies and politics. It's always kind of muddled Josh Sobel is announcing frigging awesome studios Very cool. Check out the tweet with all information about all the services that he is going to provide This is very self-serving but I saw it on Twitter And I thought it was really nice that Jessica was tagging me here with the work that we did during the workshop If you're interested in a workshop There is a link with all information in the description on this YouTube channel, of course Last but not least animal logic is posting that the Vancouver studio is looking for lead animator to work on super pets And that's it for this week. You can always find the animation minutes every Monday at 8 a.m Thank you for watching and I'll see you next week


You, finding life pretty dull, dreaming again of exotic places, wishing you were somewhere else, we offer you escape. Escape, designed to free you from the four walls of today for a half hour of high adventure. Escape with us now, to the year 100,000 and 80, and a world where beauty and terror live side by side, as H.G. Wells describes it in his immortal story, the Time Machine. Dudley, you must be mad, the Time Machine. Yes, my friend, the Time Machine. This, this thing, this very thing, this contraption, this framework made of quartz and bronze and ivory with its levers and its dials and its seat in the middle, this is the result of three years' hard work.  By working these levers, a man can choose his century, his year, his very day. Oh, really, old man. Time is only a kind of space. If we can move about in all the other dimensions of space, why not in time, too? It's impossible, out of the question. Then what of the journeys I've already taken on this little contraption? I'm afraid you've been having a bad dream. You mean I've developed into a liar? Very well. You shall have proof, my friend. How? Just climb on, Father. Sit in the seat beside me, face these ivory dials, and I'll take you for a little spin. Well, you mean right now? Right now. Or just in case this thing should take off like the flying red horse, are there any... Any preparations? No, Father, no. You won't need any luggage on this trip, not even a toothbrush. You'll be back here in my laboratory in less than a minute. All right. I'm on. Now what? Oh, tight it. Sway's a good deal. I'd hate to lose you. I can't be frightened, Dudley. Then you're braver than I am. Tell me what time is it? It's just 12 noon. Before we start, I want to adjust this control a bit. Is everything in ship shape? Governor, did you notice anything just then? Only a noise, a humming noise, nothing else. And what time is it? You just asked me, old man, it's... Well, that's odd. What? My watch says 11 o'clock. I could have sworn it was noon a moment ago. There must be something wrong with it. It's only that I touched the lever to test it, and we've gone forward a full day. 23 hours at any rate. Yes, but Dudley... Finished scoffing, Father? Yes. Yes, I believe I have. Then hold tight. This'll be the real article. I'm ready, Dudley. Good man. Well? Say goodbye, Father. He went off with a shattering jar. With machines swaying under us. Walls of Dr. Dudley's laboratory suddenly fell away. Night was speeding up today like a flapping of a black wing. I saw the sun hopping across the sky, leaping swiftly across it every second, and every second marking a day. I saw the moon spinning through her quarters like a ball from new to full, all in the twinkling of an eye. Trees grove and blossom like puffs of smoke, and then pass away. All the while we were going faster. Now our pace was a year a second, so that second by second the white snow flashed across the world and was followed by the bright brief spring, and still we went on into the future. Are they'll fail, Father? Very weak. Very dizzy. Or let go, don't fall off. Where are we? How far have we come? We're in 100,000 and 50. And 60. And 70. That's enough! Dudley, Dudley, I can't stand anymore! Stop it! Yes, I... I believe so. No broken bones. What happened? Sure, I must have stopped too suddenly. Where are we, Dudley? The ground for yourself. A wide lawn. Beautiful, vast garden. I meant geographically. Just where we were when we started, where my laboratory stood 100,000 years ago. And the year, Dudley? What is the year now? 100,000 and 80. It seemed absolutely incredible. A dream. The pleasant one. For the garden in which we found ourselves was beautiful and summery. With an unexpected perfume about it, almost like platine. At some distance we could see a large and imposing building. And everything was quiet and peaceful. But almost too much so. And the sense of strangeness. An incredible strangeness sent a shiver up my spine. 100,000 and 80. Father, do you... want to go back? Yes, yes, I rather think I do. Let's go back. Dudley, from over there in the bushes. It sounded human. Come on. It's a child. Seems to be a very small girl. There's been a beast here of some kind struggle with a look at the marks on her. Now, my dear, you'll be all right now. You won't be harmed. It's not English. Motioning us to go with her. What about the animal? Did you see it? No, not a glimpse. Too fast for us. Perhaps we'd better go back, Dudley. The girl seems to be all right now. Leave her like this? Yes, yes, I've had enough. Well, they haven't, old man. Because they're here. All around us. They had crept up on soundless feet to surround us. The little people of this era. And the girl we'd saved was not a child, but a girl stood four feet high dressed in simple tunics. Beautiful creatures, but terribly frail with a plump, soft kind of frailty. They were like eerie figures in a dream. And all we could hear was the rustling of their clothes as they served happily around us their faces. Weaved their smiles. Why, they're not savage at all. They're very loving and gentle little people. There's something terribly wrong with them. How do you mean? They seem to have the minds of five-year-olds. How do you expect them to be? Far ahead of us, of course, incredibly ahead of us in knowledge and in science. Look at them. Children. They seem happy in this huge garden of theirs. Dudley, I've changed my mind. Let's stay. Maybe we shall enjoy spending a few days with our little friends. The little people led us home into their valley. They lived in colossal buildings sleeping all together in one huge hall, eating in another, playing and fiddling together in the sunshine. And we lived with them for days in utter contentment. One afternoon Dudley and I walked along the banks of the Great River. Little people all wear the same clothes, the same soft hairless skin, the same feminine roundness of limbs. I wonder if it's because they're vegetarians. They're vegetarians because they have to be. They haven't run across any horses or dogs, cattle of any kind, have you? No, now that you mention it. With good reason. All extinct by now. This is the dinosaurs with us. Dudley, there's something strange here. Something hidden away and silent here in the year 100,000 and 80. Felt the same way. I've taken the precaution of removing the control levers of the time machine, putting a master padlock on the main switches. Not much fancy the idea of someone riding away with it into another century and leaving us here for the rest of our lives. Dudley, do you know where we are? Yes, this is where we landed. I thought so. I wasn't sure. Why did you ask? What's happened to the machine? But they've taken it away. They've stolen it. This is where it was. It's right here. Look. Follow the tracks. Here where they've dragged it. Over here. Come along. Down this path. Look. Right there. The monument. There's a brass door in the base. Oh, they're locked. The machine. It must be in there. Inside. We must get it. Break down the door. How can we? Here. Use the levers. It's more... No, it's no good, Dudley. It's solid. It will never break through. Never. No. Never. We've done it through here. Right here. All our lives. We never go home again. It must open the machine. Our little time machine. How well do you know the history of your army? For example, do you know who the first chaplain was? He was the Reverend John Hurt. During the early days of the American Revolution, he served as chaplain of the 6th Virginia Infantry. Later, he became brigade chaplain. And finally, in 1790, he was appointed first chaplain of the United States Army. Thus, another page was added to the history of your United States Army. And now, we return you to escape. We were caught in a year 100,000 a day. The time machine was gone. The brass doors of the monument held. Our retreat was cut off, the thin line by which we could make our way back home, back to our own time and our own people, back to 1950. We had no way of communicating with the little people, of asking what they had done with the machine or how to get it back. There was nothing hostile in their attitude. They were more like simple, wandering children. Only one, the young woman Weena, who's life we had saved on our first day had become really friendly. She went with us wherever we walked, brought us presents of garlands, of flowers, slept near us at night in the hall. And we, in turn, had taught her a few words of English. Now, we redoubled our efforts, like men racing against a clock, so that we might speak to her and discover the secret of our immense loss. We were talking to her one night after the others had gone to sleep. No, not this, Dudley. No. How can you be so sure your people didn't steal the machine? Aren't there any thieves among them? Are they all perfect? No, no, no, that's so loud, Dudley. You'll wake them. Besides, she doesn't understand. The thief must be sleeping somewhere in this hall. Weena, they take machine. No, Dudley, no. Who then, who? We, we are our friends. Yes. We must have machine. Yes, Dudley, yes. Who took machine? Other people, not yours? Other? What about those doors, Weena? Doors, open. No, no. Weena, machine in, in there. Must open. No, no, not open. All right, my dear. Go to sleep, get some rest. Yes, Dudley. What's to become of us, Fowler? Are we caught here in this century?  We'll go back to the monument tomorrow. We'll find a way of breaking in. Good night, Dudley. Dudley? Yes. Did you just... There it was again. What? Something on my face. Cold, filthy to the touch. On my face and in my hair. It's cold as death, Dudley! You're right. There's something in here with a fan. It smells of the grave. What was it? I don't know. But look at them.  They've only been stampeded. Let's get out of here. I want some fresh air. We went quickly through the hall and outside, away from the frantic rustling of the little people. The moon was full, just overhead. And it was close to dawning. There was a faint sound speeding close behind us. And we turned. Our nerves ragged. Our muscles tensed. But it was only Weena coming swiftly to join us. Dudley, I'm afraid it's dark. Then there is something. What do you mean, Weena? Dark. What? Dark thing. Dark place. Night. Why should they be afraid of the night, Dudley? It's not the night alone. Dark place. That's our cube. Perhaps it's something underground. It was another day. We had wandered into a lovely wooded place about a mile from the community. And suddenly Weena screamed. Oh, Father! We stopped short. A pair of glaring eyes were fixed upon us. As we stood there, petrified the thing, a little ape-like figure, rushed across our path and disappeared in the clearing about 30 yards away. What was it? I couldn't see it too well.  It looked like a smorgasbord. It was running on all fours, over its arms held very low. Weena. Weena, what was it? Morlocks. They... Morlocks. Who are the Morlocks? What are they? Weena, tell me. No. No. Let's go over there and see where it disappeared. Come along, Father. In the clearing, we found a round well-like opening. Dudley and I leaned over and looked down a deep shaft.  Like a human spider, its large, bright eyes watching me as it went swiftly down, then it disappeared in the shaft. Did you see it? Like an ape. Yes, but also like a man. So there are two species of men in this world. Yes. The little people above the ground and this obscene thing, this bleached monster below. That white look, common to animals that live in the dark. Like huge rats, like worms that are cold to the touch. I know because they've touched me. Father, you can feel the air being sucked down into this shaft. Yes. There's a tiny tunnel enormously here under our feet. These monsters must live in the tunnels. I think we know now who stole our time machine. Yes. Then... Then we'll go down and have a look. No! No, not go! Why not we now? More locks. You never come back. We must have our machine, my dear, and you wait for us here. No! No! And so we went down, our heels ringing on the small metallic bars that were meant for creatures so much smaller than us. Down we climbed, down, down, ever in darkness. Down it seemed, into the center of the earth, into the core of the world. How much longer? Well, no, until we reach bottom. Can't be much further. Do you hear that? Like machinery. We're almost there. Well, thank heaven for that. All right, Father, I'm on the bottom. Come along, just a few more steps. Now, give me your hand, Father. Good. Here. Where are you here? In the land of the Morlocks. Do you have a match? Yeah, yes, yes, here. It seems to be a large vaulted cavern at the end of this passage. What do you... I suppose they'll do. They'll catch us. I've no idea. Let it take care not to be caught. Ah, another match. That throbbing noise. Probably their ventilating system pumping the air down. There must be thousands upon thousands of these Morlocks living under the earth. We haven't seen any yet, except for our friend who came down ahead of us. Why do you suppose they wanted our time machine? I think they wanted us, not the machine. And we've come to them. We must, it's our only chance. Talon, if that noise does come from air pumps, why is it so stuffy here, so oppressive? Dudley, that smell. Blood. Lighten up the match. Dudley, straight ahead. On the white metal table. Set for a meal. Yes. With a small haunch. Meat? We know that the cattle are extinct. Then what do they feed on these Morlocks? Don't you know? Yes, I know. Another match? Dudley, I have no more. I've used our last match. All right, we'll have to go back then. We know the secret now anyway. These Morlocks living here underground are the masters of this age. And our friends up above fatted cattle fed by the Morlocks' clothes supplied and housed until the day when they're cut out of the herd and brought underground as food. This is the future you're looking at. This is what we men of the 20th century shall come to. Dudley, what is this? Hands? Take one of these, let us guess. Use it as a whack-out. I guess this wall fell ahead behind me.  Back to those projecting bars, kicking and clawing ourselves loose from their talent grasping hands and climbing up again up toward daylight and freedom with their stench and the eagerness of their icy hands and they did not follow. For daylight was their enemy and their great fear and we lived among the lush gardens of the little people like prisoners like men without reprieve, like men who are dead, though they still walk the earth. For the time machine was locked away behind great brass doors and we knew we could never force them open. Then one day, Weena told us of an old building, an ancient sagging structure that had survived through many ages and was filled with many curious objects. A museum, that's what it must be, a museum fowler. Perhaps from some earlier time. I'm in no mood to go looking at a museum, don't you see? Specimens hermetically sealed in museums. Perhaps there are things, weapons, machinery, something we can use. Yes, yes, of course. If we could find some dynamite or gunpowder or something. We could blast those doors we could get in. Where is this place, Weena? This old building that no one ever goes near. I take you. It's not far. A chance, old man. A slim one but a chance nonetheless. Today we wandered through the great ruined halls. The building had been deserted, unused for perhaps a century. The childlike men of that time had long since ceased to care about anything but their own personal comforts. It was late afternoon and growing dark when we came upon the chemical section.  And it's dust. All of it. Been dust for centuries. Another dead end. Ah, it's hopeless. We were out of our heads to hope that nitrates would retain their form for a hundred thousand years. We, go now. It's nothing here. Wait just a moment. Something in this case. You can break it with your lever. Stand back a little. Box of matches. Hermetically sealed. Wait, let me see. They're perfect but they're not even damp. What shall we do with them? Burn down those brass doors. You'd better keep them. Small narrow footprints leading away into the darkness at the end of this gallery. We'd better go. We'd better run for it. I don't be frightened, my dear. It'll be all right. We came out of the gloom of that place into the deeper gloom of dusk and suddenly we saw. We were trapped all around us with a morlock. We were there by the fowls surrounding us and coming closer in the long even line of deathly fight, their eyes blinking in the half light, their tiny mouths alive with appetite. I had them dipped like a fire. Hurry, man. The forest is dry. Hurry, buddy. We'll have an inferno again in a minute if our little friends don't like light or heat. The fire leaps high to the heavens and the countryside with a flame. The morlocks turned in fear, blinded by the glare. Some of them blundered into the middle of the raging flames and the rest faded away like a fog. Dudley had left a narrow passageway for our retreat and we fled down a long corridor of deeping flames and blistering heat. We fled to safety toward the community of the little people. As we ran, we passed the huge monument to the great bronze doors that were locked tight in our time machine and suddenly in the glare of the distant fires we saw something had stopped us short. It's a trap. They're there waiting for us inside. Waiting or not, we're going in. It'll take me one minute to screw the levers on again then I touch them and we're away. All right, I'll try to give you your one. Good boy. I'll hold tight around my neck. You're coming home with us. All right. All right, let's go. We're in a look for a machine they haven't harded. I don't see them yet. Come on now quickly. The door's Dudley. The clothes get in the seat. I'll be ready in a moment. I waited for the hum that would signal our departure. There in the darkness the morlocks were finally upon us.  I held tight to wieners. A man holds fast to life. I kicked them away with my feet. Dudley, Dudley, Dudley! They get me clever quickly or we're done. They tore her from my hands at the last minute. I tried to save her. I still have a piece of a tunic. Here are my fists.  Nothing else. And so we came home again. Back into the very minute from which we had left. We were in Dudley's laboratory again. Motionless. Sitting on the ridiculous contraption which he has called a time machine. Was it all a dream? Did any of it happen? Could any of it happen? Of course not.  Then what of this? What of this little piece of thin green silk I hold in my hand? Escape is produced and directed by Norman McDonnell. Today we have brought you the time machine by H.G. Wells. Adapted for radio by Irving Ravitch and starring John Daenerys Fowler and Larry Dubkin as Dudley with Georgia Ellis as Wiener. The special music for Escape was arranged and played by Ivan Dittmarz. This is the United States Armed Forces for Radio and Television Service.


QuickBooks Online 2024, bill pay form, get ready and some coffee because we're going to get the books on key with QuickBooks Online 2024. Here we are in our Get Great Guitars 2024 QuickBooks Online sample company file. We set up in a prior presentation opening up the major financial statement reports like we do every time the reports on the left hand side in the favorites. Right-clicking on the balance sheet to open a link in a new tab. Right-clicking the profit and loss to open link in a new tab. Right-clicking the trial balance to open link in a new tab. Let's go to that tab to the right where the balance sheet is located. Close up the hamburger so we can eat it and then change the range. We're going from 010124 tab, 013124 tab and then we're going to go for a run. And then we'll tab to the right. Close up the hamburger and then we'll range change. 010124 tab, 013124 and then we need to refresh. Refresh. And then we'll tab to the right. Close up the hamburger again. Range change. 010124 tab, 013124 tab. Once again running and refreshing. Let's go back to the balance sheet this time. Now we're going to be entering another form which will record a transaction this time a pay bill form. First a word from our sponsor. Yeah actually we're sponsoring ourselves on this one because apparently the merchandisers they don't want to be seen with us.  Our crunching numbers is my cardio product line. Now I'm not saying that subscribing to this channel, crunching numbers with us will make you thin, fit and healthy or anything. However it does seem like it worked for her. Just saying. So subscribe, hit the bell thing and buy some merchandise so you can make the world a better place by sharing your accounting instruction exercise routine. If you would like a commercial free experience consider subscribing to our website at accountinginstruction.com or accountinginstruction.thinkific.com. The pay bill form being like a check form and you will recall that the check form or expense form decreases the checking account. But this time the pay bill form is specifically tied to the accounts payable. We will deal with the accounts payable more in a following presentation because most of the transactions we entered this time we entered just with a check or expense form. Next time we will be entering the bill form. This accounts payable is on the books from when we entered our beginning balances into the system. Let's take a quick look at the vendor cycle with a flow chart. This is a QuickBooks desktop flow chart but we are just using it for QuickBooks online because we are thinking we just want to see the flow of the cycle of forms. We are looking at the vendor cycle meaning the cycle for expenses or payables. The cycle in which money generally goes out at the end of the cycle in order to purchase goods and services and usually we have an expense related to it ultimately. So the easiest way to deal with this and most small companies these days especially with the advance of technology and having online banking and what not will use this easiest way and basically be on a cashed base system in which you connect to the bank feeds, you pay everything with electronic transfers which is great as we did last time when we paid off our bills like the telephone company, the utilities and that kind of stuff. And then as it clears the bank we can just record it to the proper generally expense account and that will create an expense form as we basically do the bank feeds. We will talk about doing that with bank feeds in a future course or section but that would be the easiest thing to do. The second easiest thing to do or the second method that would still be cashed based system would be that you are going to basically write checks either with a checkbook or you print the checks out of QuickBooks, still needing physical checks that are external to QuickBooks to put in the printer and then you would have to enter the checks as you write the checks even if you are physically writing them by hand. We don't want to wait till the checks clear the bank because if we wait till the checks clear the bank we don't get to see the timing difference and look at if there's outstanding checks because the big problem with checks is we know the transaction happened a lot sooner in time than the bank knows and we want to record that so that we know what our cash flow is really and we also want to be able to determine if a check has cleared or not if there's a problem with the payment of it. So we would enter the checks we would record them and then when they come through the bank feeds we would just reconcile them there or do a bank reconciliation. Now if we have an accrual system however then instead of it entering just checks or expense forms we would enter an actual bill. So now you're imagining you get the bill like the telephone bill or something like that instead of just automatically paying it when it becomes due you enter it as a bill. Note the terminology here the terminology in normal like accounting even if I say something is a bill that typically means someone is billing us or there's going to we owe someone money. They sent us something that says we owe them money for goods and services that we consumed from them or we can even use the term bill for billing our clients. Money just like we used we invoiced our client we can use those interchangeably and normal accounting concept they invoiced us. Well if the vendor invoiced us that just simply means that they sent us a bill. So but from the standpoint of QuickBooks we have to determine which side of the transaction we are on bills mean that we're purchasing the goods and services from someone else. Even though we bill our customers for goods and services that we provide them we just call it an invoice from QuickBooks. All right so that means that also if we have the bill it's even more restrictive than that because instead of when we get a bill if we enter it in the system and just pay it if I just pay it off with a check form or expense form then it's still not called a billed form for QuickBooks. It's just it's a bill it's a charge to us that we got that we paid off we didn't enter it into the system as a bill right. So if we enter it into the system as a bill form the accounts you want to tie to that is accounts payable that means we're not going to pay it off right away. We're going to put it in as accounts payable increase the liability account and then pay it off at some future point with basically a check or expense type form. But it's going to be a special one called a pay bill form which will indicate specifically that although it's a decrease in the checking account the other side is going to be decreasing the accounts payable specifically. Now quick note that oftentimes small businesses if you have the cash flow they'll they're just going to be paying off the expenses as they come do or possibly paying them off with credit cards as they become doing just wait till they clear the bank feeds. That's the easiest things to do. But as a business grows then the accounts payable becomes more and more important. So if you work for a larger type of business then you're going to be managing a lot more closely the accounts payable most likely. Why is that the case because for example if I got a bill today for $100 and I could pay it 15 days from now or I could just pay it now which would be the easiest thing to do. Then I would I would just pay it now like what's the point. I'm not going to wait till 15 days it's due. I'm just going to say it's I'll pay it when it's due. But if I had a lot of transactions that 15 days becomes relevant right 15 days for $100 doesn't make much difference. But if I had a thousand transactions for $100 or I had a few transactions for for thousands of dollars then the 15 day difference makes a big impact on our cash flow. That's why we would we were going to try then from a cash management standpoint to pay the bill as late as possible so that we can hold on to the cash as long as possible and earn interest on it or be able to use it in our business basically as long as possible. Without angering our vendor in the process and while still being able to take advantage of any kind of discounts like cash discounts that we might have.  Because it's probably not going to save you a whole lot of money when you're talking about low low amount of transactions and low dollar amounts. But again as the transactions get larger that becomes quite significant that 15 day period and so therefore you're going to be managing the accounts payable a lot more. So we have the accounts payable on the book if we look at it this way the vendors are up top. We entered check forms last time when we paid like our credit card bills I mean our utilities and whatnot. We could have used an expense form same kind of idea decreasing the checking account. This time we're imagining the bill was entered with a bill form. However it was done when we entered the beginning balances when we added the vendor then we entered the amount that they owe us then it generated a bill automatically and then of course we're going to pay the bill with a pay bill form. So quick reminder how this happened. Here's our bill and accounts payable. If we go into it we can see that the let's go back to 2023 on the date range. We can see that we have the bill 15,000 was put in place. Other side went to opening balance equity because it was during our starting process I'm going to go back and exit. There is a sub ledger to the accounts payable just like there is to the ARR account up top. This time not breaking it out by customer but by vendor. We need to know by vendor. So let's go to the tab to the right and right click on it and duplicate it and then we're going to go down to the reports on the left hand side and then close up the hamburger and looking for the reports that support the accounts payable. Not going to be who owes you it's who you owe what you owe okay. So then we have the accounts payable agents and so on which we might talk about later but we are just want the classic report which is just a sub ledger the vendor balance detail. I'll right click on that open link in a new tab going to the new tab closing up the hamburger and so there we have the dates and obviously there's only one thing in it. So it's not that interesting but if we had multiple vendors in here then all the vendors would add up and the total broken out by a vendor would match what's on the balance sheet as it does here. And it always has to match by the way because with the accounts payable like with the accounts receivable QuickBooks will not allow us to post something to it without adding a vendor. That way QuickBooks is saying I'm going to make you have the have the sub ledger work out because we're going to make you assign a vendor every time you enter something to accounts payable. All right let's go and check it internally if I go to the internal and attract the expenses area which I would call the vendor center that's what it used to be called here. It's going to be a lot more important like with the accounts receivable side on the customer side when we had outstanding invoices it was a lot more important to then manage the center for the customers. On the expense side it's the same thing if you're just paying the expenses as they become due you're probably not going to need to come in here that much unless you want to look up a particular payment. And even then you're probably going to drill down on the account and find the payment or in the cash account from the reports. But if you're using accounts payable it's going to be a lot more important because you're going to have to manage the bills that you're going to pay and which ones you're going to pay and when. So multiple places we can go to find them we can go into the expenses tab and then we can sort by this time bills. So there's all of our bills all one of them we can filter the bills for the status of all status open overdue or paid. So the open bills means we have not yet paid them overdue of course means that we're going to put the due date when we enter the bill. Not everybody does that by the way. But if you're managing the bills and trying to pay them as late as possible let's just take a look at that. Wait a second I said I said let me see this one more time open not paid and then pay and then we paid OK. If you go into the bill let's check it out. Notice we have the bill date so we might enter the bill date basically when we got the bill now the due date is over here. Now a lot of people kind of ignore the due date when you're just when you're just because you're just entering the bills fairly quickly right. Similar to the checks and you can't usually use the terms like you can with an invoice because it's not like when you get the bill it's not going to always be 30 days away. Because you don't know exactly when you got the bill it might have been mailed to you or something like that. If you're managing and trying to pay as late as possible you got to put the due date of the bill in there so that you can sort your information over here by due date. And then you can pay your bills as late as possible while still taking into consideration any cash discounts you might have. And then you can sort this on the bills side as well which is probably the most likely place to go when you just want to look at the outstanding bills. So you've got the bills here we've got the vendors drop down and the bill dates that we can manage on the filters. And then the breakout between unpaid and paid is by tab now so these are the unpaid ones it's going to shift over to the paid ones once we pay it. If we go to the vendor tab we can also manage our bills over here we've got the quick filters up top we can go into the overdue quick filters. There we have it and there's our bill the next thing we would do of course is make a payment we could we could create a bill create an expense if we needed to. But we can make a payment by clicking on it like this and it opens up the bill payment form and it lists the bills down below. So notice when we open the bill payment form if we had multiple bills it would have multiple bills down here but it checks off the one that were opened automatically. We can also just go into if I close this back out and I go into the plus button up top and we're in the vendor section there's our bill here's our pay bill form. If I go into that it's basically the same thing it's going to come out of the checking account the date let's put on the date what did I want on the date let's try to tie this into my practice problem. Let's say it was the 25th let's go to 28 let's bring it up to 28 and then I have to change the check number because we messed with the check numbers before because I messed them up. So we're on 1011 I want that to tie out to the future section or course for the bank reconciliations and then we've got our bills that were entered down below. So if we have multiple bills we can check off multiple bills this is another area that we can sort the bills by so we've seen multiple errors we can sort the bills by to then pay the ones that we want. Now it's possible to pay part of the bill over here so if I just paid like a thousand dollars of the bill do you know I don't want to leave if I paid a thousand even know what you're talking about why did you even why would you even suggest that I didn't click on anything. Whatever we could pay a thousand dollars of the bill and would look like that but we're just going to pay the whole thing off. You did it again I don't want to leave. What in what made you think I did QuickBooks. Oh dude. So in any case and then so there we have it and then if we were to print these items then we would want to select the printer we can print later or we can print them as we go. So if we were actually physically printing checks we would still need external checks that we would be purchasing putting into the printer having the start number line up to what's on the actual checks and be able to then print them all at one time if there was more than one check or even if there was more than one check. And then if we're don't want to have checks and we just want to make it like it's an electronic transfer then we can simply delete the the check number here and we'll use the same pill pay bill form but which is just a reduction to the checking account like an expense form or normal check form. But we won't have the check number on it. You can put like it like some other indication that it is an electronic transfer or something like that possibly. And if you're writing checks with your checkbook and not printing them out with QuickBooks you can do that too. You just want to make sure that you still line up the check number and you just simply won't print them kind of like what we're doing here. I'm imagining I'm handwriting my checkbook here which has check number 1011 and I'm going to send it out right. So then when I save it I have the options to save it save and close or save and print. We're going to go ahead and save and close when we do what's it going to do. It's a pay bill form. The first thing that should come to mind in a pay bill form should be that it's it's going to be decreasing the accounts payable. Now that's kind of the other thing that should come to mind is it's decreasing the checking account because the pay bill form is a type of basically check or expense form form that decreases the checking account. But the thing that makes it special or differentiates it from an expense or paycheck form is that it's decreasing the accounts payable. So let's go ahead and save and close. I'm going to stop saying right. I'm developing a tick to say right all the time. Is that right? Do you agree? Do you agree dear listener with my assessment? Okay. I'm going to stop doing that. I can feel it. I feel that happening. So if I go into my accounts payable, I'm going to go into the AP and so if I go back to 2000. Here we go. So now we've got the bill and then we've got the pay bill. That's the pattern we expect to see in the accounts payable similar to the pattern we saw in the accounts receivable where we had the increases with an invoice that decreases with the receive payment. That's all we're going to see here. Notice all these other accounts that we look at, they're a lot simpler to look at the detail than the checking account. If I go into the checking account, notice it's a mess because there's a lot of stuff happening here. And so now I have another kind of form here in the checking account, which is another check form. And we could have a bunch of different transaction types that go through different cycles in the checking account. Why? Because the checking account is the lifeblood of the whole accounting system. It's running through the veins of every cycle. Whereas every other account has its own special duty and it's not part of every other system. It's not interwoven in every other system as intimately as the cash. So but on the cash side, we have the payment check. Notice it's still just a check. We have a check number, but now it's a bill payment which tells us specifically it's an accounts payable related one, which we already know as well because it's in the sub account over here. Notice it's really, I like it that QuickBooks has these other forms to give us an indication that this check, this decrease to the checking account has a special use. But it also gets a little bit tedious as well because when I filter and sort for decreases to the checking account, I have to take into account and remember all the different kind of decreases there are. Like in the desktop version, for example, they don't even have a difference between an expense form and a check form. These two forms are basically the same except that one has a check number and one doesn't. So you could just use the check form and not enter a check number for those items where you're not doing a check. You could put something else like E for electronic transfer or something like that. It's the same type of form. I said right again, didn't I? I totally did. I'm going to stop that. Stop that. So these forms are basically the same. This form, same kind of thing as well, but this time the other side's going to the accounts payable. So if I filter over here and I just want to look at the decreases and not the increases and I add a filter. Usually we often filter by type, right? Am I right, people? Am I right? And then we're going to say this equals and then I have to find all the ones that I need. So like expense form, expense. Why aren't you expensing? Oh, there it is. Expense form. And then I need to find the check form. Let's say check. Oh, man. Let's go back up and search for check. What is it? My filtering option to search. Check form. And then I'd also have to search for the other bill form. See, it's a little bit tedious to filter. Whereas if everything that decreased it was one form like a check form or an expense form, whatever you want to call it. Then it would be a little bit easier. So there's some pros and cons to that. Just want to point that out. Not criticizing the point. I think QuickBooks's detail there is nice, but everything has its ups, its downs, its ins and outs. It's complicated, you know, a lot of ins, a lot of outs. So let's go to the, to the, to the sub ledger. And the sub ledger should disappear now. Nothing's in it. If I look at it on the internal side of things. We can then say, let's go to the right and open up the hand buggy. And we're going to go down to the expenses area. Close up the hand buggy. We'll go into the expenses. And if we look at the bills, so now we're looking at the bills and we can filter them by all status. Or we can filter the open ones and apply. So no open ones at this time. We can say we want the bills filter and overdue or paid status. There's the paid status. We would more likely be doing that in the bills area because that's what it's here for. And so the unpaid are gone. And if I go to the paid side, there's the paid side. So we can, we can show the payment here. And it gives us a nice little showing of the payment down below, which is nice. We can then open it up and see the full bill. It's paid over here. It connects to the payment. Everything is linked together. So there's the payment. I can go into the payment. If I so choose, there's the pay. There's the bill payment, which made the check. So everything's tied together over here. It's all integrated and whatnot. If I go to the vendors, which is nice. And then so now there's no overdue or open bills outstanding.  And who was it that we paid? I forgot it was, uh, it was epiphone. Yeah, there's a bill. There's the bill. And then there's the bill payment. So these things are intimately connected.  Boom connected together. And so I can see my payment right here. And we go into that. Everything, everything's connected together and that ties out to the bill. So very nice, very nice. Okay. All right. So let's, let's open up our trial balance to see what has happened over here. Uh, the trial balance. That's not the trial. But here's the trial balance. And we're going to see K for crying out loud. Paso was my Spanish, my Spanish English K for crying out loud. Paso K Paso. Let's go ahead and run it. And then, uh, this is what we have thus far. We've got the balance sheet on top of the income statement. And so if we just run through, if your numbers tie up to these numbers, great. If not change the date, see if you can increase the date, see if it's a date issue. If it is drill down to the actual form, possibly change the date from there. Balance sheet on top of the income statement. So we got checking account. It's a cash account. The ARR account is an accounts receivable account. Is an asset. The inventory is an asset. Investment is an asset. Payments to deposit asset. Accumulated depreciation. The funny contra asset bringing down the assets tied intimately and part of an asset. The furniture and equipment, the PPE and the property insurance is an asset prepaid insurance. The assets are one side of the coin. That's what we have not measured in units, measured in the measuring stick of dollars. Even when we're talking about furniture, the couch is measured in dollars and whatnot. So that is that. And then if we go to who has claimed to them liabilities, no, it's now zero. That's going to be the third party of vendors. We've got the loan payable, the bank, and then our claim to those business assets in the equity section, owner investment, owner's equity, and then part of owner's equity broken out, giving us the last year of information, the story of what has happened last year. And I'll tell you what, it was a great story, one that you're going to want to stay tuned to as we go forward because it's not over. The story is not over. But if I have a loan, the story is not over. But if I add this up, 46877 plus 5180 minus 37242 minus 500 minus 410 minus 620, that gives us 13285. And then if I go to the income statement, we can see that the income statement is 13285. If I go back to the trial balance and I was to add that to the equity, oh man, what did I do? Let me do it again. 46877 plus 5180 minus 37242 minus 500 minus 410 minus 620. And then plus the equity, which would be retained earnings if it were a corporation, 77896. I get to 91818, which we can scrunch together in one number by going to the following year, 5103125 and run it to refresh it. And so there, see now it's everything is inequity. Income statement, part of equity. It's just giving us detail in essence about the equity, which represents the book value of the company, assets minus liabilities, giving us the story of what happened last year, not the whole story, not going back to the beginning of time, just like a movie doesn't do that. We're only telling like a year's worth of story, or like that show 24 that was, I guess that's a pretty old show at this point, but it just goes back one day, right? Because otherwise it would be a long, really long story and you couldn't keep people interested. So there's that.