Let's see what would happen from a programming point of view: # units are semitones Any programmer would blame you to the death. And that's not only without considering 'theoretic' tonalities, but even modal modes, which would make it to (at least) 336 scales. Then, as soon as you're dealing with other scales -as you are asking-, you'll end up with at least 48 constants. They are just 24 constants in your mind, for which you also have to add other constants to indicate the relative tonalities. There's no real correlation between them. You could try to begin storing scales as constants, and that's fine if you're just having simple situations with basic major and minor scales: 24 constants 'to rule them all'.

Unless we're talking about good 'forms' of eidetic memory, our brains generally have limited amount of 'static memory', and, as soon as some structure is found, it's much more easy to make that structure 'standard practice'.Ĭonsider it from the perspective of programming languages. It's structured, both notes and rhythm are based on time relations, not absolute constants, and there's no benefit in trying to 'force' our way in using that kind of memorization. But what if I ask you 17×31? That's why we learn how to multiply, and that's why we learn how scales and their intervals work. What you're asking is almost the same as 'any good methods to memorize times tables?'. I'm going for a huge oversimplification, since we're not talking about neuro-science, but most of our memorization processes are about structures and schemes.

Premise: the concept of 'memorization' is pretty broad and vague.

How to memorize order of flats