Same! thanks for saving the experience for me :)

The value that is being sorted isn't obvious to me. It's obvious that it is sorting it. I'm guessing maybe some dB level of each of the hits/notes. If that was the case, I'd expect the initial unsorted view to line up with the pattern of the waveforms which is not the case. Maybe it's just an unsorted list of values sorted in sync to the rhythm. It's weird though that the segment corresponds to a segment of the audio. I just don't see how they are linked.

There is some amount of the "Focus follows brain" problem here. What we want is for things to do what we meant, all the time, and in this case it's very possible that the visitor wanted to hear the music. It is not practical (without yet to invented technology) for that to work so we have a substitute - there's a switch and you should remember to press it.

"Focus follows brain" is how everybody wants windowed UIs to work. When I type on the keyboard the letters go where my brain thought they should go - duh, but of course that's unimplementable, so the Windows UI provides "Click to focus" - if I click on a Window the typing goes there until I click another window, meanwhile some Unix systems do "Focus follows Mouse" - if I move the mouse over a Window then my typing goes there even without clicking. Neither is what we actually wanted, both are trying to approximate.

The phone will still make sound if I launch a music app, why is a web page different?

And I hate web pages making sound! But the UX is confusing, and it’s changed over the years, seemingly without reason.

Iphones now have a software toggle as well, which may have coincided with the shift from “mute ringer” to “mute (almost) everything” that came with the multifunction button.