Skip to content
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

Generated VTT files are not standard compliant #72

Open
KyleMaas opened this issue Oct 28, 2022 · 0 comments
Open

Generated VTT files are not standard compliant #72

KyleMaas opened this issue Oct 28, 2022 · 0 comments

Comments

@KyleMaas
Copy link
Contributor

When I first started using this program, I took subtitles and opened them in VLC and it looked fine. But then I tried another program, and they refused to work. Took me quite a while to realize that the output of AutoSub was actually not compliant with the VTT format according to this validator:

https://w3c.github.io/webvtt.js/parser.html

Errors I get include:

You are hopeless, RTFS. (10ms)
1. Line 2: No blank line after the signature.
2. Line 7: Cue identifier cannot be standalone.
3. Line 11: Cue identifier cannot be standalone.
4. Line 15: Cue identifier cannot be standalone.
5. Line 19: Cue identifier cannot be standalone.
6. Line 23: Cue identifier cannot be standalone.
7. Line 27: Cue identifier cannot be standalone.
[many, many more of these]

Unfortunately, I can't share the subtitles that did this. However, it happened with every file I tried. I was able to build a series of sed replacements to run on the AutoSub output file to make it so it passes the validator, but that's quite a hack. I'd recommend trying validation on a file yourself - it was consistently repeatable for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant