convoluted connor @notwa@witches.town

I had a lot of fun today trying embedding methods on guitar cabinet IRs! dunno why I hadn't thought of this before. I'm still fine-tuning it all so I can find the most similar dozen IRs given any existing IR in the dataset. I just wish I still had a firewire port so I could plug my guitar into my old interface...

these manifolds look a bit like landforms https://witches.town/media/VEtl_s6HpWqVm89qM6U https://witches.town/media/rQ6vzm_5aTpCCbAHGcM

wait, is the tremolo effect on the guitar in Talk Talk's Myrrhman actually a Leslie speaker? did it take me this long to realize this?

woo https://witches.town/media/OLlhUs9avT4hHJEK2Xc

I can't fix my sleep schedule when it's getting this cold every morning

also neither of these games use more than 128 unique instructions, so you could just drop a bit and get 12.5% for free*.
* not including the LUT cost, but this is all theoretical anyway.

the main ingredient y'all

quick and *very* non-exhaustive test shows MM only(?) has ~25% more code and compresses a couple percent better.

would you have paid the price of dedicated decoding hardware to fit 30% more code in your NES game? i wonder…
if my interest in this persists, i might try this with megaman 1. it's a bigger cart to begin with, so it might take a lot more work to trace all of its subroutines, or maybe i'd just source the disassembly going around.

the answer is not quite 30%. i used Golomb coding here, but Huffman yields a very similar result.

also this code is kinda bleh (i even just spotted a var called 'asdf' and an off-by-one) but i don't feel like working on it anymore tonight.

let's find out much compression of opcodes (not including their immediate operands) would reduce the code size of Super Mario Bros.
https://gist.github.com/notwa/1aba32c1dd5fa60862aa63e7b7665b6f

i could make a bunch of toots about this analysis of opcodes in Super Mario Bros., but instead, i think i'm just gonna post the python notebook once i clean it up a little.

using C is like, "check out this thing I made!" and it's some janky looking thing that falls apart as soon as it leaves my hands. "sorry, do you have a working toolchain with a recent compiler? how standard-conforming are your header files? did you build all the dependencies? are you any good with shell scripts? you know what, forget it."

maybe this year I'll try moving away from C, even if I don't venture too far from home. C will always have a place in my heart, but having to work with it isn't something I wish upon others.

these are surely the same developers who decided to put their documentation in that special gnu info tool that nobody ever uses instead of just writing it all in the man page like any sane person. why they gotta be so extra all the time

i am irate. i know how to make the compiler do what i want, but instead i'm googling some meta-meta shit about how to tell autoconf to tell automake to tell configure to tell make to tell the compiler to do what i want. christ on a cracker.

why does autoconf exist again? seriously, what the fuck were they thinking?

augh i'm so bad at putting names to melodies. i'm just gonna guess whatever i just heard was a cover of an sm64 song

I don't know what's going on but I think that's okay.