-
Notifications
You must be signed in to change notification settings - Fork 3
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
Extract caption data #75
Comments
I've got a start at using the CLI. The only problem that I see at the moment is that it can only hand one title per command. So I think I'll need to write a shell script to determine the number of titles, and then iterate over them with HandBrakeCLI. |
This should work, but it does not:
It's the
|
Regarding extracting captions from ripped DVD files, this is likewise not working:
It generates
Note that |
Everything I'm trying isn't working. FFmpeg, mencoder, Avidemux, VLC, and Handbrake. This is really frustrating. |
CCExtractor is the solution. It was wicked easy: |
I batch-processed all 2015 and 2016 DVDs and uploaded the SRT files to the server. |
I test-uploaded an SRT to YouTube and...it's off by 10 seconds. The lag is a few seconds greater than would actually be with a live transcript. So I need to figure out how to time-shift those. There are desktop tools that do that, but that's not going to work. |
OK the transcript creator is up and running, with transcripts running live on the site. |
Wrote a transcript time-shifter, combined it with the duplication eliminator. The results of that can be seen here—it works great. Next up: load SRTs into the database, figure out how to include them with YouTube uploads, and merge them existing MP4s. |
Including SRTs with YouTube uploads is not possible with the program I'm using now. |
Apparently the General Assembly started closed captioning video last year. So, obviously, we need some way to both preserve and extract this data. Preserving that data for 2015 isn't gonna happen—that ship has sailed—but we ought to be able to extract it.
The text was updated successfully, but these errors were encountered: