25-AUG-2026

25-AUG-2026

1352

Added some quotes to the rotation, I don’t love how I have it set up right now, probably will move to a single structured file that compiles to the multiple files at build time or something, good enough for now though.

Work on stuff here has slowed as I’ve been working much more on getting the kiddo ready for kindergarten, and planning an office move to a much larger space. I’ve started thinking again about a whole-lab sound setup as well. It’s been on my punchlist for several years now to build some sort of network-attached-sound system. I have a number of SFFs and RPi’s that connect to most of the noisemaking things in my house and a many-to-many mapping system would be a very nice thing.

It coincides with me wanting to push my current daily driver machine, a M2 Studio named Hedges, to be more of a dedicated music/recording machine and less of a ‘do everything’ machine. When I initially concieved of it, I had planned an analog approach of just sending everything’s sound to a central mixing console, and then having the channels AUX into Hedges UMC1820, but this would only ever really be useful in relatively small area, as I don’t want to try to run the 50m of speakerwire through walls, especially given it’d need to be shielded. I looked into using JACK at the time and plan to look again, but I planned all of this in the days where wiring up JACK required what felt like a PhD in audio engineering, I’m hoping LLMs can take some sting out of it for me. I’m not looking to be a pro audio routing engineer here, just get my noises all filed into one box where I can mangle them and spit them out into my ears.

Much of that work may be hidden as I haven’t sorted out a way to expose my monorepo that doesn’t also expose the absolute mess that is my monorepo. Most of my projects start out as subprojects of angband. angband currently contains the live version of minas-tarwon, the homelab infrastructure from metal -> k8s running services; truncheon and all it’s constituent parts (including an army worthy of Mordor); and a bunch of other stuff that’s worth talking about, but not necessarily sharing code for (yet). I set up josh a while ago and have half an idea about using it to extract some of the code to mirror repos. The main issue is most of the monorepo is unsharable because I don’t build those projects with the intent of public use, so I’m quite happy to hardcode all sorts of stuff about my system and network. For instance, I have in that repo a tool called thrak. thrak is a CLI for the monorepo itself, it is not a very well made CLI, but more because it has no specific remit other than, “I need a place for this specific tool to live that I can use from my laptop when I’m in this repo.” Some people use just or make or rake or whatever, I’ve been all those people, but at some point I always end up thinking, “If only I’d just written a damn CLI, I wouldn’t be wondering about the call order or having to write so much friggin’ shell.”

I suppose probably the better thing to do is a careful migration where the tool is built first and projects imported, but that is a lot of work for a tool that has a constituency of one.

Since ‘constituency of one’ describes most of those projects, most of those projects are not really the sort of thing I’d feel great putting out into the world, and so much remains hidden.

I don’t have a solution I just felt like writing a bit today and this is what came out.