Using nix to maintain my fleet with automated updates so I didn’t really need to worry about it thankfully; just checking that I had relevant/patched versions. All my services are nice and up to date so didn’t even have to take anything down (yay)

What I’m excited for today is to progress personal slop project (be gentle) I started yesterday. Hoping it’ll just be one or two weekends.

I’ve been hallucinating a transcoding suite/workbench. Includes experimental sampling matrix of ffmpeg settings with a composable / layer-based project configuration; rust egui+mpv desktop client. Then the hosted orchestration server can distribute ffmpeg jobs across my worker machines (via my local headscale tailnet). Output produces a project+metadata bundle that includes hand-picked source:result JXL frame comparisons alongside both human readable reports and client readable configuration that makes the projects (more or less) reproducible (with worker tool env versioning via nix flake.lock) and logs provenance.

I intend for this to be a replacement to the piles of crappy python scripts I’ve been using for the last decade; my current workflow is to move files into host-labeled ingest folders with an argument string in a text file, then ssh to the host to run the job.

But what I’m most excited for is the experimentation matrix. I hope that it will reduce my electricity usage and disk thrashing; it will let me sample settings for ~1minute of footage around the sample frame and let me iterate my tuning much faster. Currently, it’s faster (in terms of hands-on time) to just transcode whole episodes or even entire seasons multiple times with different settings and then just discard the ones that underperform. Extremely wasteful; testing a settings matrix is something I’ve always wanted, but never had the time to build (and still don’t, hence slop).