# iCouldPlay ASS spacing: distinguish fsp letter spacing from fscx glyph scaling

Language: en
Canonical: [iCouldPlay ASS spacing: distinguish fsp letter spacing from fscx glyph scaling](<https://allluckly.cn/en/guides/icouldplay-ass-letter-spacing-fsp-versus-horizontal-glyph-scale/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-ass-letter-spacing-fsp-versus-horizontal-glyph-scale/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-ass-letter-spacing-fsp-versus-horizontal-glyph-scale/>)
Published: 2026-11-19T00:00:00+08:00
Modified: 2026-11-19T10:09:59+08:00
Author: Bison

Save a complete ASS with ordinary, spaced and horizontally scaled ABCD events, then observe it through a genuinely available path. Record spacing, glyph scale and visible line width separately; one wider screenshot identifies neither the changed parameter nor measured device dimensions.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-ass-letter-spacing-fsp-versus-horizontal-glyph-scale/>), translated on 2026-11-19. Original publication dates, attribution, code and version notes are retained.

Save a complete ASS with ordinary, spaced and horizontally scaled ABCD events, then observe it through a genuinely available path. Record spacing, glyph scale and visible line width separately; one wider screenshot identifies neither the changed parameter nor measured device dimensions.

## Fix text, font and the same source clip

Use an owned still-scene clip at least twelve seconds long, preserving video/original subtitles and a separate practice copy. Fix four ASCII letters ABCD without spaces, which would change text. Arial is an example readable style; record actual fallback/availability rather than guarantee installation. Establish the same font externally for comparison. Fix a 640 × 360 script, size 36 and initial scales 100. Hold fitting, orientation and speed fixed instead of changing video dimensions to widen subtitles, retaining restoration information.

## Map three conditions to clear intervals

Event one at 1–3 s uses spacing 0 and horizontal scale 100. Event two at 4–6 s changes only spacing to 4. Event three at 7–9 s returns spacing to 0 and changes horizontal scale to 150. All share position (120,140), size, vertical scale, text, border and shadow, with one-second gaps. Compare each modified condition with the baseline; the third is not a one-value change from the second. Preserve interval/parameter records and a clip covering beyond nine seconds rather than overlaying conditions simultaneously.

## Save the complete style and three-event ASS

Save the complete text below as UTF-8 plain-text spacing-scale.ass, including Script Info, V4+ Styles and Events. Reopen to exclude an ass.txt extension and verify Format alignment. ABCD sits outside overrides; preserve ASCII backslashes, parentheses and commas. Edit externally rather than assume an iCouldPlay subtitle editor. The literal fsp4 is not four seconds and fscx150 is not a 150-pixel video width. Preserve other projects and record this copy’s filename/source/change so stale loading is not mistaken for an ineffective parameter.

```
[Script Info]
ScriptType: v4.00+
PlayResX: 640
PlayResY: 360
WrapStyle: 2
ScaledBorderAndShadow: yes

[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,36,&H00FFFFFF,&H000000FF,&H00000000,&H00000000,0,0,0,0,100,100,0,0,1,0,0,7,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,,{\an7\pos(120,140)\bord0\shad0\fscx100\fscy100\fsp0}ABCD
Dialogue: 0,0:00:04.00,0:00:06.00,Default,,0,0,0,,{\an7\pos(120,140)\bord0\shad0\fscx100\fscy100\fsp4}ABCD
Dialogue: 0,0:00:07.00,0:00:09.00,Default,,0,0,0,,{\an7\pos(120,140)\bord0\shad0\fscx150\fscy100\fsp0}ABCD
```

## Distinguish script-unit spacing from percentage scaling

Aegisub defines fsp spacing in script-resolution pixels, allowing negative/fractional values, while fscx scales text shape by percentage, with 100 original. Both may widen a line but are different operations: more spacing is not stretched glyphs, and scaling is not a fixed extra 4 between every pair. Size 36 does not nullify horizontal scaling. Font/layout conditions affect glyphs and line bounds; no universal line-width formula or screenshot measurement is supplied.

## Use four paper reference points without replacing rendering

Separately stipulate four paper x coordinates 0, 20, 40 and 60, with three gaps of 20. Adding 4 to each gap gives 0, 24, 48 and 72, changing span 60 to 72. Multiplying coordinates by 1.5 gives 0, 30, 60 and 90. These declared geometric points are not actual ABCD advances, kerning or mandatory renderer positions. Four points define three intervening gaps, not four additions. They distinguish gap addition from scaling without passing mobile widths of 72/90. Preserve axes/units; fallback cannot turn the model into a measurement.

```
Declared paper points, NOT font metrics:
base x:     0 20 40 60
gaps +4:    0 24 48 72
scale x1.5: 0 30 60 90
gaps -2:    0 18 36 54
```

## Observe actual identity and appearance in each interval

Associate the complete file with its source through an actual supported installed path. Verify baseline ABCD, timing and identity before observing inside the second/third intervals. Record gaps, individual shapes and overall extent rather than only “wider.” Document uncontrolled font/size overrides instead of pretending identical conditions. External-editor previews are separate evidence, not an iCouldPlay pass. Without association/viewing retain source/model checks and leave rendering pending, inventing no hidden styling panel.

## Change only event two spacing for a negative-value control

Save counter-spacing.ass and change only event two from fsp4 to fsp-2. Keep all other events/fonts/scales. Reducing each paper gap from 20 to 18 gives 0, 18, 36 and 54; negative spacing is not negative playback time and need not force overlapping glyphs. Compare the actual 4–6 s result after reloading while preserving the original. For no difference inspect file/backslash/parameter scope and parsing before size changes. Literal directives require a format check, not a conclusion about scaling mathematics.

## Deliver parameters, paper values and observation scope

Retain complete ASS, conditions, four-point model, negative control and observations. Reconfirm selected files on reopening and pass only viewed intervals. Explain spacing addition versus percentage scale, why fixed font size permits horizontal changes and which values are not screen measurements. Label any saved comparison image with source time, subtitle filename and orientation; viewing only later events cannot retrospectively pass a missing baseline. Confirm all four letters remain on one line. Do not subtract a wrapped block’s bounds from a former single-line span; establish a separate display condition and repeat all three events if needed. Restore original subtitles/display without modifying video/audio. Mark unperformed control/reopen/playback separately pending, claiming no built-in typesetter, geometry analyzer/editor or universal font/script/output behavior.

## Related guides and sources

[Animated horizontal scale and time windows](<https://allluckly.cn/en/guides/icouldplay-ass-transform-relative-time-acceleration-scale-model/>); [Script coordinates versus device pixels](<https://allluckly.cn/en/guides/icouldplay-ass-pos-script-coordinate-display-pixels/>).

Checked on 19 November 2026: [Apple public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn&entity=software&timestamp=20261119-root>) lists iCouldPlay 1.1.1, requiring iOS / iPadOS 15.0 or later. The [official store](<https://apps.apple.com/cn/app/id6755653178>) describes ASS/SSA and embedded/external subtitles. Prepare source, syntax and mathematics externally; associate and observe through actual installed paths. Format support does not guarantee every instruction across all engines/devices. No completed physical-device subtitle rendering, professional pixel measurement, exhaustive-format or private-server testing is claimed.

Method references: [Aegisub ASS override tags](<https://aegisub.org/docs/latest/ass_tags/>).

