Music Theory for Musicians and Normal People
academic.udayton.edu
academic.udayton.edu
You very quickly find yourself making statements like this (taken from the second PDF in this series): "A tuplet is any non-standard division of a note. These are usually written as a group of notes delineated with a bracket and a number showing the division being made." It's correct in grammar and sense, and about as exciting as a lawn-mower repair manual.
This is probably the best series of music theory cheatsheets I've ever seen, though... just about any other music theory resource you can find, online or off, gets bogged down immediately in sleep-inducing language. I had to poke around a bit to find the example above.
The real problem is the "building blocks" approach to music theory pedagogy; that is, making students learn all of the basic concepts before they can do anything remotely interesting or useful.
It's really, really logical. It's also a sort of mental torture, in the realm of music theory, because a lot of the building blocks are arbitrarily weird for historical reasons, and it takes too much meaningless memorization before you can do something as trivial as sight-reading a piece of music you could already pick out by ear 10x faster. What about doing basic analysis of a piece of music? So, so many building blocks required first....
I think it's possible to make learning theory enjoyable, but it'd be damned hard (and not possible in a static form).
That said, if you have the external motivation already to make the slog through the basics, these are solid references to help get the details straight in your head.
I have about 200 6th-8th graders that are able to perform basic figured-bass analysis on major-key chorales in about 3-4 months by progressing in an orderly fashion from notation to rhythm to major scales to the Circle of Fifths to minor scales to intervals, to chords, and finally, to cadencial analysis. Some of them pretty much view it as a game we play with written notes, but, when reinforced by practical experience in private lessons or participation in ensembles, it is remarkable how much they like it and are sad when we move on to Music History in the second half of the year.
I've been thinking about writing a music theory lesson for programmers and "normal" people. I swear it is a conspiracy theory of music teachers to make music theory seem hard. Once you see the logic of how it all comes together, it is head-slapping easy. Music theory is all created from a few easy-to-remember patterns.
I already wrote a bit of music theory code in Python. Maybe this will be my Thanksgiving project.
Ideally, this explanation would ignore centuries of historical cruft, starting instead from the physical and physiological basics, and making full use of the infinitely malleable sound generators we all own.
It's pretty easy to teach what a tuplet is, even without written notation: play all eighth notes over a regular ♩♩♩♩ (that's 4 quarter notes) rhythm, then sixteenth notes, then play triplets.
> a lot of the building blocks are arbitrarily weird for historical reasons, and it takes too much meaningless memorization before you can do something as trivial as sight-reading a piece of music you could already pick out by ear 10x faster.
That's why I like the Suzuki method.
Just conveying the material clearly is important. Finding a way for the student to grasp the material while using it, while actually achieving something useful with it, is far more difficult.
I studied Suzuki method when I was little; I still remember playing the tune of Twinkle Twinkle to "see you later alligator", but we never touched on music theory beyond the very basics needed to read music notation (and not even much of that). We pretty much memorized everything we played AFAICR.
I do agree that it's essential to involve actual music in the instruction, but it needs to go beyond "a 5-tuplet looks like this; here's what it sounds like" -- that's still little more than a dreary list of definitions to memorize.
The trick is to engage the student in the music such that they need a name for this next concept so they can talk about it (which is what theory is for, really).
Then again, mashing 3 or 4 memorised chords on an old korg trinity gets you quite far without having to know what you are doing :)
First, sorry about the Issuu thing. These pages are actually several years old, and at the time Issuu was actually the easiest way I knew to make them available without burning out my personal hosting bandwidth. I created the index page later on, but used the Issuu links since they were there. (You have to understand, there has never been more than a trickle of a demand for them outside of my own students.)
The other reason I was a little hesitant to bundle them all together is because I'm still working on them, and I didn't want to "publish" something that had the air of being complete.
But the internet has spoken... I've added a link at the top of the page which takes you to a single PDF. (Thanks to jamie_ca and pyroMax for doing this before I stumbled into the party.) Oh, and I fixed the <title> tag, too.
Also, thanks very much for the other feedback that has been sent my way; I do genuinely appreciate it. While I'd like to retain sole authorship (at least for now) rather than make them open-source, I most definitely welcome comments on how they can be improved.
With regards to open sourcing, let me make a couple of notes which might help change your mind ;)
Firstly, open source is not the same as no control, or lack of authorship. Open sourcing simply lets others use your material in their own works, and depending on which license you use you can maintain a lot of control over what those derivative works can look like. Time and time again in the open source community we see that actively maintained projects almost always stay together. With large projects where differences arise we see the project split, often to fulfil multiple different needs, but almost always the original project remains as the single source of 'truth'. In truth, there is nothing stopping someone from trying to run their own linux kernel, and some have succeeded fairly well (such as the android kernel project), however everyone still sees Linus' as the 'true' kernel project; a lot of work went into merging the work done for android back into the mainline kernel for this reason.
What does this mean for you? The fact that you are the creator of these documents immediately gives you control of how they are shaped, even in an open sourced format. By open sourcing you allow three things to happen more easily than you would otherwise.
1. Others can use your work in their own works, according to the license you provide. This is bad or good depending on how you see it.
2. You allow someone else to keep maintaining the project if and when you lose interest. This is almost certainly a good thing.
3. You make it much easier for people to provide improvements and 'bug' fixes. You have already stated this is something you are willing for people to send you. By allowing people to actually make the changes themselves, and publish them back to you to incorporate into the 'true' version, you make it easier for people to help you. You are empowering others to do your work for you. You might claim that you lose control over what gets into the project this way - you don't. If someone points out an error you will want to correct it. If they rewrite a paragraph maybe you like the general idea but not the exact wording. You can ask them to rewrite it with suggestions until you like it, incorporate part of it using your own words, or ignore it completely; the power is yours.
Lastly, open sourcing does not inhibit you from making money from the ideas. You might want to treat carefully when selecting a license, and make sure any contributors (if you have any) are aware you might make money from the idea (sharing profits or not is a separate issue, just as important to understand). This side of it can get thorny and would be the one reason I might avoid open sourcing it, or at least avoid taking large contributions.
In any case, open source can be a great tool, and you can still maintain control of your project when using it.
----
First of all, thanks! These are some excellent notes. That said, it is extremely irritating trying to read them. If you could provide the ability to do one or all of the following it would be most excellent:
1. Download of the entire pdf as one document
2. View the documents as a web page/series of web pages
3. Open-source the documentation so others can contribute/provide fixes
http://www.emusictheory.com/interact.html
and here http://www.emusictheory.com/practice.html
I largely ran out of time to extend/improve it several years back, but it still gets quite a lot of use; students of subscribing teachers can use MIDI keyboards as well, which makes the instrument/theory link quite tangible.
If I had time, I'd start on it right away, but as it is, it's on the Big To-Do List. However, one thing I am actively working on right now is an aural skills practice site that includes the advanced stuff (most existing sites only deal with the basics) and which uses HTML5, CSS and other open standards tech (most existing sites are flash-based). I'm also designing it with an interface that works equally well using a mouse or a touchscreen. This is, IMHO, a huge need in my field. But my project is still in it's infancy, and not ready for prime time.
[1] http://www.youtube.com/watch?feature=player_detailpage&v...
One of the most interesting books I have in my library is "Effortless Mastery". Recommended by a musician and artist.
http://www.amazon.com/Effortless-Mastery-Liberating-Master-M...
These also
That was a lot of effort on their part to make an interface annoying enough for me to ignore this work.
These kind of information hijacking must be marked as am abusive business modell that is not acceptable in a free world. We have to think longterm here and defend freedom of information on a very basic level, to be prepared for the larger battles that will come when chinese investors will be the only sources of money.
Please write the authors to remove their PDFs from these services and just put them on a webserver into a PDF folder. Or to use any free file hosting service, anything, but please do not support these ancient flash-fetish-stoneagers and information-suppressors, THANKS!
After providing your age (I just turned 99 today!) among other required fields.
http://dl.dropbox.com/u/1002031/Music%20Theory%20Fundamental...
http://academic.udayton.edu/tobyrush/theorypages/complete.pd...