A third post in a series (part 1, part 2) on exploring what keys of a piano I use the most.

I’m a sucker for data. Doesn’t really matter about what—lately, election polling has been interesting to watch—but I really like seeing numbers about things I do. Music is one interesting thing, and I like that I can see my stats on last.fm, or the annual email from Spotify with my year in review. Whether it’s using time-tracking software or using a fitness app to track duration/pace/heart rate/etc when running or using GPS data and OBD sensors to figure out what part of my commute burns the most gas¹, I really enjoy being able to see changes even in fairly useless data. With that in mind, here’s an update on my attempt to keep track of the keys I play.

We left off with a page that would keep track of keys played, but every time the page was reloaded (which wasn’t infrequent, given that Edge² crashed more than occasionally when MIDI devices were added and removed) the data would be reset, so it was difficult to keep a running total.

To mitigate this, I added support for saving data per-session. If Edge decides to stop accepting MIDI data, I can simply save the session and restart the browser. This uses Dexie as an easy wrapper for IndexedDB, and stores that data in the browser’s storage³. I added some options to save the current play session, and a few extra page links:

I can then see my per-day/per-session stats:

This probably isn’t the endgame for this project, but it’s a nice move in the direction of collecting more data. Like I said, I like data! And it’s much easier to do any kind of analysis later if I’ve already been collecting the data than it would be if I wasn’t already keeping track! Here’s the aggregated total of the first few days’ collected data:

As usual, the source and the application are available to view or modify!