How to Use Quality Control Warnings

Quality control warnings help you find subtitle problems while you work.

Sublandia Editor includes automatic real-time validation for important subtitle quality checks such as CPS, CPL, WPM, number of lines, subtitle duration, gaps and overlaps. Instead of waiting until the final review, you can see many potential issues immediately while editing.

QC in Sublandia Editor is not designed to interrupt your work. It is designed to guide you. It helps you notice when a subtitle may be too fast, too long, too short, too dense, too close to another subtitle or technically invalid according to the selected ruleset.

This guide explains how to understand QC warnings and errors, how to decide what needs fixing and how to use validation as part of a professional subtitle workflow.

 Open Sublandia Editor

 

What Quality Control Means in Sublandia Editor

Quality control, or QC, is the process of checking whether subtitles follow the technical, timing and readability rules of a project.

In Sublandia Editor, QC is connected to the selected ruleset. The ruleset defines the limits and validation behavior for the project.

Sublandia Editor can validate:

• CPS - characters per second
• CPL - characters per line
• WPM - words per minute
• Lines - number of subtitle text lines
• Too short duration
• Too long duration
• Gap too small before subtitle
• Gap too small after subtitle
• Overlap

These checks help you find problems early and keep subtitle quality consistent.

 Open Sublandia Editor

 

Errors and Warnings

Sublandia Editor uses visual status indicators to help you understand how serious a QC issue is.

• Red means an error
• Yellow means a warning

A warning usually means the subtitle is outside the optimal range but may still be allowed by the selected ruleset.

An error usually means the subtitle breaks a maximum, minimum or required rule and should normally be fixed before final export or delivery.

The exact behavior depends on the selected ruleset and the QC category.

Red Errors Should Usually Be Fixed

A red error is more serious than a warning.

A red error usually means that the subtitle violates a limit defined by the selected ruleset. This can include a subtitle that is too fast, too long per line, too short, too long, overlapping with another subtitle or too close to another subtitle without a valid gap.

In most professional workflows, red errors should be fixed before export.

However, you should still review the subtitle in context. The ruleset tells you what is technically invalid, but the final edit should also consider speech, scene rhythm and delivery requirements.

CPS: Characters per Second

CPS means characters per second.

CPS measures how much text the viewer needs to read during the time a subtitle is visible.

A CPS warning or error may appear when the subtitle contains too much text for its duration.

Common fixes include:

• extending the subtitle duration
• shortening the text
• rewriting the sentence
• splitting the subtitle
• checking whether the selected ruleset is correct

CPS is one of the most important readability checks because it directly affects whether the viewer can read the subtitle comfortably.

CPL: Characters per Line

CPL means characters per line.

CPL checks how long each subtitle line is visually.

A CPL warning or error may appear when one subtitle line is longer than the optimal or maximum line length defined by the selected ruleset.

Common fixes include:

• adding a better line break
• shortening the line
• rewriting the subtitle
• splitting the subtitle into two subtitle events
• checking line balance and readability

CPL helps keep subtitles visually clean and easier to read.

Recommended guide page:

• Maximum Characters per Line and Subtitle Line Length

WPM: Words per Minute

WPM means words per minute.

WPM measures reading speed based on the number of words instead of characters.

This can be useful because two subtitles with similar character counts may still feel different depending on word length, language and structure.

A WPM warning or error may appear when the subtitle requires the viewer to read too many words too quickly.

Common fixes include:

• shortening the text
• simplifying the sentence
• extending duration if possible
• splitting the subtitle
• rewriting literal or word-heavy translations

WPM should be reviewed together with CPS, because both measure reading speed from different angles.

Lines: Number of Subtitle Lines

Sublandia Editor can validate the number of subtitle text lines.

In many subtitle workflows, subtitles should usually be limited to a certain number of lines. A common professional layout is one or two lines, depending on the ruleset and project requirements.

A line count warning or error may appear when a subtitle contains too many text lines.

Common fixes include:

