525 karma · joined March 13, 2012
wiggle the cables around to see if and when any of the lights flicker, indicating a bad or broken connection. i've found a few bad cables that would intermittently fail.
No reason this project couldn't add midi controller support directly to the backend (not via TUI!).
In a DJ TUI, how to represent the track waveform? Encoding waveform amplitude in ascii blocks or dots is a pretty low fidelity representation. Instead, you can encode waveform amplitude in single row of blocks with 256 color/intensity averaging the backing sample peaks.
And's if you ever do stems separation you have 4 such rows for each track - efficient and dense!
As the track is playing, or user is zooming or jogging, this representation would give more of the feel that the playhead is moving through the track smoothly.
maybe something like:
- this specific part of the carpet is the best place to enter onto it
- once successfully on a carpet, stay on it until done cleaning itbeen looking for something like this! will definitely check it out.
Walk this way: https://www.wario.style/s/Eg9zi56k
Live and let die: https://www.wario.style/s/8qt4OfdS
Ramblin Man: https://www.wario.style/s/wSd51DBA
Smells like teen spirit: https://www.wario.style/s/CQq6Dc6f
Paranoid: https://www.wario.style/s/202Hs3lV
and of course...
Stairway to heaven: https://www.wario.style/s/SNPSmI8u
We had an unused coax (which we disconnected from the outside world) and used MoCA adapters (actiontek) and it's been consistently great/stable. No issues ever... for years.
I think the unambiguous term for this is "Dynamic Range Compression"
Love the idea of "coding" while walking/running outside. For me those outside activities help me clear my mind and think about tough problems or higher level stuff. The thought of directing agents to help persist and refine fleeting thoughts/ideas/insights, flesh out design/code, etc is intriguing
https://en.wikipedia.org/wiki/Bombing_of_Tokyo_(10_March_194...
napkin math:
410GB/1000 dumps = 410MB per dump?
410GB/2000 dumps = 205MB per dump> Why is the project called doxxer? Because it's like somebody who doxes, by exposing the version information about Git repo to you!
My lessons learned for prompting were to have project broken down into clearly defined modules (duh...), and to constantly feed the latest module source back in as context along with the prompts. This helps ground the responses to only adjust the code related to the prompt, and to not break stuff that was already working.
Should we be checking in our prompt history into version control as a kind of source code or requirements spec? Seems prompt revision and improvement would be valuable to keep a history of.
Proposed Solution 2 without ACKs would be vulnerable to message loss if a worker were to crash before successful message delivery.