#TuningLib was a very early project for me and I'm not actually the author of all the code in it. It's got some weird things in the Key class, like you can pass in arrays of things to compute and it deals with them through a not-quite recursion?

And when you revert to a previous key, it divides by the last change to find the old tuning instead of just storing it.

Does anyone ever even use this class? I don't know.

Post #AMRO to-do list:

0. Laundry
1. Prepare for the seminar this evening that I'm attending.
2. Reply to emails and messages ✉️
3. Finish teaching observation paperwork that's overdue ✏️
4. Test and commit changes I made to #TuningLib (should there be a new point release? Is anyone missing nay features?) 🎶
5. Fix and properly test the Stop command in Domifare
6. Make the display font bold or bigger or both
7. Find out if @servus has a recording of my set 🎤
8. See if I can fix or replace the USB hub that broke in my luggage
9. Do a demo recording at home using my naff mic. 🎙️
10. Make a webpage about the project with a blurb, a photo and an excerpt. 🕸️
11. Email everyone I can think of asking if they want to book me. 📫
12. Contact the director of research in my department to get sorted on how to proceed with looking like a researcher.
13. Order new business card, removing the "is that Elon Musk?" 🙀 picture of me.
14. Tuba repairs (new cork, fifth value gets stuck when it's warm.) 🔧