• reducing the subtitle to one or two lines
• improving line breaks
• shortening the text
• splitting the subtitle into separate subtitle events
• checking whether the subtitle is too dense

Too many lines can cover too much of the image and make the subtitle harder to follow.

Too Short Duration

A subtitle is too short when it stays on screen for less than the minimum duration allowed by the selected ruleset.

This can make the subtitle flash too quickly and become difficult to read.

Common fixes include:

• extending the subtitle end time
• moving the start time earlier if appropriate
• merging it with a nearby subtitle
• shortening or rewriting the text
• checking gaps and overlaps after the change

A subtitle should stay on screen long enough to be read comfortably.

Recommended guide page:

• Minimum and Maximum Subtitle Duration

Too Long Duration

A subtitle is too long when it stays on screen longer than the maximum duration allowed by the selected ruleset.

This can make the subtitle feel disconnected from the speech or scene.

Common fixes include:

• shortening the subtitle duration
• splitting the subtitle
• removing unnecessary text
• retiming the subtitle to follow speech more naturally
• checking whether the subtitle stays on screen after the dialogue ends

A subtitle should not remain visible much longer than necessary unless there is a clear reason.

Recommended guide page:

• Minimum and Maximum Subtitle Duration

Gap Too Small Before Subtitle

A gap too small before subtitle issue means the subtitle starts too close to the previous subtitle.

Professional subtitle workflows usually require a valid gap between consecutive subtitle events. If the gap before a subtitle is too small, the transition can feel too tight or may break the selected ruleset.

Common fixes include:

• moving the subtitle start time later
• shortening the previous subtitle
• adjusting both subtitles slightly
• using ruleset-based gap correction
• checking whether the previous subtitle timing is too long

The goal is not to remove gaps. The goal is to keep valid professional spacing between subtitles.

Recommended guide page:

• How to Fix Subtitle Gaps

 

Gap Too Small After Subtitle

A gap too small after subtitle issue means the subtitle ends too close to the next subtitle.

This can happen when the current subtitle stays too long, or when the next subtitle starts too soon.

Common fixes include:

• shortening the current subtitle
• moving the next subtitle later
• adjusting both subtitle lines
• checking whether an overlap is about to happen
• using Auto Fix Gap if the selected ruleset supports it

A valid gap helps subtitles feel clean and readable from one event to the next.

Recommended guide page:

• How to Fix Subtitle Gaps

 

Overlap

An overlap happens when one subtitle starts before the previous subtitle has ended.

Overlaps are usually more serious than small gap warnings because two subtitle events are active at the same time.

Common fixes include:

• shortening the previous subtitle
• moving the next subtitle later
• adjusting both subtitle lines
• merging subtitles if they belong together
• checking whether the overlap comes from a larger sync problem

Overlaps should normally be fixed before export, especially in professional subtitle workflows.

Recommended guide page:

• How to Fix Overlapping Subtitle Lines

 

How to Decide What to Fix First

When a subtitle has multiple QC issues, fix the most structural problems first.

A good order is:

1. Overlap
2. Invalid gaps
3. Too short or too long duration
4. CPS and WPM reading speed
5. CPL and line length
6. Number of lines
7. Final wording and line breaks

This order helps because timing problems often affect readability. For example, if you fix a duration problem first, the CPS warning may disappear automatically.

 

Do Not Fix QC Mechanically

QC warnings and errors are important, but they should not be fixed blindly.

Before changing a subtitle, check:

• the dialogue
• the scene rhythm
• the speaker timing
• the selected ruleset
• the subtitle standard
• the delivery requirement
• the surrounding subtitles
• the viewer’s reading experience

The goal is not only to remove red and yellow indicators. The goal is to create subtitles that are technically valid, readable and natural.

 

When a Warning Can Be Accepted

Some warnings may be acceptable depending on context.

For example:

• a short subtitle may be acceptable for a very short phrase
• a slightly high CPS may be acceptable in fast dialogue
• a longer line may be acceptable if breaking it would damage meaning
• a gap may be acceptable if it follows the scene rhythm
• a line break may be unusual but still readable

