Feature: FFProbe Stats

[TheTaylorLee]

Feature Target Details

Considering adding a SQL table that stores probed media data. Would need to decide what to store in the database.

• Languages
• Audio format
• video format
• subtitles
• etc

Why is this change needed? This would provide interesting information regarding the overall stored media. Data could then be leveraged to produce additional grafana stat views.

[TheTaylorLee]

$probe = ffprobe -loglevel -8 -print_format json -show_format -show_streams
$convert = $Probe | ConvertFrom-Json
$convert.<key01>.<key02>
$convert.streams[0].codec_name

• Consider a function to auto build columns based on the json structure and if a column exists yet. How will that or this work with grafana based on lack or existence of datatypes?
• Streams might best be best saved as type blob and then parsed in Grafana to reduce column counts and keep it simple. Alternatively might have separate tables for each stream which can then be retrieved through queries. Would need an index table.
• Performance using SQLite might be atrocious if storing all probe data.
• A separate and optional database might be pertinent and a separate function/s dedicated to the stream statistics.

[TheTaylorLee]

This grows the database significantly unless only retaining limited metadata. The performance impacts would not be worth the additional statistics.