Skip to main content

Pre-Export Checks

Every time you initiate an export from Closed Caption Creator, the application runs a set of automatic structural checks on the events being exported before the file is written. These checks are not configurable and cannot be disabled — they exist as a final safety net to prevent files with critical defects from leaving the application. If any check fails, you will be presented with a clear description of the problem and given a choice of how to proceed.

What Is Checked​

The pre-export validation inspects every event in the event group being exported and evaluates the following conditions.

Missing start timecode. If an event does not have a valid start time, it cannot be placed correctly in the output file. An event in this state is typically the result of an incomplete edit session where a new event was created but never given a timecode.

Missing end timecode. Similarly, an event without a valid end time cannot define when a caption should leave the screen. Events in this state are flagged for the same reason as those with missing start timecodes.

Start and end timecode are identical. An event whose start and end times are the same has zero duration and would either not appear on screen or would behave unpredictably in different player implementations. This check catches timecodes that were set to the same value inadvertently.

Start timecode is after end timecode. An event where the start time is later than the end time is invalid in all caption formats. This condition can occur after manual timecode edits where both fields were modified independently and the order was accidentally reversed.

Overlap with the previous event. If an event begins before the preceding event has finished, the two events overlap. Sub-frame overlaps — those smaller than a single frame — are silently corrected by the export process, as they are typically caused by rounding during timecode conversion and are not meaningful errors. Overlaps of one frame or more are flagged, because they can cause visible display problems and are rejected by many delivery specifications. This check does not apply to the first event in the group.

Missing text. An event that has timecodes but no caption text will produce an empty on-screen area or, in some formats, an explicit blank subtitle. Empty events are flagged so that you can confirm whether they are intentional or were created accidentally.

Responding to a Failed Check​

When a check fails, a dialog will appear describing the problem with the specific event and offering three options.

Choosing Abort cancels the export entirely. The export dialog will close, the editor will select the failing event, and the timeline will scroll to bring it into view. This is the safest response if you are not certain about the nature of the problem — it puts you directly at the relevant event so you can inspect and correct it before attempting the export again.

Choosing Ignore skips the failing event and continues the validation process. The export will proceed but the skipped event will be excluded from the output file. Use this option only when you are certain that eliminating the event from the export is acceptable.

Choosing Ignore All skips the current check for all remaining events of the same type. This is useful when, for example, a project intentionally contains placeholder events without text and you want to acknowledge them all at once without being prompted individually for each one.

The Relationship Between Pre-Export Checks and Style Guide Review​

Pre-export checks cover structural validity only — the properties that make a file technically well-formed regardless of delivery specification. They do not evaluate reading speed, character counts, line limits, or any of the content constraints defined in a style guide. Those checks are the responsibility of the Style Guide review workflow and Realtime Error Detection, which should be completed before export. A file that passes all pre-export checks is structurally valid but is not guaranteed to meet the content requirements of any particular delivery specification.

For best results, complete a style-guide review pass before exporting, resolve any remaining errors, and allow the pre-export checks to serve their intended role as a final structural gate rather than a substitute for content QC.