![]() The easiest way to run these is inside of docker,Īs the dependencies are handled for you. They are run as part of a pull request, but for debugging purposes they can alsoīe run locally (even in an IDE) before a pull request is issued. These are intended to be run as integration tests and verify that nothing hasīroken as a result of a change. While the testing is not complete yet, there are several Unit Tests, Integration Tests, and System Tests that run Regression Testing the Caption Inspector Executable Underneath the current directory, specifically. and the input file is located in a directory This example, the output file is located in the current directory. You will need to prefix your input and output paths to that so that it can place the files in the correct spot. In the docker run command, your current working directory will be remapped to /files inside of the container, so Once the GPAC library has been built the same instructions are used as above.ĭocker run -tv $(pwd):/files caption-inspector -o /files /files/test/media/BigBuckBunny_256x144-24fps.tsĭocker run -tv $(pwd):/files caption-inspector -o /files /files/test/media/Plan9fromOuterSpace.scc -f 2400ĭocker run -tv $(pwd):/files caption-inspector -o /files /files/test/media/NightOfTheLivingDead.mcc This library is located and must be pulled and built. Gets linked as a shared object is required. Specifically a modified library of GPAC which Building the Caption Inspector Executable Locally with MOV SupportĬaption Inspector requires the inclusion of the Library. Running against the caption file NightOfTheLivingDead.mcc demonstrates decoding an MCC file, CEA-608 Captions, and CEA-708 Captions. Running against the caption file Plan9fromOuterSpace.scc demonstrates decoding an SCC file and CEA-608 Captions, as well asĬonverting the contents of the SCC file into an MCC file. Running against the video file BigBuckBunny_256x144-24fps.ts demonstrates decoding closed captions from a video file. Running with the -h option will simply print out the help text. test/media/Plan9fromOuterSpace.scc -f 2400 To install FFMPEG Version 4.0.2, follow the below list (for Mac), using the Dockerfile as a reference: Version of FFMPEG from here and install it in your machine.Ĭaption Inspector is known to run with FFMPEG Version 4.0.2. Decoding a SCC Caption file and writing the decoded captions into a MCC Caption File, a CEA-608 Decode File,Īnd a Closed Caption Descriptor Decode File.īuilding and Running the Caption Inspector Executable LocallyĬaption Inspector requires FFMPEG to be installed on your machine.Decoding a MCC Caption file and writing the decoded captions into a CEA-608 Decode File,.Pulling Captions from a Video Asset and writing them to an MCC Caption File, a CEA-608 Decode File,Ī CEA-708 Decode File, and a Closed Caption Descriptor Decode File.Currently, the following are the main use cases that the Caption New plugins to perform various transformations. mp4 containers), MCC (MacCaption Closed Captions), and SCC (Scenarist Closed Captions) files.Ĭaption Inspector has a plugin pipeline architecture that can be configured in various ways and allows the user to add Caption Inspector Supports CEA-608 and CEA-708 in MPEG-2 and The Caption Inspector project builds a C library, C executable, and Docker image that can be used to extract and decodeĬlosed-Captions from various Video or Caption File Formats.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |