Probably not, I haven't really touched any of the i2c code.
Particularly for me, the i2c code is hard to test as to do any serious development I need to remove my teletype from my main case to get it nearer to my computer. Also, I'm really a high level coder (I was a web developer before I became a stay at home dad), I'm much more at home with the 'how to write your own programming language' stuff, than the low level interrupts and data structures that the i2c code needs.
Although nicer code makes it a lot easier for new contributors to join in, and hopefully makes it easier for older hands to locate bugs. Which is just as well as we've got another baby on the way in the summer so I'll need to take a break from everything for a few months.
Separate issue... and another potential breaking change. I've just been updating the mute code and am wondering if it is worth combining the
At the moment:
MUTE x to mute
UNMUTE x to unmute
MUTE x to get mute status for input
MUTE x y to set mute status for input
y is a
0 or a