FV Player stores videos in wp_fv_player_videos and playlists in wp_fv_player_players with rows tying playlists to videos via wp_fv_player_player_videos. Encoding jobs run by the Coconut integration write progress to wp_fv_player_encoding, and per-video and per-player view stats live in wp_fv_player_stats. The plugin's admin gives a per-player editor and a separate stats page; what it does not give is a flat table of every video across every player with source, duration, and view counts.

SleekView reads the four tables and surfaces video title, source URL, source type (MP4 file, HLS, YouTube, Vimeo), duration, parent player, view count, and encoding status as first-class columns. Saved views like MP4 files awaiting encode, HLS streams across all players, or videos with zero plays in 30 days load with one click. The players view sits beside the videos view with player title, video count, autoplay setting, and total plays.

Inline edits cover title, source URL, captions URL, and player assignment. Writes route through FV Player's own update functions where available so the encoding pipeline and stats associations stay consistent. The Coconut encoding view shows current jobs with progress, output format, and elapsed time; useful for spotting stuck encodes before they affect a publish deadline.

FV Player handles a lot of operational complexity: HLS streams, MP4 sources, Coconut encoding, captions, ads, lightbox, and per-video stats. The default admin gives each player its own editor and the stats page its own dashboard, which is fine for one or two players but underpowered for a site running courses, knowledge bases, and marketing pages with dozens of players and hundreds of videos. The questions an operations team has cut across players: which videos are stuck encoding, which captions are missing, which sources point at a moved CDN URL, which videos have zero plays despite being live, which players consume the most bandwidth.

SleekView pivots the five FV Player tables into flat catalog and encoding views with those columns and filters available at list level. Editorial teams use it for catalog cleanups, marketing teams use it for cross-player analytics rollups, and site admins use it to monitor the encoding queue without opening dialogs one by one. The plugin keeps owning playback, encoding, and stats collection exactly as it does today; SleekView just gives the catalog the operational surface a site running real video at scale actually needs.