5 ms·
what is an example of this. I find the idea of armchair music experts to be amusing.
by paulpauper 5y ago
what is an example of this. I find the idea of armchair music experts to be amusing.
- iainctduncan 5y agohmm, hard to summon one, but mostly about stuff spanning probability/machine learning and tuning systems/harmony. Lots of very naive statistical inferences with conclusions that seem supported by the data - because they don't understand the data. Like "we found out X because of our analysis of the intervals/chords/whatever they are counting" in these pieces. Where the numerical prevalence really doesn't mean anything similar to what they are positing it means. Tuning and systems and harmony are a) freaking complicated b) almost neat, but so, so not neat on closer examination. :-)
- smartscience 5y agoIf you want to go digging on Usenet, check out Albert Silvermann (I think it was) on rec.music.theory.
- ThreePhotons 5y agoHere's an example: https://dwheeler.com/essays/sight-reading.html https://dwheeler.com/essays/sight-reading.html It's funny (fascinating actually!) because it reads just like your typical highly opinionated software engineering blog post, only applied to music. Yet most of it, particularly the first three points, has no basis in reality. (E.g. point 3 - any music theorist will tell you there is a VERY valid reason for choosing a double-sharp over a natural in particular contexts.)
- vcxy 5y agoEven without a music theorist telling you that point 3 is wrong, it just makes the music harder to read. Of course, the reason is what the theorist would give, but it highlights that he isn't really reading music. He's reading notes. He hasn't learned what those notes mean in context. It's like he's learned how to sound out written words in a foreign language but doesn't actually know what any of the words mean. Thanks for the link, it gave me a good laugh.
- t8sr 5y agoTo me, that mostly reads like a UX report. This person admits he has no musical education, and just wants to play - the issue seems to be that reading a score maybe shouldn’t require a degree in musical theory, the same way that using a piece of software doesn’t require a CS degree. As another amateur musician, I was nodding at most of these points. I fully believe it’s all very complex and double sharps exist for some reason, but how much of that do you really need the reader to understand?
- thaumasiotes 5y agoThe only really solid rule I've seen stated for accidentals is that you want to use sharps when you're going up (as in, playing a rising sequence of notes) and flats when you're going down.[1] There are also many, many people out there who will tell you that you use sharps when the key signature has sharps and flats when the key signature has flats, which (1) is really easy to implement, but also (2) makes no sense. Anyway, my first guess for a double sharp would be that you're e.g. notating an F# which is itself sharp for whatever reason, and you can't just notate it as a G because Gs are also sharped. (As will be true in any key signature with three or more sharps.) Then the reason for marking F𝄪 rather than G♮ is exactly the same as the reason you'd mark F# rather than G♭ in a key that didn't sharp either note. And even from a pure usability perspective, if you're in a key with three sharps and you're doing a lot of alternating between F𝄪 and G#, it's kind of nice having the two notes at the positions of F and G so that you can give them the appropriate accidentals once per measure instead of every time you play either note, the way you'd need to do if they were both on a G. I ran into some trouble with this exact problem when engraving this score recently: https://musescore.com/user/36584999/scores/7810499 https://musescore.com/user/36584999/scores/7810499 The first half of the vibraphone part looks like you're mainly doing downward variations, so I wrote it with flats. But the second half obviously suggests that it wants F#s rather than G♭s, and it felt really weird to use F# sometimes and G♭ other times. Since I know virtually no music theory, my approach was to ask people for help on the internet. I found someone who had majored in music theory and his response was "hmm, interesting", followed by asking a bunch of his friends. Consensus eventually worked out as something like "Hmm, interesting! Could go either way, but maybe F# is a little better than G♭. Whatever you choose, be consistent." It was all fairly unsatisfying and I'd be interested in other comments on how the accidentals in the piece should be marked. Following the general theme of "F# looks a little better, but be consistent" I interpreted every accidental anywhere in the piece as a departure upward rather than downward. :/ [1] I've also seen sharps used while going down, but it was pretty obvious what was going on there - the music had changed keys, but the score hadn't changed key signatures. Those sharps just reflected the new key rather than being departures from it.
- alar44 5y agoThere was an article the other day where someone was saying something like "people who listen to more dissonant music, like heavy metal, may not be as good at hearing nuances in less dissonant music like classical." That sentence right there is just jam packed with bullshit and misunderstanding.
- autarch 5y agoAh, the most dissonant of all chords, the perfect 5th plus an octave, also known as the power chord.
- raverbashing 5y agoThat's a musical-theoretical perfect burn
- vintermann 5y agoThere's really only one mistake, he's misusing the word dissonant. It's certainly true that being deeply into one style of music makes you pay less attention to the things that don't vary much in "your" music but does vary in "their" music, making "your" music seem more varied and "their" music sound all the same.
- alar44 5y agoRight, thats where I tried to meet them in the middle, but they were talking about discreet frequencies. Like listening to classical boosted the ability to recognize harmonics better.