Reading load and content changes

Compare caption reading load at two durations in iCouldPlay

Calculate text per second for one original sixteen-character cue, then compare understanding and picture tasks without universal readability thresholds.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

A cue can be legible when paused yet too demanding during playback. Hold one original sentence fixed and vary duration, comparing text load, viewing conditions and comprehension. Characters per second are not a universal pass threshold, and this differs from semantic line breaking. iCouldPlay supplies viewing; you count, calculate and assess understanding without an assumed reading-speed evaluator. Start with one cue rather than letting a whole-file average hide local difficulties.

Fix original text and a counting rule

Use the original sentence “先保存原始文件再核对字幕时间范围”. Count its sixteen Chinese characters only, excluding spaces, timing arrows and markup. Count individually and verify against the sentence rather than assuming the length. A different punctuated or English sentence needs its own counting definition; word counts and Chinese-character counts are not directly comparable. Keep this wording as the reference for every copy. It concerns file checks and needs no film dialogue or restricted captions.

Create four-second and two-second copies

Choose a permitted self-made clip with a simple background. Following the existing VTT method, make A show the sentence from four-to-eight seconds and B from four-to-six, with all else fixed. Load one at a time and name them four-second and two-second copies. Check structure and intervals at file level; integer player time is not a millisecond calibration tool. Keep picture actions explainable and record competing attention demands rather than silently substituting easier pictures.

Calculate load without judging the reader

A is sixteen divided by four, four characters per second; B is sixteen divided by two, eight. This describes cue scheduling, not innate reading ability or universal suitability. Then consider font, screen and familiarity. Recalculate after text or timing changes. Gaps between cues also affect continuous load, so a single-cue calculation does not represent a whole passage. Keep this first comparison fixed and observe longer segments separately.

View the longer version at normal speed

Load A in iCouldPlay and confirm video, normal speed and caption size before playing from several seconds earlier. Without pausing to memorize it, paraphrase the requested first action and later check, noting missed picture actions. Prior knowledge introduces familiarity, so label this known-text practice rather than a study of unfamiliar-caption readers. Resolve invisible size/contrast conditions first, then fix settings for comparison rather than conflating illegibility with insufficient time.

Hold other conditions for the shorter copy

Load B alone and retain speed, size, orientation and viewing distance. Repeat playback and note completion, understanding of order and any replay need rather than merely “fast” or “slow”. Ease with the shorter copy may reflect familiarity and does not justify requiring it of everyone. Do not manufacture difficulty through smaller text or greater distance. Keep conditions with subjective results so the comparison describes the task, not whether a viewer reads fast enough.

Separate reading completion from integrated understanding

On another pass, separate seeing all text, paraphrasing meaning and following the picture. Completing words does not guarantee comprehension; understanding text can still miss an important arrow. In your own instructional captions, consider longer necessary cues or less redundant wording, preserving revisions and qualifications. For others’ finalized material, use permitted pause/replay rather than overwriting captions. Record a concrete difficulty, such as missing the final two terms, instead of explaining every issue through one average number.

Interpret the rate within this sample only

Record both schedules, rates and observations without claiming iCouldPlay measured a person’s reading speed or certified readability. Language, age, familiarity and picture complexity limit transfer; no audience experiment is claimed. For voluntary feedback, explain prior text knowledge and conditions without collecting unrelated identity data or setting a universal threshold from one or two people. Arithmetic helps explain an edit; actual integrated understanding remains a separate check.

Keep versions and one next revision target

Keep wording, counting definition, both intervals, playback conditions and the three comprehension observations. Restore original captions and speed and retain the unique video. For your own next revision, change one factor, such as removing redundant wording at four seconds, then recheck meaning and qualifications; shorter is not automatically better. W3C WebVTT describes timed-text structure without a universal reading-rate answer. Success explains the scheduling change and observation limits rather than producing a supposedly scientific pass number without conditions.

Segment caption phrases, Check caption meaning.

Checked on November 6, 2026 against the official iCouldPlay App Store listing and Apple public lookup: version 1.1.1, requiring iOS / iPadOS 15.0 or later. The public 1.1.1 release notes list Kodi, OpenList / AList and S3-compatible storage, with improvements to source switching and captions after seeking. The tasks use this public scope and existing playback capabilities. Check controls in your installed version. Self-made samples, manual records and external file preparation are workflows, not newly promised automatic features. No physical-device or private-server test is claimed.