Loopback pain very sad
First thing I’m working on is the audio loopback,
grabbing the sound going to the speakers.
Since I’m doing this in rust, I’m using the cpal library, which is kinda annoying ngl
It seems to support most os so hopefully I won’t have to deal with that myself.
I think I have a working setup, but we’ll have to see
To-do:
- [] Getting system audio
- [] analyzing the audio in real time
- [] generating the pretty picture
- [] displaying to the background
- [] add customization (optional)
Devlog the fourth: IT MOVES
You heard it right folks: I’ve finally got something moving on screen!
didn’t capture it though cuz I didn’t feel like setting up screen capture rn
despite the progress however, C just doesn’t feel right for this project. I could get it to work, but it would be hard to expand, which is the opposite of this project.
the road ahead (realized “roadmap ahead” didn’t make sense”)
- this repository’s getting rusty ;)
Devlog the third: IT’S ALIVE
I mostly finished up the cmake config! it was actually a bit easier than I expected (although I did have to ask gemini a few questions)
I don’t think I really understand it fully though, so I’ll keep tinkering with it while I move on to the next things
speaking of which…
the roadmap ahead:
- tinker with cmake a bit more
- drawing something on screen!
- prettying up the code (header files and what not)
- MOVEMENT crazy stuff, I know.
Devlog the second: Ok quick detour, I promise it’ll be fast
so I’ve officially decided on using C for this project (for now…)
I technically know how to write C, but I don’t know how to do so effectively, if you know what I mean.
also I need to link raylib to get the program to compile
So, why not use this as an excuse to learn all about compilers, cmake, .h files, libraries, linking, gcc, sublime text build systems,
seems like a lot, is a lot
the roadmap ahead:
- setup cmake so compiling with raylib isn’t annoying
- setup sublime text so running cmake isn’t annoying
- compile with raylib!
Devlog the first: the beggi the beginni the beginging the
just set up the github, and made some rudimentary structs
I won’t lie my C skills are Rusty af
the roadmap ahead:
- drawing stuff on screen (raylib my beloved)
- making a circle drop (force -> velo -> pos)
- more circles
expect this list to shift as I move ahead on this journey ;)
Firmware time
Omg the firmware is so much harder than I hoped
I have no idea what I’m doing, I’m already tired and stressed, and the resources haven’t helped much so far.
This feels like trying to piece together a program from someone else’s random programming language. At least it has ok documentation (for what I’m trying to do), but it’s just
so
confusing
omg
I’m like entering crash-out territory on this project
Need help!
Bro I just want to be done with this project
hsit just keeps getting fuffufd bro
so heres an updated list
- knob (might just grab a model off the internet
- keycaps (might just buy some)
- color (different print filament?)
- holes (why is this explained so vaugely in the guide bro im gonna crash out over this these stupid freaking holes omg)
- firmware, still gotta do that
so uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
yeah, not goin great rn. Maybe I should have just made a 3 key rectangle…
srry no new pic this time, im just too tired rn
Been working on the details of the case. I’m really pulling out all of the stops (that I am aware of) for this project. Here’s the rough sketch!
Man I wish I made the case together with the pcb. having to go back and edit the pcb because something didn’t turn out quite right on the case is such a pain
Lapse ate 2hrs of work today, turns out I’m not supposed to pause the recording and then turn the computer off or else the recording corrupts silently. if anyone knows where I can find the 3d models to the components, please tell me!
New pcb design, hopefully it’s good! kudos to Anicetus on slack for the idea
BIG problem, pcb too big. need help!
