mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-14 21:23:42 +00:00
[PROPOSAL] Add support for .mcc files #302
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @madykstra on GitHub (Apr 12, 2017).
Please prefix your issue with one of the following: [BUG], [PROPOSAL], [QUESTION].
CCExtractor version (using the --version parameter preferably) : 0.85
In raising this issue, I confirm the following (please check boxes, eg [X]):
My familiarity with the project is as follows (check one, eg [X]):
Necessary information
-autoprogramVideo links
Please make the affected input file available for us (no screenshots, those don't help!). Public links to Dropbox, Google Drive, etc, are all fine. If it is not possible to make it available publicly, 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.
Additional information
I saw a single reference to an .mcc file in the GSOC - Finish CEA-708 support #3 issue.
The mcc file format was created by MacCaption, now owned by Telestream, and is supported and used by Adobe Premiere. In the MacCaption user guide they say this "The MCC format is an open specification and free for any hardware or software manufacturer to use. Please contact Telestream for more information." I submitted a support request at:
http://www.telestream.net/telestream-support/captioning/contact-support.htm
and they sent me the white paper right away. I did not know if it would be proper for me to drop their document here without permission, so I've included the link to request it yourself.
The rationale for the .mcc file format was to support the added functionality of CEA-708 captions, since other file formats only supported 608. Since finishing CEA-708 support is a major push for the CCExtractor project, I figured this file format could be integral in this implementation. In its simplest form, an mcc file is made up of lines of timecode, each followed by a VANC line 9 CDP packet. As such, it contains both 708 and 608 information. It seems to suggest that it is not required to be able to decode the 708 data, just extract it and place it. I think the CCExtractor .bin file already stores raw CDP packet data, so hopefully this is not too far of a divergence. Its use in Adobe Premiere should offer a wide variety of testing and examples.
PS: 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.