-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ FEATURE ] media metadata #577
Comments
Could also be interesting to be able to extract and display other metadata especially TITLE etc which is embedded in MP4 files etc. Sometimes release groups tag title with "RELEASE BY TEAM - TITLE" etc which in some cases might override title in KODI/PLEX etc. Would be nice to be able to see this in SR with an Icon on TITLE column or something to inform that file has embedded title etc. |
Closing this as it has been added to the #282 Master Feature List to track all feature requests. Discussion specific to this feature can continue in this thread. |
This request it's amazing, I have toons of 4k files recognized as SD. And something like this will fix my library. |
Incorporate a way to scan video files and extract metadata like video codec (x264?x265?vp8? resolution? bitrate? etc) information, audio codec information (bitrate, codec, channels etc) and store in a new table in the database.
this could be off by default as it might be a bit more heavy on cpu/hdd to scan, but if turned on it would scan either automatically or by manual initiate scans pr show and display the information if it exists on DisplayShow.
Reason for this feature request is to ensure that if a user wants to be 100% sure about what a videofile actually is in regards to resolution, codec etc he can scan and see this information in the episode list.
So if I open a show like Falling Skies I can easily identify and confirm 100% (not just by what has been tagged as Downloaded quality) the real resolution and codec of the episode to ensure I have the episodes/seasons in the quality that was/is intended.
The text was updated successfully, but these errors were encountered: