Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Should `--all-sub` works also for automatic captions or only for subtitles? #1412
Comments
|
The way I understand it,
|
|
Done, but currently |
|
After a lot of trial and error, reading the manpages and the issue tracker, plus finding a proper demo video, I determined the subtitle logic as of I wanted to achieve this: I specify my desired languages. If manually created subtitles exists, download these, else try to get auto subtitles. Manually created subtitles are preferred over auto subtitles, no need to keep both versions. Thus no language code conflicts, no need for a further "auto" language code class for me. BTW: The auto-translated version at best comes from translating a manual subtitle or from translating from an audio/speech recognition of the audio source plus, or its a combination from multiple manual subtitles, and/or speech recognition, or some even weirder Big Data algorithm voodoo. Test videohttps://www.youtube.com/watch?v=4zVS7BLbbkk has an English manual subtitle.
Command line and results
The EN manual subtitle is downloaded. I'm certain as it contains the character name prefixes and paraphrases. The CCs as stated by Youtube seem to not always work
|
|
|
|
Thanks, the |
|
No. |
|
But with "en,en-us,en-uk,en-gb,etc" one should be safe? I'd welcome a language wildcard ("I want 'en' no matter what, or I want 'en-uk,en*' as in 'British English else any English available' ") to spare the user lengthy language code guesswork/generalisation or the need for a manual |
|
Format code in general is arbitrary string since this metadata is provided by video services. |
|
No possibility for a wildcard syntax which greps through those arbitrary strings, empowering us as they anyhow potentially differ across providers? |
|
@porg as explained in the bug reporting instructions, please open a new issue. |
I think that it should also work for automatic captions.
The other question is if
--all-subshould set--write-subto keep backwards compatibility or if it would require either--write-subor--write-auto-subto work.