Like any other programming environment, SmarterPlaylists needs to help its programmers debug their programs, otherwise, the only debugging tool will have is thinking. And that’s often not good enough. With this in mind, I’ve pushed out an update to SmarterPlaylists that gives you detailed info on your run including: how many API calls were made across the whole run and for each component; how many tracks flowed through each component, cache hits, time spent waiting for the API to return, and more.
Here’s a screenshot of a simple program that grabs tracks from 3 playlists, combines them into a single alternating list of tracks, filtering them to keep only those that were released in this decade, and have lower energy. The stats section shows all the details – like the ‘alternate’ component is responsible for the most API calls since it is responsible for decorating the tracks.
With these stats I’ve already found and fix bugs in the engine – so its already paying off.
Music Machinery 