Finishing touches before V2.0 release!

Just commented some debugging code and recompiled everything for the V2.0 release.
She’s ready!

A nicer alarm

Check it out! Much nicer than a text box, don’t you agree?
This means that V2.0 is finally ready to ship!!!!
tomorrow
it’s 2 rn ;-;

INSTALLER

also the setup menu is working correctly now.

Making the installer was SO EASY ITS INSANE
people (windows devs) really need to do this more, It’s one of the easiest ways to make your little project feel more professional, like a real, big boy application, not just a silly program you made.

SHOUT OUT TO INNO SETUP
would not have been possible without it. It’s great, check it out!
Drew orph myself btw :)

2.0 is so close, I can lick it! The only major feature left is a better alarm! yippee

GUI config editor almost complete

after much pain and memory wrangling, the config GUI is almost complete! I just need to fix a few save/load bugs.
It looks very stripped down at the moment, but I’ll be sprucing it up soon, you’ll see.
1st 2.0 feature (almost) complete!

Improvement of UI WIP

I’ve started work on improving the UI of the program, specifically the config setup, using
Raylib!
It’s going well so far, but I’m not quite done yet
I’m really not looking forward to having to deal with keyboard input ;-;

V1 COMPLETE

It actually happened! I implemented every feature I wanted for V1!!!!!!!!!!!
of course, it looks pretty bad at the moment. But all of the core features are working.
User input isn’t broken, it runs in the background, and it actually rings at the correct time.

First ship, here I come!

Ok, I’m going to ship V1 in 2 days.

Cuz I wanna be able to buy something from stardance

here’s the plan:

1. update readme
2. finish user input
3. make it run in the background (maybe)
4. make sure it works

Will this pan out? we’ll see.

Bare Bones functionality

This project is migrating from Out To C, so this is a fairly large devlog. (I’m moving because I like the fact that stardance forces me to log my work, and I get a wider range of prizes)
I’ve pretty much completed the bare bones functionality of the program. You can set your target time, and it will automatically store the settings and ring at the right time.
There is still TONS to do, so stay tuned!

Command line arguments

now you can control the resolution and framerate at runtime!
It runs really slow rn though

Version 1

pretty much the minimum viable product.
just a screen, with random colors every frame

but i don’t plan on stopping here >:)

Fancy Keys!

I added piano keys!
also fixed the mounting holes.
custom knob next???
(actually I should fix the firmware first…)

Loopback not working. Loopback REALLY not working

so tl;dr windows audio loopback is driver dependent and basically useless. all the work I’ve done, while not completely a waste, is a lot less progress than I would have hoped.

fixed up my old visualizer demo though
that’s cool

Loopback working! (for now…)

I can definitally see some flaws in it, but it’s working!
It’s actually capturing audio!
next step is to make a very basic visualizer to actually see what it’s capturing
Stay tuned!

Prototype: 33% complete

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 ;)