You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are the naming conventions for forced, sdh (hearing impaired subs) and commentary subtitles, to be correctly tagged by your tool when merged?
At the moment they all are distinguished by language only, so the user has to trial and error if he got the wanted sub.
How about to let the batch-tool user define his preferred languages from all available languages, let the user bring these languages into a sort order and save this as a preference? I don't mean the default tag.
Like MKVToolnix GUI does this with forced and sdh subtitles and recognizes 'forced' and 'sdh' as part of a filename.
Example naming conventions for filenames that already work good with MKVToolnix GUI:
forced.eng.srt
sdh.eng.srt
Besides the language, MKVToolNix Batch Tool would need to recognize the word 'forced' and 'sdh' to automatically set the tag for forced display and give it a custom name 'Forced', same with the other, set the tag for hearing impaired and give it a custom name 'SDH'.
Commentary tracks could be recognized similarly as they all have 'omment' as similarity when languages come from same origin, like many european languages do.
If there is more than one commentary track we prepare them with the name of the commentator, this could be recognized as commentary track one and two and three, etc.
Example:
comment-director.eng.srt
would mean that this track is a commentary track with the director speaking.
MKVToolNix Batch Tool would need to recognize the word 'comment' and 'director' to automatically set the tag for commentary and give it a custom name 'Commentary Director'.
The text was updated successfully, but these errors were encountered:
What are the naming conventions for forced, sdh (hearing impaired subs) and commentary subtitles, to be correctly tagged by your tool when merged?
At the moment they all are distinguished by language only, so the user has to trial and error if he got the wanted sub.
How about to let the batch-tool user define his preferred languages from all available languages, let the user bring these languages into a sort order and save this as a preference? I don't mean the default tag.
Like MKVToolnix GUI does this with forced and sdh subtitles and recognizes 'forced' and 'sdh' as part of a filename.
Example naming conventions for filenames that already work good with MKVToolnix GUI:
forced.eng.srt
sdh.eng.srt
Besides the language, MKVToolNix Batch Tool would need to recognize the word 'forced' and 'sdh' to automatically set the tag for forced display and give it a custom name 'Forced', same with the other, set the tag for hearing impaired and give it a custom name 'SDH'.
Commentary tracks could be recognized similarly as they all have 'omment' as similarity when languages come from same origin, like many european languages do.
If there is more than one commentary track we prepare them with the name of the commentator, this could be recognized as commentary track one and two and three, etc.
Example:
comment-director.eng.srt
would mean that this track is a commentary track with the director speaking.
MKVToolNix Batch Tool would need to recognize the word 'comment' and 'director' to automatically set the tag for commentary and give it a custom name 'Commentary Director'.
The text was updated successfully, but these errors were encountered: