4 ms·
Music. Is. Hard. Understanding it and building useful models of it are really really hard. Even building a functional content-driven also-bot is hard, altho
by TheOtherHobbes 4y ago
Music.
Is.
Hard.
Understanding it and building useful models of it are really really hard.
Even building a functional content-driven also-bot is hard, although you can always solve that problem by cheating and aggregating playlist preferences.
Supposedly simple concepts like 'track BPM' just don't work reliably in the real world. (What's the tempo of a recording of a symphony, or even just a folk album that wasn't recorded to a click track? Or an EDM track with subtle tempo shifts - which quite a few tracks have?)
If they'd known more about music when they started they'd have understood this.
- midoridensha 4y ago>Supposedly simple concepts like 'track BPM' just don't work reliably in the real world. Sure it does, you just have to give up on the idea of there only being a single value. A song could have multiple different BPM values, so in your database you'd just record a set (or a tuple in Python parlance). For subtle tempo shifts, you'd run the music through some kind of filter algorithm which would isolate sections with significantly different tempos, then for each section would find the average, then would make a set with those values and store it. The only place this would fall down is some weird music with constantly-changing tempo, where you'd end up with an average over the whole song.