# iCouldPlay HLS compatibility versions: calculate minima from feature combinations

Language: en
Canonical: [iCouldPlay HLS compatibility versions: calculate minima from feature combinations](<https://allluckly.cn/en/guides/icouldplay-hls-rfc8216-minimum-version-feature-ledger/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-hls-rfc8216-minimum-version-feature-ledger/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-hls-rfc8216-minimum-version-feature-ledger/>)
Published: 2026-11-16T00:00:00+08:00
Modified: 2026-11-16T10:52:10+08:00
Author: Bison

Audit five separate RFC 8216 examples requiring 3, 4, 5, 6, 7 without confusing playlist compatibility with app or latest-protocol versions.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-hls-rfc8216-minimum-version-feature-ledger/>), translated on 2026-11-16. Original publication dates, attribution, code and version notes are retained.

A larger VERSION does not supply missing resources, and a lower number does not simplify media. Within RFC 8216 section 7, build a minimum-compatibility ledger from five independent reading samples. This is no inventory of every current HLS extension or guarantee that an iCouldPlay path decodes a declared version.

## Define scope and five independent files

Make five external cards A–E, each beginning with its own EXTM3U, not five VERSION tags in one file. Record playlist role, features, requirements and resulting declaration. App 1.1.1 is no HLS compatibility level. RFC 8216 was published in 2017; this task covers its stated rules, without calling 7 the limit of every current HLS specification. No actual media is supplied. Real playback additionally needs bytes, dependencies and client capability, so complete text is not a prefilled pass.

## Use floating durations to require 3 in A

A is an ended one-segment media playlist with EXTINF 4.5, requiring at least 3 here. Target duration 5 satisfies the rounded duration bound but does not cause the compatibility minimum. Do not copy target 5 into VERSION. Lowering the declaration to 2 while retaining floating duration does not remove the requirement. Base corrections on actual content and the specification rather than bypass an unsupported client. Correct minima still establish neither real 4.5-second bytes nor playback.

```text
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:5
#EXTINF:4.5,
float-a.ts
#EXT-X-ENDLIST
```

## Use byte ranges to require 4 in B

B has two four-second entries using 1000 bytes at 0 and 1000 bytes at 1000 of one resource. BYTERANGE requires at least 4. Inclusive ranges are 0–999 and 1000–1999, adjacent and disjoint; they are byte positions, not frames or seconds. Record minimum 4 separately from total 8 seconds. Deleting BYTERANGE while repeating the resource name changes segment references rather than merely lowering a version. Keep the sample intact instead of replacing structural inspection with suffix or number edits.

```text
#EXTM3U
#EXT-X-VERSION:4
#EXT-X-TARGETDURATION:4
#EXTINF:4,
#EXT-X-BYTERANGE:1000@0
media.ts
#EXTINF:4,
#EXT-X-BYTERANGE:1000@1000
media.ts
#EXT-X-ENDLIST
```

## Combine I-frame-only and MAP requirements in C

C declares I-FRAMES-ONLY and MAP. Their requirements here are at least 4 and 5, so the combined minimum is the higher value 5, not 4+5=9. No initialization or I-frame bytes are supplied, and suffixes do not certify container structure. This is a tag-combination audit. A four-second I-frame interval is no four-second continuous action. Removing the I-frame-only declaration changes the MAP condition and calls for recalculation.

```text
#EXTM3U
#EXT-X-VERSION:5
#EXT-X-TARGETDURATION:4
#EXT-X-I-FRAMES-ONLY
#EXT-X-MAP:URI="iframe-init.mp4"
#EXTINF:4,
iframe-a.m4s
#EXT-X-ENDLIST
```

## Require 6 for MAP without I-frame-only in D

D also has MAP but lacks I-FRAMES-ONLY, requiring at least 6 under section 7. Circle the absence condition instead of treating every MAP as minimum 5. Initialization is not another timed media item needing EXTINF; the actual entry below has four seconds. Copying C’s 5 into D is the intended fault, which mp4/m4s suffixes cannot repair. Other format requirements may apply. These five cards audit selected conditions, not every output format or tag.

```text
#EXTM3U
#EXT-X-VERSION:6
#EXT-X-TARGETDURATION:4
#EXT-X-MAP:URI="init.mp4"
#EXTINF:4,
fragment-a.m4s
#EXT-X-ENDLIST
```

## Require 7 for a master using SERVICE in E

E is a master whose caption INSTREAM-ID is SERVICE3, requiring at least 7 here. Three names a CEA708 service block, not segment 3, and not every master inherently requires 7. The entry has no URI because caption data belongs in the corresponding media; a declaration creates no bytes. Changing to CC1 does not prove every remaining requirement falls to 1: re-audit the master and references. This illustrates one compatibility condition, without claiming actual readable SERVICE3 data.

```text
#EXTM3U
#EXT-X-VERSION:7
#EXT-X-MEDIA:TYPE=CLOSED-CAPTIONS,GROUP-ID="cc-service",NAME="Service three",DEFAULT=NO,AUTOSELECT=NO,INSTREAM-ID="SERVICE3"
#EXT-X-STREAM-INF:BANDWIDTH=900000,CODECS="avc1.4d401e,mp4a.40.2",CLOSED-CAPTIONS="cc-service"
video.m3u8
```

## Separate declarations from real playback observations

For an owned source, identify role, list applicable conditions and meet their highest minimum. Higher declarations imply no better quality. RFC clients unsupported at the declared version must not attempt playback; lowering the tag is no universal workaround. Observe startup, sequential playback and ending on an available iCouldPlay path without inventing engine-version diagnostics. Keep version, resource access and decoding results separate. Preserve failures rather than change encoding, URIs and version together and lose causal evidence.

## Reopen and verify 3, 4, 5, 6, 7 by card

Reopen each card and reconstruct floating 3, range 4, I-frame MAP 5, non-I-frame MAP 6 and SERVICE master 7. Verify one VERSION each, no master/media tag mixing and no concatenated examples. Deliver role, feature, minimum and actual playback or unperformed status, not a complete modern-version catalogue. Added KEYFORMAT or other extensions need their own evidence rather than another copied number. A declaration is neither transcoding, supplied dependencies nor an installed app update.

## Related tutorials and sources

[iCouldPlay HLS initialization: separate EXT-X-MAP from timed media segments](<https://allluckly.cn/en/guides/icouldplay-hls-map-initialization-media-segment-ledger/>); [iCouldPlay HLS I-frame playlists: one frame entry is not four seconds of continuous action](<https://allluckly.cn/en/guides/icouldplay-hls-iframe-only-interval-preview-boundary/>).

Method sources: [RFC8216 §7](<https://www.rfc-editor.org/rfc/rfc8216#section-7>); [RFC8216 §4.3.1.2](<https://www.rfc-editor.org/rfc/rfc8216#section-4.3.1.2>).

Checked on 16 November 2026: the [official iCouldPlay listing](<https://apps.apple.com/cn/app/id6755653178>) and [Apple public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn&entity=software&timestamp=20261116>) list version 1.1.1, requiring iOS / iPadOS 15.0 or later. Prepare samples manually in external plain text; iCouldPlay selects an existing real source for playback observations through installed controls. Placeholder URIs provide no media. Keep syntax, paper calculations and playback separate, marking unperformed steps accordingly. No exhaustive physical-device, private-server, engine or output-device compatibility testing is claimed.

