All bases exist ! any non-zero number can be a base (even complex numbers cf. Dragon curve - Wikipedia , Complex-base system - Wikipedia ) as long you’re sticking to it (but you might feel lonely using it, and it might not be super helpful or convenient to use)
you can set whatever rule as long as enough people comply with it. Base 16 is arbitrary, but it didn’t come from nowhere : 2 things :
- text based tabbed interface, you can express rather large numbers, control, notes, instruments refs with just 2 characters, so a screen real-estate problem
- western music notation inherently mult/div by 2 a lot, and measure of 4/4 is conveniently give 16 16th notes, so it makes a ton of sense there. Im not aware of a step sequencer not complying with this
- bonus : midi norm also tries to miniminze its flow, and use 128 (note numbers, basic CC)/256 (CC number, verbs) range a lot.
base64 are actively to encode binaries as some fairly short text, symbol-wise, it’s lowercase and uppercase latin alphabet, digits and “+” and “/” for base64, base32 existed before too (it’s really not in use anymore) and use alphabet+digits between 2 and 7 (not 0 or 1 as their easily confused with O and I)
Base 17 in a tracker creates more problems than it solves. this is not a « just add G » issue.