Is your feature request related to a problem? Please describe.
The web interface does not support subtitle track identification.
Describe the solution you'd like
Add support for subtitle track identification as with audio track identification. This should include identification of the language and markers, such as "Forced".
Describe alternatives you've considered
Additional context
Some films embed critical foreign dialog or other textual information in the form of forced subtitle tracks. Players are capable of detecting and playing these tracks automatically, but MakeMKV does not have this capability. Instead, tracks need to be manually set as forced using tools such as MKVToolNix in a post-processing step. Knowing which track to label and mark as such requires experimentation or a database. Currently, the best database I know of for managing this is a Google Sheet (https://docs.google.com/spreadsheets/d/1nAMVVnmk3vSaUiuFXcN7D0R69FHIP4tfIkTdThTkXEk/edit?usp=sharing). However, this solution is a bit imprecise and inelegant. This database is naturally positioned to capture the same information and obviate the need for the separate spreadsheet.
Is your feature request related to a problem? Please describe.
The web interface does not support subtitle track identification.
Describe the solution you'd like
Add support for subtitle track identification as with audio track identification. This should include identification of the language and markers, such as "Forced".
Describe alternatives you've considered
Additional context
Some films embed critical foreign dialog or other textual information in the form of forced subtitle tracks. Players are capable of detecting and playing these tracks automatically, but MakeMKV does not have this capability. Instead, tracks need to be manually set as forced using tools such as MKVToolNix in a post-processing step. Knowing which track to label and mark as such requires experimentation or a database. Currently, the best database I know of for managing this is a Google Sheet (https://docs.google.com/spreadsheets/d/1nAMVVnmk3vSaUiuFXcN7D0R69FHIP4tfIkTdThTkXEk/edit?usp=sharing). However, this solution is a bit imprecise and inelegant. This database is naturally positioned to capture the same information and obviate the need for the separate spreadsheet.