MP3 Audio Player (by Sonaar Music, sometimes referenced as the Sonaar player) stores playlists as the sr_playlist custom post type with each playlist's tracks stored in postmeta as an array of track objects (title, artist, MP3 URL, duration, artwork URL). Shortcodes embedded in wp_posts.post_content reference playlists by ID. The plugin's admin gives a per-playlist editor and a settings page; it does not give a flat list of every track across every playlist, nor a list of where each playlist is embedded.

SleekView reads the sr_playlist CPT and unpacks the tracks array into a flat tracks view with one row per track and parent playlist as a column. Saved views like tracks across all playlists missing artwork, external-URL tracks, or playlists embedded zero times are one click away. The playlists view sits beside the tracks view with playlist title, track count, total duration, and embedding posts as columns.

Inline edits cover track title, artist, source URL, and artwork URL. Writes update wp_postmeta on the parent sr_playlist post through the plugin's update hooks so the player's cache and any companion analytics plugin behave normally. Bulk actions cover replace source URL (for CDN migrations), reorder tracks across playlists, and normalise artwork.

A music or podcast plugin that stores tracks inside playlist postmeta arrays makes sense for the plugin's own UI, where each playlist is edited as a unit. It does not make sense for the cross-playlist questions a catalog owner actually has. Which tracks are missing artwork across the whole catalog, which playlists have grown larger than a CDN free-tier file count, which tracks point at a host that just disappeared, which playlists are no longer embedded anywhere on the site: these need a flat track index, not a per-playlist editor.

The default admin treats playlists as posts and hides the tracks array inside postmeta, which is the right shape for the player and the wrong shape for the catalog. SleekView unpacks the array into a flat track index with parent playlist as a column, source type and artwork presence as filterable columns, and embed-count joins back to post_content for usage auditing. Music and audio editors use it for catalog cleanups, site admins use it for CDN migrations, and editorial analytics teams use it to find playlists no longer driving any embeds.

The plugin keeps owning playback, shortcode rendering, and the player UI; SleekView just gives the catalog the queryable surface it has always needed once it grew beyond a handful of playlists.