3 ms·
Instead of imagining performing music as a series of notes coming at you, A C G B A, imagine it as a series of motions: A-C, C-G, G-B, B-A. The purpose of a tec
by jerf 16y ago
Instead of imagining performing music as a series of notes coming at you, A C G B A, imagine it as a series of motions: A-C, C-G, G-B, B-A. The purpose of a technical exercise like a scale is to put those motions into your muscle memory, so your conscious mind is no longer thinking about them. Scales should not be the only exercises you do; I do not play guitar, but a piano player should certainly also do arpeggios, circle-of-fifths, "circle of thirds" (rolling up major and minor scales by thirds, also going up and down the keyboard in pure major and minor thirds. there's also some good multi-finger exercises you should do to, like scales+fifths, and some genres really call for yet other technical exercises). I don't know what the guitar equivalents would be but I am sure there are some.
Unfortunately, the only way to put something into muscle memory is with repetition... endless, endless repetition. Alas. (No sarcasm.)
It is absolutely true that you can play without this, but instead of a powerful set of abstractions stuck in your muscle memory, you will have a patchy set of whatever you happened to need. Which, on average, due to the uneven need for them, will indeed correspond to most of what you need. But you will have holes compared to someone who is doing the full set, and the further you try to go the more those holes will bite you.
I say this without judgment. Far be it from me to condemn somebody for learning an instrument and choosing not to devote the time to become an utterly awesome expert. I think it's a perfectly viable choice to choose to become pretty decent. But you should know what you are doing.
It is not at all like needing to know Turing Machines to know how to program. It is much more like (though not identical to) needing to know how to type fluently to program; if you're hunting around for the open parenthesis, you're not programming. This metaphor breaks down because your editor will wait for you to find the key, at worst it breaks your flow; when playing music if you come up against a missing muscle routine you just failed something.
(Incidentally, when I put it this way it seems obvious, but for all the music training I've had and for all the various instruments I've learned or at least poked at, nobody has ever put it this way to me. It's too easy to insist that it's simply tradition, or to start babbling about some semi-mystical thing or other, when really it's quite simple: you can't play at a high level, or even a middling level, with your conscious mind. The vast bulk of your instrument-playing routines need to live in the cerebellum. It's that simple. It's not merely because it's tradition and there are concrete and simple reasons why technical exercises are necessary, appeals to authority are unnecessary.)
- noname123 16y agoI'm answering to you as I just finished my daily guitar practice, with stupid scales practice (triplet/reverse triplet/minor 7th flat five/pattern 1-5) and I still hate it. However I agree with you that practicing scales is excellent for building up your "typing" ability, whether it be on the guitar or on the piano to play fast licks. Same thing with the circle of fifth to identify which mode a particular song is in, and to be able identify which key/scale/chord you choose to solo on. But this is more philosophical than technical - you learn rules so that you can break them. Even scales are derived from other scales "hacked" into (diatonic => pentatonic scale, the "monkey-wrench" notes are what gives it a bluesy feel). Some songs have intentionally mismatched notes from a wrong scale that clash over a chord, to evoke an eerie feeling from the listener. Similarly, a performing musician never stops playing/strumming if he/she doesn't hit the right note or finger-down a whole entire chord, you keep going on. "There's never a wrong note, only a opportunity" - Miles Davis. Even if you are a straight-edge classical pianist, you have the artistic freedom to perform your piece with accents and timbre in the constraints of the tempo and melody of the sheet music. Similarly when you program, some people like to take time to define their interfaces and draw out the class diagrams to figure out how all of the pieces fit together. I personally, like to open up NotePad++ and start typing the first thing that comes to mind, and run compile, probably get a bunch of compile errors, so I go back and correct them and run compile again and get errors again, and so forth until I get one piece working, and I build off that piece the second piece. Sure you need to learn typing, before you program. I'm just saying that for someone who's motivated to express themselves, whether that be through programming or music, that motivation makes them get through the technical barrier, not that the other way around. tl;dr - Everyone has got a right to be wrong; http://www.youtube.com/watch?v=xHVSptF3_G8&feature=avmsc2 http://www.youtube.com/watch?v=xHVSptF3_G8&feature=avmsc...
- jerf 16y agoMy personality isn't really amenable to endless scale repetition either, which is part of the reason I'm here on Hacker News and not hanging out at Musician's News. But I did at least come to an appreciation for what I'm missing out on. Like I said in my original message, I have no desire in propagating the "If it's worth doing at all, it's worth doing right". I don't really believe that anymore, despite having been raised that way. If you have to choose between that and half-assing everything, do it right every time, but if you understand the reasons for that "rule" then there are plenty of times it's worth just doing enough.