However, accepted warnings should be intentional. They should not be ignored simply because they are yellow.

 

When an Error Should Not Be Ignored

Red errors should usually be fixed.

This is especially true for:

• overlaps
• subtitles below minimum duration
• subtitles above maximum duration
• CPS above maximum allowed value
• CPL above maximum allowed value
• invalid gaps that break the selected ruleset
• too many subtitle lines

If the file needs professional delivery, red errors can cause rejection, playback problems or poor viewing experience.

 

 

QC and Final Review

Real-time QC helps you work faster, but it does not replace final review.

Before export, you should still watch or review the subtitle file and check:

• timing
• readability
• spelling
• line breaks
• terminology
• sync
• gaps
• overlaps
• duration
• export format
• selected ruleset

QC can show technical issues, but human review is still needed for language quality, context and natural subtitle flow.

 

Practical QC Workflow

Use this workflow when Sublandia Editor shows QC warnings or errors:

1. Check whether the issue is yellow or red.
2. Identify the QC category.
3. Review the selected ruleset.
4. Play the subtitle in context.
5. Check nearby subtitles.
6. Fix timing problems first.
7. Then fix reading speed and line length.
8. Review text, line breaks and meaning.
9. Confirm that the fix did not create a new issue.
10. Continue only when the subtitle is readable and technically valid.

QC works best when it is part of the editing process, not only a final step.

 

QC Checklist Before Export

Before exporting subtitles, check:

1. No unresolved red errors remain.
2. Yellow warnings have been reviewed.
3. CPS and WPM are acceptable for the selected ruleset.
4. CPL and line breaks are readable.
5. Subtitle line count follows the ruleset.
6. Minimum and maximum duration errors are fixed.
7. Gaps before and after subtitles are valid.
8. Overlaps are fixed.
9. Timing still matches the video.
10. The selected ruleset matches the project requirements.
11. The final subtitle file has been reviewed in context.
12. A project backup has been created if needed.

This helps make the subtitle file cleaner before export and delivery.

 FAQ

What are QC warnings in Sublandia Editor?

QC warnings are real-time validation indicators that show potential subtitle quality issues, such as high reading speed, long lines, invalid duration, small gaps or overlaps.

 

Does Sublandia Editor validate subtitles automatically?

Yes. Sublandia Editor automatically validates CPS, CPL, WPM, number of lines, subtitle duration, gaps and overlaps while you work.

 

What does yellow mean?

Yellow means warning. A warning usually means the subtitle is outside the optimal range but may still be allowed by the selected ruleset.

 

What does red mean?

Red means error. An error usually means the subtitle violates a limit or requirement defined by the selected ruleset and should normally be fixed.

 

Are QC warnings controlled by the ruleset?

Yes. QC limits and validation behavior are defined by the selected ruleset.

 

What is CPS validation?

CPS validation checks characters per second and helps identify subtitles that may be too fast to read.

 

What is CPL validation?

CPL validation checks characters per line and helps identify subtitle lines that may be too long.

 

What is WPM validation?

WPM validation checks words per minute and helps measure reading speed based on word count.

 

What does “gap too small before subtitle” mean?

It means the subtitle starts too close to the previous subtitle according to the selected ruleset.

 

What does “gap too small after subtitle” mean?

It means the subtitle ends too close to the next subtitle according to the selected ruleset.

 

What is an overlap?

An overlap happens when one subtitle starts before the previous subtitle has ended.

 

Should I fix all yellow warnings?

Not always, but all yellow warnings should be reviewed. Some may be acceptable in context, while others should be improved.

 

Should I fix all red errors?

In most cases, yes. Red errors usually indicate a ruleset violation or serious timing/readability problem.

 

Can fixing one QC issue create another?

Yes. For example, extending duration may fix CPS but create an overlap or invalid gap. Always check nearby subtitles after making changes.

 

Does QC replace human review?

No. QC helps identify technical and readability issues, but final review is still needed for meaning, language quality, context and natural subtitle rhythm.