iCouldPlay ASS alignment: map keypad positions to caption anchors

An ASS alignment value of nine is not a nine-pixel move, and one is not cue number one. Sketch a nine-position anchor grid and compare three identically worded cues in iCouldPlay. Edit externally and use existing subtitle controls, separating alignment definitions, observed rendering and device orientation without promising automatic layout or universal style fidelity.

1. Fix orientation and the wording baseline

Choose an owned clip of at least twelve seconds without the same burned-in sentence and confirm continuous playback. Record identity, source, orientation and display mode, using the visible video area rather than mixing bars and whole screen. Save a UTF-8 ASS copy externally and preserve originals. Without loading controls, report source review only. Fix text size and display mode so device rotation does not confound file alignment.

2. Save a complete alignment-only sample

Copy this complete original file. Only the per-cue alignment override changes; style, wording and non-overlapping durations remain comparable. Keep the style default separate from cue overrides. Font substitution does not itself show an alignment-number error. Preserve Events field order and one literal backslash; put the braced override in Text, not the Style field. Do not add position or movement commands that could confound the comparison.

[Script Info]
ScriptType: v4.00+
PlayResX: 640
PlayResY: 360

[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Arial,24,&H00FFFFFF,&H000000FF,&H00000000,&H00000000,0,0,0,0,100,100,0,0,1,1,0,2,20,20,20,1

[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:01.00,0:00:03.00,Default,,0,0,0,,{\an1}Keep the anchor clear.
Dialogue: 0,0:00:04.00,0:00:06.00,Default,,0,0,0,,{\an5}Keep the anchor clear.
Dialogue: 0,0:00:07.00,0:00:09.00,Default,,0,0,0,,{\an9}Keep the anchor clear.

3. Read the numbers as a keypad grid

The Aegisub alignment documentation uses keypad ordering: bottom row one/two/three, middle four/five/six, top seven/eight/nine. Mark this example’s bottom-left, center and top-right rather than arranging one through nine on a coordinate axis. These are caption-layout directions, not physical gravity or a character’s viewpoint. Margins, wording and rendering still affect the result. The grid is explanatory, not pixel measurement, and legacy alignment-number conventions must not be mixed with an.

4. Play continuously and check wording before placement

Play from zero beyond nine seconds. Transcribe the full sentence before recording placement, line count and obstruction relative to the video. Keep control-bar visibility comparable. Report matching directions only for this sample. Preserve absent differences or literal tags before editing rather than forcing an expected result. Resume after pausing to verify cue endings. Complete wording and layout compatibility remain separate outcomes.

5. An anchor is not the text filling a grid cell

Bottom-left alignment does not put every glyph inside a bottom-left paper cell or reduce character width or font size to a third. Describe text around its reference position with margins retained, not only the last glyph’s location. Record wrapping separately from alignment definitions. For a longer-sentence experiment, change all three cues to identical longer wording in a separate copy; shortening only one confounds content and alignment. No automatic anchor-grid button or video overlay is required.

6. Keep a separate style-default control

Save a control removing the three overrides while preserving the default style. Record the shared source condition without copying predictions into observations. Verify filenames after switching because identical wording can conceal stale selection. If a real app positioning control exists, record its actual option in another round rather than treating it as the ASS markup editor. Otherwise use file variants. Restore original settings afterward and keep a readable fallback.

7. Troubleshoot override placement and extra positioning rules

Literal an text or backslashes call for checking format, braces and escaping, not hiding the problem with smaller text. For unexpected placement, inspect accidentally pasted positioning/movement commands, subtitle identity and interval. If all cues are absent, check loading and timing before blaming video integrity. Change one identified issue at a time, preserve versions and selection records, and avoid clearing the library. Documentation is not a test of every iCouldPlay playback path; unperformed device checks stay untested.

8. Reopen and verify directions and limits

Leave the playback page, reopen the clip, reselect the exercise copy and replay all three cues from the beginning. Keep identity, keypad convention, override values, default condition, observations and unknowns, limiting conclusions to this round. Play the fallback once more and preserve originals. Another reader should reproduce bottom-left/center/top-right comparisons without confusing numbers with pixels, times or rotation angles. This does not certify all ASS animations or styles. Add a record for changed viewing conditions.

Related tutorials and sources

ASS line breaks, ASS style fidelity.

Checked on November 12, 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.