Live data from Hacker News

Basic Music Theory in ~200 Lines of Python

mvanga.com

41–50 of 192 posts

Re: Basic Music Theory in ~200 Lines of Python

#41
post #35

Earlier quoted context omitted.

what you are describing is a graph. The laplacian spectrum of a graph is arbitrary.

Every rigid object has a fundamental frequency, regardless of whether you put it on a graph.

Sure. But the other frequencies need not be integer multiples of the fundamental.

Re: Basic Music Theory in ~200 Lines of Python

#42

This is great but if we could go back in time and influence the naming conventions so that the 12 semitones were called A-L or just numbered 1 to 12, and if the intervals were named after the actual semitone distance (a 'fifth' is actually seven semitones) the whole thing would be soooo much less jargonny. With all that bumf removed, the patterns of the 'scales' and 'chords' would be foregrounded and thats the actual…

People have had this idea before but I've never seen a version of it that is better than our existing notation systems. Most of our music is diatonic, and we named the notes in our scale A B C D E F G. Seven notes in the scale, seven letters. Seven positions on the staff.

Our harmonies are built on stacked thirds, and the stacked thirds line up perfectly on a staff. Line, line, line; or space, space, space. Three dots stacked neatly on top of each other. Easy peasy. Easy to read all the common intervals at a glance, once you get past an octave it starts getting a bit harder.

If you had chromatic notation, you'd allocate a bunch of extra space and names for things that you spend most of your time not using. An octave would have eleven spaces in the middle, which is practically unreadable.

I think in the long-run chromatic notation is just hostile. Go ahead and use chromatic solfege, that's super useful, but chromatic notation is usually not.

Most often I hear the criticsm from people who are not musicians or do not know how to read music. It's often smart people with an analytical mind, but people who don't have much experience with music. Just speaking from my own experience, it's much harder to read a chord from a piano roll than to read a chord from traditional notation.

Re: Basic Music Theory in ~200 Lines of Python

#43
post #24

Earlier quoted context omitted.

Agreed. I whinge about this all the time. The C-based system is convenient for piano players but it's a mess for guitar players, violinists, and other instruments where there are no There have been many attempts at a chromatic music notation, but nothing has caught on so far [1]. Things are a little better with solfege -- there is "chromatic fixed do" solfege, where every note has its own name, rather than only havin…

I find the paino-roll notation on DAWs to be a lot more intuitive. Not much good for perfomers of course, but it helped me understand things better. Each semitone is given the same amount of space.

I find piano roll very hard to work with. The notes are just too far apart vertically.

Re: Basic Music Theory in ~200 Lines of Python

#45
post #40
post #17

There are maybe three aspects to music theory: (1) Theory of how things sound like: Tones, melodies, scales, chords, based on the frequencies of individual sounds. (2) How to name things. (3) How to handle the mess of naming things in Western music theory, where things have 12 different names, depending on which note you choose as the base. This post seems to focus on 3.

I once listened to a podcast where fourier transforms were used to generate sounds that otherwise don't exist.

> sounds that otherwise don’t exist.

hmmm

Re: Basic Music Theory in ~200 Lines of Python

#46
post #40
post #17

There are maybe three aspects to music theory: (1) Theory of how things sound like: Tones, melodies, scales, chords, based on the frequencies of individual sounds. (2) How to name things. (3) How to handle the mess of naming things in Western music theory, where things have 12 different names, depending on which note you choose as the base. This post seems to focus on 3.

I once listened to a podcast where fourier transforms were used to generate sounds that otherwise don't exist.

Could you maybe share which podcast? Generating “sounds that otherwise don’t exist” does not sound particularly remarkable taken at face value. It’s basically what any synthesizer or audio processor does, and Fourier transforms are also a very commonly used in audio processing.

Re: Basic Music Theory in ~200 Lines of Python

#47
post #44

> For historical reasons, there are no sharps or flats between the notes B/C, and E/F. Come on, that is not for "historical reasons", that is because those notes are only one semitone apart!

Different way of saying the same thing.

"For historical reasons the notes B/C and E/F are one semitone apart."

Re: Basic Music Theory in ~200 Lines of Python

#48
A perfect 5th is not the same as a diminished 6th unless we assume equal temperament tuning. Granted it is the dominant tuning, but it irks me when this is just silently assumed.

Plenty of music around that is recorded using actual perfect intervals, so why muddy the waters?

Re: Basic Music Theory in ~200 Lines of Python

#49
post #44

> For historical reasons, there are no sharps or flats between the notes B/C, and E/F. Come on, that is not for "historical reasons", that is because those notes are only one semitone apart!

The idea of a semitone in Western classical music is historical not (just) tonal.

Re: Basic Music Theory in ~200 Lines of Python

#50

It would be awesome to add short audio clips. I mean, the examples are correct and all, but it's like discussing painting or photography without a single picture.

As a musician, I’d say no. Sure, you don’t get the significance of “what is this Dorian thing” unless Scarborough Fair is playing, but nothing in the article really applies to hearing music.
Post reply on HN