Doing a final once over the code and docs. Probably not going to add tests to this project as its just an example project that I’m not planning on using anywhere special. The docs however are now really detailed, and lots of comments explaining everything. I think I’m also finding my documentation often follows a bit of a template Also, finding lots of re-usable code, which means it all could be useful in importable utilities...
Created a video to share on social today. It only took a day to create and included: 3D rendering / animation animated text circuit visualisation usage demonstration construction demonstration web app recordings The editing part probably took the longest, however the 3D animation probably took the longest. Although I used existing 3D models, I needed to texture, and do the animation myself....
received some feedback regarding the use of the audio cable / jack for the controller connection. If the jack is pulled out while there’s power, then there’s a chance of a short. I’m yet to deeply look into if this is actually possible with the way the circuit is designed, but its good to note. There’s defintely better options available for type of connections in this case, so I’d be more inclined to use them in future....
building the controllers and input interface so that its much more usable with the app, current design allows the use of audio cables, so its super easy to connect the controllers to the pico via audio jacks building stuff in electronics can be slow, and has a whole host of dangers to keep in mind thing randomly popping into the air hot solder and solder fune...
considering using Tau * 1000 (tausend) - 6283, to represent potentiometer value getting the values aligned between button up and down is a little difficult, but it’s likely a “close enough” situation. Not sure if its better to calculate “real change” values on the pico or in the app, will test this. Get tripped up on passing a float to sleep_us, this the annoying thing about using an IDE without any kind of function / type suggestions....
Bugs from yesterday were solved relatively easily, so not sure code architecture is an issue (yet), was mostly caused by not fully thinking through the implementation, for example, setting the position of capsule in a sequence to the note index, despite it being incremented beyond after the active circle value is already set, and not resetting the capsule state back to the initial value when re-occupied some tone....
adding the capsule to the sequencer note looks strange because it seems to be offset or ahead of the active circle the collision detection and state change for a capsule in a sequence is super hairy, need to make it more coherent, seems to be calling code in all different places, right now this results in not being able to enter them without having forward active, might be just a little bug somewhere...
Getting polyphony to place nicely is difficult, there’s definitely an upper limit to the amount of synthesized sounds being played. Changing the rate of sounds, and their speed affects it, so something to do with synthesizing lots of sounds rapidly seems to kill the efficiency. Resolve to use 2 polysynths playing different sounds, mix the sounds between them makes it sound nice, along with randomly changing and sharing notes etc....
trying to find a simple displacement algorithm, can’t seem to find one well, displacement is just acceleration (which in this case is a continually decreasing value), multiplied by time delta, + velocity (just a displacement unit over time). Acceleration decreases a certain amount each cycle. Most of the code for something like the character can be put into the player’s class instance (like “draw”) if the drawing context is passed in....
I’ve decided I might make the game and “controlled” thing first, because I figured I could make some design decisions for the controller based on how the game ends up looking. Create a basic game design based on elektroplankton Utilising an stripped down observer + web component system to render the web app Getting player character to move around the screen space, nothing fancy - no momentum, smoothness, personality, just moving around the screen...