|January 25th, 2020|
|contra, jammer, music, tech [html]|
My rhythm stage setup is in an awkward position here, because general-purpose computers aren't all that reliable. Not only do computers sometimes break, but my setup isn't something I can properly back up, and could be hard to replicate on another computer.
This is a silly situation: one of the amazing things about computers is that copying things is free. I should be able to upload my setup, and then download it onto any other computer in minutes, and be going right away. Why can't I do that with my stage setup? I found out yesterday when my computer died and I was trying to set up a new one  before the next Kingfisher gig (Saturday). Issues I ran into:
These sounds were running in Kontakt 5, and the new thing is Kontakt 6. While I could restore my Reaper session from backup it wasn't able to transfer my settings between Kontakt versions. I needed to manually set a zillion individual sliders (ex: "Hammond > Amp > Rotor > Balance > One notch CCW from top"). Luckily my old computer was working well enough to let me read the settings, with patience, so I've now documented them.
I haven't succeeded in building my Bass Whistle Plugin in a way that will run on computers it wasn't built for, so I needed to rebuild from source. This required downloading the plugin SDK, which then didn't work against my forked copy of the plugin framework. It turned out to be easiest to start with a fresh copy of the framework and copy over my implementation on top of it.
The Reaper export doesn't seem to keep track of MIDI mappings, so I needed to tell Reaper about all of my MIDI devices and which device controlled which track. There's no information here, it's just "
jammer-hammondshould drive the
hammondtrack" but it's still fiddly by-hand configuration.
Some of my sounds that use Apple's DLS Music Device with ReaControlMIDI are getting EXC_I386_DIV (divide by zero) errors and crashing Reaper. I use sounds like these for cases where I want a simple overlay on top of the piano, because they're very fast and responsive, and not taxing on the computer. They're not great sounds, but they're much better than Sforzando with the free Fluid_R3 sound font. I'd like to post my crash report to the Reaper forum, but I'm waiting for my account to be verified. (posted now) If I don't have this sorted out by my gig next weekend I'm going to need to find adequate replacements for a bunch of sounds.
There were, of course, other parts that went well. My main routing code is open source and worked out of the box. My stand-alone pitch-to-midi code also had no issues. My Reaper backup worked ok aside from losing plugin settings. Part of me wants to move entirely to an open-source synthesize-everything-myself way of doing things so I can just download and run my software, but this bumps into the hard realism of creating sounds being difficult and requiring skills I don't have.
For years I've tried to live my life so that if my computer died tomorrow I wouldn't lose anything, and while that's true from a "lose data" perspective it's far from true with a "lose time" perspective.
 Yesterday morning all the USB C ports on my MacBook stopped working suddenly. It rebooted itself out of nowhere and when it came back it wouldn't charge, wouldn't talk to the external monitor, and of course couldn't see my various MIDI devices. It freezes and reboots after running for 5-10min. It will still charge when it's suspended, so it's not quite dead, but it's pretty dead.
I have a long-term loan of an older Mac with a cracked screen, that I usually use for recording. The screen makes using it on its own tricky, but now that I have an external monitor I like it's ok:
This post is from setting that up for music.