-
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 ] Display episode embedded tracks/subs #607
Comments
one way of reading the info is using ffmpeg's ffprobe which i believe should be available in most OS's.
the supplied file is using title "Surround 5.1" as name for both streams. Usually this is where it would say ENG or English / NOR or Norway etc. So there would be a need for a lookup table translating different settings to language so we can use country flags. Also for audio it should be possible to find out how many different types we have.. like surround 5.1, 7.1, 2ch stereo etc and have icons for those as well. |
This would also be nice since it would give instant info if a Commentary track is available etc. |
Hi, Could we have at least subs displayed wether they are activated or not? Cheers |
@ratoaq2 |
Sorry. I haven't realised. Probably while reading it on my mobile, I pushed the close button unintentionally. Reopening it |
what do you think about my comment above? Could we have subs displayed wether they are activated or not? |
This might help for mkv files: https://github.com/Diaoul/enzyme Subliminal uses it to get video info, embedded subs, etc |
enzyme library is integrated into SR already. |
i would love to be able to see how many, what languages and what is default subtitle track of those embedded in video container. |
Added to master feature request list - discussion for feature will continue here even though issue is closed. |
if you ever got a media codec info extract solution in place it would be very cool if we could see the following:
reason for this is to ensure better insight into what is accurate when it comes to the episode container file.
The text was updated successfully, but these errors were encountered: