Remember how I said I was going to write up how I fixed the Akumajo Dracula MIDIs for old MT-32? Well, as I was writing up the technical details I discovered I was *completely wrong* and none of this worked the way I thought it had. Join me for a weird and surprising MIDI deep dive. https://www.mistys-internet.website/blog/blog/2026/08/25/how-i-fixed-an-mt-32-midi-soundtrack-for-the-hardware-i-use/
10
Replies
1
Boost
@misty I joined and I now know about "Bubblegum Octopus" and MT-32 MIDIs. Thank you for your time.
@vramvoolenaar Thank you for reading! I hope you enjoyed the music.
@misty very serious question: how are you running octopress in 2026 still? The last time I tried to get it working I got stuck in a hellscape of ruby dependencies that don't work. So https://warewolf.github.io/ continues to be a site that is largely dead :(
@xabean It requires Ruby pre-3.0; I'm running it on 2.7.3. With that Ruby version, it works just fine with its specified set of dependencies.
I am planning on tackling a jekyll upgrade at some point though.
@misty thank you, this might help me actually get back into documenting my side projects again. ❤️
@xabean You're welcome! Let me know if you still have trouble, I might be able to help.
@misty I think my biggest problem is that I'm not a ruby dev so the whole ecosystem of bundler v.s. system packages is a nightmare to me https://warewolf.github.io/blog/2013/04/28/adventures-in-ruby/
@xabean Absolutely makes sense, yeah. Well, if you do have trouble with those getting it running, just let me know and I'll try to help! And if I do manage to get it updated to newer Jekyll, I'll let you know.
@misty mmf, I'm still running into the same problems, basically that octopress is from 2013 and I live in 2026 with 2024 software. 2024 compilers don't like 2013 Ruby gems, throwing loads of compiler warnings/errors including some transition-period yajl-ruby-1.1.0 rb_cFixnum to rb_cInteger where one part of the ruby ecosystem transitioned over and another half hadn't yet. :/
I feel like my problem is I'm basically starting over from scratch in 2026, and hoping decades-old software will compile, rather than what I'm assuming is your situation - a lovingly curated local Ruby install maintained over years that continues to work.
@xabean Are you using rbenv? Using that and ruby-build, I found it wasn't too hard to get an older Ruby going, and once I had that older Ruby I could install the right gems in it. I'd suggest trying to add a .ruby-version file to your repo that says 2.7.3, set up that version with rbenv and ruby-build, and see if that helps you any!
