Download-Tools/ccextractor
1
0
Fork 0
mirror of https://github.com/CCExtractor/ccextractor.git synced 2024-12-25 20:32:10 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
CCExtractor - Official version maintained by the core team
1,386 Commits 4 Branches 26 Tags 272 MiB
C 81.3%
Rust 15.9%
M4 0.7%
Makefile 0.7%
Shell 0.5%
Other 0.7%
532ecbd449
Go to file
Carlos Fernandez 532ecbd449 Fixed Itunes (well, MP4 generally really, maybe more) line repetition.
2016-12-13 13:32:28 -08:00
Dictionary Added 3 more TV show dictionaries. 2016-12-12 10:10:58 -08:00
docs Update using_cmake_build.txt 2016-12-02 14:02:45 +05:30
linux Fix Makefile compatibility issues with Raspberry pi 2016-12-02 21:14:25 -05:00
mac Fix Mac build process 2016-10-11 11:46:22 -07:00
OpenBSD Version 0.77 2015-06-20 17:00:19 +05:30
src Fixed Itunes (well, MP4 generally really, maybe more) line repetition. 2016-12-13 13:32:28 -08:00
windows Remove hardcoded references in project file, add relative ones instead 2016-12-10 08:38:58 +01:00
.gitignore Add VC.db file to gitignore 2016-12-10 08:38:43 +01:00
raspberrypi.md Fix Makefile compatibility issues with Raspberry pi 2016-12-02 21:14:25 -05:00
README.md Minor correction in README.md 2016-12-08 13:13:09 +05:30

README.md

logo

CCExtractor

CCExtractor is a tool that produces subtitles from TV use. Global accessibility (all users, all content, all countries) is the goal. With so many different formats, this is a constantly moving target, but we intend to keep up with all sources and formats.

Carlos' version (mainstream) is the most stable branch.

Installation and Usage

Downloads for precompiled binaries and source code can be found on our website.

Extracting subtitles is relatively simple. Just run the following command:

ccextractor <input>

This will extract the subtitles.

More usage information can be found on our website:

Compiling

Compilation instructions are coming soon.

Support

By far the best way to get support is by opening a support ticket at our issue tracker.

When creating a ticket:

  • Make sure you are using the latest CCExtractor version.
  • If it's a new issue (for example a video file that a previous CCExtractor version processed fine but now causes a crash), mention the last version you know was working.
  • If the issue is about a specific file, make that file available for us. Don't just send us the output from CCExtractor, as we can't do anything about a screenshot that shows a crash. We need the input that actually causes it. You can upload the file to Dropbox, Google Drive, etc, and make it public so you get a download link to add to your ticket.
  • If you cannot make the file public for any (reasonable) reason you can send us a private invitation (both Dropbox and Google Drive allow that). In this case we will download the file and upload it to the private developer repository.
  • Do not upload your file to any location that will require us to sign up or endure a wait list, slow downloads, etc.
  • If your upload expires make sure you keep it active somehow (replace links if needed). Keep in mind that while we go over all tickets some may take a few days, and it's important we have the file available when we actually need it.
  • Make sure you set an alert in GitHub so you get notifications about your ticket. We may need to ask questions and we do everything inside GitHub's system.
  • Please use English.
  • It goes without saying, we like polite people.

You can also contact us by email or chat with the team in Slack.

Contributing

You can contribute to the project by forking it, modifying the code, and making a pull request to the repository.

News & Other Information

News about releases and modifications to the code can be found in the CHANGES.TXT file.

For more information visit the CCExtractor website: http://www.ccextractor.org