According to my tasks page [0], it took me 10 hours to carefully read the MDN CSS module on CSS building blocks while taking handwritten notes [1]. I started reading it back in December, and finished late February. Not exactly what I'd call an exciting read.
It took another 3.5 hours to transcribe those notes [2]. ~33% time overhead seems to be pretty constant for transcription I've noticed.
I'm still plugging away at Designing Data Intensive Applications by Martin Kleppman, also taking handwritten notes [3][4]. Currently 27 hours in and I've just hit the halfway point. It's a big book crammed with stuff.
I've sometimes been called a "tech maximalist" because I buy separate devices for things like timers, alarm clocks, lights, and calculators, which are all things I can do on my phone.
In theory, I feel like my personality *would* be the type to turn my phone into a multifunctional tool. I *shouldn't* be this so-called "maximalist". It doesn't fit. Pocket computers have been a part of me for a loong time. I was the weird kid walking around with a palm pilot who did everything from notetaking to musical ear training. But, in reality, the phone software/hardware ecosystem is a mess. Also their UX has too much in common with a slot machine. I just want to be as dispassionate and distant as possible towards this rectangle.
@hazelweakly probably the risset rhythm. It's a neat audio illusion that sounds like the beat is infinitely speeding up or slowing down. fold4,wrap5 by Autechre [0] is a beautiful example of a risset rhythm being used.
This is about the second time someone was willing to pay me money (try to) make their audio DSP "go faster". Which is a terribly shitty task.
Render a full track in a DAW time how long it takes. That's how long it takes in the industry. If you're asking for it to be faster than that for your stupid music app without sacrificing quality, that's a big ask I probably won't be able to do, and you couldn't afford it even if I could.
- high contrast high density display - works in sunlight - tactile interface - insane battery life - DRM free - low latency - non-volatile storage resilient against power failures (rain/water not so much)
Controlling Kodi/Libreelec with a wired controller is so much more responsive/reliable than a wireless controller. It took me 30 seconds of using one to get an extra controller (I've been wanting another one anyways so this was a great excuse).
In about a week or so, I am planning on returning to my Rust DSP library, called BoingBoingBoing [0]. I have set up a roadmap/todo list. The hope is to port a large portion of sndkit [1] functionality to this library. At that point, I intend to take advantage of Rust's WASM support to create more interactive web-based audiovisual compositions and experiences.
I do want to get some of my gesture synthesis stuff working with Boing^3 as well, but I want to think about it, as there's too much "rewrite in Rust" syndrome happening already. I'm thinking about another portable system that already works with my current C based environment [3], whose data can be meaningfully exported like a file format and loaded into small environment implemented in Rust. Kind of like what WADs are for Doom.
Sound artist exploring the human voice, simulacrum, and mechanisms for lyricism.These are some of my favorite things: vocal synthesis, generative music, Palestrina, audio DSP, baking, croissants, tea, dogs, grids, retrogaming, computer graphics, powers of 2, 1-bit art/sound.Over the years, I've developed several audio engines and music software ecosystems, and like to talk about them here. I also have a quieter account where I mainly talk about vocal synthesis: @patchlore