WP Audio Player renders an audio track wherever an editor drops its shortcode into post_content. Tracks reference MP3 or OGG files in wp_posts attachment rows or remote URLs, plugin settings live in wp_audio_player_options, and the track footprint sits inside the post_content of wp_posts. The plugin's admin offers a settings screen but no per-post or per-format list.

SleekView parses post_content for WP Audio Player shortcodes, joins to the referenced attachment rows when the source is a media library file, and indexes the wp_audio_player_options row. File format (mp3, ogg, remote URL), host post, host post type, attachment status and post date sit as sortable, filterable columns. Pull every ogg track on a custom post type or every remote-URL audio attachment whose source went missing without opening any post by hand.

Inline edits run through standard WordPress CRUD, so post-save hooks still fire and WP Audio Player continues to render and serve audio as before. The playback pipeline stays inside the plugin.

WP Audio Player keeps its surface small: a settings screen, a shortcode, a playback widget. That smallness leaves the team without any inventory view, no mix between file formats, no idea which post types lean on audio. SleekView reads the option row, the parsed shortcodes and the attachment rows as the structured data they already are.

Producers confirm new episodes ship in the right format. Agency support fields client questions from a read-only slice. Editors track remote-URL tracks whose source may have moved.

The plugin keeps doing the playback work it does well, and SleekView gives the team a reading layer they can share.