43
Exporting / Encoding
H.264 and MPEG-2 Exports
105
CaptionMaker 6.4 User Guide
H.264 and MPEG-2 Exports
The following H.264 and MPEG-2 exports are only available in the Pro and Enterprise
versions of CaptionMaker.
SEI H.264 608/708
This export is sometimes referred to as "NAL SEI 608/708 captions" or "ATSC A/72 DTV
608/708 H.264 captions". For this export, caption data is inserted into the H.264 codec.
This is especially useful for customers delivering MP4 with embedded captions to
Akamai's Sola platform. This is used for streaming H.264 files. The wrapper can be MOV,
TS, or MP4. These extensions need to be specified when saving the output file. TS is
Transport Stream, MOV is the QuickTime container, and the MP4 wrapper is good for
multiple player compatibility. The extension tells CaptionMaker how to multiplex the
media and is not just an extension naming convention on export.
This export can create MP4 (ISO Base Media Format) files if the output file is named
.mp4; M4V format if the output file is named .m4v; and QuickTime MOV files if the
output file is named .mov. These formats are all closely related but have some minor
differences. In these cases, the source video prior to captioning can be any of the above
formats, but it can not be a Transport Stream.
This export creates an MPEG-2 Transport Stream (with H.264 codec) if the output file is
named with a .ts or .m2t extension. In this case the source video must also be a
Transport Stream (not a MP4, MOV, and so on). This export creates a generic profile
Transport Stream that is sufficient for many uses such as web streaming, however it
does not meet the strict specifications required by some broadcasters, such as the
CableLabs spec. Users who need strict control over the Transport Stream parameters
should use another multiplexing solution such as Manzanita MP2TSME.
MPEG-2 User Data
This export is similar to the "ATSC DTV 608/708 MPEG-2" export, in that it exports the
same type of caption data into MPEG-2 Elementary, Program, and Transport streams.
The resulting Closed Caption data is the same, but each export has some pros and cons,
discussed below, which is why they are both available. The export extensions should be
either .mov, .ts, or .mpg.
This is a faster mechanism than MPEG-2 ATSC export. There is only one pass required to
insert the captions into the MPEG-2 user data or A/53 style. The extension affects the
multiplexing mechanism on export.
This export creates a generic profile MPEG-2 Transport Stream without the use of
Manzanita multiplexer software. These Transport Streams do not meet the strict
specifications required by some broadcasters, such as those that require the CableLabs
spec. However, for users who just need a generic Transport Stream, it may be sufficient.
Users who need strict control over the Transport Stream parameters (including PIDs,
muxrate, descriptors, and so on) should use the Manzanita-based workflow, that is,
47
Exporting / Encoding
H.264 and MPEG-2 Exports
106
CaptionMaker 6.4 User Guide
export "ATSC DTV 608/708 Captions to MPEG-2" export together with a Manzanita
multiplexer such as MP2TSMS.
MPEG-2 ATSC Export and Manzanita
This export adds userdata in A/53 into MPEG-2 Program streams or Transport Streams.
Both 608/708 data are included in the export. If Manzanita Multiplexer is installed in the
same computer (MP2TSMS, MP2TSME) then CaptionMaker can hand off the
multiplexing part of the export operation to Manzanita. This is specially useful to
deliver CableLabs compliant streams.
When creating Transport Streams there are three critical pieces of information to know:
The video and audio PID numbers from the source file, and a Manzanita configuration
file that matches your delivery spec. (Configuration files for CableLabs-compatible HD
and SD files are included with CaptionMaker.)
The Video ID and Audio ID are determined by the source Transport Stream file. The
configuration file depends on your delivery requirements. In many cases the default
"CableLabs HD" configuration file works unless your target system requires a different
setting.
•
If you know your source file is already encoded for CableLabs, set and enable "Use
Video ID" to 481 and set and enable "Use Audio ID" to 482. The source MPEG video
must have already been encoded using these values, otherwise Manzanita will fail
to demux the file. If your file was encoded with different IDs and/or you do not
know the Video ID or Audio ID of your transport stream, please download MPEG
Streamclip from www.squared5.com or use Manzanita MPEG ID to find the correct
parameters. When you open the Transport Stream in MPEG Streamclip, you see the
Video ID and Audio ID reported in the lower left corner of the window. These are
the values you must set inside CaptionMaker.
•
If you have a Manzanita configuration file it can be applied by selecting "Encode
using user specified Manzanita config file" and clicking "Choose". This feature is
optional, and if left disabled Manzanita multiplexer will use the default CableLabs
HD configuration for the multiplexing.
•
Make sure your caption time codes match your MPEG-2 file. If you made the MPEG-
2 file from an NLE system then it might start at 01:00:00:00 or 00:00:00:00. If it was
captured from tape or video server it could have an odd starting time code such as
02:03:04:05. In any case your caption time codes need to match the MPEG-2 time
codes within the file, otherwise the captions won't line up.
Setting the Manzanita Path Variable
CaptionMaker can use Manzanita's software (such as MP2TSMS) for remuxing MPEG-2
Transport stream files. On Windows computers it is necessary to set your Path
environment variable so that CaptionMaker can find the Manzanita software.
To configure the Windows Path for Manzanita:
1. Open Control Panel and double click the System icon.
VB.NET PDF- HTML5 PDF Viewer for VB.NET Project Bookmark: Edit Bookmark. Metadata: Edit, Delete Metadata. Form Process. Read, Extract Field Data. Data: Auto Fill-in Field Create PDF Online in HTML5 PDF Viewer.
change font size pdf form reader; acrobat create pdf form VB.NET PDF - WPF PDF Viewer for VB.NET Program Bookmark: Edit Bookmark. Metadata: Edit, Delete Metadata. Form Process. Annotate PDF in WPF, C#.NET PDF Create, C#.NET Users can rotate PDF pages, zoom in or zoom
add fillable fields to pdf online; adding text to pdf form
33
Exporting / Encoding
H.264 and MPEG-2 Exports
107
CaptionMaker 6.4 User Guide
2. Select Advanced System Settings, then select the Advanced tab.
3. Click Environment Variables.
4. The folders containing the Manzanita executables must be included in the “User
Variables” PATH (to enable transport stream encoding for the current user) or in the
“System Variables” Path (to enable transport stream encoding for all users).
For example (add the following to the end of the PATH variable):
;C:\Program Files\Manzanita Systems\MP2TSMS 6;C:\Program Files\Manzanita Sys-
tems\MPEGId 3
Note: You need to use the actual folder names where the Manzanita software is
installed on your system. The item for "MPEG ID" is optional and only needed if you
have Manzanita's MPEG ID software installed and intend to use it within
CaptionMaker.
MPEG-2 720x512 422P@ML Extreme Reach SD Delivery
This export is for a special 720x512 4:2:2 MPEG-2 format used by some distributors such
as DG (DG Fast Channel), Pathfire, and Extreme Reach, and possibly others who use
hardware made by Vela.
This export is for SD video only and incorporates the Main Concept engine to add VBI
(Vertical Blanking Intervals) to the video. This is a render intensive process for these SD
videos which are already in the MPEG-2 codec. There is a generation loss, but this can
be minimized by using a higher bitrate option during export. This export is used by ad
agencies to deliver to Extreme Reach.
For detailed instructions on implementing this export, see the Telestream Knowledge
Base. The web link is on the Support page in this guide.
QuickTime Podcast Captions
The QuickTime Podcast option embeds 608 caption tracks into MP4, MOV, 3GP, and
M4V video containers. These containers are typically used for playing captions in
QuickTime Player, ITunes, and iOS devices. It is recommended to apply the Podcast
option to files that have the H.264 codec, but can be added to other codecs in the MOV
container wrapper.
26
Exporting / Encoding
Export a Subtitle Overlay for Vantage®
108
CaptionMaker 6.4 User Guide
Export a Subtitle Overlay for Vantage®
Rendering burned-in subtitles (also known as open subtitles or open captions) into a
video requires recompressing or transcoding the video, because the images are being
changed. If you need to transcode the video anyway, it is ideal to insert the subtitles
during the transcode step, instead of transcoding the video once to add the subtitles
and then transcoding it again to the final format. Vantage has a Movie Overlay filter
(listed under Video Filters) within the Flip action which can overlay subtitles on top of
the source video during a transcode.
First, you need to create a subtitle overlay video. This is a QuickTime MOV that contains
the subtitles only (no video) with an alpha channel transparent background so that it
can be overlaid on top of the video image. This can be exported from CaptionMaker
using the “(Encode Subtitles) HD Black QuickTime for NLE" export. Make sure the
resolution and frame rate of your subtitles video matches that of your source video.
Also, you must pick a QuickTime codec which supports alpha channel (Millions of
Colors Plus). Typically we recommend using the Animation codec.
The movie can then be used in the Movie Overlay filter in Vantage. Set the Overlay Left
and Top values to 0, with Width and Height values that match the source video. The
path to the video can be hard-coded, or it can come from a variable.
If you use the “Work Order” feature to submit a spreadsheet to Vantage, the variable
that points to the subtitle overlay file can be one of the columns in the work order. This
feature is handy if you want to transcode different versions of the same source video
with and without subtitles, or multiple versions with different subtitle languages.
36
109
Automated Workflow
All of the features described in this Automated Workflow chapter are only available in
the Enterprise version of CaptionMaker.
■
Overview
–
Batch Processing vs Command Line Interface
■
Command Line Interface (CLI)
–
Run a CLI .bat File on a Folder’s Contents
–
Embedding Closed Captions into Media using the CLI
–
Extract Caption Data for Re-Purposing and Internet Media
–
Bulk Frame Rate Conversion of Caption and Subtitle Data
–
Flip Caption Documents between Various Broadcast or Internet Types
–
Converting Caption and Subtitle Files to Burn-In Subtitles
■
Batch Processing
–
File Types Supported on Import
–
File Types Supported on Export
–
Naming of Exported Files
■
Vantage plus CaptionMaker Workflow Example
–
Using Vantage to Convert .SCC Files to WebVTT
–
Troubleshooting the Vantage Notify Action
40
Automated Workflow
Overview
110
CaptionMaker 6.4 User Guide
Overview
Automation is a great time saver and can handle much of the manual video file analysis,
conversion, and repetitive tasks when you need to make sure content is properly
transcoded and aired with accurate closed captioning.
You can automate many high volume caption processing tasks, such as:
•
Caption insertion and extraction.
•
Format conversion.
•
Time and frame-rate adjustment.
•
Sub-clipping and clip assembly.
•
Processing archives of video files.
•
Analyzing for quality assurance.
•
Captioning data reporting.
•
Combining with Vantage for powerful automated captioning workflows.
Batch Processing vs Command Line Interface
The following describes some differences between Batch Processing and using the
Command Line Interface (CLI) option of CaptionMaker:
•
Batch Processing runs only within the CaptionMaker user interface, whereas the
Command Line Interface can operate standalone and interface with and be initi-
ated from other applications, such as Telestream’s Vantage platform.
•
Batch Processing only performs some basic and simple linear functions, but the
Command Line Interface can perform complex multiple operations.
•
The Command Line Interface can be operated with no interaction needed with the
CaptionMaker user interface. This means that operators can perform a wide range
of captioning operations and never need to learn how to use the CaptionMaker
interface.
Documents you may be interested
Documents you may be interested
